How AllyOne is built
AllyOne is not a tool with fragile integrations underneath. It is a platform with its own delivery component, per-customer isolated accounts, and 5 real communication channels — each piece owning a real part of the operation, not an API layer over a third-party service.
Topology
The CRM is AllyOne's main application — tenant identity, contacts, campaigns, journeys and business decisions live here. Mail is just an internal delivery component, specialized in one thing (email sending infrastructure), which the CRM calls under the hood without needing to operate an MTA, DKIM or IP reputation directly.
The CRM decides what to send and to whom. Mail decides how to deliver — MTA, DKIM, IP reputation, retry. This boundary is not an implementation detail: it is what lets AllyOne operate its own delivery infrastructure (not a third-party provider behind an API) without coupling it to the CRM's business logic.
Who owns what
AllyOneCRM
Tenant identity, contact and deal data, campaign/journey orchestration, commercial decisions. It is where customers and end users log in directly.
AllyOneMail
Physical sending infrastructure: domain, DKIM/SPF/DMARC, dedicated IP, MTA (AllyMTA), warmup and reputation, delivery/bounce/suppression state.
Why WhatsApp doesn't go through Mail
WhatsApp messages use Meta's Cloud API directly from the CRM (via Embedded Signup) — there is no MTA or dedicated IP involved, because Meta is the one that operates the final delivery. Mail only enters the email path, where AllyOne actually operates the outbound infrastructure.
Why two products, not a monolith
IP reputation and email deliverability are specialized operations — pausing an IP, adjusting warmup, reacting to a reputation drop require an access and operations model different from the day-to-day of those who use the CRM. Separating the two prevents a campaign schema change from putting the sending infrastructure at risk, and vice versa.
Accounts & hierarchy
An Agency can operate several customer accounts at the same time, each isolated from the others — one customer's data is never visible to another, not even by accident.
Each account (tenant) has its own contacts, campaigns, API keys and connected channels — nothing is shared between accounts, even within the same agency.
Communication channels
AllyOne is not just WhatsApp and email — the platform talks to the end customer through 5 different channels, each with its own real provider behind it.
Native, direct with the Meta Cloud API (Embedded Signup) — no middleman.
✉️ Email
Via AllyOneMail — own domain, dedicated IP, AllyMTA.
📱 SMS
Zenvia, Twilio or Infobip — the account chooses the provider.
💡 RCS
Via Infobip — rich message (image, carousel, buttons) in Android's native SMS app.
🔔 Push
Push notification in the browser on the customer's site (Web Push).
📢 Ads
Google, Meta, TikTok and LinkedIn Ads connected — to close the funnel between paid campaigns and the contact base.
Every channel goes through the same 3 automation engines (Journey · Chat Flow · Automation) and the same contact base — switching channels doesn't mean switching platforms.