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.
New submission on your "Contact sales" form
Send a channel message to the #leads channel in your Sales team
One-directional. A submission triggers the action — nothing is written back into your form.
A prospect who fills in a contact sales form has a short window of attention. This flow posts each submission into #leads in your Sales team as it arrives, laid out so the first line already answers the question a rep asks: who is this, and are they worth a call today.
Teams-first sales groups use it as their queue. The reply thread under each message becomes the record of who took the lead and what they found. Nothing travels the other way, and Teams never writes back into the form.
Setting it up
- 1
Publish your contact sales form. The Business Inquiry Form template already collects Company Name, Company Size and Timeline, which is the qualifying set a rep wants before replying.
- 2
In Zapier, set formformform's New Submission trigger to watch that sales form only, so #leads never fills up with support or careers traffic.
- 3
Add the Microsoft Teams Send Channel Message action, connect the account that belongs to your Sales team, and pick #leads as the destination channel.
- 4
Open the message with Full Name and Company Name on the same line — that pair is what a rep scans for once the channel gets busy.
- 5
Put Work Email on its own line below, so it can be copied without dragging across a sentence.
- 6
Close the message with Type of Inquiry, Company Size and Timeline, then finish with the Tell Us More answer as the last block.
- 7
Use Zapier's Paths to @mention the sales rota only when Timeline is the soonest option; everything else posts quietly.
- 8
Send one live test submission, check how it renders in mobile Teams as well as on desktop, then switch the Zap on.
What maps where
Using the Business Inquiry 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 |
|---|---|
| Full Name | First line of the channel message, before the company |
| Company Name | First line of the channel message, after the name |
| Work Email | Its own line in the message body, ready to copy |
| Company Size | Qualifying line under the contact details |
| Timeline | Qualifying line, and the condition on the mention path |
| Tell Us More | Closing block of the message |
Variations worth knowing
Add a Zapier path on Company Size so enterprise-sized submissions post to a private channel your account executives watch, while everything under that stays in #leads for the wider team to pick up.
Keep the channel message as the shared record and add a second Microsoft Teams action that sends a chat message to the rep on duty whenever Type of Inquiry is a pricing request, so it reaches them off-channel.
If something isn't arriving
The submission left Company Name empty. Make the question required in the form editor, or give the Zapier field a default value so the first line never ends in a gap where the company should be.
Renaming a channel is usually harmless, because the action stores the selection by ID. Moving a channel to a different team is not. Reopen the Microsoft Teams step, reselect the team and channel, then retest.
Frequently asked questions
Can I post to a private channel in Microsoft Teams?
Yes, as long as the account you connect in Zapier is a member of that private channel. It then appears in the channel picker alongside the standard ones. Shared channels from another tenant are the case worth testing before you rely on them.
Will replying in the Teams thread update the submission?
No. The connection runs one direction: a submission triggers the message. Replies, reactions and edits stay in Teams and are never written back to formformform, so treat the responses list as the record of what the prospect actually sent.
How quickly does the message show up?
The New Submission trigger fires in real time, so the message usually appears within seconds of someone pressing submit. The remaining delay is Zapier's own task queue, which is longest on free plans during busy periods.
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 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.
- 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