Skip to main content
Telegram is how Vortex IQ pushes alerts into the messenger that DTC operators, growth squads, and global commerce teams already live in, with bot-driven delivery into channels, groups, and direct messages.

​
What is Telegram?

Telegram is an instant-messaging platform with a strong bot ecosystem. It is well known for cross-device sync, large group capacity (up to 200,000 members), broadcast channels, end-to-end-encrypted secret chats, and a developer-friendly Bot API. Adoption is heavy among DTC and direct-response brands, Web3 and crypto teams, and operators in Eastern Europe, the Middle East, India, and Southeast Asia. For many globally distributed commerce teams, Telegram is the operational chat layer the same way Slack is in North America. For Vortex IQ, Telegram is a primary chat-style alert channel for merchants whose teams already work there, and a secondary channel for individual operators who want a low-friction stream of personal alerts on their phone.

​
Why Vortex IQ uses Telegram as an alert channel

Vortex IQ uses Telegram in two complementary modes:
  1. Group and channel alerts: a Vortex IQ bot is invited to a Telegram group or admin-only broadcast channel and posts structured alerts as the team chat surface.
  2. Direct messages: an individual operator authorises the Vortex IQ bot and receives a private stream of alerts scoped to the categories and stores they care about.
Typical alerts:
  • Real-time revenue and conversion anomalies during campaigns.
  • Inventory thresholds on hero SKUs and out-of-stock alerts during high-traffic windows.
  • Refund-rate spikes by category or product.
  • Customer-feedback spikes on a launched product.
  • Payment-gateway and checkout incidents (with severity-one always also routed to a voice channel and PagerDuty).
Telegram is the low-latency conversational channel. It is not a replacement for voice escalation when the cost of missing the alert is large.

​
What gets delivered

Each Vortex IQ alert in Telegram is a single message with a consistent shape:
  • Header: severity emoji, alert name, store, and integration type.
  • Body: trigger metric, current value, threshold, time window, and revenue at risk where relevant.
  • Inline buttons: Acknowledge, Snooze 15m, Open in Vortex IQ, all rendered as Telegram inline keyboard buttons.
  • Footer: a short, opaque incident reference and the timestamp in dd MMM yy format with the merchant’s local timezone.
Inline button actions hit Vortex IQ webhooks; an acknowledgement clicked in Telegram lands instantly on the incident timeline in the Nerve Centre. For long-form artefacts (incident timelines, audit summaries, weekly digests), the bot posts a short header with a link rather than dumping a long message into the chat.

​
How it integrates

  • Authentication: a Telegram Bot API token, created via BotFather and stored encrypted by Vortex IQ.
  • Chat targets: each merchant maps the bot to one or more chat IDs (groups, broadcast channels, or individual users). Mapping is done via a one-time pairing flow where the bot prints its chat ID into the channel.
  • Outbound delivery: Vortex IQ uses the sendMessage and editMessageText endpoints, with Markdown and inline keyboards.
  • Inline button handling: callback queries are routed through Vortex IQ webhooks and reconciled against the active incident.
  • Rate limiting: Vortex IQ honours Telegram’s per-chat send limits (one message per second per chat, 30 messages per second globally per bot) with backoff and queueing.
  • Privacy: the bot does not read other messages in the chat, only its own callback queries and the messages it sends.

​
Operational diagnostics

The Nerve Centre exposes Telegram channel health:
  • Last successful test message per chat target.
  • Message delivery rate over the last 7 days.
  • Inline-button click-through rate (acknowledge, snooze) for incidents posted to the chat.
  • Failed-delivery log with Telegram API error codes (chat not found, bot was blocked, message too long).
  • Bot health check, with reminders if the bot has been removed from a configured chat.
If the Telegram Bot API is degraded or returning sustained errors, alerts queue briefly and fall through to the recipient’s secondary channel (email, SMS via Twilio or Vonage, or Slack, depending on the routing rule).

​
Connect Telegram to Vortex IQ

Add Telegram as a notification channel from the Vortex IQ settings page. Create a bot with BotFather, paste the bot token, invite the bot to the chats that should receive alerts, run the pairing command, and Ask Viq will start posting structured incident messages from the next deployment forward.