Why Booking.com + dassi
Booking.com 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 Booking.com
- Calendar conflict markers: Mark conflicts directly on date pickers so you don’t double-book.
- Option comparison: Extract key differences (fees, cancellation, location) across listings and compare.
- Itinerary notes: Generate a short travel plan with confirmations and next steps.
Quick start
- Open Booking.com 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)
- “Pin this product. Build a comparison table for the pinned items.” (from Side-by-Side Product Comparison, Built on the Fly)
- “Highlight which one is best for gaming vs. office work.” (from Side-by-Side Product Comparison, Built on the Fly)
- “Compare these options on cancellation policy, total price, and location tradeoffs.”
- “Check my calendar and mark conflicts on the date picker.”
- “Summarize the top 3 options as a decision memo.”
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.