Automations that start from what already happens in Sundial.
An automation can start from any event, then send a message, wait, check a condition, place a call, move the deal or hand work to a team. Every send goes through the same consent, calling-hour and plan checks as one a person makes.
Trigger events, or a time of day.
An automation starts from an event in the CRM, or on a daily schedule at a local hour. Each event can be narrowed with filters.
Deals
Stage changes, disposition set, or a value changed. Filter by engagement type and target stage.
Conversations
Inbound SMS, WhatsApp or email received. Filter by channel.
Leads and work
Lead accepted. A work item completed: a voicemail, callback, follow-up, task, web chat handoff or inbound email. Filter by status.
Appointments and follow-ups
Appointment requested, scheduled, confirmed, kept, missed or canceled. A follow-up coming due in a chosen number of days.
Steps run in order.
A call or a human task pauses the run until it finishes; a condition either continues or ends it.
Send email
Subject and body with tokens from the customer, deal, quote or appointment. Send from the org default, a verified domain or a shared inbox. Replies thread back to the deal. Optionally send at the recipient's local time.
Send SMS
Body with tokens, a from-number and a consent purpose.
Send WhatsApp
Approved templates only. Consent required.
Call: AI agent or person
An AI agent places the call with an objective and talking points, inside TCPA calling hours. Or the call goes to a team's queue as a task, and the run waits until a rep completes it.
Delay
Minutes, hours or days.
Condition
Check the deal's status, stage, value, probability or expected close date. If it fails, the run ends and the history says why.
Action
Move the deal, assign a person or team, request an appointment or call a webhook.
Every automated send is checked the same way a person's is.
Consent
Each send names a purpose and checks the person's consent for that channel and purpose before going out.
Calling hours and limits
AI calls respect TCPA calling hours in the customer's time zone and the optional daily per-contact cap. Emergency suspension stops SMS and calls at once.
Plan limits
Email, SMS, WhatsApp and AI usage are metered.
Run history
Every run lists its trigger, its contact and deal, and each step's outcome: sent, skipped with a reason, waiting, or failed.
Build on a canvas, check with a dry run.
A trigger at the top, steps beneath, drag to reorder. The side panel edits the selected step with token autocomplete and shows the consent policy that applies. A sentence at the top reads the whole automation back to you.
- Dry run against a real contact or deal: which steps would run, which tokens are unresolved, whether consent would block
- Run history with each step's reason and the message or call it produced
- Enable or disable from the list or the builder
Automations teams run today.
Text within seconds, then put a call in the queue.
Send an SMS from the sales line, wait 15 minutes, send an email with the details, then assign a call to the Sales team. The automation waits until a rep completes it.
Confirm by AI call the next day, if the deal is still there.
Wait a day, check that the deal is still open and still on that stage, then have an AI agent call to confirm. Skipped automatically outside calling hours or without consent.
Thank the customer and schedule the follow-up.
Send a thank-you email from your domain, create a delivery follow-up due in seven days, and post the deal to your data warehouse.
Offer to rebook, then put it in the scheduling tray.
Send a WhatsApp template, wait two hours, then request a new appointment for the scheduling team.
Text the caller back at 9:00 their time.
If the result was "Left message", send an SMS at 9:00 in the customer's time zone.
Fall back to a text.
Wait 10 minutes and send the same message as an SMS.
Campaigns run on the same engine.
Campaigns run on the same engine: the same send steps, consent checks, tokens and usage limits.