Why connect Telegram to Salesforce
Salesforce runs sales at enterprises and scale-ups across North America, the UK, Australia and the Gulf. Integrating Telegram means respecting its data model (Leads vs Contacts, Accounts, Opportunities, Cases), its governor limits and the security review your admin will require. A Telegram bot or Mini App without the integration creates a second customer list that nobody maintains; with it, every Telegram interaction lands on the right record, managers get alerts where they already are, and customers get updates in the chat they actually read.
How the integration works
- Auth. A Connected App with OAuth 2.0 (JWT bearer flow for server-to-server), scoped to the objects we touch, in a sandbox first.
- Inbound. Our middleware upserts Leads or Contacts on a Telegram external ID field, creates Opportunities and Cases, and writes Activities with transcripts. Bulk API is used for backfills.
- Outbound. Flows publish Platform Events or call an outbound webhook on stage changes; the middleware sends Telegram messages with templates and logs delivery back to Salesforce.
- Agents. Service Cloud agents can work Telegram conversations as Cases with replies routed through the bot; a Lightning component shows the chat inline if you want it.
Typical flows
- Lead routing: Telegram lead → Lead with assignment rules → owner notified in Telegram
- Opportunity updates: stage change → client message with next steps
- Service: Case created from the bot, SLA timers, agent replies through Telegram
- Reporting: Telegram source visible in standard dashboards
Architecture
| Layer | What runs there |
|---|---|
| Telegram | Your bot (grammY or aiogram) and Mini App; users never leave Telegram |
| Middleware | A small service on your cloud (Node.js or Python): auth with Salesforce, upserts, dedupe, templates, rate limits, retries, audit log |
| Salesforce | Native objects and automations; no custom code inside Salesforce beyond fields and triggers |
| Monitoring | Failed syncs alert your team in a Telegram group; a daily reconciliation report catches drift |
We keep business logic in the middleware so that Salesforce upgrades, API version changes and bot changes do not break each other. The middleware ships with tests, an admin page for retries and documentation your developers can extend.
Data, consent and compliance
Telegram user IDs, usernames and phone numbers are personal data. The integration stores consent (captured in the bot or Mini App), supports unsubscribe commands, honors deletion requests by removing the Telegram identity from Salesforce records, and keeps data in your Salesforce region and your cloud region. For GDPR, UK GDPR, PIPEDA and the Australian Privacy Act we provide a data flow document for your DPO.
Pricing and timeline
| Scope | Budget | Timeline |
|---|---|---|
| One-way: Telegram → Salesforce records and manager alerts | from $5,000 | 1–2 weeks |
| Two-way: plus triggered messages and operator replies | +$1,500–$3,000 | +1 week |
| Commerce or support add-ons (orders, tickets, payments) | +$1,500–$4,000 | +1–2 weeks |
Every integration includes field mapping, a sandbox phase, a go-live checklist and 30 days of fixes. Need the bot or Mini App built as well? See Telegram bot development and Mini App development.
* All prices and ranges on this page are indicative. The final cost is calculated for each project individually and depends on the complexity of the task, the number of developers and specialists required, and the delivery timeline you set. Use the ranges to understand the typical bracket, not as a fixed offer; the fixed price is confirmed in writing after scoping. Read our pricing terms.