See what changes when integrations, memberships, and the demo scenario run.
This hub replaces scattered explanations with three practical manuals. Each one uses screenshots, callouts, cause/effect tables, and reference details so a reader can prove exactly what happened.
Choose the path
Integration Workflow Manual
CRM, HR, TicketPro, Ecommerce, FlowOS, and Custom Apps. Shows connect, test, sync/webhook, local result, payload proof, and operator next action.
Open integration manualMembership Benefits Manual
Plan rules, Olivia assignment, wallet cards, booking benefit snapshot, payment ledger, package credits, usage ledger, renewal, and reporting.
Open benefits manualComplete Demo Script
Act-by-act demo script for platform handoff, vendor setup, website publishing, membership, booking, payment, support/refund, and ops review.
Open demo scriptThe one rule
If the docs cannot answer those five points, the docs are not done. The manual pages use this same order for every provider, benefit, and demo act.
Visual overview
What each page answers
| Page | Primary question | Images used | Best reader |
|---|---|---|---|
| Integration Manual | If I connect this app or run this event, what record changes and where can I prove it? | Integrations console, workflow result, custom app setup. | Vendor operator, support staff, integration developer. |
| Membership Benefits | Where do benefits appear from admin setup to customer wallet, booking, payment, receipt, and reports? | Programs, Olivia wallet, booking, payment, vendor booking. | Vendor admin, customer support, QA, demo presenter. |
| Complete Demo Script | What do I click, what do I say, and what visible proof should I show in the complete app demo? | Scenario map plus the screenshots from the two manuals. | Sales/demo presenter, product owner, QA. |
Quick impact map
Lead intake and booking mapping
CRM sync imports leads. A vendor converts a lead into a normal booking, and BookFlow stores the external lead-to-booking mapping.
Staff, locations, and leave
HR sync updates branch/location data, staff profiles, and leave blocks that affect availability and calendar behavior.
Support and refund review
Support requests and escalations attach external ticket references; paid cancellations can sit beside manual refund review metadata.
Wallet entitlements
Paid orders can create membership, package, voucher, or note-only events that appear in customer wallet and usage ledgers.
Conversation and lifecycle events
Reception channels send customer context into BookFlow; booking created/rescheduled/cancelled/completed events can be pushed outward.
Safe tenant workflows
Tenant-defined app keys, event templates, mappings, and predefined local actions create useful workflows without arbitrary code execution.
CRM and TicketPro path
Marketing starts in CRM, booking proof lives in BookFlow
Lead sync creates Lead Intake rows. Conversion creates the local booking and external mapping. Programs can send a paid ad draft back to CRM, but CRM keeps ad account credentials, approval, activation, publishing, and audit control.
Support ownership is explicit
When TicketPro is active, BookFlow creates one tracked case and marks the conversation TicketPro Handoff. When TicketPro is inactive, staff can resolve locally once and reopen only locally resolved conversations.
Source of truth
Docs are proof-led, not marketing-led.
Every manual section must include a screenshot or diagram, the action a user performs, the BookFlow record that changes, the exact screen where it appears, and the likely confusion to avoid.