Enterprise booking flow
How an employee at an enterprise client books, signs, pays, and reconciles a venue — without ever touching a personal card.
1. Summary
The enterprise booking flow is the end-to-end process by which an employee of an enterprise client books a venue, executes the contract, pays the venue, and reconciles the expense — without ever holding a personal card or filing reimbursement.
It is the operational substrate of Ande for Enterprise and the primary integration surface between the Virtual Concierge, the Concierge team, and the client's Finance org.
The flow is composed of three sold products —
Central Pay,
Central Legal, and
BYOV —
plus internal protocols that govern how the Virtual Concierge pauses, how
Jira tickets are routed, and how a virtual purchase card is issued.
Each client sits at a position on the configuration matrix
(codes C0 through C7).
2. Actors
Five actors participate in every enterprise booking. Two are humans on the client side, one is the Ande AI agent, one is the Ande human ops team, and one is the venue. Finance enters only when Central Pay is enabled.
- Booker. The employee placing the request. Sees only the Ande app and the VC chat — never a card prompt, contract, or invoice on configurations C1 or higher.
- Virtual Concierge. The AI agent that runs the booking conversation. Pauses on go-ahead, resumes after the Concierge marks the booking complete. Pause / resume protocol: RFC-09.
- Concierge team. Ande employees. Pick up the Agent Support ticket and execute the contract and payment steps. Each client has an assigned Account Owner.
- Venue. Restaurant or event space — either a partner (integrated via TripleSeat or SevenRooms) or offline. Determines Path A vs. Path B at stage 5.
-
Finance. The client's finance org plus Ande's payments team, which issues
virtual P-cards and coordinates POs in
#central-payments.
3. Related documents
All documents that intersect the enterprise flow. Blue links are live pages; dashed orange links are stubs not yet written.
4. Lifecycle stages
Every booking moves through seven canonical stages. Steps 3 and 7 are state transitions where the Virtual Concierge pauses and resumes. Step 5 is the branch point — the path taken depends on whether the venue is partner-integrated.
-
Configure.
Ande admin enables the relevant products on the client in the Admin Portal — Central Billing,
Central Legal, BYOV — and sets the configuration code (
C1–C7). From this point, checkout routing never prompts bookers for a card. Ande admin - Book. The booker picks a venue and gives the go-ahead in the VC chat or Ande app. The system reads the client's product configuration and the path forks. Key signals detected: partner flag on the venue, deposit amount, Central Legal on/off. Booker VC
-
VC handoff.
The Virtual Concierge posts a deterministic handoff message and stops auto-responding.
Wording varies by configuration:
on C1 (billing only) the booker is told the Concierge will handle payment;
on C4/C5/C7 (billing + legal) the booker is told both will be handled.
Booking is marked
awaiting concierge. VC Booker - Jira ticket. An Agent Support ticket is created automatically and routed to the client's assigned Account Owner. The ticket carries: client name, event details, venue + partner flag, deposit amount, active products, contract/payment links, and the Path A or Path B playbook. Concierge
-
Pay and sign.
Path A — partner venue: Concierge checks out at the Ande paylink using Central Billing as the instrument.
Path B — offline venue: Concierge creates a P-card from the ticket, coordinates PO / approver in
#central-payments, and pays at the venue's payment link. If Central Legal is on, the contract is signed in the same step. See Central Pay § Payment paths for the full branch. Concierge Venue - Reconcile. Receipt (and signed contract, if applicable) is uploaded to the event page in the Admin Portal. The expense is logged under "Central Billing" — card number, cardholder, and paying-user fields are hidden. Only amount, vendor, date, and attachment are recorded. Concierge Finance
-
Unpause.
The Concierge posts a completion message in the booker's chat thread, authored as the Virtual Concierge.
This re-enables auto-reply. The VC can now handle follow-up questions ("what time is the reservation?")
without a human in the loop. Booking moves to
confirmedand the 1.5% fee accrues to Ande GBV. Concierge VC Booker