AI-Powered Telegram Support System with Zendesk Integration

𝗔𝗜-𝗣𝗼𝘄𝗲𝗿𝗲𝗱 𝗧𝗲𝗹𝗲𝗴𝗿𝗮𝗺 𝗦𝘂𝗽𝗽𝗼𝗿𝘁 𝗦𝘆𝘀𝘁𝗲𝗺 𝘄𝗶𝘁𝗵 𝗭𝗲𝗻𝗱𝗲𝘀𝗸 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻

𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝗢𝘃𝗲𝗿𝘃𝗶𝗲𝘄

Client needed a support workflow that could handle common customer questions automatically while still giving users a reliable way to reach a human agent for sensitive or account-specific issues.

The goal was to connect an existing AI-powered Telegram support bot with Zendesk so that AI could handle first-line support while Zendesk became the central system for human support, ticket routing, SLAs, escalations, and agent communication.

𝗧𝗵𝗲 𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲

The existing Telegram bot already used Claude AI for customer support, but human escalations were handled through Telegram support groups.

That created several limitations:

Support conversations were difficult to manage at scale

No centralized ticket lifecycle

Limited SLA tracking

No structured routing by issue type

Harder to manage security, compliance, KYC, and payment cases

Agent responses and ticket history were spread across Telegram

No unified support experience across Telegram, website, and email

The challenge was to integrate Zendesk without replacing the existing Claude AI workflow.

𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻

I designed a hybrid support architecture where:

𝗖𝗹𝗮𝘂𝗱𝗲 𝗔𝗜 𝗿𝗲𝗺𝗮𝗶𝗻𝘀 𝘁𝗵𝗲 𝗳𝗶𝗿𝘀𝘁-𝗹𝗶𝗻𝗲 𝘀𝘂𝗽𝗽𝗼𝗿𝘁 𝗮𝗴𝗲𝗻𝘁, 𝘄𝗵𝗶𝗹𝗲 𝗭𝗲𝗻𝗱𝗲𝘀𝗸 𝗵𝗮𝗻𝗱𝗹𝗲𝘀 𝗮𝗹𝗹 𝗵𝘂𝗺𝗮𝗻 𝗲𝘀𝗰𝗮𝗹𝗮𝘁𝗶𝗼𝗻𝘀.

The final workflow:

For normal questions, Claude continues responding directly.

When a request requires human assistance, the system:

detects the issue type

determines priority

detects security/compliance-sensitive cases

summarizes the AI conversation

creates a Zendesk ticket

selects the correct Zendesk form

routes the ticket to the appropriate team

pauses Claude while the ticket is being handled

𝗦𝗺𝗮𝗿𝘁 𝗛𝘂𝗺𝗮𝗻 𝗘𝘀𝗰𝗮𝗹𝗮𝘁𝗶𝗼𝗻

Users can manually request an agent using:

The bot then creates a structured Zendesk ticket containing:

conversation summary

issue category

priority

customer language

escalation reason

Telegram user ID

Telegram username

bot session ID

internal ticket reference

The customer does not have to repeat the full conversation to the support agent.

𝗜𝗻𝘁𝗲𝗹𝗹𝗶𝗴𝗲𝗻𝘁 𝗧𝗶𝗰𝗸𝗲𝘁 𝗥𝗼𝘂𝘁𝗶𝗻𝗴

The integration automatically routes tickets based on the detected issue.

𝙋𝙖𝙮𝙢𝙚𝙣𝙩𝙨

Payment

Deposit

Withdrawal

→ 𝗣𝗮𝘆𝗺𝗲𝗻𝘁𝘀 𝗢𝗽𝗲𝗿𝗮𝘁𝗶𝗼𝗻𝘀

**𝘈𝘤𝘤𝘰𝘶𝘯𝘵 & 𝘝𝘦𝘳𝘪𝘧𝘪𝘤𝘢𝘵𝘪𝘰𝘯

KYC

Login

Account issues

→ Account & Verification

**Security

