Post support requests to your team chat
Each support request arrives in your team chat with the priority first, so whoever is on shift can pick it up from a phone.
New submission on your "Contact support" form
Send a message to your support team chat in Telegram
One-directional. A submission triggers the action — nothing is written back into your form.
Support requests do not wait for someone to open a laptop. This flow pushes each new ticket into the chat your team already has open on their phones, with the priority first so whoever is on shift can judge in a second whether to stop what they are doing.
It works best for small teams sharing one queue — an agency desk, an in-house IT rota, a two-person SaaS. The chat is a notification surface, not a ticket system: the request itself stays in formformform, where it can be searched and exported later.
Setting it up
- 1
Publish the support form and submit one test ticket marked as your highest priority, so Zapier sees a realistic sample of every field.
- 2
Create the bot in BotFather and add it to the shift chat your team already watches, rather than starting a new group nobody has muted yet.
- 3
In Zapier, choose the support form under formformform's "New Submission" trigger.
- 4
Add Telegram's "Send Message" action and put Priority at the very start of the message text — on a locked phone, that is often the only word anyone reads.
- 5
Follow the priority with Ticket Subject on the same line, then Full Name and Issue Type underneath it.
- 6
Set the parse mode to Markdown or HTML and wrap the subject in bold, so an urgent ticket is distinguishable in a busy chat.
- 7
Keep Issue Description near the bottom and map Work Email last, so the person picking the ticket up can reply without opening anything else.
- 8
Send the test, confirm the group is not muted for the people on shift, 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 | Telegram |
|---|---|
| Priority | First word of the message, before anything else |
| Ticket Subject | Bold text on the opening line, after the priority |
| Full Name | Second line, naming who reported it |
| Issue Type | Second line, next to the reporter's name |
| Affected Device or System | Its own line, so the right person can claim it |
| Work Email | Closing line of the message, for the reply |
Variations worth knowing
Put a Zapier filter on Priority so only the top level reaches an on-call chat, and let everything else post to the general queue. Two Zaps watch the same form and differ by one filter condition, which is easier to adjust than a shared chat everyone eventually mutes.
Include a Telegram @username in the message text and change it when the rota changes. The mention notifies that person directly even if the chat is muted, without needing a separate Zap or a second Telegram action step.
If something isn't arriving
The chat is muted on the phones that matter, or notifications for bot messages are turned off for that chat. Ask each person on the rota to open the chat's notification settings and unmute it. Zapier will show a success either way, so the Zap history cannot tell you this.
The test submission used to build the Zap left that question empty, so Zapier mapped a field it never saw filled. Submit a fresh test with every field answered, remap Priority from that sample, or set a default value in the Zapier step.
Frequently asked questions
Does replying in the Telegram chat reach the customer?
No. The connection runs one way, from the form into Telegram. Replies stay in the chat between your team. Answer the customer using the Work Email in the message, or through whatever channel you normally use.
What if someone deletes the message in Telegram?
The ticket is unaffected. Every submission is stored in formformform, so a deleted or lost message costs you the notification, not the request. Open the responses list, search for the name or subject, and work from there.
Can I include the reporter's phone number?
Yes. Map Phone or Extension into the message alongside the email. It helps when a ticket is marked urgent and the fastest fix is a call, though it does mean the number sits in the chat history for anyone in the group.
Related automations
- 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.
- Get feedback in a direct chat with your bot
Feedback goes straight to a one-to-one chat with your bot, so you see the rating and the comment as they arrive.
- Keep organisers updated on event RSVPs
Each RSVP posts to the organisers group with the attendee name and the session they picked, as people sign up.
- Route job applications to a private hiring chat
Applications land in a private hiring chat with the role, name and start date, so reviewers can weigh them together.
- Send new quote requests to your sales group
Every quote request lands in your sales group in Telegram with the name, company, budget and timeline a rep needs to reply.
- 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