Workspace User Journeys

Sabine's end-to-end journey through the Workspace, from tour creation to financial close-out.

Journey 1: Creation & Costing (The "Magic" Setup)

Sabine needs to get a new tour into the system and ready for sale.

• The Trigger: A partner hotel in Tuscany emails Sabine a 4-page PDF outlining the itinerary, hotel allotment (Kontingent), and group rates.
• The Action: Sabine logs into the Busflow Workspace. She clicks [+] New Tour and drags the PDF into the Magic Upload dropzone.
• The AI Co-Pilot: In 4 seconds, Busflow extracts the dates, the 5 stops, the hotel details, and the base costs. It generates a visual timeline.
• The Costing: Sabine selects the "49-Seater Coach" vehicle class and inputs the estimated toll and diesel costs based on the AI-extracted route distance. The Dynamic Margin Calculator instantly shows: "Break-even at 28 passengers." She sets the retail price and clicks Publish.
• The Outcome: The tour is instantly live on the B2C website and available for B2B partner agencies (Note: B2B invoice checkouts and commission handling are out of scope for Phase 1). Time spent: 3 minutes (previously 45 minutes of manual typing).

Journey 2: CRM & Sales (The Phone Booking)

While the website generates passive sales, Sabine still handles traditional customers who prefer to call.

• The Trigger: Herr Müller (72 years old) calls. He wants to book the Toscana tour for himself and his wife.
• The Action: Sabine opens the Rapid Manual Order Entry screen. She types "Müller" and the CRM instantly pulls up his profile, noting his preference: "Always wants front row."
• The Upsell & Seat Selection:
  • Sabine opens the Visual Seat Map and locks in seats 1A and 1B.
  • She asks if they need travel insurance (Reiseversicherung). He says yes. With one click, Busflow calculates the premium via the HanseMerkur API and adds it to the cart.
• The Payment (Online): Sabine clicks Complete. The system automatically emails Herr Müller a beautiful PDF booking confirmation with a secure Klarna/Credit Card payment link.
• The Payment (Offline): Alternative scenario: Herr Müller prefers a traditional bank transfer. Sabine selects "Manual Bank Transfer". The system generates the invoice with Busflow's smart IBAN and a unique payment reference (Verwendungszweck).

Journey 3: Dispatch & Operations (The Logistics)

The tour is two weeks away, practically sold out, and the dispatcher needs to resource it.

• The Trigger: Sabine needs to assign the physical bus and the driver.
• The Action: She opens the Dispatch Board (Gantt chart). She drags "Bus 4" (a 54-seater) and "Driver Klaus" onto the Toscana tour block.
• The Compliance Check: The DACH Compliance Copilot does a heuristic background check on Klaus's scheduled duty logs to ensure basic 11-hour daily rest. (Note: Full 14-day EU-561 rolling windows and tachograph integration are Phase 2). A green checkmark appears—no basic Lenk- und Ruhezeiten violations.
• The Allotment Alert: Busflow alerts Sabine that they only sold 48 of the 50 blocked hotel rooms. She manually contacts the hotel to release the 2 rooms, avoiding penalty fees.

Journey 4: Automated Communication (The Invisible Assistant)

The system takes over the manual administrative work leading up to departure.

• T-7 Days (Zimmerliste): Busflow automatically generates a perfectly formatted Excel/PDF rooming list (separating Herr Müller's double room from the single travelers) and emails it directly to the hotel in Tuscany.
• T-24 Hours (Passenger Comm): Busflow triggers an automated Email/SMS (or WhatsApp, if the operator has configured the advanced Business API integration) to Herr Müller: "Gute Reise! Your bus leaves tomorrow at 08:00 AM from Stop A." It includes a link to a tracking URL. (Note: The tracking link relies on 10-second polling. True 'Uber-style' live map SSE push updates and dynamic Apple Wallet ticket updates are Phase 2).
• T-0 Hours (Driver Run Sheet): Klaus opens his Busflow Driver App. His passenger manifest, route, and hotel drops are instantly synced and available offline.

Journey 5: Financials & System Control (The GF View)

The tour completes, and it is time to look at the money.

• The Trigger: It's the end of the month. Thomas (the GF) logs in to do his financial review.
• The Action: He opens the Executive Dashboard. His RBAC (Role-Based Access Control) gives him exclusive access to the margin views.
• The Insight: He clicks on the Toscana Herbstzauber tour. He sees a clean breakdown: 48 passengers, total revenue, fuel costs, insurance commissions, and an estimated net profit margin. (Note: Precise margin tax (TOMS/§25 UStG) calculation is deferred to Phase 3; Phase 1 shows estimated or deferred indicators like "~" or "nach Abschluss").
• The Bank Reconciliation (Magic Ledger): Before closing the month, Thomas uploads the company's bank statements (Camt.053/MT940 structured data or a scanned PDF). Busflow's AI Reconciliation Engine scans the incoming transfers, matches Herr Müller's unique payment reference to his booking, and automatically marks the invoice as "Paid."
• The Wrap-Up: Thomas navigates to the Accounting Sync tab. Because he previously mapped his SKR03 chart of accounts during the mandatory J0 onboarding step, he clicks Export to DATEV. The system generates a perfectly formatted CSV for his tax advisor, reconciling all payments, vouchers, and agency commissions.

This journey demonstrates how Busflow replaces at least five disparate tools (Excel, WhatsApp, Whiteboards, Legacy Booking Software, and Calculator) with one continuous flow.