Le
LeadCompass Lead Prioritization WorkbenchAI Lead Scoring and Explainable Recommendations SaaS · V29
Connecting to the live product service
AI Lead Scoring and Explainable Recommendations SaaS

Precipitate sales intuition into explainable lead ranking, reasoning and feedback closed loop.

Help teams prioritize high-potential leads by generating traceable scores, referral rationales, qualification questions, follow-up suggestions and sales feedback tags for each lead.

  1. 01
    Configure assessment projectsDefine your target market, ideal customer characteristics, dynamic business intent, qualification questions, and isolation requirements.
  2. 02
    Create a lead poolImport or enter leads to generate a browsable lead_record.
  3. 03
    Scoring and InterpretationGenerate dynamic portraits, ratings, recommendations and answers to qualification questions for leads.
  4. 04
    Feedback and follow-upSales submit likes/dislikes and follow-up actions to form private tags and status history.
  5. 05
    Audit and reviewView score versions, assessment metadata, cross-tenant isolation instructions, and feedback quality risks.
total number of leads0 cluesCount the number of lead_records in the current project.
high priority leadsNo high priority leads yetCount the number of leads whose priority_band is high in the latest lead_score_explanation.
% of leads explainedNot rated yetNumber of clues with at least one reasons and qualification_questions_answered / total number of clues.
Number of sales feedbackNo feedback yetCount the number of feedback_labels in the current project and distinguish between positive and negative.
Follow up status distributionNo follow-up action yetAggregate quantities by prospecting_action.action_status or lead_record.current_status.
Assess metadata completenessNo evaluation metrics displayedCheck whether all displayed indicators have sample_size, evaluation_window, target_definition, and calculation_method.
BUSINESS INPUT

New project

Create a lead assessment project that defines target customer profiles, scoring criteria, intent event sources, and team feedback rules.

Loading product-specific business fields.

Not saved
TRACEABLE OUTPUT

Lead priority

Results, sources, failures, approvals, and rollbacks are saved by project.

0 live runs
∅

No business results yet

No leads have been imported yet. Please upload a CSV/XLSX or paste a few lead notes.

PRIVACY

Data use boundary

Lead files and manual notes may contain business-sensitive information such as company contacts, sales opportunities, customer intentions, communication records, etc. The system is only used for lead scoring, explanation, feedback and follow-up records within current tenants and projects; users should not upload unauthorized personal privacy, regulated sensitive data or third-party confidential data. Current 10 role review supplements: Sensitive fields should cover lead_input_file, manual_lead_notes, company_name, static_profile, intent_events, qualification_answers, confidence_notes, feedback_reason, private_label, created_by, next_step_note, customer/contact/note related fields in export reports. ; Before uploading, users must be prompted to upload only the fields required for scoring. Do not upload unauthorized personal information, identity documents, financial accounts, health, children, precise location and other regulated sensitive data or third-party confidential data. ;The field mapping stage should allow non-essential columns to be ignored or deleted; raw file deletion options should be provided after parsing. ; It must be clear whether the original file is retained by default, the retention period of structured records, the retention period of audit logs, the scope of administrator deletion, and the minimum audit metadata retained after deletion. ; The export must provide desensitization/minimization options, and at least support hiding contacts, submitters, original notes, sensitive columns, and original private labels. ; All cross-project, cross-workspace, and cross-site read, export, rollback, and audit access must be filtered by object-level permissions.

RETENTION

Data retention

Project data, rating records, feedback tags and follow-up status are retained by default until deleted by the project administrator; the imported original file can be deleted according to the administrator's settings after parsing, and only the generated structured records and audit logs will be retained after deletion.

SAFETY

Human responsibility and rollback

This product outputs sales priority recommendations based on user-provided leads, project rules, and business intent definitions. It does not represent real closing probabilities, legal conclusions, financial forecasts, or external verification results. Ratings and recommendation reasons can be erroneous due to missing data, feedback bias, or improperly set rules, and should be used by sales teams in conjunction with human judgment.

Rollback only refers to undoing or restoring rating batches, feedback labels, follow-up status and report versions within this site; this product is not connected to external production systems, so it does not and cannot roll back external CRM, mailbox, calendar or other sales systems.