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.
New submission on your "Request a quote" form
Send a message to your sales group in Telegram
One-directional. A submission triggers the action — nothing is written back into your form.
A quote request is only worth as much as the speed of the reply. This flow takes each submission from your "Request a quote" form and posts it into a private sales group, so the first available rep sees the name, the company and the budget without opening a CRM.
It suits small sales teams who already live in Telegram — agencies, contractors, B2B services. The message is a one-way notification: nothing a rep types in the group travels back to the form, so the submission in formformform stays the record of what the prospect actually wrote.
Setting it up
- 1
Publish your "Request a quote" form and send one test submission, filling in every field so Zapier has a complete sample to map from.
- 2
Create your bot with BotFather, then add it to the private sales group and confirm it is allowed to post there.
- 3
Read the group's chat ID and keep the minus sign — Telegram group IDs are negative numbers, and dropping it is the most common reason a Zap fails later.
- 4
In Zapier, set formformform's "New Submission" trigger to watch the quote form specifically, not every form on the account.
- 5
Add Telegram's "Send Message" action and point it at the sales group's chat ID.
- 6
Build the message text: Full Name and Company or Organization on the first line, then Estimated Budget and Project Timeline on lines of their own so a rep can triage at a glance.
- 7
Put Project Description last. It is the longest answer, and Telegram cuts a message off at 4,096 characters.
- 8
Run a second test submission, check how it reads on a phone, then turn the Zap on.
What maps where
Using the Quote Request Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Telegram |
|---|---|
| Full Name | First line of the Telegram message, in bold |
| Company or Organization | Alongside the name, so the group sees who is asking |
| Estimated Budget | Its own line near the top, for quick triage |
| Project Timeline | The line below the budget |
| Email Address | Last line of the message, ready to copy into a reply |
Variations worth knowing
Add a Zapier filter after the trigger so only requests above your threshold reach the main sales group. Smaller ones go through a second Zap into a different chat, which keeps the group reserved for work worth a same-day call.
Add Telegram's "Send Poll" action as a second step, listing your reps as the options. The poll posts under the details and reps answer in Telegram. Their choice stays in the chat and is never written back to the form.
If something isn't arriving
The chat ID is wrong or the leading minus sign was trimmed when it was pasted. Group IDs are negative. Paste the ID in full, and check the bot is still a member of the group — being removed and re-added does not change the ID.
Telegram caps a single message at 4,096 characters. Move Project Description into a second "Send Message" step, or shorten it with a Zapier formatter, so the name, budget and timeline in the first message always arrive whole.
Frequently asked questions
Can a rep reply to the prospect from inside Telegram?
No. The bot posts one way, from the form into the group. Anything a rep types goes to the group, not to the person who submitted. Copy the Email Address out of the message and answer from your normal inbox.
Will the Zap pick up quote requests submitted before I turned it on?
No. The "New Submission" trigger only fires on submissions made after the Zap goes live. Earlier quote requests stay in your formformform responses list, where you can filter, search and export them as usual.
Can I send quote requests to two different sales groups?
Yes. Add a second Telegram "Send Message" action in the same Zap with the other group's chat ID, or build two Zaps with different filters — one per region or service line, both watching the same form.
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.
- 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.
- 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.
- 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