Its own inbox. That actually replies.
Give the agent a real email address. It receives mail, keeps proper threads, answers from your knowledge base, and can send outbound too.
Agent inbox
reception@famulor.io
Thread
Re: invoice #10482 — double charge
Mira Chen
09:14mira@northwind.io
Hi — we were charged twice for invoice #10482. Can you refund the duplicate?
FamulorAgent
09:16reception@famulor.io
Thanks for flagging this, Mira. I checked the payment — the second charge was a soft-decline retry that still settled. I’ve issued a full refund for €49; it should land in 3–5 business days.
Mira Chen
09:18mira@northwind.io
Perfect, thank you — that clears it up.
Email as a full AI channel — not a notification bolt-on
Own address, real threads, replies and sends — with the same agent memory your phone and WhatsApp already use.
An address the agent owns
Give each agent its own mailbox — on your domain or ours — so customers write to a real address, not a no-reply alias.
Real threaded conversations
Inbound mail stays in proper RFC threads. Replies, forwards and follow-ups stay one conversation in history.
AI that answers the thread
The agent reads the thread, grounds replies in your knowledge base, and sends — the same brain as your voice agent.
Outbound mail from the agent
Confirmations, summaries and follow-ups go out from the agent address after a call or chat, with full delivery tracking.
Human takeover, any time
A teammate opens the thread, sees every turn, replies as themselves, then hands control back without losing context.
Sentiment and outcome on every thread
Each conversation is scored for sentiment and outcome so support and sales see what closed — and what still needs a human.
Every agent gets a real mailbox customers can write to
Provision an address on your verified domain. MX, SPF and DKIM stay under your control — the agent simply becomes that inbox.
- Dedicated address per agent or shared reception inbox
- Custom-domain send identity with delivery hardening
- Shows up in unified history next to calls and chats
Agent mailbox
reception@famulor.io
- MXmail.famulor.io
- SPFv=spf1 include:_spf… ~all
- DKIMbek._domainkey → txt
Customers write to a real address on your domain. The agent receives, replies, and sends from that same identity.
The agent answers mail — and can start the thread too
Inbound mail is read in context, answered from your knowledge base, and sent back in-thread. The same agent can also send confirmations and follow-ups after a call.
- In-thread AI replies with proper quoting and headers
- Outbound send for summaries, links and next steps
- Same policies and tools as voice and WhatsApp
Reply & send loop
LiveCustomer emails the agent address
Thread + knowledge base grounding
AI drafts and sends in-thread
Agent can also start a new mail
Step in when email needs a person, then hand it back
Teammates see the full thread the moment they open it. Take over, reply, and return control to the agent without rewriting history.
- One-click takeover from the inbox
- Full prior turns visible to the human
- Agent resumes with complete context
Re: delivery delay — #BEK-8821
3 turns · agent + customer
Calls, chats and email stay one conversation
When a caller follows up by mail, the agent already knows the booking, the invoice and the last promise — because memory is shared.
Same agent address, same knowledge base, same outcomes — whether the next turn is spoken, typed in chat, or sent by email.
Common questions about email
Yes. You provision a mailbox for the agent — typically on your verified custom domain — so customers write to a real address.
Give your agent a real inbox
Provision an address, keep threads, and let the same agent reply by email.