Push support requests to the on-call agent
The on-call agent gets each request as a chat instead of watching a shared inbox.
New Submission on your contact or support form
Send a WhatsApp message to the support number with the subject, the message and how to reach the customer
One-directional. A submission triggers the action — nothing is written back into your form.
A shared support inbox works during office hours and fails outside them. Nobody refreshes it at 9pm, and the requests that arrive then are disproportionately the urgent ones.
Sending each submission to the on-call number turns triage into something someone can do from a sofa: read the subject, decide whether it waits until morning, and reply directly if it does not.
Setting it up
- 1
Publish the Contact Form template and make Subject a dropdown rather than free text, so the first line of every WhatsApp message is a category you can triage on.
- 2
In Zapier, add formformform's "New Submission" trigger and pick your support form.
- 3
Add WhatsApp Notifications by Zapier and choose Send Message, with your on-call number as the recipient.
- 4
Put Subject first in the message body — it is what shows in the lock-screen preview, and it is what decides whether the agent opens it now.
- 5
Map Email Address and Phone Number next so replying does not require opening a laptop.
- 6
Test with a submission that mimics an out-of-hours emergency, and confirm the preview alone is enough to make the call.
What maps where
Using the Contact Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | |
|---|---|
| Subject | First line of the message body — drives the notification preview |
| Full Name | Message body, second line |
| Email Address | Message body, for replying by mail |
| Phone Number | Message body, tappable to call |
| Message | Message body, the request itself |
Variations worth knowing
Add a priority dropdown to the form and filter the Zap on it. Everything still lands in your responses view; only the urgent subset becomes a WhatsApp message.
Use a Zapier lookup table keyed on the day of the week to pick the recipient number, so the message follows whoever is actually on call.
If something isn't arriving
Filter rather than firehose. A Zapier filter step on your priority or subject field keeps the noise in the responses view and the interruptions on the phone.
WhatsApp truncates long bodies in the preview. Put Subject and contact details before Message so nothing actionable is below the fold, and keep the full text in formformform.
Frequently asked questions
Can the agent close the ticket from WhatsApp?
No. The integration sends a message out; it does not read anything back. Resolving the request still happens wherever you track support, and the submission stays in your responses view.
Can customers attach a screenshot?
Yes — add an upload field and they attach it directly, up to 2 MB per file, which is plenty for a screenshot. The Zap can pass the file's link through to the WhatsApp message.
Does this work with a personal WhatsApp number?
Messaging your own team's number through WhatsApp Notifications by Zapier does. Messaging customers requires a WhatsApp Business account and an approved template.
Related automations
- Alert a recruiter to every new application
The recruiter gets a nudge for every applicant, with enough to decide who to call first.
- Confirm an order in the customer's WhatsApp
The buyer gets an instant order confirmation in the app they already have open.
- Confirm appointments in the booker's chat
The booker gets the date, time and service in a message they can find again later.
- Send new quote requests to your sales WhatsApp
Every quote request arrives as a WhatsApp message your rep can reply to from their phone.
- Send RSVP confirmations to guests
Guests get their RSVP details and the venue address in a thread they can find again.
- Broadcast every new order to a channel
New orders post to your orders channel with the product, quantity and buyer details, so packing can start straight away.
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