Platform overview
This page summarizes Tobachat for people assessing the product rather than using it: partner programs, marketplaces, and buyers. Everything here is covered at length elsewhere in these docs.
| Item | Detail |
|---|---|
| Product | Tobachat, a customer communication platform built on WhatsApp |
| Provider | Ciro Byte Solutions, Dutch CoC 81089058, Amsterdam |
| Role at Meta | Meta Tech Provider for the WhatsApp Business Platform |
| Market | The Netherlands |
| Languages in product | Dutch and English |
| Storage | Supabase, EU region |
| Contact | [email protected] |
What the product does
Tobachat is how a business runs its customer contact over WhatsApp. It starts with a shared inbox where several staff work one business number, with assignment, internal notes, and labels.
Around that sit the parts that handle outbound traffic: a contact list carrying consent per contact, templates Meta approves, campaigns to a group of contacts, and automations that react to a keyword, a booking, or a webhook.
So it isn't a standalone campaign tool. Campaigns are one part of the package, next to the inbox and the automations.
Who it's for
Businesses with repeat customer contact that already use WhatsApp and have hit the ceiling of the free app: one device, no view of who answered what, no clean way to reach a group of customers.
In practice that's mostly Dutch small and mid-sized businesses in leisure, retail, services, and care.
Which data we process
There are two roles. For our own customer's data we're the controller: name, email address, phone number, company name, billing details, and technical logs.
For the data of our customer's customers we're the processor. That covers phone numbers, profile names, WhatsApp message content, and metadata such as timestamp and delivery state. We process it only on our customer's instructions, and we sign a data processing agreement on request.
We don't sell data, and we don't use end-customer messages for anything beyond delivering the service. The full account, including who we share data with and how long we keep it, is in the privacy statement.
Security and separation
Data sits with Supabase in the EU. Every organization is logically separated: the database enforces per row which organization it belongs to, and a user only ever sees their own organization's data.
Access tokens for the WhatsApp connection are stored per customer. Traffic is encrypted, and access inside our team is limited to what running the service requires.
How support works
Support runs through Help in the dashboard and through [email protected]. We usually reply within 1 working day. New customers connect through Meta's own sign-up screen themselves; anyone who'd rather leave that to us gets the connection and the first templates done together with us.
Connecting to your platform
Three ways exist today to hang Tobachat off another system: a Zapier app with 7 triggers and 6 actions, webhooks that deliver contacts or events to us, and an automation step that calls an API itself.
If you want a deeper integration or a listing in your marketplace, email [email protected]. We're happy to build toward it.