What is the 'Reply with HEIDI' flow?
'Reply with HEIDI' is a dedicated folder or label. Drag a message into it and HEIDI prepares a grounded reply draft from thread context and approved documents. Drafts are review-only by default and are never sent without human approval unless setup explicitly allows it.
Capabilities
What you can do with HEIDI Workspace
No command to learn
Drag the message into the folder — HEIDI takes the cue and drafts.
Grounded in your knowledge
Drafts use thread context plus approved documents with sources visible.
Review-only by default
HEIDI does not auto-send unless permissions and setup allow it.
Syncs to native drafts
Drafts appear in the Outlook or Gmail draft where supported.
Use cases
Where teams apply HEIDI Workspace
Real workflows that benefit from visual design, automation, and governance.
Support Ops triages a long thread
Drop it in the folder; HEIDI summarises and drafts a grounded reply for review.
Customer A asks a how-to question
HEIDI uses the manual to prepare a stepwise reply with sources.
A reply needs a careful, on-brand tone
HEIDI drafts in the configured persona; the reviewer revises if needed.
Repeated question pattern
Drop similar threads in the folder for consistent grounded drafts.
Reviewer prefers drafts over commands
The folder flow needs no typing — just review and approve.
How it works
From chaos to clarity in 4 steps
Drag into the folder
Move the message to 'Reply with HEIDI' or the equivalent label.
HEIDI grounds the draft
Thread context plus approved documents, with sources shown.
Review and revise
The draft is review-only; revise on instruction.
Approve to send
Nothing leaves the mailbox without sign-off, unless configured otherwise.
Low-friction adoption for busy teams
Some operators love command bars; others just want to point at a thread and say 'handle this.' The 'Reply with HEIDI' folder is the lowest-friction entry point: no syntax, no setup per message. HEIDI prepares the grounded draft, shows its sources, and waits for the reviewer — keeping the human-in-the-loop default intact.