VoraDecide which business answer is approved.
Business knowledge needs an owner and an applicability rule. Before evaluating an assistant, decide which source controls each answer, who approves changes and what happens when no approved answer exists.
Finding a page, extracting readable text and approving an answer are distinct steps. Test them for the specific website or document rather than assuming one implies the next.
Build a bounded source register
Record the source location, owner, covered subject, applicable client or location, access limits and effective date. Keep withdrawn versions identifiable so staff can explain why an answer changed.
A hypothetical service-area assistant may need only an approved location list, opening hours and an escalation policy. An account assistant needs different authorization and source rules.
Review source readiness before expanding the source set.
Inspect what was actually extracted
Compare the readable representation with the source, especially tables, footnotes, scanned material and conditions attached to prices. Record any missing or ambiguous content.
Confirm that processing completed before judging retrieval. Then use representative questions to inspect whether the relevant passage can be found and used correctly.
This is a review method. It does not claim that Vora supports every file format, crawl condition, OCR task or source connector.
Resolve conflicting and changing answers
If the website says 24 hours and an internal document says 48 hours, identify whether they cover different locations, dates or services. Ask the business owner which rule applies.
The source-authority guide explains approval, effective time and scope. Search relevance alone does not establish policy authority.
For changing facts, specify whether the assistant may use a stored answer or must consult the current system. Review prices and availability for that distinction.
Test both permitted and unavailable answers
Use approved questions, missing-source questions, conflicting sources, withdrawn information and a request for restricted data. Define the expected answer or handoff before running the case.
Download the boundary worksheet and inspect its hypothetical example.
Prepare an evaluation with your source owner and questions. Keep provider, persistence, refresh and permission requirements explicit for the chosen setup.
Draft from a website and keep sources current
Vora drafts an agent from a business website; you review and complete the draft before it goes live.
Knowledge sources can be updated or re-synced so agents answer from the latest approved content. Record who approves each change and test the affected questions afterwards.
Confirm sources, missing answers and escalation
Confirm the approved business sources, missing-answer behavior and escalation for the configuration you evaluate.
Keep shared business knowledge separate from any customer-specific information. With the customer's consent and within one client workspace, agents can recall details from earlier conversations with the same customer; that recall is separate from the business sources on this page. Review website chat boundaries for the conversation side.