Your website and your documents. Give it your web address and it reads your sitemap, respects your robots file and picks the pages that matter most, up to 25 of them. Or upload price lists, menus and policies as PDF, Word (.docx), plain text or Markdown, up to 10 MB each.
Will it flag calls against facts I haven’t checked?
No. ListenFox drafts a short facts sheet from what you gave it, and you edit and confirm it. Nothing is checked against facts you haven’t approved.
What does a policy flag show?
The quote from the call, the moment it was said, and the fact it contradicted on your confirmed sheet. One click plays the recording at that second, so the talk with your team starts from what was actually said.
Does it use a QA scorecard?
Yes, and it is kept apart from the policy check. The handling scorecard grades how each call was handled, 1 to 5 per check, and lives with coaching. The policy check grades nothing: it compares what was said with your confirmed facts sheet and flags each mismatch.
What share of calls does it check?
Every analyzed call, once your facts sheet is confirmed. A reviewer picks a few calls to play; ListenFox reads all of them, so a wrong price quoted on the fortieth call of the day is as easy to find as one on the first.
Dismiss it. The flag leaves the open list, and the number of dismissed flags stays visible next to the open ones.
Can I keep separate facts for each branch?
You can label each source, for example by branch or product line, to keep them grouped. The policy check still uses one confirmed facts sheet for the whole workspace. Reading a whole site rather than 25 pages is on the roadmap and will be marked live on the changelog when it ships.