Outbound & webhooks

Sarah watches how people actually shop, then hands those moments to the marketing tools you already run. You keep your sender, your templates, and your deliverability. She just supplies the signal.

The problem

The best moment to follow up with a shopper is the one your store can't see from the order table alone: the cart that stalled, the browser who came back after months, the high-intent visitor who left without buying. Without a feed of those moments, your flows fire on guesses instead of behavior.

How it works

• Five behavioral triggers. Cart abandoned (1-24h), dormant customer (60-365d), welcome back (14-90d), high intent with no purchase (3+ sessions in 14 days, no order), and post-purchase (7 days after the order). You set the windows.
• Fires into your platform. Each trigger posts to your webhook URL, so Klaviyo, Mailchimp, or a custom endpoint runs the actual email or SMS. Sarah supplies the signal; your tools do the sending.
• Throttled and testable. A throttle window (default once per week per visitor) protects shoppers from repeat sends, and a test-fire lets you wire and verify a flow before it goes live.
• A wider event feed. Subscribe to twelve events, including email captured, phone captured, operator requested, sale attributed, session started and ended, human takeover start and end, product clicked, and added to cart.

What makes it real

Every webhook delivery is signed with HMAC-SHA256, so your endpoint can verify the call genuinely came from Cervito before acting on it. Destination URLs pass SSRF-safe validation, so a misconfigured or hostile URL can't be used to reach internal addresses. To be clear: Cervito does not send email or SMS itself. It wires Sarah's signals into the platform you already use.

Pairs with Campaigns and Attribution & proof.