Support
One address, answered by the people who build Wapito. There is no ticket portal and no chatbot in front of it — but there are three guides that answer most questions faster than we can, so they are listed first.
Email us
Write to support@wapito.com for anything: an integration question, a billing correction, a number that will not link, or a suspicion that something is wrong on our side. The form below composes that email in your own mail client — it is a convenience, not a helpdesk, and nothing you type is sent anywhere until you press send in your own client.
This opens your own email client with the message already written — nothing is sent from this page and nothing is stored here. Write to support@wapito.com directly if you would rather.
What to expect, and when
These are the targets we hold ourselves to. They are not a contractual service level — the Terms of Service say so too — and they are measured in business days, by a small team in one time zone rather than a 24-hour rota. If something is genuinely down, say so in the subject line and it jumps the queue on either plan.
| Plan | Queue | First reply | Channel down |
|---|---|---|---|
| Sandbox | Standard | Within 2 business days | Handled in queue order |
| Premium | Priority | Within 1 business day | Same business day for a channel that is down, banned or logged out |
The risks we cannot support you out of
Wapito is an unofficial API: it links a real WhatsApp account and speaks the protocol the phone and desktop apps use, rather than going through Meta's Cloud API. That is what makes groups, Channels, status and contact checks possible, and it is also the source of three failure modes support cannot reverse for you.
- A banned number. WhatsApp can restrict or ban a number it judges to be automated — usually for volume, cold outreach or a burst of group activity from a new number. There is no appeal a provider can file on your behalf. We detect it, raise a
channelevent, email you, and tell you what the pattern looked like. - A phone that has been offline too long. WhatsApp unlinks a companion device after roughly fourteen days without the phone coming online. We warn at day ten and day thirteen; after that the number has to be linked again.
- Linking changes at WhatsApp's end. Device linking has been unreliable for QR since the middle of 2026, which is why the dashboard leads with the pairing code and keeps QR as the fallback. When a change like that lands, it lands for every provider in this category at once, us included.
If any of those is a business risk you cannot carry, the honest answer is Meta's official Cloud API for the parts it supports. We wrote the comparison ourselves , including the parts where the official platform wins.
Reporting something sensitive
A suspected vulnerability goes to the security address instead, so it is triaged before it is discussed anywhere else. See the security page for what we store, how long we keep it and how to disclose a problem responsibly.