Skip to content

Where it answers

Most of what a small company loses, it loses in the gap: the enquiry nobody saw, the call nobody could take, the approval that sat unread for three days. This is the part of Autopilot that closes that gap.

Chat, email and phone calls arrive in one place, sorted. Two things make it more than a merged view:

  • Replies are drafted in your own writing style — learned from what your company already sends, not from a generic assistant voice.
  • A call can be handed to the right person rather than dying in a queue.

Drafts are drafts. What sends is what you release.

Incoming calls and website voice chats are answered from your own company information — opening hours, what you sell, what you do not do — whether or not someone can pick up. The alternative is not a better human answer; the alternative is a missed call.

You can ask how the business is doing and get a spoken answer, then give a spoken instruction back. It is the same operator, reachable without a screen — useful in a car, on a site, between appointments.

A personal WhatsApp number can be connected so messages there are read and answered too. For a lot of trades this is where the customer actually is, and leaving it out would mean documenting an inbox that is missing half the conversation.

An approval is only useful if it reaches you. Alerts go to email, chat or phone push — routed to the channel you actually check, not to all three.

That matters more than it sounds: the whole design of Autopilot is that nothing outward-facing ships without you. If approvals pile up unseen, the machine is not autonomous, it is stalled — and a stall is what alert routing is there to prevent.

  • Company → Inbox — the merged inbox
  • Company → Connections — connecting mail, phone, WhatsApp, social
  • Company → Approvals — the queue the alerts point at