Unauthorized access

Fraud

Suspicious activity

Account compromise

→ Security & Fraud → Urgent priority

**Compliance

Sanctions screening

AML

OFAC

Regulatory issues

→ Compliance / MLRO → Urgent priority

**Technical Issues

→ Technical Support

General questions and referrals route to Customer Support.

𝗗𝘆𝗻𝗮𝗺𝗶𝗰 𝗭𝗲𝗻𝗱𝗲𝘀𝗸 𝗧𝗶𝗰𝗸𝗲𝘁 𝗙𝗼𝗿𝗺𝘀

Instead of creating every ticket with the same support form, the backend dynamically chooses the appropriate Zendesk form:

General Support

Payment & Transfer Support

Account & Verification

Security & Fraud

Technical Issue

Compliance Escalation

This keeps agent workflows clean and ensures the correct ticket fields are available for each issue type.

𝗧𝘄𝗼-𝗪𝗮𝘆 𝗧𝗲𝗹𝗲𝗴𝗿𝗮𝗺 ↔ 𝗭𝗲𝗻𝗱𝗲𝘀𝗸 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻

The integration is fully bidirectional.

When a customer sends another Telegram message during an active human handoff:

Claude does not respond while the human agent owns the conversation.

When the Zendesk agent sends a public reply:

The customer receives the support agent's response directly inside Telegram.

Internal Zendesk notes remain private and are never sent to the customer.

𝗔𝗜 𝗥𝗲𝘀𝘂𝗺𝗲 𝗔𝗳𝘁𝗲𝗿 𝗥𝗲𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻

When a Zendesk ticket is solved:

human handoff is disabled

the ticket state is updated

Claude AI becomes available again

future Telegram questions return to AI support

This creates a clean lifecycle:

without requiring the customer to switch platforms.

𝗭𝗲𝗻𝗱𝗲𝘀𝗸 𝗦𝘂𝗽𝗽𝗼𝗿𝘁 𝗜𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲

I also configured the wider Zendesk environment, including:

Support groups

Ticket forms

Custom ticket fields

Routing triggers

Notification triggers

Automations

SLA policies

Macros

Agent views

Solved-ticket views

Business hours

Support email integration

Website messaging widget

Zendesk OAuth authentication

Secure webhook verification

𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 & 𝗖𝗼𝗺𝗽𝗹𝗶𝗮𝗻𝗰𝗲

Special attention was given to fintech-related support risks.

The AI avoids handling sensitive account-specific or compliance decisions and escalates cases involving:

unauthorized account access

fraud

missing funds

transaction-specific issues

KYC failures

sanctions screening

AML / OFAC-related cases

sensitive account investigations

Customers are also warned not to share:

passwords

OTP codes

full card numbers

private keys

seed phrases

The Zendesk integration is controlled through a feature flag:

If Zendesk is disabled, the system can fall back to the original Telegram support-group workflow.

This provides a safe rollback strategy during rollout.

Telegram User ↓ Security & Risk Checks ↓ Claude AI ↓ General Question → AI Response

or

Human/Sensitive Issue ↓ Zendesk Ticket ↓ Correct Group + Form + Priority ↓ Human Support Agent ↓ Zendesk Webhook ↓ Telegram User

𝗞𝗲𝘆 𝗥𝗲𝘀𝘂𝗹𝘁𝘀

The project transformed a Telegram AI bot into a structured omnichannel customer-support workflow with:

AI-first customer support

automated human escalation

centralized Zendesk ticket management

two-way Telegram communication

intelligent risk-based routing

security/compliance prioritization

conversation summarization

SLA-ready support operations

reliable fallback architecture

𝗧𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝗶𝗲𝘀 𝗨𝘀𝗲𝗱

Backend

Node.js

Telegram Bot API

grammY

MongoDB

Claude AI

Zendesk Support

Zendesk Messaging

Zendesk Webhooks

Zendesk OAuth API

REST APIs

Webhooks

OAuth 2.0

MongoDB ticket mapping