Ande Platform · Internal Knowledge Base
The back-office engine powering Ande's enterprise clients — from PO approvals and procurement integrations to legal agreements and centralized billing. A P0 priority for the company in 2026.
New to enterprise workflows?
From account creation to first booking — how an enterprise user experiences the Ande platform and all the workflows that activate behind the scenes.
Admin configures company profile, SSO/Okta, cost centers and access levels in Control Center
Admin onlyCentral Billing, Central Legal, Procurement (POs) are toggled on per client configuration
Config layerAdmin or booker creates Purchase Orders with budget, approvers, and user assignments
ProcurementBooker discovers venues via AI, shortlists, and requests availability through the marketplace
MarketplacePO approval → Legal signing (SA / AA) → Payment via Central Billing or P-card
E2E workflowFor self-serve bookers
Booker searches venues on Ande, selects PO at checkout, approval triggers automatically if required. Legal is managed based on the company's Central Legal config.
For off-platform venues
Booker CCs Ande AI agent on venue email. Agent captures details, creates an Event in Ande, and runs the full PO → Legal → Payment workflow natively.
Via AI assistant
Booker chats with the Virtual Concierge. VC detects enterprise config, handles the booking, and escalates to the concierge team via Jira for legal and payment steps.
Product line
Enterprise Workflows is the product line that handles everything after a venue is selected — payments, approvals, legal, and expense tracking.
Ande pays venues on behalf of enterprise clients, then invoices monthly. Supports partner venues (direct checkout) and offline venues (P-card). Fee: 1% of GBV.
Handles all legal agreements between enterprise clients and venues — via DocuSign Standard Agreement or Agent Agreement (LPOA) letting Ande sign on the client's behalf.
Full PO lifecycle management — create, assign, approve, and track purchase orders across enterprise entertainment spend. Oracle Punchout integration live for Cloudflare.
Connects Ande entertainment spend with enterprise T&E systems (Navan, Concur, SAP). Cost center tracking, expense reports, and reconciliation at scale.
Key capability
Converts unstructured email bookings at off-platform venues into fully structured Ande events. Enforces PO approvals, legal agreements, and centralized billing — even when the venue isn't in the marketplace.
Booker contacts venue directly and CCs the Ande AI agent. Agent identifies client, validates BYOV is enabled, and collects required data via the email thread.
System creates the Event container in Ande. Sends the Event Submission Page (Stepper) to the booker. Booker selects their PO. Approval triggers if required.
Legal begins after PO approval. System determines the path: Standard Agreement (DocuSign) or Venue Contract (Agent Agreement or direct booker signing).
Triggered only after legal is satisfied. Partner venues: concierge impersonates and checks out with Central Billing. Offline venues: concierge creates P-card and uploads receipt.
VC creates a Jira ticket (type: Agent Support) routed to the assigned account owner. Includes client, venue, PO, estimated GBV, products enabled, and instructions per config.
Reservation moves to CONFIRMED state. VC unpauses and posts completion message in the booker's chat thread as if it never stopped. Booker gets final confirmation email.
Reservation confirmation requires all of the following
AI integration
The VC detects enterprise configuration at conversation start and adapts its behavior. For enterprise users, it escalates to a Jira "Agent Support" ticket and pauses until the concierge team completes the work.
Config C0
Standard flow — no enterprise products
→ Normal VC booking
Config C1
Central Billing only — concierge pays
→ Booker signs, Ande pays
Config C2 / C3
Central Legal only — concierge signs
→ Ande signs, booker pays
Config C4–C7 (full)
Central Legal + Billing — concierge handles all
→ Ande handles everything
After enterprise escalation triggers, VC stops responding automatically. A Jira "Agent Support" ticket is created and routed to the client's assigned concierge.
Concierge handles contract review, signing (SA/AA), and payment. Responds in the same booker chat thread, appearing as the VC persona — no context break for the booker.
When concierge posts the booking confirmation, VC unpauses and resumes automated responses. Ticket is closed. Booker receives confirmation email with full booking details.
Engineering tracker
Key Linear and Jira issues across the Enterprise Workflows team. Use the issue links to get full context and current status.
Assign manager of the requestor as budget owner in Oracle Punchout flow. Impacts Cloudflare onboarding.
Email logic when Ande Approvals are turned off. Payment approval workflows section visibility.
Correct order: 1. Direct supervisor → 2. Team workflow approver → 3. Client default approver.
When venue has a signed Standard Agreement, send the signed version (not the unsigned template) to Jira.
Standard Agreement and venue contracts now visible in the event plan's contracts section.
Allow bookers to assign POs retroactively on Events. Approval flow triggered if required; no extra workflows.
Payments on reservations from Concierge Requests were not being associated with events for PO accounting.
System doesn't validate duplicate PO values when a user selects "New PO number" in checkout.
Knowledge base
Start here for specs, test plans, designs, and product definitions across the Enterprise Workflows product line.
PRD · Confluence
Full product requirements for Bring Your Own Venue — intake logic, legal engine, payment, state models, and all notification tables.
→ Open in ConfluenceTest Suite · Confluence
52-case test suite for VC × Enterprise Workflows integration. Config matrix, entry/exit criteria, E2E critical paths EP-049 through EP-052.
→ Open test suiteSpace · Confluence
The dedicated Confluence space for the Enterprise Workflows product team. PEW space for all specs and docs.
→ Open spaceSpec · Confluence
Spec for overriding PO approvals when submitting service requests from Admin Portal. Covers all 4 acceptance criteria.
→ Read specTest Plan · Confluence
Toggle behavior and email logic for all PO states: With PO, No PO, New PO, approvals on/off, same-person edge cases.
→ View test planDiagram · Figma
The complete end-to-end BYOV flow in FigJam — intake, PO, legal paths (SA/AA/fallback), payment, and reservation confirmation logic.
→ Open in FigmaDesign · Figma
All approval UI designs — checkout stepper, PO approval modal, contract signing landing page, and Control Center approval settings.
→ Open designsTest Plan · Confluence
13 test cases covering approval toggle behavior, PO creation with approvals off, and existing PO selection scenarios.
→ View test planIssue Tracker · Linear
All active and backlog Linear tickets for the Enterprise Workflows team. Filter by team "Enterprise Workflows" for full view.
→ Open LinearPeople & comms
Who to talk to and where to find conversations when you're stuck or have questions.
Core team
Slack channels