Telegram logo

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.

When this happens

New submission on your "Feedback" form

Do this

Send a message to your personal Telegram chat with your bot

One-directional. A submission triggers the action — nothing is written back into your form.

Feedback is easy to miss when it arrives as one more email among forty. A one-to-one chat with your own bot gives it a place where it cannot be buried: the rating shows in the notification, and the sentence about what to fix is the first thing you read.

Founders, solo consultants and anyone running a product without a support team use this. The chat is private to you — the bot posts, you read, and nothing you type there reaches the person who left the feedback.

Setting it up

  1. 1

    Publish the feedback form and put it where people already are: a footer link, a post-purchase email, or a slide-in on the page they just used.

  2. 2

    Create the bot with BotFather, then open a chat with it yourself and send /start. A bot cannot message a person who has never messaged it first.

  3. 3

    Find your own numeric chat ID for the Zapier action. It is your user ID, a positive number, not your @username.

  4. 4

    Point formformform's "New Submission" trigger at the feedback form.

  5. 5

    Lead the message with Overall Satisfaction, so the notification preview tells you the mood before you pick the phone up.

  6. 6

    Follow it with What could we improve? — the sentence you actually act on — and then What did you like most?.

  7. 7

    Close with Name and Email Address so you can answer personally when a response deserves it, and leave both blank-tolerant if you allow anonymous feedback.

  8. 8

    Submit a test, look at how it renders on a locked screen, then turn the Zap on.

What maps where

Using the Customer Feedback Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.

Form fieldTelegram
Overall SatisfactionFirst line, visible in the notification preview
What could we improve?Second line, the part you act on
What did you like most?Third line, for context
NameFoot of the message, when it was given
Email AddressFinal line, so you can reply by email

Variations worth knowing

Only ping me when it is bad

Put a Zapier filter on Overall Satisfaction so only the low scores reach your chat. Everything else stays in the responses list for a weekly read, which keeps the notification meaningful rather than something you learn to swipe away.

One message a day instead of many

Insert a digest step in Zapier between the trigger and Telegram to collect the day's responses and release them as a single message at a set time. Useful once feedback arrives often enough that individual pings stop being signal.

If something isn't arriving

Zapier says the bot cannot start a conversation with the user

Telegram only lets a bot message someone who has messaged it first. Open the chat with your bot from your own account, send /start, then retest the Zap. The same applies to anyone else you add as a recipient later.

The whole response arrives as one unbroken paragraph

Zapier sends the message text exactly as written in the action step. Press enter between each mapped field so every answer starts on its own line, and set a parse mode if you want the rating in bold. Test again on a phone, not a desktop.

Frequently asked questions

Can I reply to feedback from the chat with my bot?

No. Typing in that chat talks to the bot and goes nowhere near the respondent. Use the Email Address in the message to answer, and remember the person may have left the form anonymously with no address at all.

Will anonymous feedback still come through?

Yes. If Name and Email Address are optional and someone leaves them empty, the message posts with those lines blank. Add fallback text in the Zapier step so it reads "anonymous" rather than looking like a broken mapping.

Can several forms report into the same chat?

Yes. Build one Zap per form and point them all at the same chat ID. Put the form's name at the top of each message so you can tell at a glance whether it came from the product survey or the support follow-up.

Related automations

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