A message arrives at night, over the weekend or in the middle of your team's holiday, and gets an answer straight away, from the same knowledge Ada uses on your website. One thread stays one thread, the history stays inside it, and meetings keep themselves alive.
Inbound and outbound on your own domain · Polish and English templates · source citations inside the reply
The message lands in the same conversation inbox as chat, with the subject and history preserved. The reply returns in the same thread, so the customer does not get a new case number with every message, and your team does not read correspondence assembled from fragments.
We do not keep one set of content for chat and another for e-mail. Editing an article takes effect in both places at once, and an e-mail reply goes through the same coverage gate: without grounding in published material it simply does not go out.
A confirmation with a calendar attachment, reminders a day, an hour and ten minutes before the call, and a cancellation link that needs no login. Attendance stops depending on whether somebody on the team remembered.
It looks like a technical detail, and it decides whether the customer receives one message or three identical ones.
| Situation | Inline sending | Here |
|---|---|---|
| The mail provider is briefly unavailable | The message is lost, the customer gets nothing | The job waits in the queue and retries until it goes through |
| The same action clicked twice | Two identical e-mails | An idempotency key: one message, the second job recognised as a repeat |
| A failure midway through a batch | Some recipients served, some not, nobody knows which | Every job carries its own state, so you see exactly what went and what waits |
| Data needed for the content does not exist yet | An empty template goes out | The job waits for the missing piece, for example the link to the conversation room |
Somebody asks about rollout on Friday after hours. A concrete answer with a proposed slot goes out in minutes, not on Monday morning, by which time the enquiry is already sitting with three competitors.
The customer replies two weeks later, in the same thread. Your agent sees the whole case in one place, including what Ada answered earlier and from which document.
A booked demo with no reminder is an invitation to a no show. Three signals before the call cost your team nothing, because the system sends them.
The mechanics of the channel, meaning IMAP inbound, threading and templates, live on the email channel page.
This is where the mail module is heading. Everything above this block works today.
A summary of the website conversation sent to the visitor's inbox with a booking link, before they close the tab.
Notify meSeveral messages spread over time, matched to the stage of the conversation and stopped the moment the customer replies or books.
Notify meReaching out to people from a trade show or webinar with content that refers to what they saw.
Notify meA view of which messages end in a reply and a booked slot, and which land in the void.
See the Signals moduleDuring the demo we take an enquiry from your own inbox and show what Ada does with it, on your own materials.