Continuously verify that your AI support behavior follows your organization’s policies, procedures, and customer commitments—with clear evidence for every finding.
Policy Monitoring evaluates your AI support interactions against the policies and standard operating procedures (SOPs) your organization has defined. When an AI interaction deviates from a policy requirement, CraftCX flags it with an explanation, evidence from the conversation, and a severity rating.
Policy Monitoring is currently in active development. Reach out to support@craftcx.com for early access.
AI agents can produce helpful, confident-sounding responses while still violating your refund rules, authorization limits, escalation procedures, legal requirements, or internal operating guidance. These violations are difficult to catch through manual spot-checks alone.Policy Monitoring gives your team continuous coverage across every AI-handled conversation—not just a sample—so nothing slips through.
Upload your policy documents (PDFs, Word documents) or connect a Notion workspace. CraftCX supports multiple source documents per policy area.
2
CraftCX extracts your rules
CraftCX reads your documents and extracts the specific requirements, procedures, and commitments that AI interactions should follow. You can review active and draft rules in the Rules section of the platform.
3
Every conversation is evaluated
As AI-handled conversations come in, CraftCX checks each one against your active rules. Evaluations happen automatically—no manual review queue needed.
4
Violations are surfaced with evidence
When a deviation is detected, CraftCX creates a finding that includes a plain-language explanation, the relevant transcript snippets, citations back to the policy source, and a severity and confidence rating.
5
Repeated violations become incidents
If the same type of violation recurs, or a single violation is severe enough, it escalates into an Incident for your team to investigate and resolve.
A plain-language description of what happened and why it was flagged. Findings are rated by severity (high, medium, low) and a confidence score, so your team can prioritize the most impactful issues first.
Transcript snippets — the exact messages from the conversation where the deviation occurred, labeled by who sent them (AI, customer, human agent, or system).Citations — links back to the specific sections of your policy documents that were not followed, so you can verify the finding against the source material.
Reason codes — structured tags explaining the category of deviation (e.g., authorization limit exceeded, required escalation not followed).Policy risk categories — the broader risk area the finding falls under.Confidence rationale — a written explanation of why CraftCX assessed this level of confidence in the finding.
If your policies live in Notion, you can connect your workspace directly. CraftCX will pull content from the pages you select and keep rules in sync as your documents change.
After uploading a document, CraftCX generates draft rules from it. Go to Rules to review what was extracted before it goes live. Rules move from draft to active once reviewed.
If a rule doesn’t look right, you can use it as a starting point. Clearer, more specific policy language in your source documents leads to more accurate rule extraction.
Which conversations does Policy Monitoring evaluate?
CraftCX evaluates AI-handled conversations that have been ingested through your connected helpdesk integration. Human-only conversations are not included in policy evaluations.
How quickly do findings appear after a conversation ends?
Policy evaluations typically complete within a few minutes of a conversation being resolved. Timing may vary slightly depending on your helpdesk’s resolution status updates.
What if my AI was actually correct, but the policy is ambiguous?
Mark the finding as a false positive and note the ambiguity. CraftCX also detects stale, conflicting, or unclear guidance in your policy documents over time, which helps you identify where policies need clarification.
Can I see trends across all findings for a specific policy?
Yes. The Monitor view lets you filter findings by policy rule and see how violations trend over time. Recurring violations for the same rule are a strong signal that either the AI configuration or the policy itself needs attention.
What file formats are supported for policy documents?
CraftCX currently supports PDF and Word documents for uploads. You can also connect a Notion workspace to pull policy content directly from pages.
How is this different from AXIS scoring?
AXIS scoring measures the overall quality of a conversation—whether it was resolved accurately, efficiently, and with smooth handoffs. Policy Monitoring specifically checks whether AI behavior followed your defined rules and procedures. A conversation can score well on AXIS while still violating a specific policy, or vice versa.
Incidents
See how repeated violations escalate into incidents your team can track and resolve.