Send rush orders straight to the lead on shift
Orders marked rush go out as a private chat to the fulfilment lead, with the job details, rather than waiting in a busy channel.
New submission on your order form marked "rush"
Send a chat message to the fulfilment lead with the order details
One-directional. A submission triggers the action — nothing is written back into your form.
A busy channel is the wrong place for something that has to move in the next hour. This flow reads the urgency answer on your order form and, when it comes back as rush, sends the whole order as a direct Teams chat to whoever is covering fulfilment that day.
Dispatchers, service coordinators and small operations teams run it this way. Ordinary orders keep flowing to the board or channel they already use, and only the rush ones interrupt a person.
Setting it up
- 1
Publish your order form from the Work Order Form template. Its Urgency question is the switch this whole flow turns on, so keep it required.
- 2
In Zapier, add formformform's New Submission trigger for that order form, then add a Filter step that only continues when Urgency is the rush option.
- 3
Add the Microsoft Teams Send Chat Message action rather than Send Channel Message, and set the recipient to the fulfilment lead's account.
- 4
Lead the message with Service Type and Urgency, so the first line of a phone notification already says what and how fast.
- 5
Map Service Location Address and Preferred Time Window into the body as separate lines — those are the parts read out loud on the way to the van.
- 6
Keep Problem Description as the closing paragraph, since it is the answer that decides what gets loaded.
- 7
Add Customer Name and Phone Number at the end so the lead can call ahead without opening anything else.
- 8
Submit one rush test order and one ordinary one, confirm only the rush order produces a chat, then turn the Zap on.
What maps where
Using the Work Order Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Microsoft Teams |
|---|---|
| Urgency | Filter condition, and the first line of the chat message |
| Service Type | First line of the chat, next to the urgency |
| Service Location Address | Body of the chat, on its own line |
| Preferred Time Window | Body of the chat, under the address |
| Problem Description | Closing paragraph of the chat message |
| Phone Number | Contact line at the foot of the message |
Variations worth knowing
The lead on duty changes through the week. Use a Zapier lookup table to turn the day of the week into a recipient, so the chat reaches whoever is covering rather than one hard-coded account that goes quiet at weekends.
Where two people share cover, point the same action at a group chat containing both of them. The order stays off the main channel while still reaching whichever of them picks it up first.
If something isn't arriving
The filter is missing or comparing against the wrong text. Copy the rush option exactly as it is written in the form editor into the Zapier condition, because the comparison is literal and capitals and trailing spaces count.
The Microsoft Teams account connected in Zapier has to be able to start a chat with that recipient. Guests and people outside your tenant often cannot be messaged this way, so retest against an internal colleague to isolate the cause.
Frequently asked questions
Can I send the chat to more than one person?
Point the action at a group chat that already contains them rather than adding a step for each person. Zapier posts into the chat as the connected account, so everyone sees one message with the full order in it.
Does the customer see anything in Teams?
No. The chat stays inside your own tenant, with the person you selected. The customer sees the form's confirmation screen and any email you send separately, and nothing about the Teams message is visible to them.
Can I take the rush fee on the form?
Yes. Add products and priced options to the form, then collect payment through secure hosted checkout with Stripe, PayPal, or Square. Payment status is tracked alongside the response.
Related automations
- Post event registrations to the events channel
Every registration posts to #events with the attendee and ticket type, so organisers see numbers build during a campaign in real time.
- Post feedback scores to the product channel
Each response posts to #product-feedback with the score and the comment behind it, so verbatims get read rather than exported quarterly.
- Post new job applications to your hiring channel
Every application posts to #hiring with the role and candidate name, so the panel can react in the thread instead of forwarding it round.
- Post new sales enquiries into your leads channel
Each contact sales submission lands in #leads with company, size and timeline included, so a rep can reply the same hour.
- Post support requests into a triage channel
Every support request posts to #support-triage with its subject, priority and requester, so agents watch one channel instead of an inbox.
- Alert the on-call team when a support ticket arrives
Each new ticket posts to #support with its subject and priority, and @here fires only when the priority justifies interrupting a shift.
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