Answer service for complex products

Your product is complex. Getting answers about it shouldn't be.

Imbizo turns your manuals, integration guides, release notes, training videos and recorded sessions into one place your partners and your customers can ask — and get an answer grounded in your own material, cited to the page it came from or the second of video it was said in.

Try it right now — ask the live assistant a question and get a grounded, cited answer in seconds. Or see more examples.

imbizo — Zulu for a gathering called so that questions can be put to the people who know the answers.

Live demo

Ask Imbizo about Imbizo

Demo mode: a limited number of questions, answered only from the Imbizo user guide. No sign-in, nothing stored about you.

§ 01Who asks

Two audiences ask about the same product

Integrators, resellers and installers need to build with it. Customers need to run it. Today both routes end at the same small team — yours.

Your channel

Partners who sell and integrate

A partner who can't find the answer doesn't file a ticket — they slow down, or they stop quoting your product. That is channel revenue, not just support cost.

  • Integration and API questions answered from your actual docs
  • Commissioning, wiring and configuration, straight from the manual
  • Certification and compliance answers with the source attached
  • Onboarding a new partner stops meaning a week of your engineers' time
Your customers

Customers who run it every day

The same "how do I…", "why is it doing this…", "is this within spec…" questions, arriving one email at a time. Answered from the documentation you already wrote.

  • How-to and troubleshooting, cited so they can check it themselves
  • Answers that stay current when you publish a new revision
  • Fewer repeat tickets, without a support team growing to match
  • A partner asks in Dutch and the answer comes back in Dutch, cited to the page it came from — whatever language that page is in

One corpus, different doors. Partner material, customer material and internal-only material live in the same system with different access — so a partner never sees what a customer shouldn't, and neither sees your internal notes.

§ 02Answers

An answer you can check

Ask in plain language. Get the answer, the document it came from, and the page — so the person reading it can verify it instead of trusting a chatbot.

  • Grounded in your material. Imbizo answers from the documents you load, and by default it will not fill a gap with what a general model happens to believe about your industry. Admins can allow general knowledge for their own staff; answers to everyone else stay grounded regardless.
  • Every claim carries its source. Document, page, and where you set it, the author — attached to the answer, not buried in a footnote.
  • If it isn't in your documentation, it says so. A clean "I can't find that in your material" is more useful to a partner than a confident guess — and it is enforced, not merely requested. An answer that can't point at a source is withheld and replaced with the refusal, rather than dressed up as prose.
  • Follow-ups suggested from your corpus, so the next question is one your documentation can actually answer.
An Imbizo answer showing the source document it is grounded in, the answer text, a numbered citation to page 9 of the source, and suggested follow-up questions.

Real screenshotImbizo answering from documentation loaded into it.

§ 03Documentation gaps

Every question you can't answer is a page you haven't written

Imbizo refuses when your documentation doesn't cover something. Then it keeps score. The gaps arrive as a ranked list, in the words your partners and customers actually used.

Least-grounded questions

Last 90 days
Does the wrist joint need re-greasing after a firmware rollback?0 src
What is the minimum ceiling height for the overhead mount?0 src
Can I run the calibration routine without the reference plate?1 src
Which cable glands are rated for washdown environments?2 src

Most-asked questions tell you what belongs on page one. Least-grounded questions tell you what to write next — and top askers tell you which partner needs a call rather than a document. Everything else an answer service does is a way to spend less. This is the part that makes your documentation better.

§ 04Audio & video

Your answers aren't only in PDFs

Half of what your team knows was said out loud — in a training video, a commissioning walkthrough, a partner webinar, a recorded support call. Imbizo ingests audio and video as first-class sources, not as an afterthought.

What was said

Transcription with word-level timestamps and speaker separation, so any sentence maps back to the exact second it was spoken.

What was on screen

Slides, terminal output, part numbers, error codes and UI text are read off the frame — findable even when nobody read them aloud.

What was shown

Scene-by-scene visual description of the demonstration itself — the cable being connected, the panel being opened, the gesture the words skipped over.

A recording is only useful if you can get to the right moment in it. Imbizo cites the second, not the file — clicking the citation opens the recording where the answer was given, instead of handing someone a two-hour video and wishing them luck.

Ingests .mp4 .mov .m4v .webm .mkv and .mp3 .m4a .wav .aac .flac .ogg alongside your PDFs and documents — searched together, in one answer, under the same access rules.

