How to reply to app users from Discord or Telegram
Most app developers already have Discord or Telegram open all day. A support inbox in another tab is the one you forget to check. That's the whole case for answering from a chat app: replies get faster because the message lands where you already are.
Bigger companies treat Discord as a support channel too. A Railway team member described their queue on Hacker News: emails, Discord threads, forum posts, tickets and Slack threads in one support tool, with a response target set by the customer's plan (one hour for Enterprise, 24 hours for Pro) and a page to whoever is on call when a target is missed (comment). They answer from one support tool rather than from Discord itself, but one part scales down to a team of one: the customer's plan decides how fast you answer.
Hailbell is our product, built and run by one developer, Vidur Saini. It does what this guide describes, and one section near the end says how. The steps before it apply whatever tool you use, including one you build.
What this setup is, and isn't
You get the notifications you already get, on phone and desktop, with no extra operator app. A Discord forum gives each customer a titled post with its own history, and a Telegram reply is one swipe. What it isn't: a way to talk to customers on Discord or Telegram. Your customers write inside your app and never need an account on either. Their messages come to you there, and your replies go back into the app.
1. Start with an in-app chat and one thread per customer
Everything below depends on one rule: every customer gets their own thread, and every message in it is about that customer. Never post all customers into one channel. Once two people's messages sit side by side, a reply goes to the wrong person sooner or later, and you lose track of who is still waiting.
So you need two things before you start. First, a chat in your app that knows who is writing: a user ID from your sign-in, or at least a stable device ID. Second, something in the middle that opens a thread per customer and maps each reply back to the right person. That can be a support tool or your own bot (see building it yourself).
2. Set up Discord: a forum per app, a post per customer
- Make a private server, or a private category in your team's server. Only the people who answer support should see it. Everyone who can see the channel reads every chat.
- Create a forum channel per app, such as
#support-ios-app. Forum channels show each post as a card with a title, which is what you want: one card per customer, newest activity on top. - Name each post after the customer, such as their name or email plus a short ID, so two people called Alex don't merge in your head.
- Put the context in the first message of the post (see step 4), then the customer's message under it.
- Agree on a few commands. Typing in the thread should reply to the customer. You also want a way to write a note the customer doesn't see, to close the chat, and to say "this one's mine". A common pattern is a prefix such as
//for notes and!closeto close. - Archive the post when the chat is closed and bring it back when the customer writes again. The forum then shows open chats only.
3. Set up Telegram replies, and when it beats Discord
The simplest Telegram setup works by replying. Bots can now open topics in a private chat too, but replies need no setup. Each customer message arrives as a message from your bot with the customer's name on top. You press Reply on it (swipe left on a phone), type, and the answer goes to that customer.
- Create a bot with @BotFather. It's free and takes a minute. Keep the token private; anyone who has it controls the bot, so they can read new messages sent to it and send as it.
- Connect the token to your support tool or your own server, and press Start in the bot so it knows which chat to write to.
- Reply to a customer's message to answer them. A plain message that isn't a reply has no customer to go to, so a good bot tells you that instead of guessing.
Telegram beats Discord when one person does support, mostly from a phone, and wants every chat in one list. It's worse for a team: a private bot chat belongs to one person, so nobody else sees what was said. For two or more people answering, use Discord.
4. Give every reply context: plan, purchases and what happened
The first message in each thread should answer "who is this?" before you read their question. For example (a made-up customer):
Maria · a1b2c3 · iOS
💰 Yearly plan, active, paid $59.99 on 3 Nov
Country: Germany · iPhone 16 · app 2.4.1
Closed the paywall twice this week
Hi, I bought the yearly plan but it still shows the free version?
With that block, "I paid and it still shows free" takes ten seconds: the purchase is there, so the fix is a restore, not a request for a receipt. Without it, you ask for a receipt, wait a day, and the customer leaves a review instead.
Where it comes from: the plan and purchases from your subscription backend (RevenueCat, Superwall, your own receipts), the device and version from the app, and events such as a paywall close from your own analytics call. If you can't get purchases, the device and app version alone still save a round of questions.
5. Let an AI answer first, then finish replies yourself
Chat apps make you faster, but you still sleep. An AI that answers from your own notes covers the night and the repeat questions: how to restore purchases, how to cancel, what the yearly plan includes. Three rules keep it from causing trouble:
- Give it a wait time. If you reply within a few minutes, the AI stays out. It only answers when nobody has.
- Let it hand over. Refunds, bugs and anything it isn't sure of should come to you with a note in the thread, not a made-up answer.
- Have a stop switch per chat. Once you're talking to someone, the AI shouldn't jump back in.
An AI agent such as Claude can also work the queue with you: read the open chats over an API or MCP server, draft replies, and leave them for a person to send. Start with drafts. Let an agent send on its own only once you've read enough of its drafts to trust it.
6. Teams and agencies: several apps, several people
- One forum per app keeps apps apart in one server. An agency can use one server per client, or one per team with a forum per client app.
- Link each teammate's Discord account to who they are in your support tool, so replies carry their name and you can see who answered what.
- Claim chats. A command such as
!mineassigns the chat to you, so two people don't answer the same customer. - Limit who sees which app. A contractor on one client app shouldn't read another client's chats, in Discord or anywhere else.
- Write down a response target per plan, like Railway's. Paying customers within a few hours, trials within a day is a reasonable start for a small team.
Building it yourself
Plenty of developers wire this up on their own. The parts, and where it gets harder than it looks:
- Discord webhooks are one-way. A webhook can post a customer's message into a channel, but it can't read your reply. To read replies typed as normal messages, you need a gateway connection (a long-lived WebSocket) with the Message Content intent, which a serverless function can't hold, so keep a small always-on process for it. A
/replyslash command works over plain HTTP, but it's clumsier to type. - Map threads to customers on your side. Store the thread ID next to the conversation, and ignore any message from a thread you didn't create.
- Telegram is easier. Set a webhook with
setWebhookand a secret token, remember which bot message belongs to which customer, and readreply_to_messageon each update to find who a reply is for. - The app side is the bigger job: the chat screen, delivering replies when the app is closed (push to APNs and FCM), images, unread badges, and a fallback when push fails.
Mistakes to avoid
- One channel for all customers. Replies go to the wrong person and nobody can see who's waiting. One thread per customer, always.
- A public channel. Customer emails and purchases in a server your community can read. Keep support private.
- No record outside the chat app. If the only copy of a conversation is a Discord thread, leaving the server or deleting the channel loses it. Keep the conversation in your support tool or database too.
- No way to tell the customer you replied. If the app is closed, they won't see your answer without a push notification. Send one with every reply.
When to use a full helpdesk instead
Discord and Telegram replies are best for a small team whose customers write from inside an app. Pick something else when:
- Customers write from many places (email, WhatsApp, Instagram, your website) and you want them all in one queue. Crisp is a shared inbox that also lets operators reply from Discord and Slack, with a free plan for 2 seats, paid plans from $45 to $295 a month, and a custom-priced Enterprise plan (prices checked November 19, 2026 on crisp.chat). Its omnichannel inbox starts on Essentials at $95 a month.
- Your team lives in Slack and wants Slack messages turned into tickets. Zendesk's Slack app does that. If you only need to answer each customer from a Slack thread, you don't need a helpdesk: Hailbell, Crisp and Gleap (Slack integration, checked November 19, 2026) all have Slack thread replies.
- You have ten or more agents, SLAs with reporting, ticket fields and approval steps. That is what helpdesks such as Zendesk are for.
Where Hailbell helps
Hailbell is in-app support chat and push notifications for iOS, Android and web apps, with native Swift and Kotlin SDKs, Flutter and React Native SDKs, and a web widget. Every chat is in the dashboard inbox, and Discord, Telegram and Slack are optional extra places to answer from. They all stay in sync.
- Discord. In Settings › Discord, press Connect Discord and pick your server. Then pick a forum for each app, or let Hailbell create one. Each customer gets their own post, titled with their name and a short ID, and typing in it replies to them with a push. Hailbell acts only on messages in the posts it creates and ignores the rest of your server. Closing a chat archives its post, and a new message from the customer brings it back. When the customer reads your reply, the bot reacts 👀 on it.
- Telegram. Paste your bot's token from @BotFather in Settings › Telegram, open the link and press Start. Reply to a customer's message to answer them. The chat also shows replies sent from the dashboard, Discord and the AI, so you can carry on from anywhere.
- Slack. In Settings › Slack, press Connect Slack and allow Hailbell in your workspace. Then pick a channel for each app, or let Hailbell create one; for a private channel, type
/invite @Hailbellin it first. Each customer gets one message with their plan and purchases, an Ask for a review button and a Send an offer menu, and typing in its thread replies to them with a push.!closemarks the message with ✅. - The same commands everywhere.
!close,!mineand!unassign,!humanto keep the AI out of a chat and!aito let it back,!rfor a saved reply,!reviewto ask for a review,!offerto send an offer card that opens one of your paywalls, and//for a note the customer doesn't see. - Context at the top of every thread. The customer's country, plan, whether it's active, a trial, cancelled or refunded, and what they've spent, from your Superwall or RevenueCat webhooks. Paywall closes come from your app's
Hailbell.track("paywall_decline")call. - An AI that answers first. When nobody replies within your wait time, it answers from your notes, prices and help articles, and hands the chat to you when it can't help. Every AI reply is labelled.
- Teams. Unlimited seats on every plan. Teammates link their Discord, Telegram or Slack under Profile, so replies carry their name, and admins can limit someone to some apps.
- AI agents over MCP. An agent can list, read and answer chats, with each customer's plan and purchases. Its replies are drafts a teammate sends from the dashboard, unless an admin lets agents send in that app.
The gaps, honestly:
- Slack is newer than Discord: it doesn't get alerts or the 👀 reaction when the customer reads your reply yet.
- Telegram is one chat per Hailbell account, so it suits one person. Teams should use Discord or Slack.
- Agent drafts are sent from the dashboard, not from Discord, Telegram or Slack.
- Images up to 1.5 MB go both ways. From Discord, other files reach the customer as a link. From Telegram and Slack, video, voice messages and other files don't reach them.
- Hailbell is new, with no ticketing, no email or social channels, and no import of past conversations from another tool.
Pro is $29 a month for 10,000 monthly active users, with unlimited seats and apps. There's a 14-day trial with no card, and a 14-day money-back guarantee on the first payment: ask within 14 days, while AI replies have used under 20% of the plan's monthly AI allowance. Try Hailbell or read the Discord, Telegram and Slack docs.
The same Discord and Telegram replies work on a Shopify store. Adding the chat button is covered in how to add live chat to a Shopify store.
Questions
Can I answer app support messages from Discord?
Yes, if your support chat tool posts each customer's messages into Discord and sends your replies back into the app. A Discord webhook alone only posts into a channel; it can't read your replies. Two-way replies need a bot that reads messages in the threads it created, or a tool that runs one for you.
Discord or Telegram: which is better for app support?
Discord for a team: each customer gets a thread in a forum channel, several people can read and answer, and one forum per app keeps apps apart. Telegram for one person answering from a phone: you reply to the customer's message in a private chat with your own bot.
Do customers need a Discord or Telegram account?
Not with an in-app chat. The customer writes inside your app and gets your reply there, with a push notification. Discord and Telegram are only where your team reads and answers.
Is it safe to put customer messages in a Discord server?
Use a private server or a private forum that only your support team can see, since everyone with access to the channel reads the chats. Customer messages are also stored by Discord or Telegram. If your privacy policy or a client contract rules that out, answer from your support tool's own dashboard instead.
Adding the chat itself is covered in adding support chat to an iOS app and the Android guide.
Questions about answering support from Discord or Telegram? Start a chat with us.