Why Slack + dassi
Slack 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 Slack
- Weekly analytics updates: Convert dashboards into a compact weekly summary message with key metrics and one recommendation.
- Thread summarization: Summarize long threads into decisions, open questions, and action items.
- Meeting follow-up notes: Turn call notes into a structured recap and next steps.
Quick start
- Open Slack in Chrome.
- Open the dassi sidebar.
- Start with a safe workflow: summarize → propose → draft → review → act.
Prompt recipes (copy/paste)
- “Write a weekly summary of this dashboard for Slack.” (from Analytics Dashboard That Writes Its Own Weekly Update)
- “Call out the top 3 drivers for traffic change.” (from Analytics Dashboard That Writes Its Own Weekly Update)
- “Build a prep brief for this meeting: attendee backgrounds + recent threads.” (from Meeting Prep Panel Injected Into Calendar Events)
- “Pull last touchpoints from Salesforce and summarize them.” (from Meeting Prep Panel Injected Into Calendar Events)
- “Summarize what’s on screen and propose next actions.”
- “Do the safe part first (draft / label / preview), then ask me before any irreversible action.”
- “Turn this page into a clean checklist I can follow.”
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.