01↗
Knowledge & sources
Turn documentation into cited answers
Import knowledge, inspect indexing and publication status, and locate sources by product and version. Customers get steps to follow; teammates get something they can check.
BUILT FOR B2B SOFTWARE SUPPORT
Answers with sources.
Handoffs with context.
Connect product docs, troubleshooting experience and your support team. Let AI handle familiar questions. Give people the context to solve the complex ones, so customers can move forward without starting over.
Knowledge answers · Troubleshooting · Human support
DAZHOU / SUPPORT FLOW↗
Q
Customer
After upgrading to 3.2, why can’t a member see reports?
DazhouDeskSOURCE INCLUDED
Check the member’s Report Viewer role and the applicable version.
↗Roles & permissionsv3.2
A teammate can take it from here
↗
Question, attempts, sources — togetherContext prepared · Human handoff
✓From a customer question to a next step someone can act on.
DAZHOU DESK
Customers need a next step they can act on.
↓01 / A SUPPORT CONVERSATION
Pick up the problem. Keep the context.
Choose a scenario to explore sources and a handoff. This is a workflow illustration with preset content; it does not call a live AI model.
DazhouDesk workspace
Workflow examplePermissions · v3.2EXAMPLE / 01
02 / BEYOND ONE ANSWER
Keep the know-how in your team.
From your first document to your next software release, track what an answer relies on and what changes.
02↗
Human workspace
Give people the whole conversation
Pass along the question, attempted steps, sources and risks. A teammate takes over the same conversation and carries it forward.
03↗
Corrections & evaluation
Review a correction before reusing it
Submit a support correction as a knowledge draft. Review and publish it, then check historical questions for regressions before relying on the update.
04↗
Operations & controls
Set boundaries for models and tools
Connect an OpenAI-compatible model and set usage budgets. Admit diagnostic connectors after scenario validation. Controlled actions require approval and keep an execution record.
One thread, from question to improvement.
- 01Prepare
Import product docs and known issues
- 02Answer
Show the relevant version and sources
- 03Support
Hand off context and keep working
- 04Improve
Review corrections and run regressions
03 / START WITH YOUR SUPPORT
You don’t need to move everything at once.
Choose one recurring problem, gather reliable docs, and test the path from answer to handoff. Built for software support, implementation and customer success teams of 3–20 people.
Talk about your teamGETTING STARTED↗
Start with one support scenario
- 01
Choose a real problem
Gather the relevant product docs, version notes and troubleshooting steps.
- 02
Name the people involved
Agree on knowledge reviewers, handoff owners and handling rules.
- 03
Test before using it
Configure a model and budget, then check sources and handoffs with historical questions.
04 / BEFORE YOU START
Questions worth asking before launch.
01Who is DazhouDesk built for?
B2B software, SaaS and business-system support teams dealing with permissions, version differences, integrations and product workflows. Start with web support and a human workspace.
02What if the docs don’t contain an answer?
The workflow can hand off to a person when evidence is insufficient, risk is high, a model fails or a budget is reached. Customers can ask for a person, with the collected context kept for the handoff.
03Can we bring our own model?
Yes, through an OpenAI-compatible interface. Cost and availability depend on your chosen provider. Test it against your own docs and questions; a saved configuration alone does not establish answer quality.
04Will it change customer business data automatically?
Start with knowledge answers and read-only diagnostics. Controlled actions use explicit parameters, approvals and execution records. Connector availability depends on scenario tests and admission status.
05How do we start, and what does it cost?
Email us about your product, team size and main support problems. We’ll discuss scope, deployment and model budget before pricing. This site’s examples and contact form do not require account passwords or API keys.
NEXT STEP / LET’S TALK
Give recurring questions a better way forward.
Tell us about your product and the support problem that takes the most time. Start with a small set of real scenarios and find a setup that fits your team.