Sales Blueprint
Safety checkedQualify inbound leads, book meetings, and auto-generate pre-call notes
Automatically qualify inbound prospects through conversational AI and book confirmed meetings without manual intervention. Your sales team receives AI-generated pre-call notes with company intel and product fit recommendations, cutting preparation time and improving win rates.
3 Files Included
SKILL.md
10 KB
chilipiper-edge-api.md
4 KB
What problem does this solve?
Revenue teams need to identify quality leads and understand who they are before their sales calls. Using Tidio's AI to automatically qualify inbound website visitors and filter for fit before they book a call saves time and ensures sales conversations focus on the right prospects. After that, the sales team gets detailed insights about their upcoming calls which speeds up preparation time, helps with the pitch, and increases win rates.
How does it work?
Engage website traffic 24/7 with a proactive AI conversation using Lyro AI, hosted in Tidio. Qualified leads book their own meeting directly into Chili Piper through a conversational interface (no manual scheduling required). Chili Piper connects via API to Tidio. When a meeting is booked, an automation triggers a notification in Slack. Hubi AI picks up that notification, researches the prospect against your pitch, and delivers detailed pre-call notes to the sales rep with company information and product fit recommendations.
What's the biggest win?
Reps walk into every call prepared without spending time on research, improving win rates while freeing capacity to take more inbound calls.
What's required to run this?
- Lyro AI
- install it through Tidio or standalone, on a specific page like your Contact Sales page or your entire website.
- Go to Lyro → Behavior → Proactive Roles. Choose when Lyro should start the conversation, craft the first message, and provide clear guidance on how the conversation should be handled with a focus on qualifying your leads and pushing for a booked call. Use your qualification rules in Lyro's guidance and instruct the AI to only allow booking if criteria are met.
- Chili Piper - Using Concierge via the Edge API
- Connect Lyro via Actions to the Chili Piper Edge API. One call pulls available slots, a second pushes the booking, so the whole scheduling flow happens inside the chat, conversationally.
- Slack
- A standard notification from Chili Piper to Slack shows the booked events.
- Hubi AI
- Hubi AI can join Slack channels and read the notification; email or website information can be the trigger for Hubi AI to research information about the lead.
- Hubi AI can ingest information about your product and pitch and match it against the lead that booked the call.
- A message will be sent in the Slack thread with the information the sales agent needs before the call.
What are the constraints?
This is an advanced integration that requires set-up in multiple platforms. No coding required beyond a single API configuration. Tidio's support team can help with information needed on any of the steps.
Tools in this Blueprint
About This Blueprint
- Industry
- Computer Software
More Blueprints to explore
Review Recency Insights
Cut the manual digging time from 15–30 minutes down to seconds by asking a simple question and getting back a complete diagnosis of why a product's recency score lags and exactly how many reviews the team needs by when to hit the next tier. A single 12-month snapshot shows targets, actuals, and the coaching recommendation to close the gap.
Nikita Bakodiya
Data Analyst
Automate Webinar Repurposing Into Multi-Channel Content
Extract sourced claims and quotable moments from webinar transcripts, then route verified materials to specialists who create optimized assets for blogs, social, video, and sales enablement on staggered schedules. Skip repurposing work that lacks supporting data, and measure each asset's performance back to the original webinar arguments.
Generate Shipped Changelog From Sprint Tasks
Ship customer-facing changelogs with confidence by automatically verifying that completed sprint tasks actually merged to your release branch, deduplicating related changes, and rewriting them in plain language. Your PM reviews only what truly shipped before publishing.