Module: Email

An inbox where no lead waits until tomorrow

A message arrives at night, over the weekend or in the middle of your team's holiday. If you turn on automatic replies, Ada can answer straight away, from the same knowledge she uses on your website. An email with an attachment always waits for a person. One thread stays one thread, the history stays inside it, and meetings keep themselves alive.

Inbound from your mailbox · outbound under your company name · Polish and English templates · source citations inside the reply

Three things this module does

01

Inbound and reply in one thread

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.

02

The same knowledge as on the website

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.

03

E-mails that keep meetings alive

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.

What happens when sending fails

The customer should get one message, and your team should know when they got none.

SituationWhat we do
The mail server did not accept an automatic replyThe reply stays in the thread marked as failed, your team gets a signal and can send it themselves
A reply in the panel is clicked twiceThe second click is recognised as a repeat, so the customer gets one message
A customer address bounces permanentlyAfter the bounce report the address goes on the suppression list and further emails to it are not sent
You need to check what went outEach message in the thread has its own status. Sent means accepted by the mail server, not delivered

Three moments where you notice it

An enquiry on Saturday evening

Someone asks about a rollout on Friday after hours. With automatic replies turned on, a concrete answer and a suggested date can go out within minutes, not on Monday morning, when the enquiry is already with three competitors.

A complaint thread with history

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.

The reminder that saves a meeting

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.

In progress

How this module grows

This is where the mail module is heading. Everything above this block works today.

Instant follow up after a conversation

A summary of the website conversation sent to the visitor's inbox with a booking link, before they close the tab.

Notify me

Nurture sequences

Several messages spread over time, matched to the stage of the conversation and stopped the moment the customer replies or books.

Notify me

Follow up after events

Reaching out to people from a trade show or webinar with content that refers to what they saw.

Notify me

Message performance report

A view of which messages end in a reply and a booked slot, and which land in the void.

See the Signals module

Questions we get most often

Do e-mail replies carry citations too?
Yes. It is the same knowledge base and the same coverage gate as on the website, so the reply names the document it came from.
Do messages go out from my own domain?
No. The email goes out from the platform's technical address under your company name, and the customer's reply comes back to the address you specify. Inbound comes from your mailbox. We do not offer sending from your own domain today.
What about history from before the rollout?
We do not ingest the archive. The poller starts from the moment of connection, so a rollout does not begin with a flood of replies to year old cases.
Does Ada answer everything on her own?
She answers where she has coverage in your materials. Anything outside that scope goes to a human together with the whole thread, instead of being improvised.
Will I be notified when a case needs a human?
Yes. Handovers enter a queue in the panel, and your team can receive a browser notification, including on a mobile device.

See what an answer to your real enquiry looks like

During the demo we take an enquiry from your own inbox and show what Ada does with it, on your own materials.