Are we allowed to? Answered from your policies, clause quoted
Staff describe what they are trying to do and get the policy position with the clause it comes from. Where your policies are silent, the answer says so instead of reasoning its way to a permission.
Compliance · Someone asks · 7 steps · Reads your documentsA person is asked at “Ask a person”
QuestionQuestion
RetrieveRetrieve
AnswerAnswer
If / elseGrounded in the sources?
Answer shownAnswer shown
Ask a personAsk a person
Answer shownAnswer shown
7 steps in the flowDrag the canvas, or any step, to move it around.
Why teams run it
Compliance teams field the same permission questions by email every week, and the answer depends on who picks it up. Staff who can’t get a quick answer either wait or guess, and a guess that turns out wrong becomes a finding.
How it is governed
- It is instructed never to infer a permission the policies do not grant.
- Every answer cites the policy clause it relies on.
- Escalated questions wait for compliance approval before anything is shown.
- Every question and answer is kept in the run history.
- Who runs it
- Compliance officers; Risk and policy managers; Employees across the business.
- What you supply
- Your policies as knowledge sources.
From template to a live agent
The same builder, tests and release review apply to a template as to anything built from scratch.
- Open it as a working flow
- Every step, source, branch and approval is already in place, and every one of them can be changed before it runs on your data.
- Prove it before it ships
- An evaluation set can gate the release, so a change that breaks an answer never reaches anyone. A question it cannot answer from the sources leaves the gate unproven, not passed.
- Keep a person on the decisions
- A run that needs a decision stops and says exactly what approving will do, and who it is waiting for.
- Publish where people work
- A form, an embedded widget, Microsoft Teams or a scheduled batch — with its own access and limits per deployment.
- What teams usually change
- Make the check stricter, so 'policy is silent' answers reach compliance; Name the compliance officer or queue who rules on escalations; Load regional policy variants as separate knowledge sources.
Questions buyers ask
- What happens when our policies don’t cover the question?
- The answer says policy is silent rather than reasoning its way to a yes. If the answer step returns nothing at all, the question goes to the compliance team; many teams also route 'silent' answers there.
- Can staff rely on it as a ruling?
- It reports what your written policies say, with the clause quoted, and is instructed not to go further. A ruling on anything the policies don’t settle stays with your compliance team.
- Is there a record of what people asked?
- Yes. Every question, the answer given and any escalation decision are kept in the run history, which supports review of how policy questions are being handled.
Related templates
All 60 templates- Regulator notice watcherReads a regulator page on a schedule and says only when something has appeared that affects you.ComplianceOn a schedule6 steps
- Call compliance checkTranscribes a recorded call and checks what was said against the disclosures that had to be given.ComplianceA document or recording is attached4 steps
See it run on your own data
We open it in the builder, point it at a sample of your documents and systems, and run it with you.