Text a ticket acknowledgement back to whoever reported the problem
Anyone who files a help desk ticket gets a text back with the subject they wrote and a reference to quote.
New submission on your help or contact form
Send an SMS auto-reply to the submitter's number acknowledging their request and ticket reference
One-directional. A submission triggers the action — nothing is written back into your form.
An IT help desk gets the same ticket three times when the first one goes unacknowledged. Someone submits, hears nothing, assumes the form ate it, and files it again — or walks over to the desk.
A text back within seconds settles that. It quotes the ticket subject, gives a reference, and states the response window the chosen priority earns. One-person IT departments lean on this hardest, because the acknowledgement has to be automatic when there is nobody free to send it.
Setting it up
- 1
Publish the help desk form and label the phone field clearly for mobiles — a four-digit desk extension cannot receive a text.
- 2
In Zapier, choose formformform and New Submission, then point the trigger at the help desk form.
- 3
Add Twilio Send SMS and pick a From number your staff will recognise as the help desk line rather than a random long code.
- 4
Map Phone or Extension into the Twilio To field.
- 5
Build the acknowledgement from Full Name and Ticket Subject, so the sender can see which of their tickets this is about.
- 6
Add the submission ID from the trigger step as the ticket reference — the form does not generate one of its own.
- 7
Use a Zapier Paths step on Priority to pick the response-time sentence, one branch per priority level, so the copy stays honest.
- 8
File a test ticket from your own mobile, check the reference matches the submission in formformform, then enable the Zap.
What maps where
Using the IT Help Desk Ticket as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Twilio |
|---|---|
| Phone or Extension | The Twilio To number for the acknowledgement |
| Full Name | Greeting at the top of the SMS |
| Ticket Subject | Quoted back so the sender knows which ticket was received |
| Priority | Chooses which response-time wording the message uses |
| Issue Type | A Zapier Filter condition deciding whether an SMS goes out at all |
Variations worth knowing
Swap Send SMS for Make Call and let Twilio read the acknowledgement aloud. It suits shop-floor and warehouse staff who report faults from a handset they never text on, and it works for anyone who finds a spoken confirmation easier to take in.
Add a second Twilio action after the acknowledgement, aimed at the rota mobile, carrying Ticket Subject and Affected Device or System. Put a Zapier Filter on Priority in front of it so only the tickets that warrant an interruption cause one.
If something isn't arriving
Phone or Extension accepts both, and Twilio cannot text a four-digit extension. Add a Zapier Filter that continues only when the value has at least ten digits, or split the form field into separate extension and mobile fields and map the mobile.
The reference comes from the formformform submission, not from your ticketing system, so the two are unrelated by design. If the same Zap also creates the ticket downstream, move the Twilio step after it and map that tool's ID instead.
Frequently asked questions
What can I use as a ticket number when the form does not have one?
Use the submission ID that the New Submission trigger returns. It is unique per submission and already available in the Zap. If you want something readable on a phone screen, prefix it in the message body so it arrives as TICKET-xxxx rather than a bare string.
Can people reply to the acknowledgement with more detail?
Their reply reaches your Twilio number and stops there. Nothing is written back into the form or attached to the original submission. Tell them to reply to the confirmation email or file an update instead, and keep the SMS strictly one-way.
Does this work on a customer contact form as well?
Yes, provided the form collects a mobile number. Swap the trigger form in the Zap and remap the phone field; the Twilio action is unchanged. Customer-facing copy usually needs softening, since the reader is a buyer rather than a colleague.
Related automations
- Call the on-call engineer when an urgent report comes in
A high-priority maintenance report rings the on-call engineer and reads out the location, category and issue.
- Text an appointment confirmation the moment someone books
A submitted appointment request triggers a text confirming the service, date and time before the client closes the tab.
- Text registrants the venue details straight after they sign up
New registrants receive the door, start time and check-in link by text within seconds of submitting the form.
- Text the assigned rep the moment a demo request lands
Every demo request buzzes the assigned rep's phone with the lead's name, company and the problem they described.
- Text the buyer and the packing bench when an order comes in
One submission sends the buyer a confirmation text and the packing bench a separate message with the picking details.
- Alert a recruiter to every new application
The recruiter gets a nudge for every applicant, with enough to decide who to call first.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free