Support

Write to someone who can read the routes.

No queue, and no ticket robot asking you to confirm your identity — we do not have one to confirm. Say what happened, keep the reference you are given, and check back with it.

No email needed to write in, or to get an answer

No cookie set by this page or its form

A hash is all we keep of where it came from

What is this about?

Account reference optional

Never paste your token. It is the account itself, we cannot read it, and support does not need it. The dashboard shows a short reference that is safe to share — or a batch_id, or a transaction hash.

Where should the answer go? optional

Yours to choose, and we do not verify it. Leave it blank and check back with the reference instead — that path asks nothing of you at all.

What happened?

Nothing here is stored against an identity: no cookie is set by this page, and the address it arrived from is kept only as a hash, to spot a flood.

Answered faster elsewhere

The FAQ — 32 questions, including the awkward ones
API reference — errors, webhooks, limits
Status — check here first if sending just stopped
Segments — why a message billed as two
Sender IDs — why a name was rewritten

What support cannot do

Recover a lost token. We hold a hash. There is no reset link, and that is the same property that keeps your account out of a database dump.
Refund credit to a wallet. There is no payment instrument on file to reverse.
Register a sender ID abroad. Where a market keeps a national register, only a local entity can file with it.
Make a carrier keep your sender ID. Where a network rewrites it, that is the network's decision.

Reporting abuse

If you received a message you believe was phishing or impersonation, send it with the sender ID and the time it arrived. Traffic like that poisons the routes every other sender depends on, so it is turned off on sight rather than debated.

Write to someone who can read the routes.

Create your account

This is the only copy.

Sign in