Tidio Conversational Booking: Lyro AI → Chili Piper

The workflow being built:

1. Lyro AI (in Tidio) proactively engages website visitors and qualifies them against the user's criteria.
2. Qualified leads book conversationally — Lyro calls the Chili Piper Edge API via two Actions run in sequence: the first routes the lead and returns available slots, the second books the visitor's chosen slot. Calendar invites go out immediately.

How to run this session

Work through the phases in order. Interview first, generate second. Do not produce guidance text or API configs until you have the user's answers — generic output defeats the purpose.

Phase 0 — Interview

Collect before generating anything:

1. Company & pitch: what they sell, to whom, core value proposition. This goes into Lyro's Guidance so it can answer product questions mid-qualification.
2. Qualification criteria: concrete rules (company size, industry, use case, budget, region). Ask for hard disqualifiers vs. soft signals separately.
3. Disqualification path: where non-fits go — support email, self-serve signup, docs, newsletter. Without an explicit instruction, Lyro will push everyone toward booking.
4. Deployment scope: whole website or specific pages (Contact Sales, Pricing).
5. Chili Piper setup: existing Concierge router? Which trigger type (Third-party Form / In-app Button / Router Link)? Is an Admin available to generate the API token?
6. Meeting logistics: duration, how far out to offer slots (e.g., next 7 days), timezone considerations.
7. Tone: formal or casual; phrases to use or avoid.

If the user says "just use sensible defaults," proceed but flag each assumption inline.

Phase 1 — Lyro: Proactive Roles + Guidance

UI path: Tidio → Lyro AI Agent → Behavior → Proactive Roles (this is the correct feature name).

The user enables Proactive Roles, chooses trigger conditions (pages, timing), and pastes the artifacts you generate. Separately, under Lyro's Guidance, they paste their company/pitch information.

Generate two artifacts:

(a) First message — short and contextual to the page (on a pricing page, reference evaluating the product; not a generic "How can I help?").

Chili Piper Concierge — Edge API Reference

Condensed from Chili Piper's official docs:

• "Using Concierge via the Edge API" — help.chilipiper.com/hc/en-us/articles/30935152032275
• "How do I Schedule Chili Piper Meetings Programmatically?" — help.chilipiper.com/hc/en-us/articles/50860790980627

Prerequisites

• A Concierge router with one of these triggers: Third-party Form is Submitted, Button is clicked in-app, or Router link is clicked / Router link form is submitted.
• An Admin in Chili Piper (only Admins can generate API tokens in Command Center; Workspace Managers cannot access the Credentials page).

Token generation

1. Command Center → Credentials → Generate Token.
2. Select the Concierge.schedule permission. (Add Read under Concierge only if you also need to list routers via API.)
3. Name the token after the router; scope each token to a single router.
4. The token is shown once — copy immediately; it cannot be retrieved later.

Endpoint & auth

Both calls POST to the same base and authenticate with:

Authorization: Bearer <token>
Content-Type: application/json

The router's Booking Page → Custom API tab has a Copy button with the exact URL and a starter request body for the tenant. Field names vary per tenant/trigger — the Custom API tab is the source of truth.

Two access patterns

The Lyro conversational-booking workflow uses the programmatic pattern.

Call 1 — Route lead + get slots