Approve a suggested rule

Review a rule we drafted from your own documents before it counts.

Use this when the product has noticed a way conversations keep failing that no rule in force asks about, and it is waiting on your decision.

The What we check screen with an emerging pattern waiting on a decision: the question it would ask, how many conversations it explains, and the two decision buttons.

The steps

  1. Open Scoring quality, then What we check.
  2. Look for the Emerging pattern section, above the catalogue. Its title says how many rules are waiting on you.
  3. Read the row. It gives the question the proposed rule would ask, its score area and its severity, and how many of the conversations already carrying results it explains.
  4. Open the row for Read one of them, and read a conversation the pattern was drawn from. Do this before you decide anything.
  5. Press Start counting it to accept it, or Leave it out to refuse it.
  6. Read Already decided, under the list. It says what you have accepted and what you have left out.

What to do with what you find

Accepting one moves no score you have already read. It starts counting at the next version freeze, so every figure you have quoted stays as it was.

Leaving one out is recorded and it will not be offered again. It stays readable under the retired filter in the catalogue below.

Some rows carry no buttons, and say they are ours rather than yours to decide. Those back another rule's result instead of standing on their own, so nobody is asked about them.

While you are here, read Rules that contradict each other if that section appears. Two rules that cannot both pass leave a score that depends on which one ran. Each card has Why they conflict, and a way into Setup to settle it.

A proposal with no evidence yet is counted separately above the list. That is a pattern the product has named but cannot show you conversations for, so it is the weakest kind to accept.

Read next

  • Set an alert · Get told when quality or latency drifts, without being told forty times a day.
  • Send a report to a client · Produce a dated report you can forward to a client, and the conversation list behind it.
  • Add an agent or a client · Register another agent, or another customer whose traffic you keep separate.
This page as markdown