Integration
Give each agent its own Telegram presence. Support drafters, onboarding guides, internal assistants — each reachable through its own bot, without leaking into the others.
One giant Telegram bot that "does everything" ends up doing nothing well. Users don't know what it can help with, permissions blur, and every conversation contends for attention.
Per-agent bots invert that: each bot is a role. The Quote Assistant bot only drafts quotes. The Support Drafter bot only handles support. Users pick the agent by picking the bot, and the agent knows exactly what it's there for.
Setup Model
Pinchy's Telegram setup has two layers, and the order matters.
One bot per Pinchy instance. Users identify themselves here — it's how Pinchy knows which Telegram account belongs to which Pinchy user, with which permissions.
Attached to a specific agent. Users chat with this bot, Pinchy routes the conversation to the agent. Permissions and audit trail follow from the user's identity established in step 1.
If the main bot isn't configured, per-agent bot setup is blocked with a clear empty-state. This is intentional: letting users configure out of order would lead to a half-broken world where messages reach Pinchy without identity — a bug with good manners.
The agent's Telegram bot enforces the same permission model as the web UI. A user chatting through Telegram sees exactly what that user is allowed to see.
Telegram accounts map to Pinchy users via the main bot. External users may have different access than internal staff, even when they talk to the same agent.
Messages through Telegram land in the same audit trail as any other channel. Compliance gets one view across all channels.
Agents that draft instead of send still ask for approval through Telegram. The approval step is part of the agent contract, not a channel feature.
The agent's tools and knowledge base stay the same over Telegram. A support drafter can't suddenly read finance data just because the conversation happened on Telegram.
Learn More