Slack, Telegram and your own domain

An assistant that lives only on a web page gets used when people remember to go there. Which is to say: for about two weeks after you announce it.

The three integrations here move it to where people already are. The Slack channel where the question was going to be asked anyway. The phone in someone's pocket. And a web address with your name on it instead of ours.

Slack

The Slack integration puts answers into channels, and the channel part is the point.

Your workspace gets a Docutrain bot, and specific channels are each paired with a specific document. In a paired channel, anyone can mention the bot with a question, and the bot answers in the channel, drawing on that document.

So the answer lands in front of everyone rather than in one person's DMs. The next four people with the same question read it instead of asking it. That is a different thing from a private chat interface, and usually a better one for a team.

Direct-message the bot and it explains how the integration works and lists which documents are available. In an unpaired channel it points the asker at their admin rather than failing silently.

Access rules follow the document. For anything restricted to your owner group or your admins, the bot checks the Slack user's email address against Docutrain's records before answering, and declines politely when they do not have access. A Slack workspace is not a way around your access levels.

Slack support is live, but there is no self-serve setup screen yet. Installing the bot and pairing channels is arranged with the Docutrain team: you approve the bot through Slack's own authorization screen, then say which channels should be paired with which documents.

Telegram

Each document can have its own Telegram bot, and people chat with it in the Telegram app without signing in to anything.

One requirement comes first: the document 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, but since it depends on public access, it inherits that plan requirement in practice.

Setup takes about three minutes and happens mostly in Telegram. Message @BotFather, Telegram's official bot-making bot, send /newbot, choose a display name and a username ending in "bot", and it hands you a token. Paste that token into the document's Telegram tab, add the username, and save. Docutrain connects to your bot and confirms.

Once the username is in, you get a copy button and an Open in Telegram link for the bot's t.me address, ready to hand to your audience.

Chatting there behaves as you would hope. /start names the document, /help explains itself, anything else is a question. The bot remembers the last few exchanges so follow-ups work, and it declines out-of-scope questions exactly as it would on the web.

What you give up is the citations. Telegram has no sensible way to display numbered references, so answers arrive without them. If verifiability is the reason you chose Docutrain, be deliberate about which documents you put on Telegram: it is excellent for a public FAQ or a conference handout, and a poor fit for anything where a reader needs to check the source before acting on it.

Telegram also caps message length, so an unusually long answer is truncated with a note, and a narrower follow-up gets the rest. Conversations there land in your normal conversation logs like any other chat.

Web visitors reading the document see a Telegram badge in the chat toolbar with the bot link and instructions, so people find it without you advertising it separately.

Your own domain

A custom domain serves your assistants from docs.yourcompany.com instead of a Docutrain address. Visitors see only your brand in the address bar. Docutrain handles the hosting and issues the security certificate automatically. Business plan and above.

Setup is the standard DNS dance, made about as painless as it can be. Enter your subdomain, and Docutrain gives you two records to add at your provider: a TXT record proving you control the domain, and a CNAME pointing it at us. Copy instructions packages both at once, which is what you want when someone else runs your DNS and you are sending them an email about it.

Propagation usually takes under 30 minutes, then you verify. A failure explains what went wrong and offers a retry rather than leaving you to guess.

The payoff is broader than the address bar. Once the domain is active, share links, QR codes and embed codes generated anywhere in the dashboard automatically use it. So the poster you print, the link you paste into an email and the snippet on your website all carry your domain without you having to remember to rewrite anything. A custom favicon control appears in the same card, replacing the Docutrain browser-tab icon.

Sign-in is handled for you: it completes through Docutrain and returns people to your domain, with nothing extra on their part.

If your organization has been granted shared use of another owner's domain, the card names that domain and its owner instead of the setup form. That arrangement is administered by the Docutrain team.

The emails nobody has to configure

Docutrain sends styled emails at the moments that need one, with no setup. Invitations, valid 30 days. Account approvals and one-time sign-in codes. A document-ready email with processing details and a chat link, or a processing-failed email with the reason and what to do next. Conversation PDF exports as attachments. Shared intelligence reports to their recipient.

Exactly one needs an action from anybody: when you set a contact-form recipient that is not your own address, that person has to confirm within seven days before any message reaches them. Which is the same principle as everywhere else in the product. Nobody gets mail they did not agree to receive, and nobody can point your contact form at an address they do not control.

What needs which plan

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