Support when the self-serve path stops moving.
Escalate setup issues, billing questions, product bugs, or privacy requests with enough context for the team to act quickly.
Response window
2 days
Typical reply time for email support.
Best for
Bugs
Include reproduction steps, workspace slug, and page URL.
Coverage
4 lanes
General support, technical issues, billing, and privacy.
Support lanes
Route your request to the right workflow from the start.
General support
Get help with account setup, workspace access, and product usage.
Technical issues
Report widget or reporting issues with clear reproduction steps.
Billing and plans
Questions about plans, invoices, upgrades, and workspace limits.
Security and privacy
Request privacy clarifications or security documentation details.
What to send
Requests move faster when the first message is specific.
Minimum context
Workspace slug, user email, the affected route, and whether this is blocking production tracking.
For billing issues
Mention the plan, invoice timing, and whether this affects renewal or access limits.
For bugs
Attach screenshots, console or network notes if available, and the last successful action before failure.
Self-service resources
Most support requests start with one of these guides.
Before you email
Include your workspace slug, affected page URL, browser, and a short timeline of what happened.
For tracking issues, note whether the page is published, whether the embed is visible, and whether the page toggle is enabled.