Multi-tenant communications infrastructure
Voice, messaging, email, calendar, CRM, and commerce — one engine, with one contact identity and one consent state underneath. Your brand on top. Your product. Your clients.
BUILT BY AUTOGRAF DIGITAL · CALGARY · CASL-NATIVE
Your product sits on eight modules. The modules sit on one engine. The engine talks to the channels — so you never have to.
Running in production on
The position
If you want a finished platform with someone else's name on the login page, there are plenty. AutoChat exists for the other path: agencies and software companies that want to own the product, the margin, and the relationship — and need serious plumbing underneath to pull it off.
RESELLING A PRODUCT
BUILDING ON AN ENGINE
The modules
Each module is an outcome your clients pay for — not a feature list. Switch them on per client; they all read from the same engine.
01 · AC Voice
Hosted numbers · IVR · AI receptionist · Call recording · Live & post-call transcription
02 · AC Messaging
SMS & RCS · WhatsApp · Instagram & social channels · Scheduled sends · Two-way threading
03 · AC Mail
Hosted domains & mailboxes · Transactional sending · Marketing broadcasts · Unsubscribe & suppression
04 · AC Calendar
Availability rules · Bookings · External calendar sync · Reminders in-thread
05 · AC CRM
Forms & lead capture · Pipeline · Contacts · Reviews & reputation
06 · AC Commerce
Products & inventory · Estimates & invoicing · Contracts · Online & in-person payments
07 · AC Team
Internal rooms · Resolvable discussions · Task assignment
08 · AC Analytics
Insights & reporting · Visitor behaviour · Per-client views
The shared layer
Anyone can wire five vendors together. A weekend, some webhooks, a shared spreadsheet of API keys — that part was never the moat.
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.
A customer who calls on Tuesday, texts on Thursday, and emails the week after is one conversation and one profile — not three tickets in three systems. That layer is the product. The modules are what it makes possible.
The caller, the emailer, and the DM resolve to one person with one history.
One CASL-native consent state, enforced on every channel and every send.
Calls, texts, emails, and DMs land in one thread per person, in order.
Estimates, contracts, and signatures attached to the same record as the conversation.
Recordings, attachments, and files stored once and referenced everywhere.
Quiet hours, suppression lists, throttles, and an audit trail on every outbound message.
One delivery layer for everything the platform needs to tell a human.
One template system across SMS, email, and documents — write once, send anywhere.
Every unit of usage measured per workspace and per client, ready to price.
AI agents run inside the engine with real context, not bolted on beside it.
The full history, structured so software — and agents — can actually use it.
One query across conversations, contacts, files, bookings, and money.
One person, one thread
TUE · VOICE
Calls about a quote. Recorded, transcribed, filed.
THU · SMS
Texts back a question. Same thread, same person.
MON · EMAIL
Emails to confirm. Still one conversation.
RESOLVED
On most stacks that customer is three tickets in three vendor dashboards, with three different answers to "did they opt in?" On AutoChat the engine resolves them to one person before your product ever sees them.
Two ways to build
Equal siblings on the same engine — most partners begin with one and grow into both.
PATH A
A complete operator interface, ready to carry your brand.
Day one
your-brand.app your clients logged in zero interface code
PATH B
Your product on top. The engine underneath.
Illustrative
POST /v1/conversations/{id}/messages
{
"channel": "sms",
"body": "Your Thursday 2:15 is confirmed."
}Straight answers
No — it's the other side of the decision. GoHighLevel is a finished product you resell under someone else's roadmap. AutoChat is infrastructure you build a product on. It assumes you have developers, or that you work with someone who does, and that you want to own what your clients log into.
For the API path, yes — that's rather the point of it. The standard app path needs configuration, not code: modules are switched on per client and the interface carries your branding out of the box.
Pricing is usage-based and set per partner, because a three-person agency and a vertical SaaS platform don't consume infrastructure the same way. Start a conversation and we'll price what you're actually building.
Access is by application. We're working closely with a small number of partners while the platform hardens — we'd rather do that well than widely.
On Canadian-first infrastructure, with PIPEDA and CASL as the governing frame. Residency requirements are discussed per partner — tell us yours when you apply.
Yes. Bring your existing numbers and domains or provision new ones through AutoChat — either way, your clients see your name, not ours.
Request access
Access is by application while we work with a small number of partners. Describe the product you want to run on AutoChat — we read every request and reply personally.
Prefer email? [email protected]