AI email campaigns & win-back autopilot
proHave the copilot draft a branded email campaign to a customer segment, send it only after you confirm, act on a revenue-dip insight in one click, or put win-backs on approval-gated autopilot.
The copilot can help you bring customers back. Describe a goal in plain language — "draft a win-back email for customers we haven't seen in a while" — and it writes a branded campaign, tells you exactly who would receive it, and sends only after you confirm. You can trigger it yourself, act on a proactive insight in one click, or set it on autopilot.
This extends the AI Assistant with two new actions and ties them into proactive insights and automations.
Drafting and sending campaigns is manager-level (or a user granted the email privilege). Like every customer-reaching action, a send is never automatic in chat — the copilot shows a Confirm & send card first.
The two actions
| Action | What it does | Sends? |
|---|---|---|
| Draft email campaign | Writes the campaign, resolves the audience, and shows you a preview + recipient count. | No — preview only. |
| Send email campaign | Sends the branded campaign to the segment, each email with its own unsubscribe link. | Yes — after you confirm (or immediately if you have auto-send). |
Audience segments
You choose who the campaign reaches, from booking history:
| Segment | Who's in it |
|---|---|
| All | Every customer with a real email address |
| Recent | Customers who booked within a recent window (default ~30 days) |
| Lapsed | Customers who have booked before but not recently (default ~90 days) — the classic win-back audience |
Every recipient gets a branded email with their own unsubscribe link, and customers without a real email on file are automatically skipped.
The copilot campaign path is a fast "draft & send" for a focused audience — it is capped at 200 recipients. For larger, scheduled, or multi-step sends (reminders, drip sequences, cross-channel), use Customer Journeys, which handles batching, quiet hours, consent, and frequency caps at scale.
Drafting and sending from chat
- Ask: "draft a win-back email to lapsed customers" (add a tone or offer if you like).
- The copilot writes the subject and body and replies with a preview — the segment, the recipient count, and a few sample names. Nothing has been sent.
- Review and tweak the copy. When you're happy, say "send it".
- The copilot shows a Confirm & send card. Click Confirm to send, or Cancel to discard.
Ask for the draft first, read the recipient count, then send. Seeing "247 lapsed customers" before you commit is the whole point of the two-step flow.
The one-click win-back loop
You don't have to notice the problem yourself. When your weekly revenue drops sharply versus the week before, a proactive insight appears on your dashboard — and its card now carries a Draft email button.
- The revenue-drop insight surfaces automatically (see Proactive insights).
- Click Draft email on the card.
- The copilot opens with the win-back prompt already filled in and drafts the campaign for you to review and send.
That's the full loop — the system spots the dip, explains it, and drafts the fix — with you approving the send. The button appears both on the full AI page and in the floating copilot bubble.
The detector also watches each site individually: when a single location's week falls 20% or more below the week before, a per-site dip insight is flagged automatically — nothing to run or schedule — naming the worst-hit site and carrying the same one-click draft prompt. When a per-site dip fires it replaces the broader organization-wide alert, so the same problem is never flagged twice. (Only sales tied to a site count toward a per-site dip; walk-in sales with no site stay covered by the organization-wide check.)
Win-back autopilot (scheduled)
For hands-off operation, wire a campaign into an automation. The builder includes a ready-made Win-back autopilot suggestion: it watches weekly revenue and, on a dip, runs a win-back campaign to lapsed customers.
- Add the "Send an email campaign" action to any automation. In the builder's Action section, pick Send an email campaign (win-back / promo) and set the subject, body, and segment.
- By default it's approval-gated. When the automation fires, the campaign is staged in the approval queue with a preview — a manager approves it and only then does it send. This is the safe default and mirrors every other outward automation action. The queue confirms every decision on the spot: approving shows "Approved — campaign sent to N customer(s).", rejecting shows "Action rejected — nothing was sent." — so you always know what your click did.
- Autonomy is opt-in. For a truly hands-off autopilot, tick Send autonomously (skip approval) on that automation. It then sends without waiting — but only the campaign action can be made autonomous (never webhooks or one-to-one customer messages), and it stays capped, audited, and pausable.
Turn on Send autonomously only for an automation whose copy and segment you have reviewed and trust to go out unattended. It still respects the 200-recipient cap, records every run, and every recipient keeps their unsubscribe link — but there is no human in the loop at send time. To stop it, pause (deactivate) the automation; that is the kill switch.
Did it work? Campaign outcomes
Sending is only half the loop — the assistant also measures what came back. Every campaign send, whether from chat or an autopilot automation, records exactly who it reached. About two weeks later, the assistant checks how many of those recipients have booked or bought since the send, and how much revenue returned. When customers did come back, a proactive insight surfaces — Your "…" campaign brought N customer(s) back — with the count and the returning revenue, so you can see which subjects, segments, and offers actually work and repeat them.
The attribution is honest by design: it counts customers who returned after the campaign, not provably because of it — a lapsed customer might have come back anyway. Read it as a strong signal, not a controlled experiment.
Kill switch, caps, and audit
- Pause anytime. Deactivating an automation stops it immediately — the kill switch for an autopilot.
- Capped. Every campaign is limited to 200 recipients; bigger audiences belong in Customer Journeys.
- Audited. Every send (manual, approved, or autonomous) is recorded, with who/when for approvals.
- Unsubscribe on every email. Each recipient gets a personal unsubscribe link, respecting the consent ledger.
Why it helps
Lapsed customers are the cheapest revenue you can win back — but only if someone notices and acts. This turns "we should email the people who stopped coming" into a one-line ask, a one-click insight action, or a scheduled autopilot — always inside the same confirm-and-audit guardrails your team already trusts.