Talk to a person, not a form
There is no contact form and no ticket bot. Pick the address that fits the question so it reaches the right person; if no public address is set, the in-app help is the route that works.
Use the in-app help
The public support address is not published on this deployment. If you already have an account, sign in and open Help from the app; the help centre is also available at /help. No message would reach anyone at an address that has not been set up, so none is shown.
What to send where
- Product and setup
- Start with the help centre. If the article does not answer it, include the flow or campaign id and what you expected to happen.
- Billing
- Include the invoice number and the account email. Card details live with the payment processor, so support cannot see or change them.
- Security and privacy
- Report a suspected vulnerability or a data request privately. Do not open a public issue with exploit details. The DPA explains the notification process.
- Corrections and accessibility
- Include the page URL and the sentence or barrier. Corrections to a cited guide are checked against the source and fixed in the next content update.
For developers
The developer docs cover authentication, errors, rate limits, idempotency and webhooks. The API reference is generated from the OpenAPI document, and MCP setup covers the connector URL and the stdio package.