Run BookFlow as one product story from setup to proof.
This script tells the complete Nimbus story: platform handoff, vendor setup, website publishing, membership lifecycle, customer booking/payment, support/refund review, integration workflow, and vendor ops review.
Scenario map
Each act must show a cause and an effect. Do not describe features in isolation; show the record that changed and the screen that proves it.
Demo acts
Act 1Platform
ActionStart on the platform dashboard and open the Nimbus tenant workspace.
Proof lineMaya is now inside Nimbus, so every next action is tenant-scoped.
Act 2Vendor
ActionOpen Services and create or verify Demo Recovery Therapy with price, duration, deposit, staff, location, and rebooking interval.
Proof lineThe service appears in catalog and controls what the storefront booking form can sell.
Act 3Website
ActionOpen media library and homepage studio, adjust customer-facing membership/service content, choose usable media, publish, and verify storefront.
Proof lineThe public storefront reflects published content and real images, not editor-only state.
Act 4Programs
ActionCreate Nimbus Recovery Member, set 15% discount, deposit waiver, priority slots, assign Olivia, and sell a recovery package.
Proof linePrograms shows rules, Olivia preview, active member status, package credits, and usage ledger readiness.
Act 5Customer
ActionLog in as Olivia, open wallet, book an eligible service, confirm benefit snapshot, pay, and open receipt/invoice links.
Proof lineWallet, booking summary, payment ledger, receipt, and invoice all explain the same benefit impact.
Act 6Support
ActionSubmit a support request for the booking/payment issue and cancel a paid booking to trigger manual refund review metadata.
Proof lineTicketPro case and refund review context appear beside the booking without creating a separate dispute domain.
Act 7Ops
ActionOpen booking detail, calendar, reports, receptionist, integrations, and notifications. In Receptionist, show the flagged AI conversation and the TicketPro follow-up case action.
Proof lineThe vendor can see operational impact across schedule, revenue, support, AI handoff, benefits, and external app activity.
Screens to show
Service setup
Create Service
Show price, duration, deposit, staff, location, rebooking, and service catalog proof.
Website
Builder and storefront
Show media, section edit, design controls, publish/revision, then public storefront result.
Programs
Membership rules
Show what members get, Olivia assignment, package sale, and usage ledger.
Customer
Wallet and booking
Show what I get, used, remains, booking benefit summary, and matched customer email/account.
Payment
Payment ledger
Show amount due, benefit lines, receipt creation, and portal invoice/receipt links.
Receptionist
AI to TicketPro handoff
Show normal AI answer, flagged human follow-up, Create TicketPro Follow-up Case, and the handled state that disables duplicate follow-up.
Integrations
Workflow test
Show incoming event, mapped fields, local result, linked record, payload drawer, and next action.
Presenter notes
Moment
Say this
Avoid saying
Integration simulator
This event came from an outside app, BookFlow mapped it, created or linked this local record, and logged the proof.
It just connects to apps.
Membership setup
This plan is not just a label. These rules change booking and payment behavior for Olivia.
Members get some perks.
Booking benefit
The customer sees benefits before confirming, so the price and deposit behavior are understandable.
The backend handles it.
Payment ledger
The invoice total and benefit ledger explain exactly why the amount due changed.
The discount is applied somewhere.
Support/refund
BookFlow uses support case context plus manual refund review on the booking; no separate dispute product is being invented.
We added disputes.
AI receptionist follow-up
If TicketPro is configured, BookFlow creates one tracked TicketPro case and locks duplicate follow-up. If TicketPro is missing, staff can resolve locally once and use the Configure TicketPro link.
The app sends follow-up messages automatically.
Visual proof checklist
Service catalog shows the created or verified service.Published storefront shows updated website section and valid image media.Programs shows plan rules, customer-facing preview, Olivia assignment, package sale, and usage ledger.Olivia wallet shows active perks, credits used/remaining, renewal/expiry, and support entry.Booking form shows eligible/applied benefit summary before confirmation.Payment page shows benefit ledger beside invoice totals and creates receipt proof.Vendor booking detail shows payment status, applied benefits, support case, and refund review context.Receptionist shows TicketPro configured and not configured behavior: one tracked case when active, one local resolution when inactive.Integrations Activity shows workflow test, payload/mapping, linked record, and operator next action.
Manual links
Integration details
Use the manual when the audience asks what happens after connecting CRM, HR, TicketPro, Ecommerce, FlowOS, or a custom app.
