A floating chat bubble on a marketing page works. The same bubble on a printed handout doesn't — paper can't run scripts. A full-page chat inline is perfect for a help center; a tiny button might be better on a pricing row.
Different surfaces need different wrappers. DocuTrain offers five formats so the same document chat fits where your audience already is.
Where to find them
Open any document → Embed & Share. You'll see five tabs:
[ QR Code ] [ Button ] [ Widget ] [ Inline ] [ API ]Each tab generates copy-paste code (or API notes) and a live preview. Colors, text, and position stick with the document — reopen later and your choices are still there.
1. QR Code — chat from paper
A QR image that opens the document's chat URL — great when people have phones but not your site in front of them.
Examples:
- Conference handouts and posters
- Stickers on equipment or packaging
- Slides at the end of a talk
- Business cards linking to your knowledge base
Download as SVG for sharp printing. The QR only routes people to the document — passcodes and access rules still apply when they arrive.
2. Button — intentional fullscreen chat
A styled button opens chat in a focused overlay. DocuTrain gives you HTML that links its stylesheet, places the button, and loads a small script.
You can tune button color, label, and optional title from the dashboard, with a live preview.
Good for: product pages, pricing CTAs, docs sections, anywhere you want a deliberate "start chat" moment.
3. Widget — the floating bubble
The familiar corner bubble that expands into a chat panel. Usually a single <script> tag with attributes for document slug, colors, position, title, and greeting.
Good for: marketing sites, blogs, anywhere you want help present but not dominating the layout.
4. Inline — chat is the page
A plain <iframe> you drop into your layout at whatever size you want. The Embed tab gives you a starting markup block; adjust height and width for your template.
Good for: dedicated "Ask our AI" pages, lesson pages in a course, wikis that support iframes, customer portals with a help section.
5. API — your own interface
For Unlimited plans, DocuTrain exposes a documented HTTP API for chat — streaming token-by-token or a single completed reply — so mobile apps, bespoke UIs, or voice products can use the same answering engine without an iframe.
This tier is aimed at teams building their own surface around DocuTrain (not just pasting a snippet). If you need it, your account team or docs cover authentication and request shape.
Picking the right format
| Situation | Format |
|---|---|
| Print, cards, signage | QR Code |
| Specific CTA on a page | Button |
| Persistent help across a site | Widget |
| Full-page or embedded help section | Inline |
| Custom app or native client | API (Unlimited) |
Most organizations mix two or three — e.g. widget on the marketing site, inline on support, QR on event materials.
One experience, many containers
Every format reads the same document settings: access level, custom prompt, character, citations. Update the document once; every embed reflects it. You're not maintaining separate copies — only choosing how the chat is framed.
→ Next: How Real Businesses Use DocuTrain: A Use-Case Gallery