Loading page content.
Contact
Three addresses, one ticket system behind them, and a queue staffed around the clock. Every message becomes a numbered ticket you can reply to by email, so nothing depends on someone remembering a chat thread.
Where to write
Anything sent to the wrong address is routed internally rather than bounced back at you, but the right one is faster.
Anything on a live account: gateway errors, targeting that is not resolving, usage that does not match your own counters, billing corrections, and refunds under the published policy.
Volume beyond the published tiers, invoicing and purchase-order terms, and trials larger than the standard 50MB where a real evaluation needs more.
Reselling under a written agreement, supply partnerships for residential and mobile inventory, and integrations that need something from both sides.
Response times are targets we measure against our own ticket table, not a contractual service level. Volume accounts get a named engineer and a shared channel; that is arranged through sales rather than sold as a support tier.
Open a ticket
The form opens a real ticket with a reference of its own. If you are signed in it also appears in your dashboard; if you are not, replying to the confirmation email keeps everything on the same thread.
Community
Public channels are good for announcements, incident notices and informal help. Anything touching your account, your credentials or your invoice belongs in a ticket, where it is private and auditable.
We do not run a live chat widget. It would mean admitting a third-party script to every page, and a chat transcript disappears when the agent who owned it leaves. A numbered ticket does not.
