Installation steps
- 1
Prepare
Decide which incoming conversations need an immediate response and which can wait for the next support check-in.
- 2
Configure
In Telegram, review notifications for the support group and use each topic's notification controls where available to mute lower-priority conversations.
- 3
Publish
Keep an agreed urgent path visible to the team, and pin the group so new topics are easy to find even when some topics are muted.
- 4
Verify
Check Telegram settings on both desktop and mobile, then send a test conversation and confirm the expected devices show an alert.
What MivoChat sends
MivoChat posts a conversation card and visitor messages in the Telegram topic, along with later AI or teammate turns and status updates. The code sends ordinary Telegram messages and does not select per-topic notification sound, urgency, or mute settings for your account.
When Telegram topics cannot be created, the channel can fall back to a card in the group and replies linked to that card. In that mode, group-level notification settings matter more because separate topic controls are unavailable.
Set a notification routine
Use Telegram's current controls for group notifications and, where the client exposes them, topic-specific notifications. Mute non-urgent topics or the group during focused work only if the team has another agreed check-in or escalation path.
Telegram's menus differ across desktop, iOS, and Android versions. Open the support group information and topic menu in each client, confirm which notifications are muted, and avoid assuming a setting on one device automatically reflects every device's local alert behavior.
Test the path on each device
Send one new visitor question and have a teammate reply. Confirm the group and topic behavior in the clients your team uses, then decide whether desktop is the primary queue and mobile is the urgent backup or vice versa.
For topic creation and bot permissions see /guides/telegram-topics-support-setup; for command behavior and multiple teammates see /guides/telegram-team-handoff. Also review /guides/telegram-customer-support-bot, /for/telegram-support, and /pricing before setting an expected support coverage promise.
Before you change the setup
- Who this is for
- a small support team balancing Telegram interruptions with timely customer replies
- What you need
- Telegram desktop or mobile access, an agreed urgent escalation path, and knowledge of the team's support hours
- Where it goes
- Telegram's group notification settings and per-topic controls where available in each client
- Watch out for
- MivoChat sends normal Telegram messages and does not set notification priority, mute state, or sound
Test the support boundary
- Does a new topic alert the expected desktop client?
- Does a muted lower-priority topic stay discoverable?
- Do mobile and desktop settings match the team's coverage plan?
Frequently asked questions
A visitor message does not trigger an alert
Check Telegram's group and topic notification controls on that device; MivoChat does not override Telegram mute settings.
The team misses a muted conversation
Pin the support group, schedule a queue review, or keep an explicit urgent path outside muted topics.
Fallback cards interrupt everyone
When topics are unavailable, cards use the group chat; fix Topics permissions or tune group notifications with that fallback in mind.
Desktop and mobile behave differently
Review both clients' local notification settings and send a fresh test message to each device.
Keep exploring
Related guides
The r3-final-a evaluation measured 95% answerability-tier accuracy on 224 questions; this is an evaluation result, not a guarantee. AI replies use Anthropic. See the method and results and subprocessors and data locations.