Lesson 3 of 7 · 9 min

Form to text in 60 seconds: workflow trigger on form submission

Text every form lead in 60 seconds with a workflow trigger.

Read the lesson

Goal: Build a workflow that texts every new form lead a booking link within a minute. It also gives the team a task to follow up.

You need: Core or above (Launch has manual workflows only). Carrier approval for texting in SMS registration & consent. The client's booking page link. Your before number from lesson 1.

Why this matters

In lesson 1, you measured the gap. At Rivera Heating and Air, a lead sent on a weekday evening waited 14 hours. This lesson closes that gap with one workflow.

Fig 1

Rivera's evening lead, before and after

Before
  • Form sent at 7:00 pm
  • First reply at 9:00 am next day
  • 14 hours of waiting
After
  • Form sent at 7:00 pm
  • Text with booking link by 7:01 pm
  • Customer books or replies at once
The same 7 pm lead, with and without an instant text.

The workflow does not replace the office. It buys time. The customer gets a clear next step in under a minute. They can book online at once, or reply and wait for a person. Either way, they know the business is real and awake.

This is the core build of the 60-Second Response Blueprint. Blueprints are SAU's documented builds. There is no Blueprint button in the app. You rebuild each one with workflows, templates and Build with Emma.

The shape of a good first reply

A good first text does three things. It says who is writing. It gives one clear next step. It lets the customer opt out. It does not try to sell.

Keep it to one SMS segment. One segment holds 160 plain characters. An emoji cuts that to 70 characters. A two-segment text costs twice as much, every time.

Sample text, 155 characters:

Fig 2

The first reply, on the customer's phone

  1. noteWeb form sent at 6:12 pm
  2. Hilltop Plumbing · 6:12 pmHi Sam, thanks for contacting Hilltop Plumbing! Pick a time that works for you here: hilltopplumbing.com/book or reply to this text. Reply STOP to opt out.
  3. Customer · 6:15 pmBooked Thursday morning. Thanks!
One segment, one next step and a way to opt out. No sales pitch.

Count your text before you publish. Paste it into any character counter. Put the first name in with the contact's first-name field, and leave room for long names.

Consent comes first

A form lead asked the business to contact them. That is not always consent to texts. The form needs the right wording next to the phone field.

ServiceAgent writes this wording for you. Go to Settings → Connections & developer tools → SMS registration & consent. The "Get your website ready" step creates a consent line and terms:

  • Opt-in line: "I agree to receive [marketing or non-marketing] text messages from [BUSINESS NAME] about [MESSAGE TYPES]."
  • Terms: "Message and data rates may apply. Consent is not a condition of purchase. Reply STOP to cancel."

Put both on the form before you switch the workflow on. US texting also needs carrier approval first. Check state rules with the client's advisor.

Fig 3

Where the consent wording comes from

Get your website ready

Privacy policy additionGenerated for the website
SMS terms additionRates, consent and STOP wording
Spoken consent scriptFor consent given on the phone
Consent form HTMLThe opt-in line next to the phone field
The app writes the website copy. Check state rules with the client's advisor.

Which forms trigger the workflow

ServiceAgent's Event Trigger has an event called Form Submitted. It fires when a form inside ServiceAgent is sent. Many clients also have an older form on their own website. You have three choices for those:

Form typeHow the lead gets inPlan
ServiceAgent form or booking pageForm Submitted fires directlyCore and up
Outside website formZapier or Make.com creates the contact, then Contact Created firesCore and up
Outside form by webhookWebhook TriggerFranchise only

The builder may show Webhook Trigger on lower plans. The owner ruling is that it is a Franchise feature. Below Franchise, use Zapier, Make.com or a ServiceAgent form.

Fig 4

Getting each form into the workflow

  1. A lead fills in a form
  2. Is it a ServiceAgent form or the booking page?YesForm Submitted fires directlyEnds hereNoCheck the plan
  3. Is the client on Franchise?YesWebhook Trigger can take the form inNoZapier or Make.com creates the contact; Contact Created fires
  4. The form-to-text workflow runs
Below Franchise, outside forms come in by Zapier or Make.com.

Build it in ServiceAgent

  1. Check the plan and the count of active automations. On Core, each switched-on workflow counts as 1 of 10. If 10 are already on, turn one off or move to Growth.
  2. Go to Workflows → Create. Start from the Welcome New Lead recipe, or click Build from scratch.
  3. Name it clearly: "Form lead: text booking link".
  4. Set Trigger Type to Event Trigger. Pick Form Submitted. For an outside form fed by Zapier, pick Contact Created instead.
  5. Click Add step and add a Condition. Check that the phone field is not empty. A Condition reads a field as text, such as contact.phone. Check how an empty field reads in the client's account.
  6. On the yes path, add Send SMS. Paste your text with the booking link.
  7. Add Create CRM Task. Set Title to "Call new web lead", pick an Owner, set a due date and Priority HIGH.
  8. Add Send Notification to the person who handles leads.
  9. On the no path (no phone), add Send Email with the same booking link.
  10. Click Test. The test is a free simulation with sample data. It sends nothing. Read every step.
  11. Click Save draft, then Publish. Nothing sends until you publish.
  12. Check the on/off switch in My Workflows is on.
  13. Send a real test: fill in the form from your own phone. Time the text from the moment you press send.
  14. Send a second test after 9 pm. Messaging defaults has Quiet Hours, 9:00 PM to 8:00 AM by default. Automated texts wait until quiet hours end, so a 10 pm lead gets the text at 8 am. Agree the window with the owner and the advisor.
  15. Open History → View run history and confirm both runs.
