Discord and Telegram Alerts When Your AI Can't Answer

Your AI handles the FAQ. Then a visitor asks something only you can answer—and silence kills the sale. Dispatch sends that moment to Telegram or Discord: full context, one tap to reply, no Zendesk seat required.

Solo founders, indie hackers, and agency teams already live in community apps. Chirps routes escalations, lead captures, and booking confirmations to the channels you actually check.

When Dispatch Fires

Notifications trigger on configured events—not on every message. Common triggers:

• Agent handoff: Visitor asks for a human, bot confidence drops, or escalation keywords match.
• Lead captured: Intake form, quote request, or contact artifact submitted in chat.
• Booking confirmed: Consultation or demo scheduled via in-chat booking artifact.

Step-by-Step: Telegram Dispatch Setup

1. Open your assistant in Chirps → Notifications (or Dispatch Channels).
2. Click Add Channel → select Telegram.
3. Create a bot via [@BotFather](https://t.me/BotFather) on Telegram. Copy the bot token.
4. Get your chat ID: forward any message to [@userinfobot](https://t.me/userinfobot) or add the bot to a group and read the group chat ID.
5. Paste bot token and chat ID in Chirps. Enable events: handoff, lead captured, booking (pick what you need).
6. Click Test to send a sample notification. Confirm it arrives in your chat.
7. Save. Repeat for other assistants if you run multi-brand setups.

Step-by-Step: Discord Dispatch Setup

1. In Discord, open your server → select the target channel (e.g. `#customer-escalations`).
2. Channel Settings → Integrations → Webhooks → New Webhook.
3. Name it "Chirps Alerts," copy the webhook URL.
4. In Chirps → Add Channel → Discord → paste webhook URL.
5. Select which events to receive. Test and save.

Discord webhooks post as the webhook name—you can set a Chirps logo avatar in Discord webhook settings for visual consistency.

What Each Notification Includes

Default templates include the fields your team needs to respond without opening the dashboard first:

• Event type: New lead, booking confirmed, or agent handoff.
• Visitor context: Name, email, phone (if collected), location when available.
• Conversation notes: Summary and form artifact answers (practice area, budget, issue type).
• Timestamp and assistant name (which widget/site triggered the alert).
• Dashboard link to open the full transcript and reply live.

Custom templates

Power users can override the default message template with variables: `{{lead_name}}`, `{{lead_email}}`, `{{notes}}`, `{{form_data}}`, `{{dashboard_url}}`, `{{summary}}`, and any custom form field keys from your artifacts.

Best Practices for Solo and Small Teams

• One channel per severity: Telegram for all alerts is fine at small scale; split handoff vs. marketing leads later.
• Mute off-hours wisely: Route to Discord with @here only for handoff, not every lead form.
• Reply from dashboard: Telegram/Discord are alerts—use Chirps live reply for official transcript logging.
• BYOK on free/starter: Telegram and Discord use your own bot token / webhook (bring your own keys)—no per-message dispatch tax.

Who This Workflow Fits Best

1. Indie hackers and micro-SaaS without a support inbox.
2. Agencies managing client sites who want pings, not another SaaS login.
3. Community-led products where the team already coordinates in Discord.
4. After-hours coverage where email is too slow but staffing 24/7 chat is unrealistic.