Start a conversation
Open support from the product when you need help with the workspace, a request, billing, or an integration. Include the request link and what you expected to happen when the issue is specific to one item.
Escalation context
A useful handoff includes the page, request, role, action attempted, result received, and urgency. Do not include passwords, payment credentials, or secret keys.
Keep one conversation per issue
Start a separate support conversation when the subject, request, or urgency changes. A focused thread keeps the answer and follow-up easy for your teammates to find. Teammates with access can continue the same conversation instead of opening duplicate reports.
What to include
- The request or page link
- The action you took and the result you expected
- The exact message or visible behavior you received
- Your workspace role and whether other teammates see the same issue
- A screenshot with private details removed
How replies appear
Customer-facing answers appear as PIWOT℗ Support so the help relationship stays consistent. Support notifications can also reach the configured channel. Keep passwords, card details, secret tokens, and other credentials out of the conversation even when troubleshooting feels urgent.