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.
New submission on your support intake form
Post a channel message in the #support-triage channel with the issue summary and priority
One-directional. A submission triggers the action — nothing is written back into your form.
An inbox hides the queue. You cannot tell at a glance which three tickets are urgent and which have been sitting since yesterday. Posting each intake submission into #support-triage puts the whole queue in front of the team, with the priority visible in the first line and the description underneath it.
Small support and IT teams reach for this when there is no ticketing tool yet, or when one exists and nobody watches it. The channel becomes the shift handover: claimed in a reply, closed in the same thread.
Setting it up
- 1
Publish your intake form from the IT Help Desk Ticket template, which already asks for Priority, Issue Type and Affected Device or System.
- 2
In Zapier, point the New Submission trigger at that intake form and leave every other form out of this Zap — a triage channel only works when everything in it is triageable.
- 3
Add the Microsoft Teams Send Channel Message action, choose the team your agents live in, then #support-triage as the channel.
- 4
Build the message title from Priority followed by Ticket Subject, so the sort a reader does in their head matches the queue.
- 5
Map Issue Description into the message body as its own paragraph rather than appending it to the title, which Teams shortens in the channel list.
- 6
Add Work Email and Department on a final line so an agent can reply directly without opening the submission.
- 7
Add a Zapier path so anything at the highest priority also @mentions the on-call agent, and let the rest post quietly.
- 8
Submit one test ticket at each priority level, confirm both variants land where you expect, then turn the Zap on.
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 | Microsoft Teams |
|---|---|
| Priority | Start of the message title, and the condition on the mention path |
| Ticket Subject | Rest of the message title |
| Issue Description | Main paragraph of the message body |
| Affected Device or System | Detail line under the description |
| Work Email | Contact line at the foot of the message |
| Department | Contact line, next to the requester's email |
Variations worth knowing
Add Zapier paths on Issue Type so hardware faults post to the facilities channel and account or access requests go to the identity team, while everything else carries on into #support-triage as normal.
Keep the channel post as the shared queue and add a second Microsoft Teams action that sends a chat message to whoever is on call when Priority is urgent, so it reaches a person rather than a room.
If something isn't arriving
Teams collapses a long message behind a see-more control rather than dropping the text. If the preview is what matters, keep Ticket Subject and Priority at the top and let Issue Description sit below the fold.
The condition is matching loosely. Set the Zapier path to exactly match the priority label as it is written in the form rather than using contains, which makes High match Highest and anything else holding the word.
Frequently asked questions
Do I still need a ticketing system for this?
Not at this size. The channel is the queue: an agent claims a request in a reply and closes it in the same thread. Every submission stays searchable and exportable in formformform if you need the record later.
Can the person who submitted the form see the Teams message?
No, unless they are a member of that team. The message goes to your internal channel only. The requester sees whatever confirmation the form shows them and receives nothing at all from Teams.
What happens to requests while the Zap is switched off?
They are still collected. formformform stores every submission whether or not an automation is running, so you can find the gap in the responses list and post anything that was missed once the Zap is back on.
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.
- 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.
- 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