Last updated: 2026-05-21

Sending email through Elliot

Elliot can draft a tenant or contractor email from a chat prompt and have it ready to go in a couple of seconds — but the actual send is your decision, every time. There's no path for Elliot to email anyone without your explicit click on an approval card.

The reasoning is simple. Chat is fast; mistakes in email are slow to walk back. The card gives you the From, To, Subject and Body in one glance before anything leaves.

How the flow works

You ask Elliot to send something — "Reply to Aoife about the boiler" or "Email Tom and confirm Thursday morning works for the gas service". Elliot composes the draft, then the chat renders an Email ready to send card below his message with four explicit lines:

From — your @anchorlet.ie alias (e.g. orla.hughes@anchorlet.ie)
To — the recipient address Elliot resolved
Subject — the line Elliot drafted
Body — the full message, preformatted so line breaks survive

You read it. You click Approve and send or Cancel. Approved sends play a soft chime and the card flips to ✓ Sent to aoife.brennan@example.com. Cancelled drafts collapse to a one-line Draft cancelled placeholder — Elliot can be asked to redraft if you change your mind.

The From line is you, not Anchorlet

Every send uses your personal @anchorlet.ie alias as the From address, derived from your profile's full name. When Orla Hughes asks Elliot to reply to a tenant, the email goes out from orla.hughes@anchorlet.ie — the recipient sees a message from Orla, not from a bot or a generic support address. Replies come back into your Mail Triage view automatically. More on aliases at Your @anchorlet.ie email address.

A real example

You're chatting with Elliot and type:

Reply to Aoife at Apartment 4, Burlington Road about the boiler — let her know Tom will be there Thursday morning, he'll text closer to the time.

A second or two later, the card appears below Elliot's response:

From: Orla Hughes <orla.hughes@anchorlet.ie>
To: aoife.brennan@example.com
Subject: Re: Boiler issue
Body: Hi Aoife, just confirming Tom will be over Thursday morning to take a look at the boiler — he'll text you closer to the time with an exact window. Best, Orla

You skim, click Approve and send, the chime plays, the card flips to confirm the send. Aoife gets the email from Orla's address; any reply she sends lands back in Triage and (because this was an issue-scoped reply) gets filed against the same boiler issue automatically.

What if Elliot tries to email someone on the hold list?

The card still renders so you can see exactly what Elliot wanted to send. But the Approve and send button is greyed out, with an amber banner above the buttons explaining why: "This recipient is on your hold list. Remove from Settings → Email holds to send."

Your own email address is on the hold list by default, so Elliot can't accidentally CC you on a tenant reply or mistakenly send you a message meant for the tenant. You can add or remove addresses any time at Email hold list.

Things to know

Elliot can't send unilaterally. There's no tool in Elliot's toolbox that bypasses the card. The approval click is the only path from draft to sent.
Drafts are in-memory. Refresh the chat tab and any unconfirmed draft is gone. Re-ask Elliot to redraft if you cancelled and changed your mind.
The chime is a confirmation, not a guarantee. Your browser's tab-mute, autoplay policy, or a muted speaker can silence it — the visible ✓ Sent to … banner is the authoritative confirmation.
Issue-scoped sends thread automatically. When Elliot has issue context (you've been chatting about a specific issue), the send is filed under that issue's email thread and any reply routes back to the same issue.