Why Outlook + dassi
Outlook is already where the work happens. dassi adds the missing layer: it can read what’s on the page and then take actions (draft, classify, fill, log, summarize) without you rebuilding context in a chat box.
What to automate in Outlook
- Batch triage and labeling: Cluster emails by intent and execute safe batch actions to reduce inbox overhead.
- Contextual reply drafting: Draft replies that reflect the full thread and your preferred tone.
- Email → calendar event: Parse informal scheduling text and create pre-filled calendar events.
Quick start
- Open Outlook in Chrome.
- Open the dassi sidebar.
- Start with a safe workflow: summarize → propose → draft → review → act.
Prompt recipes (copy/paste)
- “Classify this inbox: needs reply today vs FYI vs newsletters.” (from Email Triage With Batch Actions)
- “Archive all newsletters and keep anything from my boss.” (from Email Triage With Batch Actions)
- “Turn this into a calendar invite for Thursday 3pm at Blue Bottle.” (from “Add to Calendar” Button Inside Any Email)
- “Add a 25-minute buffer and include the Zoom link if present.” (from “Add to Calendar” Button Inside Any Email)
- “In Outlook, label these threads (urgent / waiting / FYI) and propose batch actions.”
- “Draft a reply that references the full thread and ends with 2 concrete next steps.”
- “Turn scheduling text in this email into a calendar event — ask me to confirm time zone.”
Safety checklist
- Tell dassi: “Never submit/send without confirmation.”
- If the page contains sensitive data, ask for redaction or aggregated outputs (totals-only, no PII).
- Prefer reversible actions first (drafting, labeling, notes) before destructive ones.