Fig 5

The form-to-text workflow

  1. Form SubmittedOr Contact Created for a Zapier form
  2. Condition: is the phone field filled in?YesSend SMS, then Create CRM Task and Send NotificationNoSend Email with the booking link
  3. Publish, then check HistoryView run history shows each run
One trigger, one check, and one clear next step for every lead.

Check it works: both test leads get the text in under a minute, or you know exactly why one waited. The task and the alert reach the right person.

How business size changes the build

  • Owner-operator. One workflow is enough. The task goes to the owner, and the alert goes to their phone. The booking link does most of the work, because they cannot call back from a roof.
  • Fleet. Leads need an owner. Set the task Owner to the lead CSR, not to "everyone". Add an Inbox SLA so a lead that nobody touches creates another task.
  • Multi-location. Each location needs its own booking link and its own sender. Build one copy of the workflow per location. Name each copy with the location, so nobody edits the wrong one.

What "60 seconds" really measures

After go-live, repeat the three tests from lesson 1: weekday, evening and weekend. Use the same form and the same question. Put the new median next to the old one. For Rivera, the target is the evening median moving from 14 hours to under 1 minute. That before-and-after pair goes into the first monthly report.

Credits

Plan for 1 credit per workflow run, plus 2 credits per SMS segment. The task and the alert are internal steps. A run with only internal steps may show no charge. Check Billing → Usage history after the first week for the real figure.

Worked example: Hilltop Plumbing

Hilltop Plumbing has 6 people on Core. You run it agency-managed, billed yearly. Example input: 60 form leads a month.

Credits per lead:

  1. Workflow run: 1 credit
  2. One-segment text: 2 credits
  3. Task and alert: 0 credits (internal steps)
  4. Total: 3 credits per lead

Credits per month: 60 x 3 = 180 credits. Core includes 2,000 credits a month. 180 / 2,000 = 9% of the plan's credits.

Now say the text runs to 170 characters. It becomes 2 segments, or 4 credits. Each lead then costs 1 + 4 = 5 credits. The month costs 60 x 5 = 300 credits. Cutting 10 characters saves 120 credits a month.

Fig 6Example numbers

Hilltop Plumbing credits

Workflow run1
+One-segment text2
+Task and alert (internal steps)0
=Credits per lead3
×Form leads a month60
Credits a month (9% of Core's 2,000)180
At 2 segments, the month costs 300 credits. Keeping one segment saves 120.

Hilltop already runs 9 active automations. This workflow is number 10. That fills Core's limit. Tell the owner now. The next workflow needs one turned off, or a move to Growth.

Common mistakes

  • Forgetting the Core limit. Core allows 10 active automations. Count them before you promise a new one.
  • Texting without consent wording. Put the generated opt-in line and terms on the form first.
  • A text that runs to 2 segments. Count the characters. Remove the emoji. Shorten the link.
  • No path for leads without a phone. Add an email step on the no path, or those leads get nothing.
  • Testing only in daytime. Quiet Hours holds a night text until 8 am. Test after 9 pm and agree the window with the owner.

Do this now

Write the first-reply text for one roster business. Count it: it must be 160 characters or fewer, with no emoji. Then list the 6 workflow steps in order, from the trigger to the email step. Work out the monthly credits at 40 leads a month.

Practice the conversation

  1. Owner We already have a form. Why change it?
  2. Operator You keep the form. We change what happens after someone sends it.
  3. Owner What happens now?
  4. Operator My test lead on Tuesday evening waited 14 hours.
  5. Owner And with this?
  6. Operator The customer gets a text with your booking link in under a minute. Your team gets a task to call them.
  7. Owner Will it spam people?
  8. Operator No. One text, only to people who asked for contact and agreed to texts.
  9. Owner What does it cost me?
  10. Operator About 3 credits a lead. At 60 leads, that is 180 of your 2,000 monthly credits.

Quick check

  1. A Core client already runs 10 active automations. You want to add the form-to-text workflow. What do you tell the owner?
    • Add it anyway, because Core has no limit on active automations
    • Turn one automation off, or move to Growth for unlimited workflows
    • Move down to Launch, which allows more automations than Core does
    • Send the texts by hand, since every workflow costs extra on Core
  2. A client gets 80 form leads a month. Each run sends one 1-segment text. How many credits do you plan for?
    • 80 credits
    • 160 credits
    • 240 credits
    • 400 credits
  3. A Growth client's web form is on its own website, not in ServiceAgent. How do you start the workflow for those leads?
    • Use `Form Submitted`, which fires for any form on the internet
    • Use the `Webhook Trigger`, because it is available on Growth
    • Send the leads in with Zapier or Make.com, then trigger on `Contact Created`
    • Ask the office to copy each lead into ServiceAgent by hand

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community