Book qualified sales meetings directly in chat

Let an AI agent qualify website visitors in conversation and schedule confirmed meetings on your reps' calendars. Visitors go from first question to booked call in a single chat.

Tidio's Lyro AI qualifies the visitor while they're still on the site and, if they fit, offers real calendar slots inside the same conversation. Unqualified visitors get routed to self-serve resources instead of your reps' calendars.

Lyro AI proactively opens a conversation with website visitors on the pages you choose, asks your qualification questions naturally, and answers product questions along the way. When a visitor meets your criteria, Lyro calls Chili Piper's Edge API through two Lyro Actions running in sequence: the first routes the lead and pulls available time slots, the visitor picks one in the chat, and the second confirms the booking. Calendar invites go out to both sides instantly. The visitor never leaves the conversation.

Qualified buyers book while intent is at its peak, mid-conversation, on your site, instead of dropping off between a form and a calendar link. Reps get meetings that were pre-screened against your criteria, with zero scheduling effort.

Tidio (Lyro AI)

• Deploy Lyro on your entire site or high-intent pages such as Pricing or Contact Sales.

• Under Lyro → Behavior → Proactive Roles, enable proactive engagement, set the opening message, and write guidance that asks your qualification questions and only offers booking when the criteria are met. Add your company and product information under Guidance so Lyro can handle questions during the conversation.

• Lyro should always collect the visitor's email and first name before booking: Chili Piper needs both.

Chili Piper (Concierge via the Edge API)

• Requires a Concierge router with a configured trigger and an Admin to generate an API token (Command Center → Credentials, permission: Concierge.schedule). The token is shown once — copy it immediately.

• In Lyro → Behavior → Actions, create two Actions that Lyro calls in sequence during the conversation.

• Action 1 — get available slots. Triggered once the visitor is qualified and ready to book. POSTs to https://fire.chilipiper.com/api/fire-edge/v1/org/concierge/routers/{routerSlug}/rest with the visitor's details (form) and a time window (interval). Save the returned schedulingData.startTimes and routeId as output variables — Lyro presents the slots in chat and reuses routeId in the next step.

• Action 2 — confirm the booking. Triggered once the visitor picks a slot. POSTs the chosen startTime to https://fire.chilipiper.com/api/fire-edge/v1/org/concierge/routing/{routingId}/schedule-simple, with the saved routeId as the routingId path parameter. Calendar invites go out immediately. Enable visitor confirmation on this Action, since it creates a real calendar event.

• The router's Custom API tab shows your exact slug and lets you confirm these field names against your own tenant before wiring anything up.

Setup spans two platforms and one API configuration; no coding beyond that. Booking sessions in Chili Piper are single-use and time-limited, so if a visitor takes long to choose a slot or the booking call fails, Lyro should re-run Action 1 for a fresh routeId and updated slots. Slot times are returned in UTC; present local times to the visitor, but submit the UTC value unchanged. Field names in the API request depend on your Chili Piper router configuration; use the Custom API tab as the reference. Tidio's support team can assist with any step.