| name | tidio-slack-takeover |
|---|
| description | Guide the user through setting up high-intent visitor alerts with live rep takeover — a Tidio Flow detects visitors on high-intent pages, Lyro AI qualifies them and collects their details, and Zapier posts an alert with the collected data into a sales Slack channel so a rep can join the live chat. Use this skill whenever the user mentions Slack alerts for website visitors, notifying sales about live chats, rep takeover from an AI agent, connecting Tidio to Slack, or implementing this G2 blueprint — even if they only ask about one piece. Claude cannot click through these platforms for the user; instead, it interviews the user for their specifics (high-intent pages, qualification data, channel and team conventions) and generates every paste-ready artifact — the Flow node chain, the Lyro Action prompt and sequence, and the Zapier configuration — then walks them through where each one goes. |
|---|
Tidio High-Intent Alerts: Flow → Lyro → Zapier → Slack Takeover
The workflow being built:
- A Tidio Flow triggers when a visitor opens a high-intent page, waits ~30 seconds, confirms they're still on the page, and asks via a Decisions node whether they'd like help. On Yes, the Flow ends and Lyro AI (enabled on the project) takes the conversation over seamlessly.
- A Lyro Action collects the visitor's details (name, email, company), writes them to contact properties, and sends the contact to Zapier.
- A Zap (Tidio → Contact Sent From the Bot → Slack → Send Channel Message) posts the alert with the collected data into the sales channel; the rep opens the conversation in Tidio, assigns it to themselves, and joins live.
Important platform facts (verified with Tidio's team — do not contradict these):
- There is no native Tidio–Slack integration; the Slack leg always runs through Zapier, regardless of plan.
- "Time on page" is not a Flow trigger; dwell detection is built from Visitor opens specific page + Delay + Current URL condition.
- A Flow cannot invoke Lyro via a node; the handoff happens by ending the Flow with the Lyro agent enabled.
- The chat widget must be installed on the trigger page.
How to run this session
Work through the phases in order. Interview first, generate second.
Phase 0 — Interview
Collect before generating anything:
- High-intent pages: which URLs signal buying intent (pricing, enterprise, checkout, contact sales)? One Flow per page or a small set — high-traffic pages turn the channel into noise.
- The offer of help: what the Decisions node should ask, phrased for their business ("Want to talk through pricing?", "Need help picking a plan?").
- Qualification data: which fields the Lyro Action must collect (name, email, company are the baseline; add what their sales team needs), and any hard rule (e.g., B2B-only — if no company name, stop and explain).
- Slack setup: which channel (recommend a dedicated one), whether to @here, and the team's claim convention (emoji reaction is simplest) so two reps don't join the same chat.
- Coverage: team working hours, and what happens off-hours — schedule the Flow, or let Lyro carry the conversation unclaimed.
- Accounts check: Tidio with Lyro enabled, a Zapier account, Slack. Zapier is required regardless of Tidio plan.
- Tone: how Lyro and the takeover announcement should sound.
If the user says "just use sensible defaults," proceed but flag each assumption inline.
Phase 1 — The Flow (intent detection)
Generate the node chain for the user to build in Tidio → Flows, per high-intent page:
