.svg)
What a documentation portal is
A documentation portal is the website where a company publishes how its products work: installation guides, specifications, how-tos and reference pages. The best ones feel personal. Each reader lands on the docs for the products they bought, in the language they read.
Reading your docs from a lab bench in Brazil
Solvane makes lab incubators, plus the sensors and cloud dashboard that monitor them, and sells to labs in the US, Germany, Japan and Brazil. Beatriz manages a cell biology lab in São Paulo that runs three Solvane incubators.
Monday, 7:50 am: her equipment, her language
Beatriz signs in to Solvane's docs. The home page is in Portuguese and shows the guides for her two incubator models and the humidity sensor her lab added last month, plus a new page on the dashboard alerts she uses.
9:30 am: an answer she can check
Her incubator sends a humidity alert every hour. She asks, in Portuguese, how to raise the alert threshold. The answer comes back in Portuguese from the sensor guide, with a link to the exact section, so she knows it's Solvane's own instruction and not a guess.
11:10 am: she sorts out the drift herself
One sensor reads two points high. She searches "sensor drift", opens the calibration steps for her model and works through them at the bench on a tablet. Twenty minutes later the readings match, with no ticket raised.
2:40 pm: a question the docs can't answer
An auditor wants a calibration certificate for the new sensor, and the docs don't cover it. Beatriz opens the chat on the page she's reading. The assistant says it has no page on certificates and passes her to Solvane's service team in Brazil, with her lab, her models and what she asked already attached. A specialist picks it up, and since she's heading into the lab, she asks for the reply by email. Until it's closed, she can check where it stands from her portal.
Wednesday: a new technician gets started
Rafael joins her lab. He reads the installation guide in Portuguese and marks one step as unclear, with a note that the photo shows an older door hinge. His note goes straight to Solvane's docs team.
Friday: the docs team behind it
Ines, Solvane's documentation lead, sees in analytics that labs searched for "calibration certificate" twelve times this week with no good result. She writes the page, reviewers approve the German, Japanese and Portuguese versions,, and swaps in the right photo for Rafael's step.
What your readers can do
Open on the docs for what they own
Each reader's portal is personalized to their products, their role and their language. A lab with two incubator models sees those two, not your whole catalog.
Get answers in their own language
Readers search with a question or a part number, or ask the assistant in plain words. Answers come from your published docs, cite the page and section, and arrive in the reader's language, reviewed by a person before it went live.
Fix things at the bench
Step-by-step procedures for calibration, setup and troubleshooting are written per model and readable on a phone or tablet. Readers finish the job themselves and get back to work.
Reach your team the way they like
When the docs run out, readers ask in the chat on any page, send a request from the portal, or email you. Their account, products and question travel with it to the specialist for that product, and they can follow its progress.
Tell you what's unclear
Every page takes a rating and a note, so a confusing step gets flagged once and your writers see it.
What your docs and support teams get
Reader questions, requests and page feedback all arrive in a single team inbox, split into queues per product line and region. Specialists claim a question, pass it along with a private note when someone else knows more, and answer by chat or email while seeing the reader's products and past requests. Reports on searches, low-rated pages and unanswered questions tell your writers exactly which page readers were hunting for.
What changes when your docs work this way
Readers solve more on their own, at any hour. Sourced answers and step-by-step procedures for each model are there in their language whenever the lab is running, not only when your office is open.
A missing page gets written once, for every market. When analytics show a gap, you write the page and reviewers approve each language, so the question stops coming back from every country.
Your specialists start from the reader's context. Products, account, the question and the pages already read come with every request, so a specialist's first answer usually closes it.
Translations readers can rely on. A person who knows the language approves each page before it's public, so a lab in Osaka and a lab in São Paulo follow the same procedure.
Docs, answers and reader help live together. The portal, the assistant, feedback and the inbox run on one platform instead of a docs site, a chat tool and a support mailbox that never talk.
Where writers and AI meet
The assistant answers only from docs you've published and shows its source every time. When a question isn't covered, it says so and hands the reader to a person, along with what they asked and which pages they read. It doesn't publish, translate or edit pages on its own, and each thing it does is recorded in a log. Your writers and reviewers stay in charge of every word readers see.
How to build your documentation portal
- Bring in your docs. Import pages from Confluence, Notion, SharePoint, Google Drive or Contentful, or write them in place, and label each one by product line and model.
- Bring in your customers. Pull customer accounts and the products each one owns from HubSpot or Salesforce, or upload a list, so every reader lands on their own equipment.
- Choose your languages. Turn on translation for each market and name the person who reviews each language before it's published.
- Decide what's public. Keep general guides open and put model-specific procedures behind customer sign-in, under your brand and web address.
- Add chat, the assistant and your team. Point the assistant at published docs and set up the queues and people who pick up reader questions.
Works with your existing tools
Confluence, Notion, SharePoint, Google Drive, OneDrive, Box and Contentful for bringing in manuals, specs and diagrams, HubSpot and Salesforce for customer accounts, and email and web chat for reader questions. Webhooks and an API reach the rest, among more than 30 sources.
Related
| Documentation portal on MatrixFlows | A standalone docs site | |
|---|---|---|
| What a reader sees first | Docs for the products they own, in their language | The full catalog, in English |
| Other languages | Translated per market and approved by a reviewer | A browser translation and some hope |
| Getting help from the docs | A question in plain words, answered with the page cited | Keyword search over page titles |
| When the docs run out | Chat, a request or email, routed to the right person with context | A generic contact form |
| Knowing where things stand | Readers follow each open request from their portal | Waiting for an email that may not come |
| Reader feedback | Ratings and notes reach your team's inbox | A comment box nobody reads |
| Finding gaps | Unanswered searches show up in analytics | Support mentions it months later |
A documentation portal your customers trust is one piece of customer operations on MatrixFlows, alongside your help center and support inbox. The same platform serves your partners and employees too.