Ask a question. Follow the evidence.
Give people a conversation with your knowledge. Answer from connected sources, show the citations, and carry the context into the next question.
What happens after the kickoff?
- You ask
- Who owns the customer handover?
- Pragence answers
- The customer success owner coordinates it.
- You can verify
- Customer playbook · Getting started
What you can do with chat.
-
Answers people can check.
Citations connect the response to the passages used to produce it. People can read the source behind an answer.
Answer → citation → source -
A conversation that continues.
Thread context supports follow-up questions, and streaming lets people read the answer as it is written.
Threads + streaming -
A clear response to missing knowledge.
Configure how the assistant handles questions without supporting sources. It can decline, or clearly label general knowledge when that option is enabled.
Make knowledge gaps visible
Explore chat in action.
Try the example with sample content. Inspect the sources, switch views, and follow the knowledge into an answer.
Find what you mean.
Search by meaning and exact words, with results ranked for relevance.
Give your agents structure.
Turn facts buried in documents into defined, reviewed records your agents can use.
Build on the same foundation.
Use the API or MCP to bring connected knowledge into your own experience.
Where can I offer chat?
Use the website widget, a hosted chat experience, configured messaging channels, or your own application. Each channel has its own setup requirements.
Does an answer authorize an action?
No. Actions use a separate proposal and approval flow. Reading an answer does not approve a follow-up or record change.
See what your knowledge
can do.
Start with Knowledge, or explore Admissions with a walkthrough of your team’s process.