Skip to content

Add a rule of your own

Write a question you want asked of every conversation, and put it live.

You do not type the rule. You give us the writing that defines good, and we compile the rules out of it, so every rule points at the sentence it came from.

  1. Open What we check in the left rail.

    Every rule a conversation is scored against.

    The Say what good looks like step: an industry pack to apply, a form for pasting your own documents, and the control that compiles rules out of them.
  2. Press Write a rule, then Say what good looks like.

  3. Under Industry pack, press Apply pack if one fits.

    It adds its rules in the background, where they decide nothing.

  4. Under Your documents, choose a Document type.

  5. Paste into Content, or Upload a file instead, then Save document.

  6. Press Compile, or Recompile if a set already exists.

    It says how many rules it wrote, how many it merged, and where your documents disagree.

  7. Press Next to reach Review.

    This is a two step form, and nothing goes live on the first one.

  8. Settle every conflict.

    Each card shows both rules. Keep this one takes that side and refuses the other.

  9. Work through the rules awaiting review, with Approve and Reject.

  10. Press Build with my decisions.

  11. Press Move to active, or Move to canary instead.

The document types

Document typeSystem prompt, SOP, Fields to extract, Guardrails, Goal, Funnel, Setup, Observed, Manual
File formats.txt, .md, .json
NoteOptional, so you can remember which version this was

Reading it right

  • Nothing you approve moves a score you have already read. A rule starts counting at the next version freeze, so old figures stay comparable with each other.
  • Read the new rule against a real conversation before you promote it. Ask whether the question reads the way a supervisor would say it out loud.
  • If two documents disagree, settling it at review is cheaper than leaving two rules in force that cannot both pass.
Note: There is no dry run. Compiling writes real rules, so there is no way to try a wording and throw the result away.

Read next

  • Approve a suggested rule · Review a rule we drafted from your own documents before it counts.
  • 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.
This page as markdown