The communications engine
Every conversation.One thread.
AutoChat is the engine underneath your product. Voice, messaging, mail, calendar, CRM, commerce and team run as one system that you brand and own.
Access is by application while we work with a small number of partners.
The problem
Your customer is one person. Your stack thinks she’s five.
The phone system has a caller. The SMS vendor has a number. The email service has an address. Each tool keeps its own copy of the customer, and none of them know about the others.
Phone system
- Caller
- Unknown
- Number
- 403 555 0142
- Left
- Voicemail · 0:42
Doesn't know her name
SMS vendor
- From
- +14035550142
- Said
- “Is Saturday still open?”
- Name
- None on file
Doesn't know she called
Calendar
- Guest
- Maya T.
- When
- Sat · 10:30
- Phone
- Not collected
Can't send a reminder
CRM
- Record
- Maya Tremblay
- Record
- Maya Tremblay (2)
- Last contact
- ?
Has her twice
Maya Tremblay
One contact · one thread
- Phone
- +1 (403) 555-0142
- [email protected]
- Consent
- SMS: express · Email: transactional
- Thread
- Calls, texts, email, bookings, invoices
- Next
- Saturday · 10:30
AutoChat keeps one. Every channel reads and writes the same person, with one history and one consent state.
The thread
One person. One conversation. One consent state. One history.
When Maya calls, then texts, then emails, AutoChat doesn’t open three tickets. It extends one thread. Your staff read it, your AI agents read it, and nobody starts from zero.
- contact
- Maya Tremblay
- channels
- voice · sms · email
- consent
- sms: express (booking call)
- email: transactional only
- next
- Sat 10:30 · 2 chairs
- open items
- none
The agent won’t add Maya to the newsletter. It can read why.
AC VoiceMon 09:12
Inbound call, answered by the AI receptionist
“Is there anything Saturday morning?” Offered 10:30, and she took it.
Recorded · transcribed · 4 min
AC CalendarMon 09:13
Booked for Saturday, 10:30
Created from the call. No form, no re-typing.
Booking confirmed
AC MessagingMon 09:13
Confirmation sent by text
“You're booked for Saturday at 10:30. Reply C to change.”
Consent checked before sending
AC MailMon 14:02
She replies by email
“Could my son come along too?” It joins her thread instead of opening a new ticket.
Threaded to Maya
AC TeamMon 14:05
Internal note: “@Jordan, can we fit a second chair at 10:30?”
Jordan: “Done, he's in.” Discussion resolved.
Internal · never visible to Maya
AC CommerceSat 11:48
Invoice paid in person
The receipt goes out by email, and the payment sits beside the conversation that led to it.
Receipt emailed
AC CRMSat 11:50
Review request sent by text
Only because she agreed to texts. The engine checked.
Consent: SMS, express
Modules
Eight modules. Use the ones your product needs.
Every module writes to the same thread, reads the same person and passes the same consent gate. Start with one and add the rest when you need them.
The engine
Anyone can wire five vendors together. Very few build the layer that makes them one system.
The modules are the warp. The engine is the weft: twelve capabilities that pass through every module. Pick a thread to see where it runs.
Identity
Contact identity and resolution
The caller, the texter and the emailer are the same person.
Phone numbers, email addresses and social handles resolve to one person inside a business. When someone calls from their mobile and replies from their work email, AutoChat links them. It never merges people on a guess.
Across every module
Every module reads and writes the same person, not its own copy.
01 / 12. Use the arrow keys to move between capabilities.
Positioning
Other platforms sell you a finished product to resell. AutoChat is the engine you build yours on.
All-in-one platforms are finished goods: you resell someone else’s cloth. AutoChat is the loom. What you weave on it, the pattern, the colour and the name, is yours.
A platform you resell
An engine you build on
- Their product, with your logo on the login screen
- Your product, all the way down
- Their roadmap decides what you can sell
- Your roadmap decides
- Packaging and margins bounded by their plans
- You set your own packaging and margins
- Customers learn their interface
- Customers learn yours, or use the standard app under your name
- Leaving means migrating every client
- The engine stays underneath while your product changes on top
We make the loom. You make the cloth.
Two ways to build
Launch on the standard app. Or build your own on the API.
Most partners do both: the standard app for clients who need it today, and the API for the product they're building next.
A complete operator app, under your name.
Inbox, contacts, calendar, pipeline, invoices and team, ready for your clients on day one. Try it: name your product and pick its colour.
Preview shows Your product in Cobalt, light appearance.
Your product entirely. The engine underneath.
Build your own interface, or none at all. Keep contacts in your own system if you’d rather: AutoChat keeps only what it needs to route, thread and respect consent.
- Every request scoped to one client
- Idempotent sends, safe to retry
- Signed webhooks for every event
- Test keys run the real pipeline in a sandbox
- Consent enforced before every send
// Every call is scoped to one of your clients.
const client = autochat.client(clinic.autochatClientId);
// Find the person, not the phone number.
const maya = await client.contacts.resolve({ phone: "+14035550142" });
// Consent is checked before it sends. A retry never double-texts.
await client.messages.send({
to: maya.id,
channel: "sms",
template: "booking.confirmed",
data: { when: booking.startsAt },
idempotencyKey: `booking-${booking.id}`,
});
Tenancy
Built for many businesses, not one.
Your workspace holds your own operation and every client you serve. Each client keeps its own data, numbers and billing, and your team sees exactly what you let them see.
Workspace
Your agency or platform
- Your own leads and operations
- Your team
- Every client you serve
- Your brand
Workspace members see every client. You decide who gets which role.
Client A
A dental clinic
- Contacts and threads
- Numbers and domains
- Usage and billing
- Consent records
Client B
A barbershop
- Contacts and threads
- Numbers and domains
- Usage and billing
- Consent records
Client C
A law office
- Contacts and threads
- Numbers and domains
- Usage and billing
- Consent records
Invite a contractor to one client, and one client is all they'll ever see. Each client's sending reputation, numbers and records stay its own.
Who builds on AutoChat
For the people who make the product.
- AgenciesStop reselling someone else's platform.Launch a communications product under your own name, package it your way, and give every client their own data, numbers and billing.Autograf Digital runs its own client base on AutoChat.
- Software platformsYou didn't set out to become a phone company.Stop stitching together vendors for numbers, texting, email and consent. Put one engine underneath your product and get back to building your product.Barberi and Huddles build on the engine.
- DevelopersThe hard parts of communications, already done.One API for every channel, with identity, threading, consent, idempotency and signed webhooks built in. You write the product. The engine does the plumbing.
Built on the engine
- Autograf Digital
- Barberi
- Huddles
Canadian-first
Consent is designed in, not bolted on.
AutoChat is built in Calgary, around Canada’s anti-spam and privacy rules (CASL and PIPEDA) from the first line of the data model, not added as a checkbox at the end.
51.0447° N · 114.0719° W
- Before every send
- Every outbound message, call reminder and campaign checks consent first. If consent can't be checked, nothing sends: the gate fails closed.
- Per sender
- A STOP ends a person's relationship with one business, not with every business on the platform. A hard bounce protects everyone's reputation.
- On the record
- Every opt-in and opt-out is kept as a record of who, when, how and on which channel, so you can always explain why someone is or isn't contactable.
- Visible to agents
- Consent sits on the thread, so staff and AI agents see it where they work, rather than in a settings page nobody opens.
Build your product on one thread.
We're working with a small number of partners while the engine grows. Tell us what you're building, and we'll tell you honestly whether AutoChat fits.