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.
New submission on your demo or quote request form
Send an SMS to the assigned rep's phone with the lead's name, company and message
One-directional. A submission triggers the action — nothing is written back into your form.
Demo requests go cold fast. A rep watching a shared inbox sees the form fill twenty minutes late, and by then the buyer has opened two other tabs. A text lands on the phone already in their hand.
Small sales teams reach for this when there is no rota and no CRM alerting worth the name. The message carries enough to decide — first name, company, job title and the buyer's own description of the problem — so the rep can ring back from the car park instead of returning to a desk first.
Setting it up
- 1
Publish the demo request form and keep What problem are you trying to solve? on it — that free-text answer is what makes the alert worth reading on a small screen.
- 2
In Zapier, choose formformform and the New Submission event, then select the demo request form as the source.
- 3
Add the Twilio Send SMS action and connect the Twilio account that owns your outbound number.
- 4
Hard-code the rep's mobile in the Twilio To field. It does not come from the form — the form's Phone Number belongs to the lead.
- 5
Build the body from First Name, Company and Job Title, then append the problem answer so the rep hears the buyer's own framing.
- 6
Finish the message with the lead's Phone Number so it is tappable straight from the alert.
- 7
Add a Zapier Filter on Company Size or When are you looking to implement? if only some leads deserve to interrupt someone.
- 8
Run a test submission, confirm the rep's handset shows the whole alert without truncation, then switch the Zap on.
What maps where
Using the Demo Request Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Twilio |
|---|---|
| First Name | Opening of the alert SMS body |
| Company | Named in the alert so the rep can pull up the account |
| Job Title | Alert body — tells the rep who they are about to ring |
| What problem are you trying to solve? | The lead's own words, trimmed into the alert |
| When are you looking to implement? | A Zapier Filter condition deciding whether the SMS fires |
| Phone Number | Tail of the alert, as a tap-to-dial callback number |
Variations worth knowing
Add a Zapier Paths step on Company Size with a Twilio action on each branch. Enterprise enquiries go to the senior rep's mobile, everything under fifty seats goes to whoever is covering inbound that week. Same trigger, two numbers, no shared inbox.
Add a second Twilio Send SMS action in the same Zap, this time mapping the form's Phone Number into To. A short line saying someone will call within the hour buys the rep time and stops the buyer filling in a competitor's form next.
If something isn't arriving
Zapier sends an empty string when an optional field is skipped or conditional logic hid it. Make What problem are you trying to solve? required on the form, or add a Zapier Formatter default so the alert reads no detail given rather than trailing off.
That happens when the Twilio action points at a Messaging Service with a number pool rather than a single number. Pick one specific From number in the Zap so the rep's phone threads every alert under the same contact.
Frequently asked questions
How fast does the rep actually get the text?
The New Submission trigger is real time, so the Zap starts as the form posts rather than waiting for a polling window. In practice the alert reaches the handset within seconds; Zapier's task queue and carrier delivery add the rest.
Can the rep just reply to the alert to reach the lead?
No. A reply goes back to your Twilio number, not to the buyer, and nothing returns to the form. That is why the lead's number sits at the end of the message body — one tap dials the buyer directly from the alert.
Do I need a CRM for this to work?
No. The Zap reads the submission from formformform and hands it to Twilio, with nothing in between. A CRM is worth adding later as a second action in the same Zap, but the text alert stands on its own from the first day.
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 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.
- 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 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