Triggers, conditions, actions and delays
Learn the four parts of every workflow: triggers, conditions, actions and delays.
Read the lesson
Goal: Build a workflow from scratch with the right trigger, a guard Condition, clear actions and sensible delays.
You need: Core, Growth or Franchise. Launch runs manual workflows only. SA 101 lesson 5.
Why this matters
Workflows are how one Operator does the work of several office roles. A good workflow sends the right message to the right person at the right time, every time. A careless one texts the wrong people. It may thank staff for their business or text a test contact twice. Owners forgive a slow office. They do not forgive a machine that embarrasses them.
Every workflow has the same four parts. Learn them once and every other lesson in this course builds on them.
- A trigger starts the run.
- A condition decides who goes on.
- Actions do the work.
- Delays set the timing.
The four parts of every workflow
- 1TriggerThe event that starts one run
- 2ConditionA gate that decides who goes on
- 3ActionsSteps that do the work
- 4DelaysSteps that set the timing
The four parts in plain words
The trigger is the event that starts one run. Open Trigger Type and you see 8 choices.
Manual Trigger: you start it by hand.Scheduled Trigger: it runs on an interval or a cron schedule, such as every Monday at 7 AM.Event Trigger: it runs when something happens in the account.Webhook Trigger: an outside system starts it. This is a Franchise feature.Call Ended: it runs after a call ends.Survey Completed,Low Score ReceivedandHigh Score Received: they run on survey results.
The 8 choices in Trigger Type
Trigger Type
The Event Trigger list covers the daily work of a service business. The events are:
- Contact Created and Contact Updated
- Deal Created, Deal Updated and Deal Status Changed
- Appointment Scheduled and Appointment Completed
- Task Completed, Form Submitted and Ticket Created
- Inbox Message Received
Appointment Completed is the "job is done" trigger. Templates also use Call missed for missed-call text-back.
The condition is a gate. A Condition step reads a field and compares it with a value. You type the field as text, for example contact.email. The compare options are Equals, Not equals, Contains, Greater than and Less than. A trigger with no condition fires for every record that matches the event. That includes staff, test contacts and vendors.
Actions are the steps that do something. Add step offers 30 steps in groups. The common ones are:
Send SMS,Send EmailandSend NotificationCreate CRM TaskandUpdate ContactUpdate Deal StageandSend Survey
Delays wait for a set time. A Delay step waits for time only. It cannot wait for a reply. There is no "wait until they answer" step.
Choosing the right trigger
Pick the trigger that matches the moment the customer cares about. A thank-you belongs after the job, so use Appointment Completed, not Appointment Scheduled. A welcome text belongs when a lead arrives, so use Contact Created or Form Submitted. A follow-up on a quote belongs when the deal moves, so use Deal Status Changed.
Ask two questions before you choose.
- Does this event happen once per customer, or many times? Contact Updated fires every time anyone edits a contact. A text on that trigger can go out many times a day. Use it only with a strong
Condition. - Does staff action start it?
Appointment Completedonly fires when a tech or the office marks the job done. If the team forgets, nothing sends. Train the team before you rely on it.
Size changes the answer. An owner-operator often marks jobs done at night in one batch. Many runs then start at once, late in the evening. A fleet of 20 techs marks jobs done all day, so runs spread out. A multi-location client needs each location's workflows checked in Working in before you publish.
Use Scheduled Trigger for work that should happen on a clock, not on an event. Examples are a Monday task list for the office or a weekly check for old quotes. A cron schedule such as "every Monday at 7 AM" is easy to read later.
Three limits you must design around
The builder has no stop rule, no exit rule and no goal rule. Once a run starts, it keeps going to the end unless a Condition stops it. So put a Condition before each message. Check that the message still makes sense. For example, before a day 3 reminder, check that the customer has not already booked.
There is no date-field trigger. You cannot start a run "30 days before the contract end date." Use a Scheduled Trigger that runs daily or weekly and a Condition that picks the right contacts.
Keep sequences short. A 3-step sequence with checks is safer than a 9-step sequence without them.
Three things the builder cannot do
- A stop, exit or goal rule
- A step that waits for a reply
- A trigger on a date field
- A Condition before each message
- A Delay, then a Condition that checks the status
- A daily Scheduled Trigger and a Condition
Credits and plan limits
Plan for 1 credit for each run, plus the cost of what it sends. An SMS segment is 2 credits. An email is 0.5. An AI follow-up is 1. A run with only internal steps, such as a task, may show no charge. Check Billing → Usage history for the real number after the first week.
On Core, each workflow that is switched on counts as 1 of 10 active automations. Growth and Franchise have no limit. Launch runs manual workflows only.
Build it in ServiceAgent
This build sends a thank-you text 2 hours after each finished job.
- Open
Workflows→Create→Build from scratch. Name it "Post-job thank-you." - Set
Trigger TypetoEvent Triggerand the event toAppointment Completed. Add step→Condition. Set the field tocontact.email. Set Not equals to your test address.- Add a second
Conditionthat skips staff. For example, skip contacts whose email contains the business's own domain. Add step→Delay. Set 2 hours.Add step→Send SMS. Write under 160 plain characters, so it stays 1 segment. Leave out emoji.- Click
Save draft. Every new workflow is a draft. Nothing sends until you publish. - Click
Test. The builder runs a simulation with sample data. It sends nothing and is free. - Read the
Summarytab. Check the trigger, both conditions, the delay and the text. - Click
Publish. Then find it inMy Workflowsand check the switch is on. - Check it works: complete one test appointment for your own contact. Confirm the run in
History→View run history.
The post-job thank-you, step by step
- Appointment Completed firesA tech or the office marks the job done
- Is it your test contact?YesStop. No text goes outEnds hereNoGo on to the next gate
- Is it a staff member?YesStop. No text goes outEnds hereNoGo on to the delay
- Delay 2 hours
- Send SMS thank-youUnder 160 plain characters, no emoji
Quiet Hours default to 9 PM to 8 AM in Messaging defaults. Test how they hold workflow texts in the client's account. Then you can tell the owner when late texts go out.
Worked example: Hilltop Plumbing
Hilltop Plumbing has 6 people on Core. Your agency runs the account and bills Hilltop yearly. Hilltop finishes about 90 jobs a month. Each run sends one 1-segment text.
The thank-you text Hilltop's customers get
- noteJob marked done at 3:10 pm
- Hilltop Plumbing · 5:10 pmThanks for choosing Hilltop Plumbing today. Any questions about the job? Reply here and we will help.
- Customer · 5:14 pmAll good, thanks. The new valve works fine.
- Credits per run: 1 for the run + 2 for the text = 3.
- Credits per month: 90 × 3 = 270.
- Core includes 2,000 credits a month, so this workflow uses 13.5% of them.
Check the count first. Core allows 10 active workflows. Hilltop ran 9 before the speed-to-lead build, and that build made 10 (Speed-to-Lead lesson 3). So this one would be number 11. Before you publish, agree with the owner to switch off a weaker workflow, or plan the move to Growth. On day 1, a first draft without conditions would have texted the 2 office staff and your test contact. The two conditions stop that. The owner never sees a thank-you sent to their own office.
Hilltop credits per month
Common mistakes
- Mistake: No
Conditionbefore the first action. Fix: Add gates for test contacts, staff and anyone who should not get it. - Mistake: Expecting a
Delayto wait for a reply. Fix: Use aConditionafter the delay to check the current status. - Mistake: Long texts with emoji. Fix: Keep under 160 plain characters. An emoji cuts a segment to 70 characters.
- Mistake: Forgetting the draft state. Fix: Click
Publishand check the switch inMy Workflows. - Mistake: Building 12 small workflows on Core. Fix: Combine related steps, or plan the move to Growth.
Before you publish
- Trigger is the right event
- A Condition skips test contacts and staff
- Texts are under 160 plain characters
- Test passed and the Summary tab reads right
- Publish clicked and the switch is on
Do this now
Build the post-job thank-you in your practice account. Add both conditions. Run Test, read the Summary tab, then Publish. Deliverable: a published workflow and a one-line credit estimate for a client with 60 jobs a month. Time: 25 minutes.
Practice the conversation
- Owner Can it text every customer after the job?
- Operator Yes. Two hours after the tech marks it done.
- Owner What if the job runs late at night?
- Operator The account has quiet hours from 9 PM to 8 AM. I test how they handle late texts before we go live.
- Owner Will my office staff get texts too?
- Operator No. I add a check that skips staff and test contacts.
- Owner What does it cost me?
- Operator About 3 credits a job. For 90 jobs, that is 270 a month.
- Owner Out of the 2,000 I get?
- Operator Yes. Plenty left for calls and reminders.
Quick check
- A new workflow sends a thank-you text on every booking. On day 1, it also texted 4 test contacts and 2 staff members. What did it miss?
- A `Condition` before the first action, to skip contacts who should not get it
- A longer delay before the text
- A second trigger
- An AI step that reads each booking
- A client finishes 120 jobs a month. Each run sends one 1-segment text. About how many credits does the workflow use a month?
- 120
- 240
- 360
- 480
- You want a reminder to stop if the customer already booked. What do you build?
- A wait-for-reply step
- A goal rule on the workflow
- A `Condition` before the reminder that checks the booking status
- A longer `Delay`
ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.