Meeting Users Where They Are: Telegram, Email, and the Web

The best chat experience in the world is wasted if it lives somewhere your users don't go.

If they're field technicians or mobile-first audiences, they're often on Telegram. If they're executives, the most reliable channel is still their inbox. Some are on your website, some are on someone else's, some are scanning a QR off a printed handout.

DocuTrain is built to reach all of them. This post walks through every channel the platform supports — what each looks like, when to use it, and how the access controls and character branding stay consistent across all of them.

The four channels

All four run on the same DocuTrain answering flow. The character, custom prompts, access controls, and document content stay consistent no matter which surface someone uses. You configure once; you reach everywhere.

1. The web — your branded landing page

The simplest channel: a DocuTrain-hosted landing page at your-owner-slug.docutrain.io or, with custom domains, at docs.yourcompany.com.

Two layout modes are available, configured under Owner Settings → Branding:

• Gallery — Grid of document cards. Use when you have many documents and the user is browsing.
• Standard — Hero image + company-intro sections + document selector. Use when the page itself needs to sell your brand alongside the documents.

The landing page assembles itself from owner fields: logo, hero image, company intro, use statement, contact info, accent color. There's no separate CMS to maintain. You fill in the owner settings, you get a landing page.

For most customers, the landing page on a custom domain is the canonical home of their DocuTrain deployment. Everything else — embeds, bots, emailed links — eventually leads back here for users who want the full experience.

2. The web — your customer's site

We covered this in detail in Embedding DocuTrain Anywhere, but in the channels picture it's worth restating: the embed surfaces are how DocuTrain reaches users while they're somewhere else.

• Floating widget on a marketing page — passive presence, available when needed
• Button on a specific product page — active call-to-action
• Inline iframe on a dedicated knowledge-base page — chat is the page
• QR code on a printed conference handout — chat from paper
• Character hub on a homepage — full document library + AI character as the entry point

These surfaces work on any website. They're a script tag, a div, an iframe. WordPress, Webflow, Notion, custom sites, Shopify — if you can paste HTML, you can embed DocuTrain.

DocuTrain is set up so embeds work on ordinary sites without a long IT checklist. Your passcodes, memberships, and document permissions still apply every time someone chats — convenience for setup doesn't mean open access to everyone.

3. Telegram — chat on the platform half your users actually live on

Telegram has 900 million monthly active users. For most of them, Telegram is the messaging app — not WhatsApp, not Signal, not Discord, not anything else. If your audience includes anyone in Eastern Europe, the Middle East, Iran, Brazil, or Southeast Asia, Telegram is probably how they communicate.

DocuTrain treats Telegram as a first-class channel. Each document has a Telegram tab in the editor where you can connect a Telegram bot. Once connected:

• Users send a message to your bot
• DocuTrain answers the same way it would on the web
• The reply comes back in Telegram-friendly formatting
• The conversation appears in your DocuTrain history like any other chat

Access control still applies. A passcode-protected document requires the passcode (entered as a Telegram command) before chatting starts. An owner-restricted document requires the user's Telegram account to be linked to a DocuTrain user with access. The five-level access model from the access control post is identical on Telegram.

A Telegram bot can be configured per-document. A medical society might have @nephrology_guidelines_bot for one guideline, @transplant_protocol_bot for another. Or one bot serving a whole owner — at the platform level, you decide.

Use cases:

• Field workers in industries where laptops aren't practical and a Telegram message is faster than opening a browser
• International audiences for whom Telegram is the default communication channel
• Member benefits for organizations whose members already use Telegram for community discussion
• Conference-time access where attendees prefer mobile

You paste the bot credentials DocuTrain asks for in the Telegram tab; the product stores them securely with that document.

DocuTrain goes deep on Telegram for messaging. We don't try to add every other chat app — WhatsApp, Discord, Teams, and the rest each have their own platform rules — but Telegram covers a huge slice of mobile-first and international audiences.

4. Email — the channel everyone still uses

Even users who don't use Telegram daily always have an inbox. DocuTrain uses email — delivered through Mailgun — for the async flows where a chat interaction isn't the right format:

The last one is worth a closer look. A user finishes a long chat with the AI — say, ten questions about a clinical guideline — and clicks "Export to PDF". DocuTrain renders the entire conversation as a styled PDF (questions, answers, citations) and emails it to them. They can forward it to a colleague, attach it to a case file, or print it. The chat becomes a portable artifact.

Each type of email has its own template so the copy stays clear and relevant for that moment.

What stays consistent across channels

This is the part that makes the channel strategy actually work: the experience doesn't change across channels.

Configure a custom prompt once on the document, and Doc (or whatever name you chose) speaks the same way on the web, in the embed, and on Telegram. Set the access level to passcode-protected, and the passcode requirement applies everywhere. Citations show on every surface.

This is a design decision that's easy to underestimate. Most platforms that try to be multi-channel end up with subtly different behavior on each one — the Telegram bot answers differently than the web chat, the embed widget loses citations. DocuTrain treats the channels as different containers for the same chat experience, not different chat experiences in their own right.

Picking your channel mix

A practical guide based on who your audience is:

The platform's job is the boring part

A lot of what makes DocuTrain reliable — safety checks, how material is segmented for search, and strict permissions — is invisible to end users. They don't see it. They don't care about it.

The platform's job is to make sure those invisible parts work the same way across every channel. The chat character on your website is the same character users see on Telegram. The access control on the embed matches the access control on the landing page. The custom prompt is the custom prompt, everywhere.

That consistency is what lets you confidently say "Just ask Doc" — using your own character name — no matter where the user happens to be. Wherever they are, the same assistant is there too — with the same tone, the same facts, the same citations, the same brand.

That's the whole pitch.