Detection rule types reference
A detection rule tells Sidekick what structured data to look for in conversation text. When a rule matches, the value is written to the custom field the rule targets if that field is empty, and listed in the Detected Insights module in the Sidekick panel.
Four detector types decide what counts as a match. Pick the one that fits your data shape.
What text gets scanned
By default, detection rules scan inbound conversation text — messages from the customer. Agent replies are never scanned. You can include more conversation context with rule settings:
- Turn on Scan internal notes to include internal notes in the scan text. Only notes written by a person are included; system, automation, Sidekick and integration notes are excluded so detection never runs on Atender’s own output
- Turn on Scan conversation subject to include the conversation subject in the scan text
Messages and notes are read from a per-conversation high-water mark, so each run only sees what arrived since the last one. The subject has no timestamp to compare against, so it is re-scanned on every run — but detection only fills a field that is empty, so a re-scan cannot overwrite a later manual edit of that field.
Editing only the conversation subject does not trigger a fresh detection run. The subject is included when a rule runs, but a subject-only change will not rerun detection by itself.
IBAN
International bank account numbers from any of the roughly 70 IBAN countries. Validates the country prefix, the length and the mod-97 checksum, so typos and made-up numbers are rejected. No configuration.
- Normalized, spaces stripped —
Pay to NO93 8601 1117 947→NO9386011117947 - —
NO9386011117948(bad checksum) → no match
Can target a Text or Textarea field.
Phone
Phone numbers via libphonenumber. One setting, Detection mode:
- Worldwide — international format only: the number must start with
+and a country code. Highest precision, but won’t catch locally-formatted numbers like22 22 22 22 - Regional — pick one or more regions. Locally-formatted numbers from those regions are detected, plus all international-format numbers. At least one region must stay selected
Spaces, dashes and parentheses inside the number are tolerated. Values are stored in E.164 (+47 22 22 22 22 → +4722222222).
Can target a Phone, Text or Textarea field.
Domain
Plain domain names typed into a message — acme.no, www.acme.no, example.co.uk, mail.acme.no. Validated against the Public Suffix List, so foo.fakeextension is rejected. No configuration.
Stored as the registrable domain: mail.acme.no becomes acme.no, and a leading www. is stripped. Domains inside a full URL (https://acme.no/page) or an email address (user@acme.no) are deliberately not matched.
Can target a Text, Textarea or URL field.
Custom regex
For everything else — invoice numbers, order IDs, serials. You supply a Pattern and Flags (gi by default), and the rule runs it against the configured scan text.
- Identifiers with a consistent prefix —
\bORD-\d{6,10}\bfor order numbers - Existing regex you already maintain elsewhere —
\bSO\d{6,}\bfor sales orders - Migrating rules from another system — Direct port
Notes:
- The rule stores the first match, following scan order, so earlier messages win. If the pattern has a capture group, the first group is stored; otherwise the whole match is
- Use word boundaries (
\b) to avoid matching substrings - Custom rules scan each message, the subject and each internal note separately. Any single text over 10,000 characters is skipped for custom rules; the other texts are still scanned
- The editor carries a live tester under the Pattern field — paste sample text and matches are highlighted with a count. Use it before saving (see Create a detection rule). The tester uses the browser’s regex engine, so it can show a match that the server refuses
- Saving refuses a pattern that is invalid, longer than 500 characters, or uses a backreference, a lookaround, or a repeat that expands past 1000. The editor shows the reason
Can target a Text, Textarea, Number, Phone, URL or Email field.
When you choose a target field, the picker only shows compatible fields that have been placed on the canvas where the detected value is written, plus the field the rule already targets. Closed field types such as select, checkbox and date are not available as detection-rule targets.
Starting a rule
New rule opens on What do you want to detect?, which offers three ways in:
- describe what you want in the box and click Suggest — the AI picks the detector type and its config, and drops you into the editor with them filled in
- pick one of the four types as a starting point
- Skip — start blank, which opens the editor on Custom regex
Picking which type
- Is it a bank account number? — IBAN
- Is it a phone number? — Phone
- Is it a bare domain name? — Domain
- Anything else with a consistent shape (order IDs, invoice numbers, serials) — Custom regex
- Is the data described differently every time, with no consistent shape? — None of these — detection rules are deterministic matchers, not an LLM extractor
Ordering and precedence
Rules run in list order, top to bottom, and every enabled rule that matches writes to its target field if that field is empty. If two rules target the same field and both match in the same pass, the one further down the list runs last and wins; once the field holds a value, later passes leave it alone. Reorder by dragging a row’s handle on the Detection Rules list.
Matches have no confidence score
Detection rules have no confidence score. Every match is written to its target field when that field is empty, with no review step and no threshold to tune. Sidekick’s AI auto-tagging is a different feature and is not governed by detection rules.