Slack, Telegram and your own domain

An assistant that only exists on a web page gets used when people remember to go there. The integrations below move it to where people already are: the Slack channel where the question would have been asked anyway, the Telegram app on a phone, and a web address carrying your own name instead of Docutrain's.

Slack

The Slack integration puts Docutrain answers into channels. Your workspace gets a Docutrain bot, and specific Slack channels are each paired with a specific document. In a paired channel, anyone can mention the bot with a question — "@Docutrain what are the key guidelines?" — and the bot replies in the channel with an answer drawn from that document, so the whole team sees it rather than one person.

Direct-message the bot instead and it replies with a friendly orientation explaining how the integration works, listing which documents are available when some are already paired. In a channel that has not been paired with anything, it asks the person to contact their admin.

Access rules follow the document. For documents restricted to your owner group or to admins, the bot checks the Slack user's email address against Docutrain's records before answering, and politely declines when the person does not have access.

Slack support is live on the platform, but there is currently no self-serve setup screen in the dashboard. Installing the bot and pairing channels with documents is done together with the Docutrain team. Contact support to arrange it; you approve the bot through Slack's standard authorization screen, then tell the team which channels should be paired with which documents.

Telegram

Each document can have its own Telegram bot. People chat with it in the Telegram app, on a phone or a desktop, and get answers drawn from the document without signing in to anything.

One requirement comes first: the document's access level must be Public. The editor shows a Requires public access notice and keeps the feature disabled otherwise. There is no separate plan gate on Telegram itself, but because it depends on public access it is effectively limited to the plans that include it. See access levels explained and plans and limits.

Setting up the bot

The document editor's Telegram tab contains the instructions as well as the fields.

1. Open Telegram and message @BotFather, Telegram's official bot for creating bots.
2. Send /newbot and follow the prompts. Choose a display name, then a username — Telegram requires usernames to end in "bot".
3. BotFather replies with a bot token, a long string of letters and numbers. Copy it.
4. In Docutrain, turn on Enable Telegram bot, paste the token into Bot token, and enter the bot's username in Bot username. The username is optional, used for display and for generating the shareable link.
5. Save. Docutrain connects to your bot automatically and a green Bot configured confirmation appears.

Once the username is saved, a Copy button and an Open in Telegram link appear so you can grab the bot's address in the form t.me/YourBotName and hand it to your audience.

What chatting there is like

Sending /start shows a welcome message naming the document, /help explains how to use the bot, and anything else is treated as a question. Every answer opens with the document's title, followed by the response with simple formatting — bold, italics, and code styling are all Telegram supports.

Answers do not include the numbered reference citations you see on the web, because Telegram has no sensible way to display them. That is the main thing you give up. The rest behaves as expected: the bot remembers the last few exchanges so follow-up questions work, and questions outside the document's content are politely declined exactly as on the web. Telegram limits message length, so unusually long answers are truncated with a note; a narrower follow-up gets the rest.

Users chat anonymously, with no Docutrain account involved, and the conversations still appear in your document's conversation logs like any other chat. See conversations and moderation.

Helping visitors find the bot

When Telegram is enabled and a username is saved, web visitors chatting with the document see a Telegram badge in the chat toolbar. Clicking it opens a Telegram Bot Access panel with the Bot Link and a Copy button, step-by-step How to Use instructions, and an Open in Telegram button. Anyone already reading the document on the web can find the bot without you advertising it separately.

Custom domains

A custom domain serves your assistants from your own web address — docs.yourcompany.com rather than a Docutrain address. Visitors see only your brand in the address bar. Docutrain handles the hosting and issues the security certificate for your domain automatically. This requires the Business plan or higher; starting setup on a lower plan opens an upgrade prompt.

Setting it up

In Owner Settings, open the Configuration tab and find the Custom domain card.

Enter your subdomain in the Domain field and select Set up custom domain. Docutrain then shows two DNS records to add at your domain provider, such as GoDaddy, Cloudflare, or Namecheap. Step 1 is a TXT record proving you control the domain. Step 2 is a CNAME record pointing your subdomain at Docutrain. Copy the exact Hostname and Value for each, or use Copy instructions to grab both at once — convenient if someone else manages your DNS.

Step 3 is verification. DNS changes take time to propagate, usually within 30 minutes, after which you select Verify domain. On success you get Domain active with your live address and the verification date. If it fails, a Verification failed notice explains the problem; recheck the records at your provider and use Retry verification. Cancel setup and Remove are available at any time, though removing the domain means your documents are no longer reachable at that address.

What you get once it is active

Your document chats, collections, and share links are served from your domain, and the share links, QR codes, and embed codes generated in the dashboard automatically use it — see embedding on your website. A Custom favicon option appears in the same card so you can replace the Docutrain browser-tab icon. Sign-in is handled automatically: it completes through Docutrain and returns users to your domain with no extra steps on their part.

In some arrangements one organization's custom domain also serves the documents of a related organization. If yours has been granted shared use of another owner's domain, the Custom domain card shows a notice naming that domain and its owner instead of the setup form. The sharing is administered by the Docutrain team, so contact support if what you see is not right.

Email notifications

Docutrain sends styled emails at key moments with no configuration required. Invitations go to people without an account and are valid for 30 days; existing users get an "added to organization" message instead. Users receive account approval notices and one-time sign-in codes. Uploaders get a document-ready email with processing details and a chat link, or a processing-failed email with the reason and retry guidance. Conversation PDF exports arrive as an attachment, and shared intelligence reports go to the recipient. Only one needs an action: when an admin sets a contact-form recipient that is not their own address, that recipient must select Confirm email address within 7 days before messages are delivered.

Availability at a glance

Plan features can also be adjusted for individual organizations by arrangement. If an integration you expect is missing from the dashboard, the plan is the first thing to check.