Before purchase
Ask about fit, early-access readiness, plans, migration, or workspace boundaries. You will get a direct answer, not an automated sales sequence.
Customer Care
Help that keeps
the whole conversation together.
Ask before you buy, get guided through setup, or follow a technical or billing request from one place. Customer support is part of the product—not a mailbox hidden after checkout.
During setup
The post-purchase wizard tracks provisioning in real time. If setup fails, your reservation and payment context stay attached to the support request.
After launch
Open a ticket in the customer portal, see public replies, add context, and keep internal support notes private by design.
The fastest route
Use the customer portal when you can.
An authenticated request is already linked to the right billing owner and account. That lets the support team help without asking you to send sensitive proof over email.
What to include
- The workspace name or subdomain
- What you were trying to do
- What happened instead
Never send passwords, MFA or recovery codes, secret keys, or full payment-card numbers. Support will not ask for them.
How care is handled
Scoped access. Visible actions.
A human stays accountable.
Account boundaries first
Support requests are linked to one customer. Agents use the existing authorized data path rather than a tenant-bypassing shortcut.
Internal notes stay internal
The customer view only receives public replies. Triage notes, investigations, and agent-only context never cross that boundary.
Sensitive actions are audited
Password resets, account status changes, and scoped billing or quota assistance remain attributable to the support agent who performed them.
Not signed in yet?
Email is always available. Messages sent to the published support address enter the same Customer Care infrastructure.