{"id":225,"date":"2026-08-07T09:04:45","date_gmt":"2026-08-07T09:04:45","guid":{"rendered":"https:\/\/znicrm.com\/guide\/?p=225"},"modified":"2026-08-07T09:04:46","modified_gmt":"2026-08-07T09:04:46","slug":"lead-scoring-guide-for-administrators","status":"publish","type":"post","link":"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/","title":{"rendered":"Lead Scoring Guide for Administrators"},"content":{"rendered":"\n<h1 id=\"lead-scoring-administrator-configuration-guide\">Lead Scoring: Administrator Configuration Guide<\/h1>\n\n\n\n<h2 id=\"overview\">Overview<\/h2>\n\n\n\n<p>Lead Scoring ranks inbound leads and existing contacts on a scale from 0 to 100. It combines a starting score with positive and negative rules based on the lead source, form answers, contact completeness, replies, deals, and other approved activity. The result is assigned to a score band such as Cold, Nurture, Warm, or Hot.<\/p>\n\n\n\n<p>Lead Scoring is designed for company administrators who want sales teams to see which leads deserve attention first. It can also provide a pre-assignment deterministic score to Advanced Lead Routing and can optionally use an LLM to enrich a contact-stage score.<\/p>\n\n\n\n<p>After configuration, users can see the selected current score:<\/p>\n\n\n\n<ul><li>in the <strong>Lead Score<\/strong> column on <strong>CRM &gt; Contacts<\/strong>;<\/li><li>on the <strong>Contact Conversation<\/strong> page, directly above <strong>Lead Status<\/strong>; and<\/li><li>in administrator-only run logs and deterministic reports.<\/li><\/ul>\n\n\n\n<p>The score is dynamic. A new inbound lead can be scored before routing and again after it becomes a contact. Later configured events\u2014such as a customer reply, deal creation, deal stage change, win, loss, or no-response timer\u2014can request a recalculation. The integration records the event; your published profile decides whether it changes the score and by how many points.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Lead Scoring is fail-open for normal CRM operations. If scoring is disabled, unavailable, or unable to calculate a score, lead capture, queue processing, routing fallback, assignment, forms, replies, deals, and workflows continue normally.<\/p><\/blockquote>\n\n\n\n<h2 id=\"when-to-use-lead-scoring\">When to use Lead Scoring<\/h2>\n\n\n\n<p>Use Lead Scoring when you want to:<\/p>\n\n\n\n<ul><li>prioritize high-intent leads consistently;<\/li><li>give different weight to Facebook, IndiaMART, Justdial, Engage, contact-form, API, or other supported inbound sources;<\/li><li>score company-specific form answers without hard-coding field names;<\/li><li>increase a score after engagement or deal progress;<\/li><li>decrease a score after no response or a lost deal;<\/li><li>apply different scoring policies to different sources, integrations, or forms;<\/li><li>route new leads using a deterministic pre-assignment score; or<\/li><li>test AI-assisted enrichment without immediately changing the score.<\/li><\/ul>\n\n\n\n<h2 id=\"before-you-begin\">Before you begin<\/h2>\n\n\n\n<p>You need all of the following:<\/p>\n\n\n\n<ul><li>a company plan that includes Lead Scoring and an active CRM licence;<\/li><li>a company <strong>Admin<\/strong> account with permission to manage Lead Scoring;<\/li><li>the relevant lead sources, forms, and integrations already connected;<\/li><li>at least one published default profile or one published profile with a matching active binding.<\/li><\/ul>\n\n\n\n<p>For dynamic provider and form fields, first submit a controlled test lead through the relevant source. The field appears only after the lead reaches the central lead queue and field discovery completes.<\/p>\n\n\n\n<p>For optional LLM enrichment, you also need:<\/p>\n\n\n\n<ul><li>the company LLM switch enabled;<\/li><li>a published profile in <strong>SHADOW<\/strong> or <strong>HYBRID<\/strong> mode;<\/li><li>at least one approved and mapped field eligible for LLM use;<\/li><li>sufficient AI credits; and<\/li><li>available capacity under every configured LLM limit.<\/li><\/ul>\n\n\n\n<h2 id=\"navigation-and-permissions\">Navigation and permissions<\/h2>\n\n\n\n<p>Open <strong>Admin &gt; Features Settings &gt; Lead Scoring<\/strong>.<\/p>\n\n\n\n<p>Only company administrators with Lead Scoring management permission can open the configuration, logs, and report pages. CRM users who can read a contact may see its score according to their normal CRM visibility scope, but they cannot configure scoring.<\/p>\n\n\n\n<p>From the Lead Scoring page, use:<\/p>\n\n\n\n<ul><li><strong>Run and Job Logs<\/strong> for individual runs, events, jobs, and safe error codes;<\/li><li><strong>Deterministic Report<\/strong> for aggregate score statistics; and<\/li><li><strong>Setup Help and FAQ<\/strong> for the in-product summary.<\/li><\/ul>\n\n\n\n<h2 id=\"how-lead-scoring-works\">How Lead Scoring works<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code>Lead enters the central lead queue\n  -&gt; source and form context is verified\n  -&gt; eligible incoming fields are discovered\n  -&gt; one published profile is selected\n  -&gt; event-stage deterministic score is calculated\n  -&gt; optional score-based routing uses that event-stage score\n  -&gt; lead is assigned and becomes a CRM contact\n  -&gt; contact-stage deterministic score is calculated\n  -&gt; optional LLM enrichment runs if every gate is satisfied\n  -&gt; the selected current score appears in CRM\n  -&gt; configured replies, deal events, timers, or workflows request recalculation<\/code><\/pre>\n\n\n\n<p>The deterministic calculation is:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Base Score\n  + matched ungrouped rule points\n  + matched grouped rule points after group caps\n  = unclamped score\n  -&gt; limited to 0\u2013100\n  -&gt; assigned to the matching score band\n  -&gt; optionally adjusted in HYBRID mode\n  -&gt; limited to 0\u2013100 again<\/code><\/pre>\n\n\n\n<p>Each enabled rule contributes its points once when its conditions match. A rule group can limit the combined positive or negative contribution of its rules. The final deterministic score can never be lower than 0 or higher than 100.<\/p>\n\n\n\n<h2 id=\"configuration-dependency-map\">Configuration dependency map<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code>Lead Scoring Status\n|\n+-- OFF\n|   +-- normal lead capture, routing, assignment, CRM, deals and workflows continue\n|   +-- no new field discovery, score calculation, behavior scoring or LLM requests\n|   +-- score cards are hidden; configuration, history and pending jobs are retained\n|\n+-- ON\n    |\n    +-- Published Profile\n    |   |\n    |   +-- Default Profile -&gt; fallback when no active binding matches\n    |   |\n    |   +-- Non-default Profile -&gt; requires at least one active binding\n    |       +-- exact form\/provider object\n    |       +-- integration\n    |       +-- marketing source\n    |       +-- broad source\/module\/service\n    |\n    +-- Deterministic Rules\n    |   +-- system facts\n    |   +-- approved direct profile fields\n    |   +-- active reusable dimensions\n    |   +-- rule groups and contribution caps\n    |   +-- complete 0\u2013100 score bands\n    |\n    +-- CRM Score Display\n    |   +-- latest current score\n    |   +-- selected published profile -&gt; requires Published profile selection\n    |   +-- hidden\n    |\n    +-- Routing Integration\n    |   +-- requires Advanced Lead Routing\n    |   +-- uses only completed event-stage deterministic facts\n    |\n    +-- Behavior Trigger Policies\n    |   +-- require matching scoring rules to change the score\n    |   +-- debounce controls when recalculation starts\n    |   +-- lookback controls how long the signal remains active\n    |   +-- expiry recalculates when a timed signal expires\n    |\n    +-- Optional LLM Scoring\n        +-- company LLM switch ON\n        +-- published profile mode SHADOW or HYBRID\n        +-- approved field allows LLM use\n        +-- profile mapping enables LLM use\n        +-- privacy\/type policy permits the field\n        +-- AI credits and all resource limits are available\n        +-- SHADOW -&gt; stores insight but does not change the effective score\n        +-- HYBRID -&gt; applies a bounded adjustment only at\/above Min Confidence<\/code><\/pre>\n\n\n\n<h2 id=\"setting-precedence\">Setting precedence<\/h2>\n\n\n\n<h3 id=\"profile-selection-precedence\">Profile selection precedence<\/h3>\n\n\n\n<p>When more than one published profile could match a lead, selection is resolved in this order:<\/p>\n\n\n\n<ol type=\"1\"><li>exact form or provider-form binding;<\/li><li>integration or provider-object binding;<\/li><li>marketing lead-source binding;<\/li><li>broad source, module, service, or source-ID binding;<\/li><li>the published default profile.<\/li><\/ol>\n\n\n\n<p>Within the same level, a higher <strong>priority<\/strong> wins. If priorities are equal, the binding with more populated selectors wins. Publishing rejects overlapping bindings at the same specificity and priority when they could select different profiles.<\/p>\n\n\n\n<h3 id=\"field-and-dimension-precedence\">Field and dimension precedence<\/h3>\n\n\n\n<p>When multiple mapped fields provide a value for the same dimension, the lower <strong>mapping_priority<\/strong> value is considered first. If values differ:<\/p>\n\n\n\n<ul><li><strong>INVALID_CONFLICT<\/strong> stops scoring safely; or<\/li><li><strong>FIRST_NON_MISSING<\/strong> uses the first available value by mapping priority.<\/li><\/ul>\n\n\n\n<h3 id=\"rule-and-score-precedence\">Rule and score precedence<\/h3>\n\n\n\n<ul><li>Conditions determine whether a rule matches.<\/li><li>Each matched rule contributes once.<\/li><li>Rule-group minimum and maximum caps are applied before the final score is limited to 0\u2013100.<\/li><li>Score bands label the resulting score; they do not add points.<\/li><li>In <strong>SHADOW<\/strong>, the deterministic score remains effective.<\/li><li>In <strong>HYBRID<\/strong>, a valid LLM adjustment can change the effective score only when confidence meets <strong>Min Confidence<\/strong> and only within <strong>Max Adjustment<\/strong>.<\/li><li>Initial routing always uses the event-stage deterministic score, never the contact-stage or LLM-adjusted score.<\/li><\/ul>\n\n\n\n<h2 id=\"recommended-configuration-order\">Recommended configuration order<\/h2>\n\n\n\n<ol type=\"1\"><li><strong>Enable Lead Scoring.<\/strong> This allows field discovery and scoring jobs to run.<\/li><li><strong>Send controlled test leads.<\/strong> Use each source or form whose fields you plan to score.<\/li><li><strong>Review incoming fields.<\/strong> Approve only fields with a confirmed type, privacy classification, and scoring purpose.<\/li><li><strong>Create reusable dimensions when needed.<\/strong> Use dimensions for the same concept across differently named provider fields.<\/li><li><strong>Create the first profile as the default.<\/strong> Keep <strong>Apply recommended starter rules<\/strong> enabled unless you intentionally want an empty draft.<\/li><li><strong>Map approved fields.<\/strong> Save mappings before writing rules so the page can show current profile-field IDs.<\/li><li><strong>Review the base score, rules, group caps, triggers, and bands.<\/strong> Adapt starter values to your business.<\/li><li><strong>Configure bindings.<\/strong> A non-default profile cannot be published without at least one active binding.<\/li><li><strong>Run a synthetic preview.<\/strong> Use only non-personal test values.<\/li><li><strong>Validate and publish.<\/strong> Publishing freezes that version.<\/li><li><strong>Choose CRM display and routing behavior.<\/strong> Enable routing integration only after Advanced Lead Routing is ready.<\/li><li><strong>Optionally enable LLM enrichment.<\/strong> Start with SHADOW, monitor cost and quality, then consider HYBRID.<\/li><li><strong>Verify with a new test lead.<\/strong> Check Contacts, Contact Conversation, Run and Job Logs, and the report.<\/li><\/ol>\n\n\n\n<h1 id=\"configuration-guide\">Configuration guide<\/h1>\n\n\n\n<h2 id=\"1-company-level-settings\">1. Company-level settings<\/h2>\n\n\n\n<h3 id=\"lead-scoring-status\">Lead Scoring Status<\/h3>\n\n\n\n<p><strong>Enable lead scoring for this company<\/strong> is the master switch.<\/p>\n\n\n\n<ul><li><strong>Enabled:<\/strong> supported intake events can discover fields, calculate scores, create behavior events, expose event-stage facts to routing, display scores in CRM, and schedule eligible LLM requests.<\/li><li><strong>Disabled (default):<\/strong> normal CRM activity continues, but no new scoring work is produced or processed. Existing profiles, scores, logs, and pending jobs are retained. Pending jobs can resume after the switch is enabled.<\/li><\/ul>\n\n\n\n<p>Turning the switch off does not delete or reset historical scores. CRM score cards are hidden while the feature is off.<\/p>\n\n\n\n<h3 id=\"routing-integration\">Routing Integration<\/h3>\n\n\n\n<p><strong>Allow advanced inbound routing rules to use the deterministic event-stage score<\/strong> controls whether Advanced Lead Routing can use three read-only scoring facts: routing score, routing band, and profile key.<\/p>\n\n\n\n<ul><li><strong>Enabled:<\/strong> a completed pre-assignment deterministic score can be used by Advanced Lead Routing rules.<\/li><li><strong>Disabled (default):<\/strong> routing follows its normal configured rules and fallback without score facts.<\/li><\/ul>\n\n\n\n<p><strong>Requires:<\/strong> Lead Scoring enabled and Advanced Lead Routing enabled for the company.<\/p>\n\n\n\n<p>If event scoring fails or no profile matches, routing continues with its normal fallback. LLM results and later contact activity never alter initial assignment.<\/p>\n\n\n\n<h3 id=\"crm-score-display\">CRM Score Display<\/h3>\n\n\n\n<p>Use <strong>Score to display<\/strong> to choose the current score users see on the Contacts list and Contact Conversation page.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Option<\/th><th>Behavior<\/th><th>When to use<\/th><\/tr><\/thead><tbody><tr><td><strong>Latest current score (recommended)<\/strong><\/td><td>Shows the most recently evaluated eligible profile for each contact. This is the default.<\/td><td>Most companies with one profile or source-specific profiles.<\/td><\/tr><tr><td><strong>A selected published profile<\/strong><\/td><td>Shows only the current score produced by the chosen profile. Contacts without a score for that profile show no completed score.<\/td><td>When one profile is the official sales-priority score.<\/td><\/tr><tr><td><strong>Do not show lead scores in CRM<\/strong><\/td><td>Hides scores from both CRM screens without disabling calculations, logs, routing, or reports.<\/td><td>When administrators are testing scoring privately.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>Published profile<\/strong> appears only when <strong>A selected published profile<\/strong> is chosen. It is required and accepts only an active profile with a published immutable version.<\/p>\n\n\n\n<h3 id=\"optional-llm-scoring\">Optional LLM Scoring<\/h3>\n\n\n\n<p><strong>Enable optional LLM enrichment<\/strong> is off by default. Enabling it does not create a score by itself. Deterministic contact-stage scoring must complete first.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Setting<\/th><th>Default<\/th><th>Valid range<\/th><th>What users observe<\/th><\/tr><\/thead><tbody><tr><td><strong>Daily request limit<\/strong><\/td><td>100<\/td><td>1\u201310,000<\/td><td>Once reached, new eligible LLM operations are skipped for the rest of the day; deterministic scoring remains available.<\/td><\/tr><tr><td><strong>Daily credit limit<\/strong><\/td><td>200.00<\/td><td>0\u20131,000,000.00, up to 2 decimals<\/td><td>A request that would exceed the daily configured credit budget is skipped. A value of 0 prevents chargeable LLM requests.<\/td><\/tr><tr><td><strong>Maximum queued jobs<\/strong><\/td><td>50<\/td><td>1\u20131,000<\/td><td>When the number of pending, waiting, or running LLM jobs reaches this limit, additional eligible requests are skipped.<\/td><\/tr><tr><td><strong>Maximum concurrent jobs<\/strong><\/td><td>2<\/td><td>1\u201350<\/td><td>Limits how many LLM jobs for the company may run at the same time. Excess claimed work waits and retries.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>The page shows the current AI-credit balance and current per-lead price. A provider request is not sent if the balance is below the required price. Successful LLM operations are billed using the current Lead Scoring LLM price. Provider failures are not charged. Both SHADOW and HYBRID can consume credits because both call the LLM.<\/p>\n\n\n\n<h2 id=\"2-discovered-incoming-fields\">2. Discovered incoming fields<\/h2>\n\n\n\n<p>Fields are discovered from supported, company-owned intake contexts. Current adapters include Facebook, IndiaMART, Justdial, contact forms, CRM custom forms, Web Lead, API, Engage, TradeIndia, Google Ads, Calendly, and inbound email when those sources use a supported intake path.<\/p>\n\n\n\n<p>Discovery stores field metadata, not a sample value for administrators. Unknown fields never affect a published profile automatically.<\/p>\n\n\n\n<h3 id=\"review-incoming-field\">Review Incoming Field<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Setting<\/th><th>Options\/default<\/th><th>Behavior and dependencies<\/th><\/tr><\/thead><tbody><tr><td><strong>Type Override<\/strong><\/td><td>Use observed type (default), TEXT, NUMBER, BOOLEAN, DATE, SINGLE_SELECT, MULTI_SELECT<\/td><td>Changes the approved interpretation only when compatible with observed metadata. Do not choose NUMBER for IDs, phone numbers, postcodes, or values with significant leading zeros.<\/td><\/tr><tr><td><strong>Privacy Classification<\/strong><\/td><td>PUBLIC, BUSINESS (default selection), PERSONAL, SENSITIVE<\/td><td>May keep or raise the system privacy floor, never lower it. PERSONAL and SENSITIVE fields cannot be approved for deterministic or LLM scoring.<\/td><\/tr><tr><td><strong>Allow deterministic scoring<\/strong><\/td><td>On by default<\/td><td>Allows the approved revision to be mapped for deterministic rules, provided its type and privacy policy are eligible.<\/td><\/tr><tr><td><strong>Allow LLM use (policy still applies)<\/strong><\/td><td>Off by default<\/td><td>Allows later LLM use only for eligible PUBLIC\/BUSINESS NUMBER, BOOLEAN, DATE, SINGLE_SELECT, or MULTI_SELECT fields. This switch alone does not send the field.<\/td><\/tr><tr><td><strong>Resolve an observed type conflict<\/strong><\/td><td>Off by default<\/td><td>Must be enabled when the field is in TYPE_CONFLICT state and you have intentionally selected the correct compatible type. It has no purpose for fields without a conflict.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Select <strong>Approve Revision<\/strong> to create a versioned approval. If the provider later changes the field identity, type, or extraction shape, review the new revision and publish an updated profile.<\/p>\n\n\n\n<h3 id=\"hide-and-block\">Hide and Block<\/h3>\n\n\n\n<ul><li><strong>Hide<\/strong> changes the field to HIDDEN so it no longer remains an approved current field. Any draft mapping to it becomes stale and cannot be published until removed or reapproved.<\/li><li><strong>Block<\/strong> marks the field BLOCKED and removes the Review action. Block fields that must never be used for scoring. Existing published evidence remains historical, but future drafts cannot map the blocked field.<\/li><\/ul>\n\n\n\n<p>Credentials, passwords, tokens, OTPs, payment-card data, and other prohibited technical or secret fields are excluded from discovery.<\/p>\n\n\n\n<h2 id=\"3-reusable-dimensions\">3. Reusable dimensions<\/h2>\n\n\n\n<p>A dimension gives differently named fields one stable business meaning. For example, Facebook <code>company_size<\/code>, IndiaMART <code>employee_count<\/code>, and a custom form <code>team_size<\/code> can all map to <code>COMPANY_SIZE<\/code> if their approved types are identical.<\/p>\n\n\n\n<p>Dimensions are optional and never add points by themselves.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Setting<\/th><th>Required\/default<\/th><th>Rules and effect<\/th><\/tr><\/thead><tbody><tr><td><strong>Dimension Name<\/strong><\/td><td>Required; maximum 160 characters<\/td><td>Human-readable name, such as Company Size.<\/td><\/tr><tr><td><strong>Dimension Key<\/strong><\/td><td>Required; 1\u201380 characters<\/td><td>Must start with a letter and contain only uppercase letters, numbers, and underscores. Use a stable key because rules reference it.<\/td><\/tr><tr><td><strong>Description<\/strong><\/td><td>Optional; maximum 500 characters<\/td><td>Explain the business meaning and expected values. This description may accompany an eligible LLM fact.<\/td><\/tr><tr><td><strong>Canonical Type<\/strong><\/td><td>Required; TEXT, NUMBER, BOOLEAN, DATE, SINGLE_SELECT, MULTI_SELECT<\/td><td>Must exactly match every approved field mapped to the dimension.<\/td><\/tr><tr><td><strong>Privacy Floor<\/strong><\/td><td>BUSINESS by default; PUBLIC, BUSINESS, PERSONAL, SENSITIVE<\/td><td>Must be at least as restrictive as every mapped field. PUBLIC is least restrictive; SENSITIVE is most restrictive.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>New dimensions are created as Active. The current page lists dimensions but does not provide an edit control. Plan the key, type, and privacy floor carefully before use. Once a dimension is used by a published version, its identity and policy are treated as immutable.<\/p>\n\n\n\n<h2 id=\"4-create-a-scoring-profile\">4. Create a scoring profile<\/h2>\n\n\n\n<p>Select <strong>New Profile<\/strong>.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Setting<\/th><th>Default\/validation<\/th><th>What it controls<\/th><\/tr><\/thead><tbody><tr><td><strong>Profile Name<\/strong><\/td><td>Required; maximum 160 characters<\/td><td>Administrator-facing name shown in configuration, logs, reports, and CRM score details.<\/td><\/tr><tr><td><strong>Profile Key<\/strong><\/td><td>Required; 1\u201380 characters; starts with a letter; uppercase letters, numbers, underscores; unique<\/td><td>Stable profile identifier used in bindings, evidence, and optional routing rules. It cannot be reused.<\/td><\/tr><tr><td><strong>Description<\/strong><\/td><td>Optional; maximum 500 characters<\/td><td>Explains which leads and outcome the profile covers.<\/td><\/tr><tr><td><strong>Base Score<\/strong><\/td><td>40 in the UI; integer 0\u2013100<\/td><td>Starting deterministic score before rules. The default 40 begins in the starter Nurture band.<\/td><\/tr><tr><td><strong>Default profile<\/strong><\/td><td>Off<\/td><td>Makes this profile the fallback when no more-specific binding matches. The first profile should normally be default. Only one active published default profile is allowed.<\/td><\/tr><tr><td><strong>Apply recommended starter rules<\/strong><\/td><td>On<\/td><td>Adds editable bands, groups, rules, and behavior windows. It does not publish, enable LLM, or guess company-specific fields or values.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Select <strong>Create Draft<\/strong>. The Manage Lead Scoring Draft page opens.<\/p>\n\n\n\n<p>The recommended template adds:<\/p>\n\n\n\n<ul><li>score bands: Cold\/Junk 0\u201319, Low Intent 20\u201339, Nurture 40\u201359, Warm 60\u201379, Hot 80\u2013100;<\/li><li>up to +10 for contact completeness;<\/li><li>+12 for a customer reply;<\/li><li>-7 for no response after 24 hours;<\/li><li>+8 for deal creation;<\/li><li>+15 for a won deal; and<\/li><li>-20 for a lost deal, subject to the configured group caps.<\/li><\/ul>\n\n\n\n<p>Review these values before publishing. They are a starting point, not a universal definition of a qualified lead.<\/p>\n\n\n\n<h2 id=\"5-score-and-llm-policy\">5. Score and LLM Policy<\/h2>\n\n\n\n<h3 id=\"base-score\">Base Score<\/h3>\n\n\n\n<p><strong>Base Score<\/strong> is an integer from 0 to 100. It applies to every evaluation using this profile version. A neutral starting score around 40\u201350 leaves room for both positive and negative rules.<\/p>\n\n\n\n<h3 id=\"llm-mode\">LLM Mode<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Mode<\/th><th>Effect<\/th><th>Credits<\/th><th>Recommended use<\/th><\/tr><\/thead><tbody><tr><td><strong>OFF<\/strong><\/td><td>Deterministic scoring only. This is the default for a new profile.<\/td><td>None<\/td><td>Initial rollout or no AI requirement.<\/td><\/tr><tr><td><strong>SHADOW<\/strong><\/td><td>Runs eligible LLM enrichment and records its proposed adjustment, confidence, reasons, and optional safe summary, but the effective score remains deterministic.<\/td><td>Successful requests are billed.<\/td><td>Recommended first AI stage for quality and cost evaluation.<\/td><\/tr><tr><td><strong>HYBRID<\/strong><\/td><td>Applies a valid adjustment when confidence is at least Min Confidence.<\/td><td>Successful requests are billed, including low-confidence valid results.<\/td><td>Use only after SHADOW results are proven reliable.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 id=\"llm-adjustment-controls\">LLM adjustment controls<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Setting<\/th><th>Recommended\/default<\/th><th>Range<\/th><th>Important behavior<\/th><\/tr><\/thead><tbody><tr><td><strong>Max Adjustment<\/strong><\/td><td>10<\/td><td>0\u2013100; must be at least 1 for SHADOW\/HYBRID<\/td><td>The LLM cannot suggest an adjustment outside this positive or negative bound.<\/td><\/tr><tr><td><strong>Min Confidence<\/strong><\/td><td>0.75<\/td><td>0\u20131, up to 5 decimals<\/td><td>HYBRID applies an adjustment only at or above this value. SHADOW records confidence but never applies an adjustment.<\/td><\/tr><tr><td><strong>Rubric Version<\/strong><\/td><td><code>sales-intent-v1<\/code><\/td><td>1\u201360 letters, numbers, dots, underscores, or hyphens when LLM is enabled<\/td><td>Identifies the server-managed evaluation rubric. Keep the supplied value unless your deployment operator provides another version.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 id=\"llm-policy-json\">LLM Policy JSON<\/h3>\n\n\n\n<p>Select <strong>Apply Recommended LLM Settings<\/strong> to load a working bounded policy. The button changes the editor only; select <strong>Save Score and LLM Policy<\/strong> to store it.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Policy setting<\/th><th>Recommended<\/th><th>Allowed range\/options<\/th><th>Effect<\/th><\/tr><\/thead><tbody><tr><td><code>max_input_facts<\/code><\/td><td>30<\/td><td>1\u2013100<\/td><td>Maximum eligible mapped facts in one LLM request.<\/td><\/tr><tr><td><code>max_fact_value_chars<\/code><\/td><td>300<\/td><td>1\u20131,000<\/td><td>Maximum characters allowed for one eligible fact value.<\/td><\/tr><tr><td><code>max_total_input_bytes<\/code><\/td><td>8,192<\/td><td>256\u201316,384<\/td><td>Maximum total encoded request size.<\/td><\/tr><tr><td><code>max_estimated_tokens<\/code><\/td><td>2,000<\/td><td>64\u20134,000<\/td><td>Maximum estimated input-token allowance.<\/td><\/tr><tr><td><code>max_free_text_fields<\/code><\/td><td>0<\/td><td>0\u201310<\/td><td>Maximum free-text fields if free text is allowed. Current field-approval policy does not approve normal TEXT fields for LLM use, so increasing this does not bypass field eligibility.<\/td><\/tr><tr><td><code>allow_business_free_text<\/code><\/td><td>0<\/td><td>0\/Off or 1\/On<\/td><td>Permits eligible BUSINESS free text only when field policy also permits it and <code>max_free_text_fields<\/code> is at least 1. It does not permit PERSONAL or SENSITIVE data.<\/td><\/tr><tr><td><code>allow_safe_summary<\/code><\/td><td>1<\/td><td>0\/Off or 1\/On<\/td><td>Allows the validated result to contain a bounded safe summary.<\/td><\/tr><tr><td><code>safe_summary_max_chars<\/code><\/td><td>240<\/td><td>0\u2013500; at least 1 when summaries are on<\/td><td>Maximum summary length.<\/td><\/tr><tr><td><code>reason_code_allowlist<\/code><\/td><td><code>STRONG_INTENT<\/code>, <code>NEEDS_REVIEW<\/code><\/td><td>Up to 50 unique uppercase codes<\/td><td>The LLM result may return only listed reason codes.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Provider, model, endpoint, prompt body, credentials, and API keys are centrally managed and cannot be added to this policy.<\/p>\n\n\n\n<h2 id=\"6-tenant-field-mappings\">6. Tenant Field Mappings<\/h2>\n\n\n\n<p>Mappings connect an approved incoming-field revision to this draft. Use <strong>Approved Field and Dimension IDs<\/strong> on the right side of the page; IDs are company- and version-specific and must not be copied from another company or an old draft.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Mapping setting<\/th><th>Default\/options<\/th><th>Behavior<\/th><\/tr><\/thead><tbody><tr><td><code>inbound_field_revision_id<\/code><\/td><td>Required positive approved revision ID<\/td><td>Selects the exact approved, current field revision. A later provider change can make the mapping stale.<\/td><\/tr><tr><td><code>dimension_id<\/code><\/td><td>0<\/td><td>Use 0 for a direct field, or an active compatible dimension ID to share meaning across sources.<\/td><\/tr><tr><td><code>display_label<\/code><\/td><td>Required; maximum 190 characters<\/td><td>Human-readable snapshot for this profile mapping.<\/td><\/tr><tr><td><code>transformation_policy.trim<\/code><\/td><td>1\/On<\/td><td>Removes leading and trailing whitespace before comparison.<\/td><\/tr><tr><td><code>transformation_policy.case_mode<\/code><\/td><td><code>NONE<\/code>; <code>NONE<\/code>, <code>UPPER<\/code>, <code>LOWER<\/code><\/td><td>Optionally normalizes text case before rules evaluate it. Comparisons are otherwise exact and case-sensitive.<\/td><\/tr><tr><td><code>transformation_policy.sort_multi_values<\/code><\/td><td>0\/Off<\/td><td>Sorts a multi-select value after normalization for stable representation.<\/td><\/tr><tr><td><code>missing_value_policy<\/code><\/td><td><code>NO_MATCH<\/code>; <code>NO_MATCH<\/code> or <code>FAIL_SAFE<\/code><\/td><td>NO_MATCH ignores a missing\/invalid value and allows other facts to score. FAIL_SAFE stops that evaluation safely.<\/td><\/tr><tr><td><code>mapping_priority<\/code><\/td><td>10 in the example; integer 0\u20131,000,000<\/td><td>Lower values are considered first when several fields map to one dimension.<\/td><\/tr><tr><td><code>conflict_policy<\/code><\/td><td><code>FIRST_NON_MISSING<\/code> in the example; <code>FIRST_NON_MISSING<\/code> or <code>INVALID_CONFLICT<\/code><\/td><td>Selects the first value or safely rejects conflicting dimension values.<\/td><\/tr><tr><td><code>deterministic_enabled<\/code><\/td><td>1\/On<\/td><td>Must remain on for an active draft mapping to pass publication validation. Remove an unused mapping instead of saving it disabled.<\/td><\/tr><tr><td><code>llm_enabled<\/code><\/td><td>0\/Off<\/td><td>Allows the mapping to be considered for LLM input only when the approved revision is also LLM-eligible and all privacy\/type\/policy gates pass.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Select <strong>Load Tenant Field Example<\/strong> to start from the first compatible approved field, then replace values as needed. The example is not saved automatically. Select <strong>Save Field Mappings<\/strong>. The page reloads and shows generated <strong>Current profile field<\/strong> IDs for direct-field rules.<\/p>\n\n\n\n<h2 id=\"7-score-bands\">7. Score Bands<\/h2>\n\n\n\n<p>Every integer score from 0 through 100 must belong to exactly one band. Gaps and overlaps block publication.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Band setting<\/th><th>Validation<\/th><th>Behavior<\/th><\/tr><\/thead><tbody><tr><td><code>band_key<\/code><\/td><td>Required unique uppercase identifier, maximum 80 characters<\/td><td>Stable band identifier. Common keys such as HOT, WARM, and COLD also receive matching CRM colors.<\/td><\/tr><tr><td><code>band_name<\/code><\/td><td>Required; maximum 160 characters<\/td><td>User-facing label shown beside the score.<\/td><\/tr><tr><td><code>color_key<\/code><\/td><td>Maximum 40 characters; <code>DEFAULT<\/code> if omitted<\/td><td>Controls the Contact Conversation tone. HOT\/HIGH\/SUCCESS\/GREEN are high; WARM\/MEDIUM\/WARNING\/AMBER\/YELLOW are medium; COLD\/LOW\/DANGER\/RED are low. Unknown values fall back to score thresholds.<\/td><\/tr><tr><td><code>minimum_score<\/code><\/td><td>Integer 0\u2013100<\/td><td>First score included in the band.<\/td><\/tr><tr><td><code>maximum_score<\/code><\/td><td>Integer 0\u2013100 and not below minimum<\/td><td>Last score included in the band.<\/td><\/tr><tr><td><code>priority<\/code><\/td><td>Integer 0\u20131,000,000; default 100<\/td><td>Stable ordering metadata. Range coverage determines the matching band.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>If <code>color_key<\/code> is not recognized, the Contact Conversation card uses high at 80+, medium at 50\u201379, and low below 50. The Contacts list has dedicated badge colors for HOT, WARM, and COLD and a neutral style for other keys.<\/p>\n\n\n\n<h2 id=\"8-behavior-trigger-policies\">8. Behavior Trigger Policies<\/h2>\n\n\n\n<p>Trigger policies are optional. They decide which authoritative CRM events request contact-stage recalculation and how long their signals remain active. A trigger does not add points unless a rule references its signal or behavior count.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Trigger setting<\/th><th>Default\/validation<\/th><th>Behavior<\/th><\/tr><\/thead><tbody><tr><td><code>trigger_key<\/code><\/td><td>Required; one of LEAD_ASSIGNED, MESSAGE_REPLY_RECEIVED, DEAL_CREATED, DEAL_STAGE_CHANGED, DEAL_WON, DEAL_LOST; unique per profile<\/td><td>Selects the authoritative event.<\/td><\/tr><tr><td><code>signal_key<\/code><\/td><td>Required uppercase identifier, maximum 80 characters<\/td><td>Tenant-defined signal exposed to rules through active signal keys.<\/td><\/tr><tr><td><code>enabled<\/code><\/td><td>0\/1<\/td><td>Disabled policies ignore that event.<\/td><\/tr><tr><td><code>lookback_seconds<\/code><\/td><td>0\u201331,536,000<\/td><td>How long the event remains active. 0 has no timed expiry. Positive values require REEVALUATE.<\/td><\/tr><tr><td><code>debounce_seconds<\/code><\/td><td>0\u201331,536,000 and less than lookback when lookback is positive<\/td><td>Delays application. A newer same-type event inside the window supersedes the older delayed job. For LEAD_ASSIGNED, use this as the no-response waiting period.<\/td><\/tr><tr><td><code>expiry_policy<\/code><\/td><td><code>NONE<\/code> when lookback is 0; <code>REEVALUATE<\/code> when positive<\/td><td>REEVALUATE schedules another score calculation when the signal expires.<\/td><\/tr><tr><td><code>maximum_occurrences<\/code><\/td><td>1\u2013100<\/td><td>Caps how many active events of this type contribute to behavior counts. It does not multiply a rule automatically; the rule still contributes once when matched.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>The starter no-response setup delays LEAD_ASSIGNED for 24 hours, keeps the waiting signal active for 7 days, and checks that reply count remains zero. A reply received before the delayed check changes the behavior facts so the no-response rule does not match.<\/p>\n\n\n\n<h2 id=\"9-source-and-form-bindings\">9. Source and Form Bindings<\/h2>\n\n\n\n<p>Bindings decide which published profile applies. A default profile may have no bindings. A non-default profile needs at least one active binding.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Binding setting<\/th><th>Default\/validation<\/th><th>Behavior<\/th><\/tr><\/thead><tbody><tr><td><code>binding_name<\/code><\/td><td>Required; maximum 160 characters<\/td><td>Administrator-facing description.<\/td><\/tr><tr><td><code>source_key<\/code><\/td><td>Optional supported source key<\/td><td>Matches the trusted inbound source, such as FACEBOOK, INDIAMART, JUSTDIAL, CONTACT_FORM, CUSTOM_FORM, ENGAGE, API, or WEBLEAD.<\/td><\/tr><tr><td><code>module_scope<\/code><\/td><td>Optional supported module<\/td><td>Narrows the source module. Usually matches the intended source family.<\/td><\/tr><tr><td><code>service<\/code><\/td><td>Optional; maximum 20 characters<\/td><td>Narrows the accepted service context. Leave empty unless you know the exact server-owned service value.<\/td><\/tr><tr><td><code>source_id<\/code><\/td><td>0 or a valid non-negative source ID<\/td><td>Narrows the operational source record.<\/td><\/tr><tr><td><code>marketing_lead_source_id<\/code><\/td><td>0 or an active company\/global lead-source ID<\/td><td>Selects a CRM marketing source.<\/td><\/tr><tr><td><code>form_type<\/code><\/td><td>Empty, PUBLIC_CONTACT_FORM, CRM_CUSTOM_FORM, or FACEBOOK_FORM<\/td><td>Must be paired with <code>form_reference<\/code>.<\/td><\/tr><tr><td><code>form_reference<\/code><\/td><td>Empty or valid form reference, maximum 160 characters<\/td><td>For public\/custom forms, use the numeric company form ID. For Facebook, use the synchronized provider form reference.<\/td><\/tr><tr><td><code>integration_id<\/code><\/td><td>0 or valid company integration ID<\/td><td>Used with exact provider objects such as a Facebook form.<\/td><\/tr><tr><td><code>provider_object_type<\/code><\/td><td>Empty or valid provider type, maximum 40 characters<\/td><td>For Facebook form bindings, use FACEBOOK_FORM.<\/td><\/tr><tr><td><code>provider_object_reference<\/code><\/td><td>Empty or exact provider reference, maximum 160 characters<\/td><td>Must match the form\/provider reference and requires a valid integration.<\/td><\/tr><tr><td><code>priority<\/code><\/td><td>100; integer 0\u20131,000,000<\/td><td>Higher priority wins between matching bindings at the same specificity.<\/td><\/tr><tr><td><code>status<\/code><\/td><td>ACTIVE; ACTIVE or INACTIVE<\/td><td>Only active bindings can select a profile. Inactive bindings remain stored in the published version but have no selection effect.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>For a Facebook form, all three form\/integration values must agree: the synchronized integration ID, <code>FACEBOOK_FORM<\/code>, and the exact provider form reference.<\/p>\n\n\n\n<h2 id=\"10-rule-groups-and-rules\">10. Rule Groups and Rules<\/h2>\n\n\n\n<h3 id=\"rule-groups\">Rule groups<\/h3>\n\n\n\n<p>Groups cap the combined effect of related rules.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Group setting<\/th><th>Default\/validation<\/th><th>Behavior<\/th><\/tr><\/thead><tbody><tr><td><code>group_key<\/code><\/td><td>Required unique uppercase identifier, maximum 80 characters<\/td><td>Referenced by rules.<\/td><\/tr><tr><td><code>group_name<\/code><\/td><td>Required; maximum 160 characters<\/td><td>Human-readable group name.<\/td><\/tr><tr><td><code>minimum_contribution<\/code><\/td><td>Default -100; integer -100 through 0<\/td><td>Most negative combined contribution allowed for the group.<\/td><\/tr><tr><td><code>maximum_contribution<\/code><\/td><td>Default 100; integer 0 through 100<\/td><td>Most positive combined contribution allowed for the group.<\/td><\/tr><tr><td><code>priority<\/code><\/td><td>100; integer 0\u20131,000,000<\/td><td>Ordering metadata for stable configuration. Rule priority controls the order in which capped contributions are applied.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Example: three matched engagement rules total +37, but the group maximum is +25. Only +25 reaches the score.<\/p>\n\n\n\n<h3 id=\"rules\">Rules<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Rule setting<\/th><th>Default\/options<\/th><th>Behavior<\/th><\/tr><\/thead><tbody><tr><td><code>enabled<\/code><\/td><td>1\/On<\/td><td>Disabled rules are ignored and do not need to pass active-rule condition checks.<\/td><\/tr><tr><td><code>rule_type<\/code><\/td><td>FIELD_SIGNAL; SOURCE_WEIGHT, FIELD_SIGNAL, CUSTOM_RULE<\/td><td>Classification for administrators and audit. Matching behavior comes from conditions and points.<\/td><\/tr><tr><td><code>reason_code<\/code><\/td><td>Required unique uppercase identifier, maximum 80 characters<\/td><td>Stable explanation code recorded with matched factors.<\/td><\/tr><tr><td><code>rule_name<\/code><\/td><td>Required; maximum 160 characters<\/td><td>Human-readable explanation shown in factor details.<\/td><\/tr><tr><td><code>rule_description<\/code><\/td><td>Optional; maximum 500 characters<\/td><td>Explains the business intent.<\/td><\/tr><tr><td><code>group_key<\/code><\/td><td>Optional<\/td><td>Places the rule under an existing group cap. Blank rules are ungrouped.<\/td><\/tr><tr><td><code>match_mode<\/code><\/td><td>ALL; ALL or ANY<\/td><td>ALL requires every condition. ANY requires at least one.<\/td><\/tr><tr><td><code>points<\/code><\/td><td>Required integer -100 through 100<\/td><td>Added once when the rule matches; negative values subtract.<\/td><\/tr><tr><td><code>priority<\/code><\/td><td>100; integer 0\u20131,000,000<\/td><td>Lower values are evaluated first. This matters when a group cap is reached.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 id=\"rule-conditions\">Rule conditions<\/h3>\n\n\n\n<p>Each enabled rule needs 1\u201350 conditions.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Condition setting<\/th><th>Options\/default<\/th><th>Behavior<\/th><\/tr><\/thead><tbody><tr><td><code>condition_source_type<\/code><\/td><td>SYSTEM_FACT, PROFILE_FIELD, DIMENSION<\/td><td>Chooses where the value comes from.<\/td><\/tr><tr><td><code>system_fact_key<\/code><\/td><td>Required for SYSTEM_FACT<\/td><td>Uses an allowlisted source, presence, or behavior fact. Must be blank for PROFILE_FIELD.<\/td><\/tr><tr><td><code>dimension_key<\/code><\/td><td>Required for DIMENSION<\/td><td>Uses an active dimension mapped in this profile. Its comparison type must equal the dimension type.<\/td><\/tr><tr><td><code>profile_field_id<\/code><\/td><td>Required positive current ID for PROFILE_FIELD; otherwise 0\/blank<\/td><td>Targets one exact mapped field in this draft. IDs can change in a new draft, so use dimensions for cross-source concepts.<\/td><\/tr><tr><td><code>operator<\/code><\/td><td>See operator table below<\/td><td>Defines the comparison.<\/td><\/tr><tr><td><code>comparison_type<\/code><\/td><td>TEXT, NUMBER, BOOLEAN, DATE, SINGLE_SELECT, MULTI_SELECT<\/td><td>Normalizes both actual and configured values. DATE uses <code>YYYY-MM-DD<\/code>.<\/td><\/tr><tr><td><code>comparison_value<\/code><\/td><td>Required except EXISTS\/NOT_EXISTS<\/td><td>Main target value. IN, NOT_IN, ANY_OF, and ALL_OF require a non-empty list of up to 200 values.<\/td><\/tr><tr><td><code>comparison_value_to<\/code><\/td><td>Required only for BETWEEN<\/td><td>Inclusive upper bound.<\/td><\/tr><tr><td><code>priority<\/code><\/td><td>100; integer 0\u20131,000,000<\/td><td>Stable condition order; it does not change ALL\/ANY logic.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h4 id=\"supported-operators\">Supported operators<\/h4>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Operator<\/th><th>Meaning<\/th><th>Compatible types<\/th><\/tr><\/thead><tbody><tr><td>EQUALS \/ NOT_EQUALS<\/td><td>Exact normalized equality or inequality<\/td><td>All scalar types; use list operators for MULTI_SELECT<\/td><\/tr><tr><td>CONTAINS \/ NOT_CONTAINS<\/td><td>Text contains or does not contain text<\/td><td>TEXT, SINGLE_SELECT<\/td><\/tr><tr><td>STARTS_WITH \/ ENDS_WITH<\/td><td>Text prefix or suffix<\/td><td>TEXT, SINGLE_SELECT<\/td><\/tr><tr><td>IN \/ NOT_IN<\/td><td>Scalar is or is not in the configured list<\/td><td>TEXT, NUMBER, BOOLEAN, DATE, SINGLE_SELECT<\/td><\/tr><tr><td>GREATER_THAN \/ GREATER_THAN_OR_EQUAL<\/td><td>Numeric or date comparison<\/td><td>NUMBER, DATE<\/td><\/tr><tr><td>LESS_THAN \/ LESS_THAN_OR_EQUAL<\/td><td>Numeric or date comparison<\/td><td>NUMBER, DATE<\/td><\/tr><tr><td>BETWEEN<\/td><td>Inclusive lower and upper range<\/td><td>NUMBER, DATE<\/td><\/tr><tr><td>EXISTS \/ NOT_EXISTS<\/td><td>Value is present or absent<\/td><td>Any type; no comparison value required<\/td><\/tr><tr><td>ANY_OF<\/td><td>At least one configured option exists in the multi-select value<\/td><td>MULTI_SELECT<\/td><\/tr><tr><td>ALL_OF<\/td><td>Every configured option exists in the multi-select value<\/td><td>MULTI_SELECT<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Text comparisons are exact and case-sensitive after mapping transformations. Use <code>case_mode<\/code> when providers vary capitalization.<\/p>\n\n\n\n<h4 id=\"allowlisted-system-facts\">Allowlisted system facts<\/h4>\n\n\n\n<p>Rules can use source key, module, service, operational source ID, source-instance type\/reference, marketing source ID\/name, provider form ID, page ID, campaign ID, ad set ID, ad ID, received date\/time, email\/phone\/company presence, latest behavior event\/signal, active signal keys, reply count, deal-created count, deal-won count, and deal-lost count.<\/p>\n\n\n\n<p>Use the exact keys displayed in <strong>Rule Reference<\/strong>. Other submitted field keys are not accepted as system facts; company-specific fields must be approved and mapped.<\/p>\n\n\n\n<h2 id=\"11-synthetic-deterministic-preview\">11. Synthetic Deterministic Preview<\/h2>\n\n\n\n<p>Preview uses three JSON containers:<\/p>\n\n\n\n<ul><li><code>system<\/code>: allowlisted synthetic system facts;<\/li><li><code>profile_fields<\/code>: current mapped profile-field IDs and synthetic values; and<\/li><li><code>dimensions<\/code>: active mapped dimension keys and synthetic values.<\/li><\/ul>\n\n\n\n<p>Use non-personal values only. Preview reads no contact, persists no run or score, changes no routing, calls no LLM, and consumes no AI credits.<\/p>\n\n\n\n<p>Select <strong>Run Deterministic Preview<\/strong>. A successful result shows the score, band, matched factors, and group-cap breakdown. Preview confirms deterministic logic only; it does not prove that a real provider will supply a mapped field.<\/p>\n\n\n\n<h2 id=\"12-validate-and-publish\">12. Validate and publish<\/h2>\n\n\n\n<p>Select <strong>Validate Draft<\/strong> after saving every section. Validation checks the profile, field revisions, dimensions, mappings, rules, conditions, bands, bindings, triggers, LLM policy, and conflicts with other published profiles.<\/p>\n\n\n\n<p>Select <strong>Publish Draft<\/strong> only after validation passes. Publishing:<\/p>\n\n\n\n<ul><li>freezes the version for repeatable scoring and audit;<\/li><li>makes it eligible for new matching events;<\/li><li>retires the profile&#8217;s previous published version; and<\/li><li>increments profile-selection configuration for future events.<\/li><\/ul>\n\n\n\n<p>Publishing does not retroactively recalculate every existing contact. Existing immutable runs remain tied to the version that produced them.<\/p>\n\n\n\n<p>To change a published profile, select <strong>Create Next Draft<\/strong>. The new draft copies the published mappings, groups, rules, conditions, bands, bindings, triggers, and LLM policy. Edit, preview, validate, and publish the next version.<\/p>\n\n\n\n<h2 id=\"13-workflow-recalculation\">13. Workflow recalculation<\/h2>\n\n\n\n<p>When Lead Scoring management is available, Workflow actions include <strong>Recalculate Lead Score<\/strong> for contacts.<\/p>\n\n\n\n<p>This action requests a contact-stage recalculation using the contact&#8217;s eligible published\/frozen profile and current approved scoring facts. It does not accept a score or arbitrary point adjustment from the workflow. The recalculation action is processed before later actions in the same workflow. Duplicate causal re-entry is suppressed to prevent scoring loops.<\/p>\n\n\n\n<p>Use it after a workflow changes data that your scoring rules depend on but that does not already emit one of the supported reply or deal events.<\/p>\n\n\n\n<h2 id=\"14-crm-score-display\">14. CRM score display<\/h2>\n\n\n\n<p>On <strong>CRM &gt; Contacts<\/strong>, the Lead Score column displays the effective score and band. A dash means the score is pending, unavailable, not selected by the display policy, or no eligible run has completed.<\/p>\n\n\n\n<p>On <strong>Contact Conversation<\/strong>, the Lead Score card appears above Lead Status. It shows:<\/p>\n\n\n\n<ul><li>effective score;<\/li><li>score band and profile name;<\/li><li>last update time; and<\/li><li>a high, medium, low, or neutral color treatment based first on the band&#8217;s color key and then on score thresholds.<\/li><\/ul>\n\n\n\n<p>Possible messages include <strong>Lead scoring has no published profile<\/strong>, <strong>No eligible scoring run has completed<\/strong>, and <strong>Score is temporarily unavailable<\/strong>.<\/p>\n\n\n\n<h2 id=\"15-run-and-job-logs\">15. Run and Job Logs<\/h2>\n\n\n\n<p>Open <strong>Run and Job Logs<\/strong> to troubleshoot individual activity. Raw lead payloads, trusted intake context, provider responses, and LLM content are intentionally not displayed.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Filter<\/th><th>Default\/options<\/th><th>Use<\/th><\/tr><\/thead><tbody><tr><td><strong>Profile<\/strong><\/td><td>All profiles<\/td><td>Limit all tables to one company profile.<\/td><\/tr><tr><td><strong>Phase<\/strong><\/td><td>All, Event, Contact<\/td><td>Event is pre-assignment; Contact is post-assignment or later recalculation.<\/td><\/tr><tr><td><strong>Run status<\/strong><\/td><td>All, COMPLETED, FAILED_SAFE, SKIPPED_NO_PROFILE, SKIPPED_UNCHANGED, SKIPPED_SECURITY_POLICY<\/td><td>Find completed, safely failed, or skipped evaluations.<\/td><\/tr><tr><td><strong>From<\/strong><\/td><td>Empty<\/td><td>Includes records from 00:00:00 on the selected date.<\/td><\/tr><tr><td><strong>To<\/strong><\/td><td>Empty<\/td><td>Includes records through 23:59:59 on the selected date.<\/td><\/tr><tr><td><strong>Contact ID<\/strong><\/td><td>Empty; positive ID<\/td><td>Limits to one company-owned contact.<\/td><\/tr><tr><td><strong>Queue ID<\/strong><\/td><td>Empty; positive ID<\/td><td>Limits to one company-owned inbound queue event.<\/td><\/tr><tr><td><strong>Job type<\/strong><\/td><td>All plus the listed discovery, evaluation, LLM, rescore, backfill, and delivery types<\/td><td>Filters operational jobs. Some listed future\/reserved types may have no records in the current release.<\/td><\/tr><tr><td><strong>Job status<\/strong><\/td><td>All, PENDING, RUNNING, RETRY_WAIT, COMPLETED, FAILED_FINAL, CANCELLED<\/td><td>Shows current processing state.<\/td><\/tr><tr><td><strong>Rows per table<\/strong><\/td><td>100<\/td><td>1\u2013500 rows in each table.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Select a run ID to see sanitized facts, matched-factor breakdown, and safe run metadata. Use <strong>CRM Scoring Events<\/strong> to confirm event\/signal acceptance and <strong>Evaluation Jobs<\/strong> to inspect attempts and safe error codes.<\/p>\n\n\n\n<h2 id=\"16-deterministic-report\">16. Deterministic Report<\/h2>\n\n\n\n<p>The report includes only completed deterministic evaluations. It does not use LLM-adjusted effective scores.<\/p>\n\n\n\n<p>Filters are <strong>Profile<\/strong>, <strong>Phase<\/strong>, <strong>From<\/strong>, and <strong>To<\/strong>, with the same phase and inclusive date behavior as logs.<\/p>\n\n\n\n<p>The report shows:<\/p>\n\n\n\n<ul><li>completed runs, profiles, event runs, contact runs, average score, and score range;<\/li><li>results by profile, version, phase, and band;<\/li><li>daily trend; and<\/li><li>results by source and form.<\/li><\/ul>\n\n\n\n<p>Statistics are suppressed until a cohort contains at least five completed runs. Exports are not available from this report.<\/p>\n\n\n\n<h1 id=\"which-mode-should-i-choose\">Which mode should I choose?<\/h1>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Requirement<\/th><th>Recommended choice<\/th><\/tr><\/thead><tbody><tr><td>Start safely with explainable scoring<\/td><td>Deterministic rules, LLM Mode OFF<\/td><\/tr><tr><td>Evaluate AI quality without changing priority<\/td><td>SHADOW<\/td><\/tr><tr><td>Apply controlled AI adjustments after testing<\/td><td>HYBRID with Max Adjustment 5\u201310 and Min Confidence 0.75 or higher<\/td><\/tr><tr><td>Use one policy for most leads<\/td><td>One default profile<\/td><\/tr><tr><td>Use a different policy for one exact form<\/td><td>Non-default profile with an exact form binding<\/td><\/tr><tr><td>Reuse budget\/company-size logic across sources<\/td><td>Reusable dimension<\/td><\/tr><tr><td>Ignore optional missing data<\/td><td>NO_MATCH<\/td><\/tr><tr><td>Stop scoring if required data is missing<\/td><td>FAIL_SAFE<\/td><\/tr><tr><td>Prefer one of several equivalent mapped fields<\/td><td>FIRST_NON_MISSING with deliberate mapping priorities<\/td><\/tr><tr><td>Reject inconsistent values<\/td><td>INVALID_CONFLICT<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h1 id=\"complete-configuration-examples\">Complete configuration examples<\/h1>\n\n\n\n<h2 id=\"example-1-basic-deterministic-starter-setup\">Example 1: Basic deterministic starter setup<\/h2>\n\n\n\n<h3 id=\"business-requirement\">Business requirement<\/h3>\n\n\n\n<p>A small sales team wants every new lead ranked using contact completeness, replies, and deal progress.<\/p>\n\n\n\n<h3 id=\"configuration\">Configuration<\/h3>\n\n\n\n<ol type=\"1\"><li>Enable Lead Scoring.<\/li><li>Create <strong>Inbound Sales<\/strong> with key <code>INBOUND_SALES<\/code>, Base Score 40, Default profile On, and starter rules On.<\/li><li>Keep LLM Mode OFF.<\/li><li>Review the starter bands, groups, rules, and triggers.<\/li><li>Preview, validate, and publish.<\/li><li>Keep CRM display on Latest current score.<\/li><\/ol>\n\n\n\n<h3 id=\"result\">Result<\/h3>\n\n\n\n<p>New matching leads start at 40 and gain up to 10 contact-quality points. Replies and deal events recalculate the contact-stage score according to the starter rules. Scores appear in CRM after an eligible contact run completes.<\/p>\n\n\n\n<h2 id=\"example-2-facebook-company-size-qualification\">Example 2: Facebook company-size qualification<\/h2>\n\n\n\n<h3 id=\"business-requirement-1\">Business requirement<\/h3>\n\n\n\n<p>Facebook leads answering <code>over_50_users<\/code> should gain 20 points.<\/p>\n\n\n\n<h3 id=\"configuration-1\">Configuration<\/h3>\n\n\n\n<ol type=\"1\"><li>Submit a test Facebook lead and approve the company-size field as SINGLE_SELECT and BUSINESS.<\/li><li>Create <code>COMPANY_SIZE<\/code> as a SINGLE_SELECT dimension.<\/li><li>Map the approved revision to that dimension with deterministic scoring enabled.<\/li><li>Add a +20 rule using DIMENSION, key <code>COMPANY_SIZE<\/code>, operator EQUALS, type SINGLE_SELECT, value <code>over_50_users<\/code>.<\/li><li>Bind the profile to the exact synchronized Facebook form.<\/li><li>Preview using <code>dimensions.COMPANY_SIZE = over_50_users<\/code>, then validate and publish.<\/li><\/ol>\n\n\n\n<h3 id=\"result-1\">Result<\/h3>\n\n\n\n<p>Only leads using the matching profile and exact approved answer receive the 20 points. Other Facebook answers do not match the rule.<\/p>\n\n\n\n<h2 id=\"example-3-engage-pricing-page-intent\">Example 3: Engage pricing-page intent<\/h2>\n\n\n\n<h3 id=\"business-requirement-2\">Business requirement<\/h3>\n\n\n\n<p>A visitor who submits a lead after viewing the pricing page should gain 15 points.<\/p>\n\n\n\n<h3 id=\"configuration-2\">Configuration<\/h3>\n\n\n\n<ol type=\"1\"><li>Send a controlled Engage lead containing the conversion-page context.<\/li><li>Approve the discovered conversion-page field as TEXT and BUSINESS for deterministic use.<\/li><li>Map it to a direct profile field or a TEXT dimension such as <code>CONVERSION_PAGE<\/code>.<\/li><li>Add a +15 rule with EQUALS or CONTAINS for your exact pricing-page URL\/value.<\/li><li>Bind the profile to ENGAGE or the intended source\/form context.<\/li><li>Preview, validate, and publish.<\/li><\/ol>\n\n\n\n<h3 id=\"result-2\">Result<\/h3>\n\n\n\n<p>The lead receives the points only when the approved normalized page value matches. The application does not hard-code which URL is a pricing page.<\/p>\n\n\n\n<h2 id=\"example-4-dynamic-no-response-scoring\">Example 4: Dynamic no-response scoring<\/h2>\n\n\n\n<h3 id=\"business-requirement-3\">Business requirement<\/h3>\n\n\n\n<p>Reduce the score by 10 if no customer reply is received within 48 hours of assignment.<\/p>\n\n\n\n<h3 id=\"configuration-3\">Configuration<\/h3>\n\n\n\n<ol type=\"1\"><li>Add an enabled LEAD_ASSIGNED trigger with signal <code>AWAITING_RESPONSE<\/code>, debounce 172800, lookback longer than 172800, and REEVALUATE.<\/li><li>Add an enabled MESSAGE_REPLY_RECEIVED trigger with a suitable lookback.<\/li><li>Add an ALL rule worth -10 requiring active signal <code>AWAITING_RESPONSE<\/code> and reply count equal to 0.<\/li><li>Validate and publish.<\/li><\/ol>\n\n\n\n<h3 id=\"result-3\">Result<\/h3>\n\n\n\n<p>The first recalculation occurs after 48 hours. If no reply is active, the rule subtracts 10. A qualifying reply prevents the no-response rule from matching. The expiry job recalculates again when the configured signal window ends.<\/p>\n\n\n\n<h2 id=\"example-5-advanced-profile-selection-and-routing\">Example 5: Advanced profile selection and routing<\/h2>\n\n\n\n<h3 id=\"business-requirement-4\">Business requirement<\/h3>\n\n\n\n<p>Use a general default profile, but a stricter policy for one Facebook enterprise-demo form; route Hot enterprise leads to a specialist team.<\/p>\n\n\n\n<h3 id=\"configuration-4\">Configuration<\/h3>\n\n\n\n<ol type=\"1\"><li>Publish a default general profile.<\/li><li>Create a non-default enterprise profile with an exact FACEBOOK_FORM binding, valid integration ID, and matching form\/provider references.<\/li><li>Publish it and enable Routing Integration.<\/li><li>In Advanced Lead Routing, create a rule for profile key <code>ENTERPRISE_DEMO<\/code> and routing band HOT.<\/li><li>Keep a normal routing fallback.<\/li><\/ol>\n\n\n\n<h3 id=\"result-4\">Result<\/h3>\n\n\n\n<p>The exact form binding outranks the broad\/default profile. A completed event-stage deterministic Hot score can select the specialist route. If scoring is unavailable, the standard routing fallback still assigns the lead.<\/p>\n\n\n\n<h2 id=\"example-6-llm-limits-and-exceptions\">Example 6: LLM limits and exceptions<\/h2>\n\n\n\n<h3 id=\"business-requirement-5\">Business requirement<\/h3>\n\n\n\n<p>Evaluate AI enrichment safely without changing sales priority or exceeding 50 requests and 100 credits per day.<\/p>\n\n\n\n<h3 id=\"configuration-5\">Configuration<\/h3>\n\n\n\n<ol type=\"1\"><li>Set profile LLM Mode to SHADOW, Max Adjustment 10, Min Confidence 0.75, and apply the recommended policy.<\/li><li>Approve and map at least one eligible BUSINESS structured field with both LLM flags enabled.<\/li><li>Enable company LLM enrichment.<\/li><li>Set Daily request limit to 50 and Daily credit limit to 100.00.<\/li><li>Keep a conservative queue and concurrency limit.<\/li><\/ol>\n\n\n\n<h3 id=\"result-5\">Result<\/h3>\n\n\n\n<p>Eligible contact-stage runs can call the LLM and successful calls consume credits, but the CRM score remains deterministic. Requests stop when any configured resource limit or available-credit check fails; deterministic scoring continues.<\/p>\n\n\n\n<h1 id=\"what-happens-if\">What happens if?<\/h1>\n\n\n\n<h3 id=\"no-profile-matches-a-lead\">No profile matches a lead<\/h3>\n\n\n\n<p>The system uses the published default profile. If there is no published default, the scoring attempt is skipped with no score. Normal routing and assignment continue.<\/p>\n\n\n\n<h3 id=\"two-bindings-match\">Two bindings match<\/h3>\n\n\n\n<p>The more-specific binding wins. At equal specificity, higher priority wins; then the binding with more selectors wins. Publishing blocks ambiguous equal-specificity\/equal-priority overlap across profiles.<\/p>\n\n\n\n<h3 id=\"a-mapped-field-is-missing\">A mapped field is missing<\/h3>\n\n\n\n<p>NO_MATCH ignores it. FAIL_SAFE stops the evaluation without producing a misleading score.<\/p>\n\n\n\n<h3 id=\"two-fields-mapped-to-one-dimension-disagree\">Two fields mapped to one dimension disagree<\/h3>\n\n\n\n<p>INVALID_CONFLICT safely rejects the evaluation. FIRST_NON_MISSING uses the value from the lowest mapping-priority number.<\/p>\n\n\n\n<h3 id=\"rule-points-exceed-a-group-maximum\">Rule points exceed a group maximum<\/h3>\n\n\n\n<p>The group contributes only its configured maximum. Later rules in that group may contribute zero or only the remaining allowance.<\/p>\n\n\n\n<h3 id=\"the-calculated-score-is-below-0-or-above-100\">The calculated score is below 0 or above 100<\/h3>\n\n\n\n<p>It is limited to 0 or 100 before band selection. A HYBRID adjustment is also limited to the same range.<\/p>\n\n\n\n<h3 id=\"llm-is-enabled-but-no-score-appears\">LLM is enabled but no score appears<\/h3>\n\n\n\n<p>LLM does not create the base score. Confirm Lead Scoring is on, a matching profile is published, deterministic contact scoring completed, and the CRM display policy permits that profile.<\/p>\n\n\n\n<h3 id=\"ai-credits-or-llm-capacity-are-unavailable\">AI credits or LLM capacity are unavailable<\/h3>\n\n\n\n<p>No provider request is sent, no failed request is charged, and deterministic scoring remains effective. Check Run and Job Logs for the safe skip code.<\/p>\n\n\n\n<h3 id=\"lead-scoring-is-turned-off-with-pending-jobs\">Lead Scoring is turned off with pending jobs<\/h3>\n\n\n\n<p>Pending jobs remain stored and unprocessed. They may resume after the feature is enabled again. Normal CRM operations continue.<\/p>\n\n\n\n<h3 id=\"a-published-profile-needs-editing\">A published profile needs editing<\/h3>\n\n\n\n<p>Published versions cannot be edited. Create the next draft, change it, preview, validate, and publish the replacement.<\/p>\n\n\n\n<h1 id=\"common-configuration-mistakes\">Common configuration mistakes<\/h1>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Problem<\/th><th>Why it happens<\/th><th>How to fix it<\/th><\/tr><\/thead><tbody><tr><td>Lead Score shows <code>--<\/code><\/td><td>No matching published profile or no eligible contact run completed.<\/td><td>Publish a default or bound profile and inspect logs. If scoring work never progresses, ask your deployment administrator to verify background processing.<\/td><\/tr><tr><td>LLM is on but score remains deterministic<\/td><td>Profile mode is OFF\/SHADOW, confidence is too low, or no eligible mapped facts exist.<\/td><td>Use HYBRID only after SHADOW testing; verify both field-approval and mapping LLM switches.<\/td><\/tr><tr><td>Draft says LLM policy is incomplete<\/td><td>SHADOW\/HYBRID has Max Adjustment 0 or a blank Rubric Version.<\/td><td>Select <strong>Apply Recommended LLM Settings<\/strong>, choose the intended mode, and save.<\/td><\/tr><tr><td>A field cannot be approved for scoring<\/td><td>Its privacy is PERSONAL\/SENSITIVE, type is ineligible, or a conflict is unresolved.<\/td><td>Keep\/raise privacy, select a compatible type, and explicitly resolve genuine conflicts. Do not bypass privacy restrictions.<\/td><\/tr><tr><td>A mapping blocks publication<\/td><td>The approval is stale\/hidden\/blocked, deterministic mapping is off, or the dimension is incompatible.<\/td><td>Reapprove\/remap the current revision, remove unused mappings, or select a matching active dimension.<\/td><\/tr><tr><td>A direct-field rule stops working in a new draft<\/td><td>It uses an old generated profile-field ID.<\/td><td>Save mappings first and use the current ID, or use a stable dimension key.<\/td><\/tr><tr><td>Text matching is inconsistent<\/td><td>Provider capitalization or whitespace varies.<\/td><td>Enable trim and choose UPPER or LOWER consistently, then use the normalized comparison value.<\/td><\/tr><tr><td>Bands will not save or publish<\/td><td>There is a gap, overlap, duplicate key, or the ranges do not end at 100.<\/td><td>Sort ranges from 0 upward and cover every integer exactly once.<\/td><\/tr><tr><td>Non-default profile will not publish<\/td><td>It has no active binding.<\/td><td>Add at least one company-owned active source\/form binding.<\/td><\/tr><tr><td>Binding validation fails<\/td><td>Form type\/reference are incomplete, Facebook identifiers disagree, or a selector belongs to another company.<\/td><td>Use the IDs shown in this company and complete every linked selector.<\/td><\/tr><tr><td>No-response rule applies at the wrong time<\/td><td>Debounce was treated as lookback, or reply trigger is missing.<\/td><td>Use debounce as the wait time, keep a longer lookback, and configure reply tracking.<\/td><\/tr><tr><td>Trigger exists but score does not change<\/td><td>No rule references its signal\/count, or group caps absorb its points.<\/td><td>Add or adjust the matching rule and review group contribution limits.<\/td><\/tr><tr><td>Report shows Suppressed<\/td><td>The selected cohort has fewer than five completed deterministic runs.<\/td><td>Broaden the date\/profile filters or wait for more completed runs.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h1 id=\"recommended-configurations\">Recommended configurations<\/h1>\n\n\n\n<h2 id=\"small-team\">Small team<\/h2>\n\n\n\n<p>Best for one sales process:<\/p>\n\n\n\n<ul><li>one default profile;<\/li><li>Base Score 40;<\/li><li>starter rules reviewed and simplified;<\/li><li>Latest current score display;<\/li><li>LLM OFF; and<\/li><li>routing integration off until the team trusts the bands.<\/li><\/ul>\n\n\n\n<h2 id=\"growing-multi-source-team\">Growing multi-source team<\/h2>\n\n\n\n<p>Best for several inbound channels:<\/p>\n\n\n\n<ul><li>one default profile plus exact-form profiles only where policy truly differs;<\/li><li>reusable dimensions for budget, company size, product interest, and page intent;<\/li><li>active reply\/deal\/no-response triggers;<\/li><li>strict mapping conflicts for important numeric values;<\/li><li>deterministic score-based routing with a fallback; and<\/li><li>SHADOW mode with conservative daily limits.<\/li><\/ul>\n\n\n\n<h2 id=\"advanced-operation\">Advanced operation<\/h2>\n\n\n\n<p>Best for mature governance:<\/p>\n\n\n\n<ul><li>exact bindings with documented priorities;<\/li><li>tested group caps and complete bands;<\/li><li>synthetic preview cases for every critical rule boundary;<\/li><li>SHADOW analysis before HYBRID;<\/li><li>HYBRID Max Adjustment no more than 5\u201310 initially;<\/li><li>Min Confidence at least 0.75;<\/li><li>explicit credit, queue, and concurrency limits; and<\/li><li>regular review of logs, skipped jobs, score distribution, and sales outcomes.<\/li><\/ul>\n\n\n\n<h1 id=\"settings-quick-reference\">Settings quick reference<\/h1>\n\n\n\n<p>The table below accounts for every persistent setting and customer-facing operational control in the current Lead Scoring UI.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>ID<\/th><th>Setting\/control<\/th><th>Purpose<\/th><th>Default<\/th><th>Depends on<\/th><th>Recommended use<\/th><\/tr><\/thead><tbody><tr><td>C001<\/td><td>Enable lead scoring for this company<\/td><td>Master runtime switch<\/td><td>Off<\/td><td>Plan, CRM, admin permission<\/td><td>Enable after at least one draft is ready to test.<\/td><\/tr><tr><td>C002<\/td><td>Routing Integration<\/td><td>Expose event deterministic facts to routing<\/td><td>Off<\/td><td>C001, Advanced Lead Routing<\/td><td>Enable only after score bands and routing fallback are tested.<\/td><\/tr><tr><td>C003<\/td><td>Score to display<\/td><td>Select CRM score policy<\/td><td>Latest current score<\/td><td>C001<\/td><td>Use Latest for most companies; hide during private testing.<\/td><\/tr><tr><td>C004<\/td><td>Published profile<\/td><td>Restrict CRM display to one profile<\/td><td>None<\/td><td>C003 = selected profile<\/td><td>Use when one published profile is the official CRM score.<\/td><\/tr><tr><td>C005<\/td><td>Enable optional LLM enrichment<\/td><td>Company LLM runtime switch<\/td><td>Off<\/td><td>C001, eligible profile\/facts\/credits<\/td><td>Start only after deterministic scoring works; use SHADOW first.<\/td><\/tr><tr><td>C006<\/td><td>Daily request limit<\/td><td>Cap daily LLM operations<\/td><td>100<\/td><td>C005<\/td><td>Set from expected eligible lead volume and budget.<\/td><\/tr><tr><td>C007<\/td><td>Daily credit limit<\/td><td>Cap estimated daily LLM credits<\/td><td>200.00<\/td><td>C005<\/td><td>Use as the company&#8217;s hard daily AI-spend guardrail.<\/td><\/tr><tr><td>C008<\/td><td>Maximum queued jobs<\/td><td>Cap queued\/running LLM work<\/td><td>50<\/td><td>C005<\/td><td>Keep conservative unless sustained queue growth is expected.<\/td><\/tr><tr><td>C009<\/td><td>Maximum concurrent jobs<\/td><td>Cap simultaneous LLM work<\/td><td>2<\/td><td>C005<\/td><td>Increase only when provider capacity and budget allow it.<\/td><\/tr><tr><td>C010<\/td><td>Profile Name<\/td><td>Name the scoring profile<\/td><td>Required<\/td><td>New Profile<\/td><td>Use a clear business name such as Enterprise Inbound.<\/td><\/tr><tr><td>C011<\/td><td>Profile Key<\/td><td>Stable unique identifier<\/td><td>Required<\/td><td>New Profile<\/td><td>Choose a permanent key before publishing or routing by it.<\/td><\/tr><tr><td>C012<\/td><td>Profile Description<\/td><td>Explain profile purpose<\/td><td>Blank<\/td><td>New Profile<\/td><td>Record included sources, audience, and qualification goal.<\/td><\/tr><tr><td>C013<\/td><td>New Profile Base Score<\/td><td>Starting deterministic score<\/td><td>40<\/td><td>New Profile<\/td><td>Use 40\u201350 for a neutral starting position.<\/td><\/tr><tr><td>C014<\/td><td>Default profile<\/td><td>Use as fallback<\/td><td>Off<\/td><td>Only one published default<\/td><td>Make the first general-purpose profile the default.<\/td><\/tr><tr><td>C015<\/td><td>Apply recommended starter rules<\/td><td>Add starter bands\/rules\/triggers<\/td><td>On<\/td><td>New Profile<\/td><td>Keep on for the first profile, then adapt every starter value.<\/td><\/tr><tr><td>C016<\/td><td>Dimension Name<\/td><td>Name shared business concept<\/td><td>Required<\/td><td>New Dimension<\/td><td>Use when differently named fields represent one concept.<\/td><\/tr><tr><td>C017<\/td><td>Dimension Key<\/td><td>Stable rule key<\/td><td>Required<\/td><td>New Dimension<\/td><td>Choose a permanent business key such as COMPANY_SIZE.<\/td><\/tr><tr><td>C018<\/td><td>Dimension Description<\/td><td>Explain meaning\/values<\/td><td>Blank<\/td><td>New Dimension<\/td><td>Document expected source fields and normalized values.<\/td><\/tr><tr><td>C019<\/td><td>Canonical Type<\/td><td>Fix shared value type<\/td><td>TEXT shown first<\/td><td>Compatible mapped fields<\/td><td>Match the approved type of every field in the dimension.<\/td><\/tr><tr><td>C020<\/td><td>Privacy Floor<\/td><td>Set minimum privacy<\/td><td>BUSINESS<\/td><td>Compatible mapped fields<\/td><td>Keep BUSINESS unless a stricter source field requires more.<\/td><\/tr><tr><td>C021<\/td><td>Type Override<\/td><td>Approve effective field type<\/td><td>Observed type<\/td><td>Field Review<\/td><td>Override only after confirming the provider&#8217;s real data shape.<\/td><\/tr><tr><td>C022<\/td><td>Privacy Classification<\/td><td>Confirm\/raise privacy<\/td><td>BUSINESS selected<\/td><td>System privacy floor<\/td><td>Classify conservatively; never lower the detected privacy floor.<\/td><\/tr><tr><td>C023<\/td><td>Allow deterministic scoring<\/td><td>Permit deterministic mapping<\/td><td>On<\/td><td>Eligible type\/privacy<\/td><td>Enable for fields intended for explainable scoring rules.<\/td><\/tr><tr><td>C024<\/td><td>Allow LLM use<\/td><td>Permit later LLM mapping<\/td><td>Off<\/td><td>Eligible structured type\/privacy<\/td><td>Enable only for necessary, eligible structured business facts.<\/td><\/tr><tr><td>C025<\/td><td>Resolve observed type conflict<\/td><td>Confirm intentional conflict resolution<\/td><td>Off<\/td><td>TYPE_CONFLICT field<\/td><td>Use only after reviewing conflicting samples and selecting a type.<\/td><\/tr><tr><td>C026<\/td><td>Hide field<\/td><td>Remove field from current approval use<\/td><td>Action<\/td><td>Discovered field<\/td><td>Hide irrelevant fields that may be reviewed later.<\/td><\/tr><tr><td>C027<\/td><td>Block field<\/td><td>Prevent future review\/use<\/td><td>Action<\/td><td>Discovered field<\/td><td>Block prohibited or permanently unsuitable scoring data.<\/td><\/tr><tr><td>C028<\/td><td>Draft Base Score<\/td><td>Starting score for this version<\/td><td>Profile value<\/td><td>Draft<\/td><td>Tune with rule ranges so positive and negative movement is useful.<\/td><\/tr><tr><td>C029<\/td><td>LLM Mode<\/td><td>OFF, SHADOW, or HYBRID<\/td><td>OFF<\/td><td>Draft; C005 for runtime<\/td><td>Use OFF initially, SHADOW for evaluation, HYBRID after validation.<\/td><\/tr><tr><td>C030<\/td><td>Max Adjustment<\/td><td>Bound LLM adjustment<\/td><td>10 recommended<\/td><td>C029 SHADOW\/HYBRID<\/td><td>Start at 5\u201310 to preserve deterministic influence.<\/td><\/tr><tr><td>C031<\/td><td>Min Confidence<\/td><td>HYBRID application threshold<\/td><td>0.75 recommended<\/td><td>C029 HYBRID<\/td><td>Start at 0.75 or higher and tune from SHADOW evidence.<\/td><\/tr><tr><td>C032<\/td><td>Rubric Version<\/td><td>Select server rubric version<\/td><td>sales-intent-v1<\/td><td>C029 SHADOW\/HYBRID<\/td><td>Keep the supplied version unless an operator provides another.<\/td><\/tr><tr><td>C033<\/td><td>max_input_facts<\/td><td>Bound LLM fact count<\/td><td>30 recommended<\/td><td>C029, eligible mappings<\/td><td>Keep only enough facts to cover the sales rubric.<\/td><\/tr><tr><td>C034<\/td><td>max_fact_value_chars<\/td><td>Bound each LLM value<\/td><td>300 recommended<\/td><td>C029<\/td><td>Use a conservative bound for concise structured facts.<\/td><\/tr><tr><td>C035<\/td><td>max_total_input_bytes<\/td><td>Bound total LLM input<\/td><td>8,192 recommended<\/td><td>C029<\/td><td>Keep the recommendation unless validated facts require less.<\/td><\/tr><tr><td>C036<\/td><td>max_estimated_tokens<\/td><td>Bound estimated input tokens<\/td><td>2,000 recommended<\/td><td>C029<\/td><td>Use as an input-size and cost safeguard.<\/td><\/tr><tr><td>C037<\/td><td>max_free_text_fields<\/td><td>Bound eligible free-text facts<\/td><td>0 recommended<\/td><td>C038 and field policy<\/td><td>Keep at 0 unless an approved policy explicitly permits free text.<\/td><\/tr><tr><td>C038<\/td><td>allow_business_free_text<\/td><td>Permit eligible BUSINESS free text<\/td><td>Off<\/td><td>C037 &gt;= 1, field policy<\/td><td>Keep off for privacy and predictable input control.<\/td><\/tr><tr><td>C039<\/td><td>allow_safe_summary<\/td><td>Permit bounded result summary<\/td><td>On<\/td><td>C040 &gt;= 1<\/td><td>Enable when administrators need a short validated explanation.<\/td><\/tr><tr><td>C040<\/td><td>safe_summary_max_chars<\/td><td>Bound result summary<\/td><td>240 recommended<\/td><td>C039<\/td><td>Keep short enough for review without storing verbose content.<\/td><\/tr><tr><td>C041<\/td><td>reason_code_allowlist<\/td><td>Restrict returned LLM reasons<\/td><td>Two recommended codes<\/td><td>C029<\/td><td>List only reason codes used by the business rubric.<\/td><\/tr><tr><td>C042<\/td><td>inbound_field_revision_id<\/td><td>Select exact approved field revision<\/td><td>Required<\/td><td>Approved field<\/td><td>Copy the current approved ID shown beside the draft.<\/td><\/tr><tr><td>C043<\/td><td>dimension_id<\/td><td>Map to shared dimension<\/td><td>0<\/td><td>Compatible active dimension<\/td><td>Use 0 for an exact field or a dimension for cross-source reuse.<\/td><\/tr><tr><td>C044<\/td><td>display_label<\/td><td>Label mapped field<\/td><td>Required<\/td><td>C042<\/td><td>Use a recognizable business label for administrators.<\/td><\/tr><tr><td>C045<\/td><td>transformation trim<\/td><td>Trim whitespace<\/td><td>On<\/td><td>Mapping<\/td><td>Keep on for stable comparisons.<\/td><\/tr><tr><td>C046<\/td><td>transformation case_mode<\/td><td>Normalize text case<\/td><td>NONE<\/td><td>Mapping<\/td><td>Use UPPER or LOWER when provider capitalization varies.<\/td><\/tr><tr><td>C047<\/td><td>transformation sort_multi_values<\/td><td>Sort multi-select values<\/td><td>Off<\/td><td>MULTI_SELECT mapping<\/td><td>Enable when option order should not affect normalized evidence.<\/td><\/tr><tr><td>C048<\/td><td>missing_value_policy<\/td><td>Ignore or fail safely on missing value<\/td><td>NO_MATCH<\/td><td>Mapping<\/td><td>Use NO_MATCH for optional facts; FAIL_SAFE for mandatory facts.<\/td><\/tr><tr><td>C049<\/td><td>mapping_priority<\/td><td>Choose first equivalent candidate<\/td><td>100 if omitted<\/td><td>Shared dimension candidates<\/td><td>Give the preferred source field the lowest number.<\/td><\/tr><tr><td>C050<\/td><td>conflict_policy<\/td><td>Select or reject conflicting values<\/td><td>INVALID_CONFLICT if omitted<\/td><td>Shared dimension candidates<\/td><td>Use INVALID_CONFLICT for important facts; otherwise FIRST_NON_MISSING.<\/td><\/tr><tr><td>C051<\/td><td>deterministic_enabled<\/td><td>Use mapping in deterministic scoring<\/td><td>On<\/td><td>C023; required for publish<\/td><td>Keep on for every saved active mapping.<\/td><\/tr><tr><td>C052<\/td><td>llm_enabled<\/td><td>Offer mapping to LLM policy<\/td><td>Off<\/td><td>C024, C005, C029<\/td><td>Enable selectively after the field approval also allows LLM use.<\/td><\/tr><tr><td>C053<\/td><td>band_key<\/td><td>Stable score-band identifier<\/td><td>Required<\/td><td>Score Bands<\/td><td>Use permanent business keys such as HOT, WARM, and COLD.<\/td><\/tr><tr><td>C054<\/td><td>band_name<\/td><td>User-facing band label<\/td><td>Required<\/td><td>Score Bands<\/td><td>Use labels sales users can interpret immediately.<\/td><\/tr><tr><td>C055<\/td><td>color_key<\/td><td>CRM color category<\/td><td>DEFAULT if omitted<\/td><td>Score Bands<\/td><td>Use supported semantic colors to distinguish priority visually.<\/td><\/tr><tr><td>C056<\/td><td>minimum_score<\/td><td>Inclusive band minimum<\/td><td>Required<\/td><td>Complete 0\u2013100 coverage<\/td><td>Start the first band at 0 and avoid gaps.<\/td><\/tr><tr><td>C057<\/td><td>maximum_score<\/td><td>Inclusive band maximum<\/td><td>Required<\/td><td>Complete 0\u2013100 coverage<\/td><td>End the final band at 100 and avoid overlaps.<\/td><\/tr><tr><td>C058<\/td><td>band priority<\/td><td>Stable band order metadata<\/td><td>100<\/td><td>Score Bands<\/td><td>Use distinct values for predictable administrator ordering.<\/td><\/tr><tr><td>C059<\/td><td>trigger_key<\/td><td>Choose authoritative event<\/td><td>Required<\/td><td>Trigger policy<\/td><td>Add only events that should cause score reconsideration.<\/td><\/tr><tr><td>C060<\/td><td>signal_key<\/td><td>Name active company signal<\/td><td>Required<\/td><td>Rule behavior condition<\/td><td>Use a stable key that clearly describes the active behavior.<\/td><\/tr><tr><td>C061<\/td><td>trigger enabled<\/td><td>Activate\/deactivate policy<\/td><td>Off if omitted<\/td><td>Trigger policy<\/td><td>Enable after a matching behavior rule is configured.<\/td><\/tr><tr><td>C062<\/td><td>lookback_seconds<\/td><td>Signal lifetime<\/td><td>0<\/td><td>C064 expiry consistency<\/td><td>Set to the period in which the activity should influence scoring.<\/td><\/tr><tr><td>C063<\/td><td>debounce_seconds<\/td><td>Delay\/coalesce recalculation<\/td><td>0<\/td><td>Less than positive lookback<\/td><td>Use as the wait period for no-response logic or event coalescing.<\/td><\/tr><tr><td>C064<\/td><td>expiry_policy<\/td><td>NONE or REEVALUATE<\/td><td>Based on lookback<\/td><td>C062<\/td><td>Use REEVALUATE whenever a positive lookback can expire.<\/td><\/tr><tr><td>C065<\/td><td>maximum_occurrences<\/td><td>Cap behavior event count<\/td><td>1<\/td><td>Trigger policy<\/td><td>Increase only when rules intentionally inspect repeated activity counts.<\/td><\/tr><tr><td>C066<\/td><td>binding_name<\/td><td>Describe profile selector<\/td><td>Required<\/td><td>Binding<\/td><td>Name the source\/form scope clearly for future audits.<\/td><\/tr><tr><td>C067<\/td><td>binding source_key<\/td><td>Match inbound source<\/td><td>Blank<\/td><td>Binding context<\/td><td>Use for a broad provider or intake-family match.<\/td><\/tr><tr><td>C068<\/td><td>binding module_scope<\/td><td>Match source module<\/td><td>Blank<\/td><td>Binding context<\/td><td>Add when the same source key can occur in different modules.<\/td><\/tr><tr><td>C069<\/td><td>binding service<\/td><td>Match service<\/td><td>Blank<\/td><td>Binding context<\/td><td>Leave blank unless the exact trusted service value is known.<\/td><\/tr><tr><td>C070<\/td><td>binding source_id<\/td><td>Match operational source<\/td><td>0<\/td><td>Company source<\/td><td>Use to narrow a broad source to one company source record.<\/td><\/tr><tr><td>C071<\/td><td>marketing_lead_source_id<\/td><td>Match CRM source<\/td><td>0<\/td><td>Active company\/global source<\/td><td>Use when CRM lead-source classification selects the profile.<\/td><\/tr><tr><td>C072<\/td><td>form_type<\/td><td>Select form family<\/td><td>Blank<\/td><td>Must pair with C073<\/td><td>Set with an exact form reference for form-specific scoring.<\/td><\/tr><tr><td>C073<\/td><td>form_reference<\/td><td>Select exact form<\/td><td>Blank<\/td><td>C072; company-owned form<\/td><td>Use the current company form\/provider reference.<\/td><\/tr><tr><td>C074<\/td><td>integration_id<\/td><td>Select provider integration<\/td><td>0<\/td><td>Provider object binding<\/td><td>Use for an exact connected-provider object such as Facebook form.<\/td><\/tr><tr><td>C075<\/td><td>provider_object_type<\/td><td>Select provider object family<\/td><td>Blank<\/td><td>C074\/C076<\/td><td>Pair with the provider reference and integration.<\/td><\/tr><tr><td>C076<\/td><td>provider_object_reference<\/td><td>Select exact provider object<\/td><td>Blank<\/td><td>C074\/C075<\/td><td>Use the exact synchronized provider reference.<\/td><\/tr><tr><td>C077<\/td><td>binding priority<\/td><td>Resolve equal-specificity matches<\/td><td>100<\/td><td>Matching bindings<\/td><td>Raise only to prefer one match at the same specificity.<\/td><\/tr><tr><td>C078<\/td><td>binding status<\/td><td>Activate profile selector<\/td><td>ACTIVE<\/td><td>Published profile<\/td><td>Use INACTIVE to retain a binding without allowing selection.<\/td><\/tr><tr><td>C079<\/td><td>group_key<\/td><td>Stable rule-group identifier<\/td><td>Required<\/td><td>Rule group<\/td><td>Use a permanent key for related scoring factors.<\/td><\/tr><tr><td>C080<\/td><td>group_name<\/td><td>Name rule group<\/td><td>Required<\/td><td>Rule group<\/td><td>Use a business label such as Customer Engagement.<\/td><\/tr><tr><td>C081<\/td><td>minimum_contribution<\/td><td>Cap negative group points<\/td><td>-100 if omitted<\/td><td>Grouped rules<\/td><td>Set a deliberate downside limit for related negative rules.<\/td><\/tr><tr><td>C082<\/td><td>maximum_contribution<\/td><td>Cap positive group points<\/td><td>100 if omitted<\/td><td>Grouped rules<\/td><td>Prevent several related signals from dominating the score.<\/td><\/tr><tr><td>C083<\/td><td>group priority<\/td><td>Stable group order<\/td><td>100<\/td><td>Rule group<\/td><td>Use distinct values for predictable administrator ordering.<\/td><\/tr><tr><td>C084<\/td><td>rule enabled<\/td><td>Activate\/deactivate rule<\/td><td>On<\/td><td>Rule<\/td><td>Disable to retain a draft rule without applying it.<\/td><\/tr><tr><td>C085<\/td><td>rule_type<\/td><td>Classify rule<\/td><td>FIELD_SIGNAL<\/td><td>Rule<\/td><td>Choose the category that best describes the business factor.<\/td><\/tr><tr><td>C086<\/td><td>reason_code<\/td><td>Stable unique factor code<\/td><td>Required<\/td><td>Enabled rule<\/td><td>Use a permanent code that explains matched evidence.<\/td><\/tr><tr><td>C087<\/td><td>rule_name<\/td><td>Human-readable factor name<\/td><td>Required<\/td><td>Rule<\/td><td>Write the outcome users should understand in score details.<\/td><\/tr><tr><td>C088<\/td><td>rule_description<\/td><td>Explain rule intent<\/td><td>Blank<\/td><td>Rule<\/td><td>Record the business justification and expected values.<\/td><\/tr><tr><td>C089<\/td><td>rule group_key<\/td><td>Apply group caps<\/td><td>Blank\/ungrouped<\/td><td>Existing group<\/td><td>Group related rules that need a shared contribution cap.<\/td><\/tr><tr><td>C090<\/td><td>match_mode<\/td><td>Require ALL or ANY conditions<\/td><td>ALL<\/td><td>Rule conditions<\/td><td>Use ALL for strict qualification and ANY for alternatives.<\/td><\/tr><tr><td>C091<\/td><td>points<\/td><td>Add\/subtract score<\/td><td>Required<\/td><td>Matching rule<\/td><td>Choose an impact proportionate to the signal&#8217;s business value.<\/td><\/tr><tr><td>C092<\/td><td>rule priority<\/td><td>Evaluate lower values first<\/td><td>100<\/td><td>Especially group caps<\/td><td>Give stronger preferred rules lower values inside capped groups.<\/td><\/tr><tr><td>C093<\/td><td>condition_source_type<\/td><td>SYSTEM_FACT, PROFILE_FIELD, DIMENSION<\/td><td>Required<\/td><td>Condition<\/td><td>Prefer DIMENSION for reusable concepts and SYSTEM_FACT for trusted context.<\/td><\/tr><tr><td>C094<\/td><td>system_fact_key<\/td><td>Select allowlisted system fact<\/td><td>Blank<\/td><td>C093 SYSTEM_FACT<\/td><td>Select only a key shown in Rule Reference.<\/td><\/tr><tr><td>C095<\/td><td>dimension_key<\/td><td>Select stable mapped dimension<\/td><td>Blank<\/td><td>C093 DIMENSION<\/td><td>Use the active dimension key saved in this profile.<\/td><\/tr><tr><td>C096<\/td><td>profile_field_id<\/td><td>Select exact current field<\/td><td>0\/blank<\/td><td>C093 PROFILE_FIELD<\/td><td>Use only for one exact mapped field in the current draft.<\/td><\/tr><tr><td>C097<\/td><td>operator<\/td><td>Choose comparison<\/td><td>Required<\/td><td>C098 type<\/td><td>Choose the simplest operator matching the business test.<\/td><\/tr><tr><td>C098<\/td><td>comparison_type<\/td><td>Normalize comparison<\/td><td>TEXT if omitted<\/td><td>Fact\/dimension type<\/td><td>Match the source fact, approved field, or dimension type exactly.<\/td><\/tr><tr><td>C099<\/td><td>comparison_value<\/td><td>Main target value\/list<\/td><td>Operator-dependent<\/td><td>C097<\/td><td>Enter the normalized value actually delivered by the source.<\/td><\/tr><tr><td>C100<\/td><td>comparison_value_to<\/td><td>BETWEEN upper bound<\/td><td>Blank<\/td><td>C097 BETWEEN<\/td><td>Supply only for the inclusive BETWEEN range.<\/td><\/tr><tr><td>C101<\/td><td>condition priority<\/td><td>Stable condition order<\/td><td>100<\/td><td>Condition<\/td><td>Use distinct values for readable, stable ordering.<\/td><\/tr><tr><td>C102<\/td><td>Preview system facts<\/td><td>Test allowlisted source\/behavior facts<\/td><td>Example values<\/td><td>Draft preview<\/td><td>Test source and behavior boundaries with synthetic values.<\/td><\/tr><tr><td>C103<\/td><td>Preview profile fields<\/td><td>Test current mapped field IDs<\/td><td>Empty object<\/td><td>Saved mappings<\/td><td>Test exact-field rules with current draft IDs only.<\/td><\/tr><tr><td>C104<\/td><td>Preview dimensions<\/td><td>Test active mapped dimensions<\/td><td>Empty object<\/td><td>Saved mappings\/dimensions<\/td><td>Test reusable cross-source rules with synthetic values.<\/td><\/tr><tr><td>C105<\/td><td>Apply Recommended LLM Settings<\/td><td>Fill bounded working LLM defaults<\/td><td>Action<\/td><td>Draft LLM editor<\/td><td>Use before first SHADOW\/HYBRID save, then review the values.<\/td><\/tr><tr><td>C106<\/td><td>Apply Starter Template<\/td><td>Add starter rules to an empty draft<\/td><td>Action<\/td><td>No groups\/rules\/triggers<\/td><td>Use for an empty first draft instead of building every rule manually.<\/td><\/tr><tr><td>C107<\/td><td>Load Tenant Field Example<\/td><td>Load first compatible mapping example<\/td><td>Action<\/td><td>Approved field<\/td><td>Use as a starting structure, then replace IDs and policies deliberately.<\/td><\/tr><tr><td>C108<\/td><td>Load Group Example<\/td><td>Load example group JSON<\/td><td>Action<\/td><td>Rule editor<\/td><td>Use to learn the group format before creating business-specific caps.<\/td><\/tr><tr><td>C109<\/td><td>Load Tenant-Aware Rule Example<\/td><td>Load context-aware rule example<\/td><td>Action<\/td><td>Mapped field\/dimension if available<\/td><td>Use after mappings exist to create a valid draft rule structure.<\/td><\/tr><tr><td>C110<\/td><td>Load No-response Rule<\/td><td>Load example negative behavior rule<\/td><td>Action<\/td><td>Matching group\/triggers<\/td><td>Use with assignment\/reply triggers, then adjust timing and points.<\/td><\/tr><tr><td>C111<\/td><td>Load Reply Example<\/td><td>Load reply trigger example<\/td><td>Action<\/td><td>Trigger editor<\/td><td>Use when customer replies should cause rescoring.<\/td><\/tr><tr><td>C112<\/td><td>Load No-response Triggers<\/td><td>Load assignment\/reply trigger examples<\/td><td>Action<\/td><td>Trigger editor<\/td><td>Use as the base for delayed no-response scoring.<\/td><\/tr><tr><td>C113<\/td><td>Load Facebook Example<\/td><td>Load broad Facebook binding example<\/td><td>Action<\/td><td>Binding editor<\/td><td>Use as a template and narrow it to the intended form when possible.<\/td><\/tr><tr><td>C114<\/td><td>Run Deterministic Preview<\/td><td>Test draft in memory<\/td><td>Action<\/td><td>Valid synthetic facts<\/td><td>Run after every material rules, mapping, or band change.<\/td><\/tr><tr><td>C115<\/td><td>Validate Draft<\/td><td>Run publication checks<\/td><td>Action<\/td><td>All draft sections saved<\/td><td>Run after saving every section and before publishing.<\/td><\/tr><tr><td>C116<\/td><td>Publish Draft<\/td><td>Activate immutable version<\/td><td>Action<\/td><td>C115 passes<\/td><td>Use only after preview and validation match expected outcomes.<\/td><\/tr><tr><td>C117<\/td><td>Create Next Draft<\/td><td>Copy published version for editing<\/td><td>Action<\/td><td>Published profile with no draft<\/td><td>Use for every change to an already published profile.<\/td><\/tr><tr><td>C118<\/td><td>Logs Profile<\/td><td>Filter logs by profile<\/td><td>All profiles<\/td><td>Logs page<\/td><td>Select when troubleshooting one policy.<\/td><\/tr><tr><td>C119<\/td><td>Logs Phase<\/td><td>Filter event\/contact runs<\/td><td>All phases<\/td><td>Logs page<\/td><td>Use Event for routing issues and Contact for later scoring.<\/td><\/tr><tr><td>C120<\/td><td>Logs Run status<\/td><td>Filter evaluation outcome<\/td><td>All statuses<\/td><td>Logs page<\/td><td>Filter skipped\/failed-safe statuses when a score is missing.<\/td><\/tr><tr><td>C121<\/td><td>Logs From<\/td><td>Inclusive start date<\/td><td>Empty<\/td><td>Logs page<\/td><td>Set the start of the incident or test window.<\/td><\/tr><tr><td>C122<\/td><td>Logs To<\/td><td>Inclusive end date<\/td><td>Empty<\/td><td>Logs page<\/td><td>Set the end of the incident or test window.<\/td><\/tr><tr><td>C123<\/td><td>Logs Contact ID<\/td><td>Filter one contact<\/td><td>Empty<\/td><td>Company-owned contact<\/td><td>Use when investigating a Contact Conversation score.<\/td><\/tr><tr><td>C124<\/td><td>Logs Queue ID<\/td><td>Filter one queue event<\/td><td>Empty<\/td><td>Company-owned queue record<\/td><td>Use when investigating one inbound lead before assignment.<\/td><\/tr><tr><td>C125<\/td><td>Logs Job type<\/td><td>Filter processing category<\/td><td>All types<\/td><td>Logs page<\/td><td>Select the specific discovery, scoring, or LLM operation.<\/td><\/tr><tr><td>C126<\/td><td>Logs Job status<\/td><td>Filter processing state<\/td><td>All statuses<\/td><td>Logs page<\/td><td>Use to find waiting, retrying, failed, or completed work.<\/td><\/tr><tr><td>C127<\/td><td>Rows per table<\/td><td>Limit each log table<\/td><td>100<\/td><td>1\u2013500<\/td><td>Keep 100 normally; increase for a wider troubleshooting window.<\/td><\/tr><tr><td>C128<\/td><td>Report Profile<\/td><td>Filter deterministic report<\/td><td>All profiles<\/td><td>Report page<\/td><td>Select one profile to evaluate its score distribution.<\/td><\/tr><tr><td>C129<\/td><td>Report Phase<\/td><td>Filter event\/contact results<\/td><td>All phases<\/td><td>Report page<\/td><td>Separate pre-routing scores from later contact scores.<\/td><\/tr><tr><td>C130<\/td><td>Report From<\/td><td>Inclusive start date<\/td><td>Empty<\/td><td>Report page<\/td><td>Set the beginning of the reporting period.<\/td><\/tr><tr><td>C131<\/td><td>Report To<\/td><td>Inclusive end date<\/td><td>Empty<\/td><td>Report page<\/td><td>Set the end of the reporting period.<\/td><\/tr><tr><td>C132<\/td><td>Recalculate Lead Score workflow action<\/td><td>Request governed contact rescore<\/td><td>Action<\/td><td>Lead Scoring permission and workflow contact<\/td><td>Use after workflow changes relevant contact data without a native scoring event.<\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>Lead Scoring: Administrator Configuration Guide Overview Lead Scoring ranks inbound leads and existing contacts on a scale from 0 to 100. It combines a starting score with positive and negative rules based on the lead source, form answers, contact completeness, replies, deals, and other approved activity. The result is assigned to a score band such [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v19.3 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Lead Scoring Guide for Administrators - ZNICRM Guide<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Lead Scoring Guide for Administrators - ZNICRM Guide\" \/>\n<meta property=\"og:description\" content=\"Lead Scoring: Administrator Configuration Guide Overview Lead Scoring ranks inbound leads and existing contacts on a scale from 0 to 100. It combines a starting score with positive and negative rules based on the lead source, form answers, contact completeness, replies, deals, and other approved activity. The result is assigned to a score band such [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/\" \/>\n<meta property=\"og:site_name\" content=\"ZNICRM Guide\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-07T09:04:45+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-07T09:04:46+00:00\" \/>\n<meta name=\"author\" content=\"Lowell Samuel Walton\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Lowell Samuel Walton\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"41 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https:\/\/znicrm.com\/guide\/#organization\",\"name\":\"ZNICRM Guide\",\"url\":\"https:\/\/znicrm.com\/guide\/\",\"sameAs\":[],\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/znicrm.com\/guide\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/cdn.znicrm.com\/guide\/wp-content\/uploads\/2022\/07\/18161430\/logo-112x28-1.png\",\"contentUrl\":\"https:\/\/cdn.znicrm.com\/guide\/wp-content\/uploads\/2022\/07\/18161430\/logo-112x28-1.png\",\"width\":112,\"height\":24,\"caption\":\"ZNICRM Guide\"},\"image\":{\"@id\":\"https:\/\/znicrm.com\/guide\/#\/schema\/logo\/image\/\"}},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/znicrm.com\/guide\/#website\",\"url\":\"https:\/\/znicrm.com\/guide\/\",\"name\":\"ZNICRM Guide\",\"description\":\"Help topics for CRM, TeamSpoor &amp; Engage\",\"publisher\":{\"@id\":\"https:\/\/znicrm.com\/guide\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/znicrm.com\/guide\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/\",\"url\":\"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/\",\"name\":\"Lead Scoring Guide for Administrators - ZNICRM Guide\",\"isPartOf\":{\"@id\":\"https:\/\/znicrm.com\/guide\/#website\"},\"datePublished\":\"2026-08-07T09:04:45+00:00\",\"dateModified\":\"2026-08-07T09:04:46+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/znicrm.com\/guide\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Lead Scoring Guide for Administrators\"}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/\"},\"author\":{\"name\":\"Lowell Samuel Walton\",\"@id\":\"https:\/\/znicrm.com\/guide\/#\/schema\/person\/982abbb26b23872deeb011dd70aec446\"},\"headline\":\"Lead Scoring Guide for Administrators\",\"datePublished\":\"2026-08-07T09:04:45+00:00\",\"dateModified\":\"2026-08-07T09:04:46+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/\"},\"wordCount\":8208,\"publisher\":{\"@id\":\"https:\/\/znicrm.com\/guide\/#organization\"},\"articleSection\":[\"General\"],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/znicrm.com\/guide\/#\/schema\/person\/982abbb26b23872deeb011dd70aec446\",\"name\":\"Lowell Samuel Walton\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/znicrm.com\/guide\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/2ea5466b737a565f00d9effed54ce913?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/2ea5466b737a565f00d9effed54ce913?s=96&d=mm&r=g\",\"caption\":\"Lowell Samuel Walton\"},\"sameAs\":[\"https:\/\/znicrm.com\/guide\"],\"url\":\"https:\/\/znicrm.com\/guide\/author\/tushar\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Lead Scoring Guide for Administrators - ZNICRM Guide","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/","og_locale":"en_US","og_type":"article","og_title":"Lead Scoring Guide for Administrators - ZNICRM Guide","og_description":"Lead Scoring: Administrator Configuration Guide Overview Lead Scoring ranks inbound leads and existing contacts on a scale from 0 to 100. It combines a starting score with positive and negative rules based on the lead source, form answers, contact completeness, replies, deals, and other approved activity. The result is assigned to a score band such [&hellip;]","og_url":"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/","og_site_name":"ZNICRM Guide","article_published_time":"2026-08-07T09:04:45+00:00","article_modified_time":"2026-08-07T09:04:46+00:00","author":"Lowell Samuel Walton","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Lowell Samuel Walton","Est. reading time":"41 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Organization","@id":"https:\/\/znicrm.com\/guide\/#organization","name":"ZNICRM Guide","url":"https:\/\/znicrm.com\/guide\/","sameAs":[],"logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/znicrm.com\/guide\/#\/schema\/logo\/image\/","url":"https:\/\/cdn.znicrm.com\/guide\/wp-content\/uploads\/2022\/07\/18161430\/logo-112x28-1.png","contentUrl":"https:\/\/cdn.znicrm.com\/guide\/wp-content\/uploads\/2022\/07\/18161430\/logo-112x28-1.png","width":112,"height":24,"caption":"ZNICRM Guide"},"image":{"@id":"https:\/\/znicrm.com\/guide\/#\/schema\/logo\/image\/"}},{"@type":"WebSite","@id":"https:\/\/znicrm.com\/guide\/#website","url":"https:\/\/znicrm.com\/guide\/","name":"ZNICRM Guide","description":"Help topics for CRM, TeamSpoor &amp; Engage","publisher":{"@id":"https:\/\/znicrm.com\/guide\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/znicrm.com\/guide\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/","url":"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/","name":"Lead Scoring Guide for Administrators - ZNICRM Guide","isPartOf":{"@id":"https:\/\/znicrm.com\/guide\/#website"},"datePublished":"2026-08-07T09:04:45+00:00","dateModified":"2026-08-07T09:04:46+00:00","breadcrumb":{"@id":"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/znicrm.com\/guide\/"},{"@type":"ListItem","position":2,"name":"Lead Scoring Guide for Administrators"}]},{"@type":"Article","@id":"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/#article","isPartOf":{"@id":"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/"},"author":{"name":"Lowell Samuel Walton","@id":"https:\/\/znicrm.com\/guide\/#\/schema\/person\/982abbb26b23872deeb011dd70aec446"},"headline":"Lead Scoring Guide for Administrators","datePublished":"2026-08-07T09:04:45+00:00","dateModified":"2026-08-07T09:04:46+00:00","mainEntityOfPage":{"@id":"https:\/\/znicrm.com\/guide\/225\/lead-scoring-guide-for-administrators\/"},"wordCount":8208,"publisher":{"@id":"https:\/\/znicrm.com\/guide\/#organization"},"articleSection":["General"],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/znicrm.com\/guide\/#\/schema\/person\/982abbb26b23872deeb011dd70aec446","name":"Lowell Samuel Walton","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/znicrm.com\/guide\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/2ea5466b737a565f00d9effed54ce913?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/2ea5466b737a565f00d9effed54ce913?s=96&d=mm&r=g","caption":"Lowell Samuel Walton"},"sameAs":["https:\/\/znicrm.com\/guide"],"url":"https:\/\/znicrm.com\/guide\/author\/tushar\/"}]}},"_links":{"self":[{"href":"https:\/\/znicrm.com\/guide\/wp-json\/wp\/v2\/posts\/225"}],"collection":[{"href":"https:\/\/znicrm.com\/guide\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/znicrm.com\/guide\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/znicrm.com\/guide\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/znicrm.com\/guide\/wp-json\/wp\/v2\/comments?post=225"}],"version-history":[{"count":1,"href":"https:\/\/znicrm.com\/guide\/wp-json\/wp\/v2\/posts\/225\/revisions"}],"predecessor-version":[{"id":226,"href":"https:\/\/znicrm.com\/guide\/wp-json\/wp\/v2\/posts\/225\/revisions\/226"}],"wp:attachment":[{"href":"https:\/\/znicrm.com\/guide\/wp-json\/wp\/v2\/media?parent=225"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/znicrm.com\/guide\/wp-json\/wp\/v2\/categories?post=225"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/znicrm.com\/guide\/wp-json\/wp\/v2\/tags?post=225"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}