CRM automations and nurture
What this covers: All CRM automation wizards — follow-ups, at-risk escalation, deposit confirmation, re-booking, and event capture. CRM automations handle the repetitive work: nudging quoted customers, flagging stalled deals, confirming bookings when a deposit arrives, and inviting last year's customers to re-book. Each wizard lives under Automations → New Automation → CRM.
CRM automation wizards
Quoted follow-up
When to use: You've sent a quote and want an automatic nudge if the customer hasn't responded.
How it works:
- Deal enters Quoted.
- Wait N days (default: 3).
- Check the deal is still Quoted.
- Send an SMS and/or email follow-up.
Setup: Automations → New Automation → Quoted Follow-up → choose delay and message channel → Activate.
Tentative reminder
When to use: A deal is tentatively interested but hasn't committed. Send a reminder before it goes cold.
Same flow as Quoted Follow-up, but watches the Tentative stage instead.
Flag stalled quotes as at risk
When to use: Quotes that sit too long need to stand out on the board — without anyone having to check manually.
How it works:
- Deal enters Quoted.
- Wait N days (default: 14; options from 3 to 21).
- If still Quoted, move to At Risk.
No message is sent. This is a visual escalation on the Kanban board so your team knows to follow up.
Requirement: Your pipeline must include the At Risk stage. If you've customized stages and removed At Risk, this wizard won't appear.
Deposit confirms deal
When to use: When a customer pays a deposit, you want their deal moved to Confirmed automatically.
How it works:
- An order or deposit is completed.
- The order includes a matching product (you pick which product counts as a deposit).
- If the contact has an open deal, it moves to Confirmed.
Deals already Confirmed, Won, or Lost are left alone. If the contact has no open deal, nothing happens.
Requirement: Your account needs the Orders add-on, and your pipeline must include the Confirmed stage.
Invite last year's customers to re-book
When to use: Annual events — birthday parties, corporate outings, school field trips that book once a year.
How it works:
- Runs weekly.
- Finds contacts whose deal closed Won about 11 months ago (configurable).
- Creates a new deal in your chosen starting stage.
- Skips contacts who already have an open deal.
The 11-month default gives you a month of runway before the anniversary of the event.
Stamp event journey entry point
When to use: Fundraisers, group events, or any campaign where you want to track which touchpoint brought someone in.
How it works:
- Someone arrives via form, text chat, or SMS (including QR code text-ins).
- The automation stamps three fields on the contact:
- Entry point — Form, Text Chat, or SMS
- Entry timestamp — when they arrived
- Campaign name — the event or fundraiser name you configure
One automation per campaign. Run it for the duration of a fundraiser, then deactivate it. The campaign name is what separates one QR code from the next in reporting.
Different outreach by event type
When to use: Birthday inquiries and corporate inquiries need different messaging.
How it works:
- A contact's Event Type is updated.
- The automation branches by type — each type gets its own SMS and/or email message.
Pick which event types get branches during setup. You can add more branches on the canvas afterward.
Default event types: Birthday, Corporate Event, Fundraiser, Field Trip, Team Party, Holiday Party, Bachelor / Bachelorette, Reunion, Other.
General tips
Do
- Start with Add Inbound Enquiries To The Pipeline — it's the foundation everything else builds on.
- Leave duplicate suppression on for auto-created deals.
- Test automations with a test contact before going live.
- Use Quoted Follow-up and At Risk together — nudge first, escalate later.
Don't
- Turn off duplicate suppression unless you understand the consequences (one deal per message).
- Run multiple "stamp entry point" automations for the same campaign simultaneously.
- Expect deposit confirmation to work without the Orders add-on.
Troubleshooting
|
What you see |
What to try |
|---|---|
|
Wizard not in the list |
Check CRM (and Orders, for deposit wizard) is enabled; some wizards require specific pipeline stages |
|
Follow-up sent but deal already moved |
The automation re-checks the stage before sending — if the deal moved, the message is skipped |
|
Deposit didn't confirm the deal |
Confirm the order product matches your wizard's deposit product; check the contact has an open deal |
|
Re-booking created duplicate deals |
Duplicate suppression should prevent this — check the contact didn't have multiple closed-won deals |