What are @HEIDI commands?
@HEIDI commands are plain-English instructions you type inside an email draft or the workspace. HEIDI parses the command, prepares an approval request, and after approval runs skills such as drafting a grounded reply, researching a company, generating a PDF, extracting invoice fields, or attaching a document from OneDrive or SharePoint.
Capabilities
What you can do with HEIDI Workspace
Plain-English, not a query language
Type what you want. HEIDI parses the intent and prepares the action for review.
A catalog of governed skills
Draft, research, generate documents, extract fields, schedule, attach, notify — each with an approval gate.
Grounded in your knowledge
Drafts and answers pull from approved documents with sources visible.
Approval before external action
Nothing sends, attaches, or updates a system until a human approves.
Use cases
Where teams apply HEIDI Workspace
Real workflows that benefit from visual design, automation, and governance.
@HEIDI draft a grounded reply
HEIDI retrieves the right manual or SOP and prepares the reply with sources for approval.
@HEIDI research this company and attach a brief
HEIDI compiles a short PDF brief and proposes attaching it to the draft after approval.
@HEIDI extract the invoice fields
HEIDI reads the attached PDF and pulls amount, due date, and vendor for review.
@HEIDI suggest meeting times
HEIDI proposes slots from the calendar and drafts the scheduling reply.
@HEIDI find the order confirmation and attach it
HEIDI locates the document in OneDrive or SharePoint and adds it to the reply for approval.
How it works
From chaos to clarity in 4 steps
Type @HEIDI in a draft
Inside Outlook or Gmail, write a plain instruction.
HEIDI parses the command
It maps the request to the right skill and gathers context.
HEIDI prepares an approval request
You see what will happen and the sources used.
Approve, and HEIDI executes
The skill runs — draft, attach, generate, or notify — only after sign-off.
Avoid these
Common mistakes (and how to avoid them)
Treating @HEIDI as auto-send
Commands prepare actions; they do not bypass approval.
Use commands to assemble the work, then approve before anything external runs.
Why a command layer beats a chat box
Most AI email tools stop at 'summarize and suggest text.' A command layer lets the operator stay in the draft and ask HEIDI to complete the operational task — research, documents, calendar, attachments — while keeping a human approval step before anything leaves the mailbox. The instruction is natural; the execution is governed.