Why Google Maps + dassi
Google Maps 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 Google Maps
- Calendar-aware planning: Check meeting locations and conflicts while you plan routes or appointments.
- Place research brief: Summarize hours, parking notes, and options into a short plan.
- Itinerary drafting: Turn multiple places into an ordered itinerary you can share.
Quick start
- Open Google Maps in Chrome.
- Open the dassi sidebar.
- Start with a safe workflow: summarize → propose → draft → review → act.
Prompt recipes (copy/paste)
- “Check my calendar and mark conflicts on this date picker.” (from Travel Booking Page That Shows Your Calendar Conflicts)
- “Only show options that avoid conflicts on weekdays.” (from Travel Booking Page That Shows Your Calendar Conflicts)
- “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.