Every transaction has a built-in mailbox on its Email tab. Messages you send from there, and every reply that comes back, stay with the transaction — so the whole conversation history lives next to the documents and deadlines it's about.
Transaction email is included on every LetterScript workspace (see Plans and usage). Your free first transaction includes 10 sent emails; transactions on purchased transactions send without a meter.
The transaction's own email address
Open a transaction and go to the Email tab. At the top you'll see the transaction's unique address (it looks like d-a1b2c3d4e5f6@deals.letterscript.com) — click it to copy.
That address is the magic piece:
- Replies route themselves. Anything you send from the Email tab carries this address as its reply-to, so when escrow or the other agent hits Reply, their answer lands back in this tab — in the right conversation thread.
- CC it from anywhere. Add the transaction address as a CC on any email you send from your own inbox, and a copy files into the transaction automatically.
- Attachments come along. Files on inbound email are stored with the message — download them straight from the thread.
The address is unguessable on purpose: mail to anything that isn't a live transaction address is dropped, so the tab stays free of spam.
Emailed documents file themselves
When someone on the transaction emails a contract, disclosure, or report to the transaction address, the attachment doesn't just sit on the message — it's added to the transaction's documents and processed like an upload: the text is read, the document is classified, and the transaction record, checklist, and timeline update from it. Forward the executed purchase agreement and the transaction builds itself.
A few things happen behind the scenes to keep this safe and tidy:
- Known senders file automatically. "Known" means your workspace members, anyone on the transaction's Parties list, anyone you've emailed from the transaction, and senders you've trusted before. An attachment that filed shows an In documents badge.
- Unknown senders wait for your OK. Their files are held, with an Add to documents button on each attachment and a banner offering Trust sender & add all — one click files everything they sent and auto-files whatever they send later. Messages that fail email authentication checks are held too, even from a familiar-looking address, so a forged "listing agent" can't quietly change your transaction record. The banner names the reason as it stands now, not as it stood when the mail arrived: add the sender to Parties afterwards and it changes to "… is on this deal now — their files are still waiting for your OK", so a failed authentication check is never dressed up as a roster problem or the reverse.
- A deleted document can be put back. If an attachment filed and the document was deleted later, the attachment shows Removed rather than a green In documents badge over nothing — and Add to documents returns, because the file itself is still held safely.
- Attachments that didn't file now say so. Something the mailbox couldn't take — a file type it doesn't read, an inline signature image, an attachment that errored on the way in — carries a Not filed or Couldn't file tag, and hovering it gives the reason. The message shows a line saying how many weren't added, and the conversation list marks the thread N not filed, so you can see it without opening every message. The file is still there to download; it just isn't in the transaction's documents.
- Duplicates are caught. The same executed contract often arrives three times — from the agent, from escrow, from the coordinator on the other side. Identical copies get a Duplicate badge and aren't processed again, so they don't clutter the transaction or spend your pages.
- Link-only emails get a nudge. If a message says "here's the signed contract" but carries a DocuSign or Drive link instead of a file, the thread shows a reminder to download and upload it yourself — LetterScript never follows external links on its own.
For known senders, the email text itself joins the transaction's record too: facts that only live in correspondence — "close of escrow moved to the 21st", an escrow officer's direct line in a signature — become searchable, citable in transaction chat, and feed the extracted record. On your free first transaction, each indexed email counts as one page of its included allowance; purchased transactions have no page meter.
Writing an email
The first time you send, LetterScript asks you to confirm your sending address — a one-time step at the top of the tab; New email and Reply stay disabled until you do it. Once confirmed, click New email and address it by picking from the transaction's parties (anyone with an email on the Overview tab appears as a suggestion), choosing a group, or just typing an address and pressing Enter.
Mail then goes out from your confirmed name and address — the composer shows "Sending as …" — with replies still routed to the transaction so they file back here. Until you've confirmed an address, messages are sent from your name "via LetterScript" instead. Sending is plain text — what you type is what they get.
To reply inside an existing conversation, open the thread and click Reply — the recipient and subject are pre-filled and the message threads correctly in the recipient's email client too. When a conversation has more than two people on it, Reply all appears beside it with the number it will reach; it carries everyone still on the thread into Cc, minus you and the transaction's own address. Every recipient is a chip you can remove before sending, so reply-all is a starting point rather than a commitment.
An unfinished message keeps itself. If you leave the composer — switching tabs, pressing Back, or closing the browser — the draft is saved on this device and restored the next time you open that reply, with a note saying when it was saved and a Start fresh button to throw it away. Discard asks first, and offers Leave it saved if you only meant to step away. Drafts are cleared once the message sends, and expire after a week.
Drafting with AI
In the composer, click Draft with AI, describe what the email should say — "ask escrow for updated wire instructions and confirm the closing date" — and click Draft. The assistant writes a subject and body using only what it knows about this transaction (its record, parties, deadlines, and the conversation so far), and you can edit everything before sending.
On your free first transaction, each AI draft uses one smart answer from its included allowance — the same allowance the transaction assistant uses. Transactions on purchased transactions draft without a meter.
If a draft discusses moving money or changing payment details, the composer says so before you send: messages like that go out with a wire-fraud verification notice added for the recipient. A draft that contains a suspicious link is flagged the same way, with the link shown. Neither blocks sending — genuine closing email discusses wires — and the notice clears as soon as you edit the message, because what gets checked is whatever you actually send.
Automated drafts
Separately from the composer, LetterScript drafts the routine transaction emails for you — the kickoff intro when a transaction goes into contract, the wire-fraud warning, deadline reminders you've set to Draft first, the closing-week summary, and a congrats note at close. They appear in a Drafts ready for review strip above the conversations; nothing sends until you review and click Send. Which moments draft and when is configured on the global Automations page; template drafts are addressed to the party roles you pick there, while reminder drafts — and reminders you set to Auto-send — go to you, the transaction owner — see Automated email drafts and Automations: reminder and email moments.
Recipient groups
Open the mailbox's Settings menu (the gear button in the top-right) and choose Recipient groups to create named CC lists for this transaction — for example "Buyer side" (buyer + buyer's agent) or "Escrow + lender". In the composer, picking a group adds all of its members in one click. Groups belong to the transaction, so each transaction can have its own.
Reading and threads
Conversations are grouped into threads on the left; unread ones are marked with a green dot and open automatically marks them read. Outbound messages show a delivery state (Sent → Delivered, or Bounced if an address was bad), so you know it arrived.
All transactions at once: the Inbox page
Inbox in the top bar opens the cross-transaction view: every transaction listed with its unread count and latest message, most recent activity first. Expand a transaction to see its conversations, and click any conversation to jump straight into that transaction's mailbox with the thread open. All mail / Unread narrows the list to transactions with something still unread, and the filter box narrows it by transaction name, address, sender, or subject — handy once several transactions have active email.
Good to know
- Recipients see the message from your confirmed sending name and address (or, before you've confirmed one, from your name "via LetterScript"), with replies routed to the transaction address — not from your personal email account.
- One send can address up to 25 people across To and CC.
- The mailbox is per-transaction. Mail never crosses between transactions, even when the same people are on both.