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.
Demo mode: a limited number of questions, answered only from the Imbizo user guide. No sign-in, nothing stored about you.
Press Tab to select this question, or type your own in the box — then hit Ask.
Want to see it on your material? Book a demo · Read the guide (PDF).
The live demo is paused right now.
You can still see it answering on your own material — book a 30-minute demo and we'll run it against a slice of your documentation.
Integrators, resellers and installers need to build with it. Customers need to run it. Today both routes end at the same small team — yours.
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.
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.
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.
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.
Real screenshotImbizo answering from documentation loaded into it.
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.
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.
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.
Transcription with word-level timestamps and speaker separation, so any sentence maps back to the exact second it was spoken.
Slides, terminal output, part numbers, error codes and UI text are read off the frame — findable even when nobody read them aloud.
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.
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.
Real screenshotThe access matrix — teams down, collections across.
Access to the product runs through an authenticated sign-in. Remove someone from a team and their answers stop with them.
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.
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.
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.
There is no documentation platform to move into, no taxonomy project, and nothing to rewrite before you start.
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.
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.
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.
Four things we hold ourselves to — say them back to your own partners and customers.
Specifications, tolerances and part numbers are quoted from your material — never invented, never averaged from something a model read elsewhere.
Every answer links back to the source: the page of the manual, or the moment in the video.
When your documentation doesn't cover it, Imbizo says so — and the dashboard tells you exactly where the hole is.
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.
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.
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.
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.