One thread per client, tied to the transaction
A conversation in Connect is not just an inbox row. It carries the client, the transaction it belongs to, the waiting state, and the automation history, so anyone opening the thread sees the whole picture in seconds.
Because messages live on the transaction record, the communication trail is part of the file, not a separate archive someone has to reconstruct when a question comes up.
- Email, SMS, and call logs unified per client and per transaction
- Waiting-on-you and waiting-on-them states on every thread
- The thread is part of the record, not a separate archive
EVE drafts, you approve
EVE reads the thread and prepares the follow-up: the nudge for an unanswered question, the on-track update before closing, the reconnect after a quiet stretch. Sensitive topics, like offers, pricing, and complaints, always come to you first.
Connect your Gmail or Outlook and EVE keeps the awareness fresh automatically, so the briefing knows who replied without you lifting a finger.
- Drafted replies and follow-ups inline in the thread
- Gmail and Outlook connect with real-time ingest
- Escalation gate: sensitive topics always route to a human
From conversation to calendar
When a conversation lands on a meeting, EVE sends a real calendar invite from the thread: an ICS the client can accept in one tap, plus the matching appointment on your REALM calendar.
Outbound email and SMS ride the same canonical send path, so delivery status, opt-outs, and history stay accurate on the record.
- Calendar invites sent from the thread in one click
- Delivery outcomes and opt-outs tracked on the record
- Voice calls logged into the same client history
EVE offers only times you are actually free, sends the invite, and puts it on the calendar the rest of your work already lives on.
Frequently asked questions
Do I have to give up my email address?
No. Connect your existing Gmail or Outlook and REALM works with it: conversations ingest into the client's thread, and sends go out through your connected inbox where possible.
Can my team see client conversations?
Visibility follows the transaction and workspace roles. A team lead or transaction coordinator working the file sees its thread; another agent's unrelated clients stay private to them.
Does EVE send messages on its own?
Only if you put it in Autopilot mode, and even then sensitive topics (offers, pricing, contracts, complaints, opt-outs) always drop to a human for approval. In Suggest and Guided modes, EVE drafts and you approve every send.
What happens when a client replies to an automated sequence?
EVE pauses the sequence immediately and notifies the agent, so a real reply is never answered by a drip step. The thread shows the pause and the reason.