The platform
This page is the whole shape of AutoChat: what each module does, what the shared layer underneath actually handles, and how the tenancy model draws its data boundaries. Builders evaluate structure — so here it is.
The engine
Every module reads from the same capability layer. This is what separates an engine from a bundle of integrations — and it's the part you can't stitch together from vendors.
01
The caller, the emailer, and the DM resolve to one person with one history.
02
One CASL-native consent state, enforced on every channel and every send.
03
Calls, texts, emails, and DMs land in one thread per person, in order.
04
Estimates, contracts, and signatures attached to the same record as the conversation.
05
Recordings, attachments, and files stored once and referenced everywhere.
06
Quiet hours, suppression lists, throttles, and an audit trail on every outbound message.
07
One delivery layer for everything the platform needs to tell a human.
08
One template system across SMS, email, and documents — write once, send anywhere.
09
Every unit of usage measured per workspace and per client, ready to price.
10
AI agents run inside the engine with real context, not bolted on beside it.
11
The full history, structured so software — and agents — can actually use it.
12
One query across conversations, contacts, files, bookings, and money.
The hard part is the layer underneath: the thing that knows the caller, the emailer, and the Instagram DM are one person. That holds one consent state across every channel, so a single unsubscribe means unsubscribed everywhere. That gives an AI agent one coherent history to read from instead of five partial ones.
The modules
Each module earns its place by ending a category of problem for your clients. Turn them on per client; every one of them reads and writes the same engine.
01 · AC Voice
Hosted numbers, IVR, and an AI receptionist that picks up when your client's front desk can't. Every call is recorded, transcribed live and after the fact, and filed against the person who made it.
02 · AC Messaging
SMS, RCS, WhatsApp, Instagram, and social channels in one thread per person — with scheduled sends, so campaigns go out when they should, not when someone remembers.
03 · AC Mail
Hosted domains and mailboxes, plus marketing and transactional sending — all from infrastructure the product controls, so the from-address belongs to your client, not a third party.
04 · AC Calendar
Availability rules, booking pages, and sync with external calendars. Confirmations and reminders land in the same conversation thread as everything else.
05 · AC CRM
Forms and lead capture feeding a pipeline, contacts that stay whole across every channel, and reviews and reputation handled where the relationship already lives.
06 · AC Commerce
Products and inventory, estimates that become invoices, contracts that get signed, and payment collected online or in person — recorded against the same customer as the conversation.
07 · AC Team
Internal rooms beside the customer inbox, discussions that resolve instead of scrolling away, and tasks assigned to the person who will actually do them.
08 · AC Analytics
Insights and reporting across every module, plus visitor behaviour — so the platform can answer questions instead of exporting spreadsheets.
Tenancy
Multi-tenant platforms live or die on their data boundaries, so here is AutoChat's shape, plainly:
TIER 1
Your own tenancy, your own team, your own billing relationship with AutoChat. Everything you operate lives under it.
TIER 2
Every client sits inside your workspace with its own data boundary and its own billing — their contacts and conversations are theirs, never pooled.
TIER 3
Its own team, and optionally its own numbers and calendars — while the client's customer records stay whole across all of them.
Team members hold scoped access at any tier. Contacts stay whole across locations: a customer who visits two sites is still one person, with one history and one consent state.
Two ways to build
Neither is the junior option. The standard app is how you launch this quarter; the API is how you make the product entirely yours. Partners routinely start with one and grow into both.
PATH A
A complete operator interface, ready to carry your brand.
A finished, brandable app your team and your clients log into on day one. Configuration, not code.
Day one
your-brand.app your clients logged in zero interface code
PATH B
Your product on top. The engine underneath.
Build your own product entirely — your interface, your data model, your roadmap — with AutoChat as the communications engine behind it.
Illustrative
POST /v1/conversations/{id}/messages
{
"channel": "sms",
"body": "Your Thursday 2:15 is confirmed."
}Next step
Access is by application while we work with a small number of partners. The conversation starts with your product, not our pitch.