HomeGrounded answers
Answers only from what you approved. Sources under every one.
An assistant that speaks for an organization has to be right, and has to be able to say where it got that. Serviceplane retrieves from the pages, documents and answers your team approved, cites them, and says nothing when they don't cover the question. Here is exactly what that means and how it is enforced.
The rules, and where they live
Grounded is a set of enforced rules, not a promise in a prompt
Each rule below is code in the answer path that every channel shares — chat, phone, text, email and the staff copilot. A model can be told to behave; these are the parts that do not depend on it.
Approval gates answering
Pages and documents are ingested into versioned articles with a status. On public channels only approved content is searched. Re-crawling a changed page bumps its version and drops it back to review, so superseded text stops answering the moment the source changed.
Status: draft · review · approvedApproved answers win, word for word
Your team can write the answer to a question once, as an answer card. When a question matches a card closely enough, the card's text is returned verbatim — no model rewrites it. A whole FAQ can be imported in one step.
Answer cardsEvery answer carries its source
The passages the answer was built from are shown under it as links to the page and section — one link per page, never five passages of the same article. The chat widget also lists which sources the assistant is allowed to search, so a resident knows where the answers come from before asking.
CitationsNo source, no answer
When nothing approved matches, the assistant abstains and offers a person — it never falls back to what a model happens to know. Each abstention is recorded as a gap in a review queue, so the missing page gets written rather than guessed at.
Abstain, then reviewSources are ranked, and disagreements are flagged
Each knowledge source carries a precedence. When two approved passages answer a question differently, the more authoritative one wins, the answer says another source differs, and a conflict item lands in the same review queue with both pages named.
Precedence · ConflictsRecord data only after identity
Facts from a person's own record — an account balance, a parcel's assessment — appear in a public-channel answer only after that person has proven identity with what the record already holds. Staff see records in their own workspace; the public path never does without the check.
Identity verificationPolicies only make it more conservative
Rules written in plain English — "anything about a payment dispute goes to Billing", "never discuss an open court case" — are compiled into topic and signal matches that refuse, escalate or route. A policy can never add knowledge or unlock record data; it can only narrow what the assistant does.
Plain-English policiesMeasured before it is live, and every night after
A channel starts in shadow mode: every question is answered to a private log while staff keep answering, and reviewers grade the pairs. Your own question set runs as an accuracy evaluation — pass phrases, expected sources, expected abstentions — with a model judge as a second opinion on every answer, nightly if you want it. The bar is 95% by default; you set it.
Shadow mode · EvalsThe public can flag an answer, and the flag reaches the right queue
"Was this helpful?" under every answer. A no asks why — wrong, out of date, didn't answer — and opens a review item carrying the question, the answer and the passages it used, so a wrong answer becomes a fix to a page, not a lost complaint.
Feedback → review queueKnowledge has owners and expiry dates
Each source and article can name an owner and a validation cadence. Overdue or expired approved content is flagged to its owner; a page that has vanished from your website is flagged too, and the article keeps answering only until a person decides. Nothing silently goes stale.
GovernanceOne answer, taken apart
What the visitor reads, and what it was built from
Illustrative wording. On a real deployment the sentence comes only from the passage on the right.
Both events share one trace id, so "why did it say that" is a single query.
Plain words
What grounded means here, and what it does not
It means
- Retrieval is limited to content with an approved status, filtered by the reader's permissions in the database query itself
- The model is given the passages and told to answer from them; the passages are shown to the reader
- No approved passage shares anything with the question → abstain and offer a person
- An approved answer card is returned verbatim, with no model in the loop
- Every answer is an event with the passages it used, kept on an append-only log
It does not mean
- That a model can never misread a passage — it can, which is why shadow mode, the judge, reviewer verdicts and public flags exist
- That the assistant knows things your pages don't say — it doesn't, on purpose
- That approval is automatic — a person approves, unless you choose to auto-approve a trusted source
- That one model is hard-wired — you choose the model chain per task, and swapping it changes nothing above
Questions we get
The ones that come up in every evaluation
Can it still hallucinate?
Which model does it use?
What happens when a page changes?
Can we use our PDFs and Word documents?
Can we test it against our old tickets before going live?
Does the answer show the source to the visitor?
Read next
The record behind every answer, and who it is built for
See it answer from your own pages — and decline what they don't cover.
We build a workspace from your public site, ask it your hardest questions, and show you the passages behind every answer and the queue behind every miss.