Overview
AllyOneCRM is AllyOne's customer relationship platform: contacts, deals, campaigns and three distinct automation engines, with a native connection to the WhatsApp Cloud API.
A tenant in AllyOneCRM is a customer's account — all data (contacts, deals, journeys, API keys) belongs to exactly one tenant. Agency accounts can operate multiple end-customer tenants from a single administrative view.
What you build here
CRM
Contacts and companies with custom attributes, per-channel opt-in (email, WhatsApp, push, SMS, RCS) and bulk import via CSV.
Native WhatsApp
Direct connection to Meta's Cloud API through Embedded Signup — no manually pasted token, no middleman.
Three automation engines
Journeys (audience-driven sequence), Chat Flow (real-time reply inside a conversation) and Automations (simple event-based rule) — each solves a different problem. See the full comparison.
Multichannel campaigns
Mass sends combining WhatsApp, email (via AllyOneMail) and social channels from a single audience.
Essential glossary
| Term | Meaning |
|---|---|
Tenant | A customer's account. Every API resource belongs to a tenant. |
Agency | An account that operates multiple end-customer tenants. |
Contact | A person — phone and/or email, custom attributes, tags, per-channel opt-ins. |
Company | A company associated with contacts (1:N relationship — a contact belongs to at most one company). |
WABA Account | A WhatsApp Business (Meta) account connected to the tenant via Embedded Signup. |
Journey | A sequence of steps triggered by an audience event (contact created, tag added) — lasting days or weeks. |
Chat Flow | An automatic-reply flow inside an ongoing conversation — real time. |
Automation | A declarative "if this event, then this action" rule — no visual canvas. |
If you're integrating for the first time: Authentication → Quickstart → Connect WhatsApp.