Automate with conditional actions

Conditional logic that reacts to what each visitor actually says

The difference between a chat that captures leads and a chat that converts them is what happens after a response. A static form fires the same auto-responder to every submission, sends every lead into the same pipeline, and treats a $5k buyer identically to a tyre-kicker. Ryvet’s actions engine turns every answer into a branching decision point — redirect this visitor to the enterprise page, send that one to a self-serve tier, ping the on-call mobile when an emergency keyword is detected — without writing a single line of code.

Each rule is built as a simple when this condition is met, do this action pairing. Conditions can chain (budget > $5k AND timeline within 30 days), nest (apply only when the visitor is on a specific page), and reference any field the chat has collected. Actions stack: a single qualifying answer can simultaneously redirect the visitor, notify a sales rep, fire a Google Ads conversion, and tag the lead in your CRM. Every action runs server-side the moment the answer is given, so workflows happen in real time — not on a delayed batch sync.

Real-time lead routing and email alerts

The fastest way to lose a hot lead is to make them wait for a callback. Ryvet’s email-alert action fires the instant a conditional rule matches — typically within 200ms of the visitor selecting an answer — sending a fully-formatted lead notification to the right person on your team. Different conditions can route to different inboxes: enterprise budget leads go to your founder’s mobile, support requests go to the support queue, and out-of-area requests go to your referral partner.

Alerts include the full conversation transcript, captured fields, and (where configured) calculated values like quote estimates or risk scores. Most customers see the median time-to-first-touch drop from 4-6 hours under the old contact-form workflow to under 5 minutes once real-time alerting is in place, with corresponding lifts in lead-to-meeting conversion of 30-50%.

Conversion tracking for Google Ads, Facebook, and LinkedIn

Most chat tools fire a generic “conversation started” event into your ad platforms, which is useless for optimisation — the algorithm rewards visitors who open the chat, not visitors who actually become leads. Ryvet’s conditional conversion-tracking actions fire pixel events only when a visitor meets your real qualification criteria: budget bracket selected, timeline confirmed, demo booked. Google Ads, Meta, and LinkedIn now optimise toward genuinely qualified leads instead of vanity clicks.

Enhanced Conversions for Google Ads is supported natively — captured email and phone are passed back hashed for offline-conversion matching, so your campaigns get credit for leads that close weeks later. Server-side Conversion API is supported for Meta to bypass iOS 14+ tracking restrictions. Setup takes a single tag drop plus mapping which conditions count as which conversion event.

Group assignments and CRM sync

Tagging and segmentation usually happen after the lead lands in your CRM — by which point a sales rep has either already followed up incorrectly or is waiting on a manual classification step. Ryvet’s group-assignment action handles segmentation inside the conversation: a visitor who indicates “enterprise” gets tagged Enterprise the moment they say so, routed to the right pipeline stage, and assigned to the right rep before they even see the “thanks, we’ll be in touch” message. Native integrations with HubSpot, Salesforce, Pipedrive, and ActiveCampaign push these tags through automatically; webhook support covers anything else with an API.