The full chain of providers behind the AI Employee, who owns each account, and what happens if something goes wrong. We spell it all out because almost nobody else in this market does.
When one of your customers writes on WhatsApp, the message goes through these steps, always inside services with EU-grade data protection safeguards:
| Step | Provider | What it does |
|---|---|---|
| 1 | Meta / WhatsApp Business Platform | Carries the message between the user and the business's WhatsApp account |
| 2 | 360dialog | Meta-authorized Business Solution Provider (BSP) that connects that account to Zyneronix's platform |
| 3 | Google Gemini | AI model that drafts the reply, using only the information the business has approved (prices, hours, FAQs) |
| 4 | Google Cloud / Firebase (EU) | Hosts the platform, the panel and the conversation history, in the European Union |
| 5 | Stripe | Processes the business's subscription payment to Zyneronix; it never touches the conversation with users |
There's no hidden step and no extra middleman: it's the same chain for every client, and the full detail (including sub-processors) is in the data processing agreement (Spanish PDF; an English summary is available on request).
The WhatsApp Business API account is opened with the business's own tax details, not Zyneronix's. The business is the owner from day one: if it ever stops working with us, the account, the number and the history stay with it. Zyneronix configures and connects it to the assistant, but never appears as the owner to Meta. The full picture of how it coexists with the regular WhatsApp app is on the coexistence page.
Our contract has a specific clause for this, instead of leaving it to fine print: if Meta limits or blocks a client's number, Zyneronix helps file the appeal with the required documentation and, if the block drags on, sets up an alternative number in coexistence so the business isn't left without WhatsApp. The rules to avoid getting there are summarized in the anti-ban one-pager (a one-page PDF).
Before activating the assistant on a client's account, we sign a data processing agreement under Article 28 of the GDPR: who is the controller, who is the processor, what data is handled, how long it's kept and which sub-processors are involved (the table above). You can download the full document and share it with your data protection officer if you have one.
Download the data processing agreement (PDF) →
Article 50 of the EU AI Act requires an automated conversational system to disclose that it is one. The AI Employee does this in the first message of every new conversation, without exception and without an off switch: it never pretends to be a person.
The assistant hands the conversation to a person at the business the moment it detects a clinical question, a complaint, an emergency, or simply when the user asks for it. It also steps back automatically the moment someone at the business writes from the WhatsApp app itself: that's the coexistence mechanism explained on its own page.
Answer questions, quote approved indicative prices, book and confirm appointments, and alert the business by email.
It never diagnoses or gives medical advice, never prescribes or recommends treatment, and never sells or takes payment inside the WhatsApp chat itself: any payment happens through the business's own official channels.
Last updated: September 13, 2026 · AI Employee · Coexistence · Try your bot · Guarantee · Back to zyneronix.com