Where this runs. Your documents, your search index and your media are stored in the EU, and answer generation runs on EU-hosted models under no-training terms. Transcription and frame understanding currently use specialist providers outside that EU envelope; we'll tell you exactly which before you upload anything, and moving them into it is on the roadmap. We would rather say this than let you find it in a DPA.

§ 05Access

Nothing is open by default

One answer service for partners, customers and your own team only works if access is a setting you can inspect — not a promise in a contract. In Imbizo it's a grid you can see, applied before anything is searched.

  • Access by team, not by person. Tick a cell to let a team read a collection. Add a partner to the Partners team and their access is already right.
  • Inheritance you can read off the screen. Grant a parent team and child teams follow, shown as a locked tick — no guessing why someone can see something.
  • Videos obey the same rules as documents. A partner-only walkthrough is not reachable by a customer, citation link or not.
  • An activity log of who changed access, who added documents and what was asked — and you can export the whole question log as CSV or JSON — every question, the answer that was given, and how many sources backed it. The evidence a customer or auditor will eventually ask you for.
The Imbizo access matrix: teams as rows, document collections as columns, and tick boxes granting each team read access to a collection.

Real screenshotThe access matrix — teams down, collections across.

01

Everyone signs in

Access to the product runs through an authenticated sign-in. Remove someone from a team and their answers stop with them.

02

Applied before the search

A question only ever searches the collections that person's teams are granted. Material they aren't entitled to isn't stripped out afterwards — it is never retrieved.

03

Source files too

Opening a cited page or jumping to a cited moment re-checks the same permission against the file itself. A citation link is not a way around the grid.

04

Your own partition

Your search index, your documents and your media sit in storage separated per customer, in the EU. Records in the shared database are scoped to your tenant on every query.

§ 06How it works

Start with three folders

There is no documentation platform to move into, no taxonomy project, and nothing to rewrite before you start.

A folder per audience

Partners, Customers, Internal. What goes in the Partners folder is what partners can be answered from. When you need more, the same folders carry team-by-team access, nested teams and delegated admins — but you can start with three.

Add your files to it

Manuals, PDFs, Word and PowerPoint, release notes, recordings. Add a file and it is processed and answerable on its own — no conversion beforehand, no separate ingest step afterwards.

Delete to retire

Superseded a manual, or replaced a training video? Delete it and it stops being answered from. Keeping the corpus current is one click, not a content project.

It sits beside your documentation system, not in place of it. Confluence, a docs site, GitHub, SharePoint, a shared drive — keep publishing exactly as you do today and put a copy here. One folder takes all of it: manuals and PDFs, Word and PowerPoint, podcasts and recorded calls, training video. In PDFs, the diagrams, charts and screenshots are read rather than skipped as pictures. A single question searches every one of those sources at once.

§ 07Commitments

What you get, stated plainly

Four things we hold ourselves to — say them back to your own partners and customers.

Answers

From your documents

Specifications, tolerances and part numbers are quoted from your material — never invented, never averaged from something a model read elsewhere.

Citations

Always attached

Every answer links back to the source: the page of the manual, or the moment in the video.

Refusal

No source, no answer

When your documentation doesn't cover it, Imbizo says so — and the dashboard tells you exactly where the hole is.

Residency

Stored in the EU

Documents, index and media in the EU; answer generation on EU-hosted models under no-training terms. The media pipeline is not there yet, and we say so.

§ 08Fit

Built for companies whose product needs explaining

Small and mid-size companies with a technical product and a partner channel — where the AI talent belongs on the product, not on the support stack around it.

Robotics & machine vision Industrial & scientific equipment Med-tech & regulated devices API & developer platforms OEM and white-label suppliers Technical B2B software

The tell: if your partners get answers today by emailing your engineers, digging through a shared drive, or scrubbing through a two-hour training recording — that's the problem Imbizo removes. And if you resell under someone else's brand, it carries your logo, your wording and your own CSS, so it looks like your product rather than a vendor's.

See it answering on your own material

Send us a slice of your documentation — a manual, an integration guide, one training video. In a 30-minute session we'll show it answering your real questions, with the citations, before you decide anything.

hello@imbizo.ai

Book a demo

A 30-minute working session on a sample of your own documentation. We reply within one business day.

That didn’t go through — please email us directly at hello@imbizo.ai.

Thank you.

Your request is on its way — we’ll come back to you within one business day.