Skip to main content Enter
ERP.AI CRM with Lead Scoring

CRM with Lead Scoring

Start now
Pricing Frequently asked questions Get started
Build with Proto

Modules

Lead captureBring incoming prospects into a consistent qualification queue. Scoring and AIExplain why a lead deserves attention before the team acts. Routing and alertsPut the next lead with someone who can act on it.
Outreach and preferencesCoordinate useful follow-up while respecting contact preferences. Qualification and handoffGive account executives the context to accept a qualified lead. Funnel analysisLearn which sources and signals lead to accepted opportunities.

CRM with Lead Scoring

Start now
Pricing Frequently asked questions Get started
Build with Proto

Processes

Capture and prioritize leadsCapture and prioritize leads. Approve a scoring policyApprove a scoring policy.
Route and qualify prospectsRoute and qualify prospects. Complete the CRM handoffComplete the CRM handoff.

CRM with Lead Scoring

Start now
Pricing Frequently asked questions Get started
Build with Proto

Industries

Inside sales teamsSales development and account executive teams sharing prospect qualification and follow-up. Demand generation teamsMarketing teams comparing acquisition sources and handing accepted prospects to sales.
Partner-led sales teamsSales teams receiving referred prospects while preserving source attribution and territory ownership.

CRM with Lead Scoring

Start now
Pricing Frequently asked questions Get started
Build with Proto

Reference

Roles and permissionsUnderstand roles and permissions for CRM with Lead Scoring. Reports and analyticsUnderstand reports and analytics for CRM with Lead Scoring. Data modelUnderstand data model for CRM with Lead Scoring.
IntegrationsUnderstand integrations for CRM with Lead Scoring. ImplementationUnderstand implementation for CRM with Lead Scoring. Agent and automationUnderstand agent and automation for CRM with Lead Scoring.

CRM with Lead Scoring

Start now
Pricing Frequently asked questions Get started
Build with Proto
All systems
Modules
Lead captureBring incoming prospects into a consistent qualification queue.Scoring and AIExplain why a lead deserves attention before the team acts.Routing and alertsPut the next lead with someone who can act on it.Outreach and preferencesCoordinate useful follow-up while respecting contact preferences.Qualification and handoffGive account executives the context to accept a qualified lead.Funnel analysisLearn which sources and signals lead to accepted opportunities.
Processes
Capture and prioritize leadsCapture and prioritize leads.Approve a scoring policyApprove a scoring policy.Route and qualify prospectsRoute and qualify prospects.Complete the CRM handoffComplete the CRM handoff.
Industries
Inside sales teamsSales development and account executive teams sharing prospect qualification and follow-up.Demand generation teamsMarketing teams comparing acquisition sources and handing accepted prospects to sales.Partner-led sales teamsSales teams receiving referred prospects while preserving source attribution and territory ownership.
Reference
Roles and permissionsUnderstand roles and permissions for CRM with Lead Scoring.Reports and analyticsUnderstand reports and analytics for CRM with Lead Scoring.Data modelUnderstand data model for CRM with Lead Scoring.IntegrationsUnderstand integrations for CRM with Lead Scoring.ImplementationUnderstand implementation for CRM with Lead Scoring.Agent and automationUnderstand agent and automation for CRM with Lead Scoring.
Sign in
Sign in Start now
CRM with Lead Scoring References
Data model3 of 6
  • Roles and permissions1 of 6
  • Reports and analytics2 of 6
  • Data model3 of 6
  • Integrations4 of 6
  • Implementation5 of 6
  • Agent and automation6 of 6

Data model

Understand data model for CRM with Lead Scoring.

25 tables · 59 relationships

Data model 25 tables
mastertransaction Users.Territory → Territories Territories.Manager → Users TerritoryStates.Territory → Territories ScoringRules.AppliesToSource → LeadSources ScoringRules.PreparedBy → Users ScoringRuleValues.Rule → ScoringRules RoutingRules.Territory → Territories RoutingRules.AssignToUser → Users Lists.Owner → Users ListMemberships.List → Lists ListMemberships.Lead → Leads ListMemberships.AddedBy → Users ScoringModels.PreparedBy → Users IntegrationConnections.Owner → Users DuplicateMembers.Cluster → DuplicateClusters DuplicateMembers.Lead → Leads ScoringEvents.Lead → Leads ScoringEvents.Rule → ScoringRules ScoringEvents.TriggerActivity → LeadActivities ScoringEvents.Run → ScoringRuns Leads.Source → LeadSources Leads.Territory → Territories Leads.Owner → Users Leads.LatestScoringRun → ScoringRuns LeadActivities.Lead → Leads LeadActivities.Owner → Users LeadNotes.Lead → Leads LeadNotes.Author → Users LeadAssignments.Lead → Leads LeadAssignments.AssignedTo → Users LeadAssignments.Rule → RoutingRules DuplicateClusters.ResolvedBy → Users DuplicateClusters.SurvivorLead → Leads LeadConversions.Lead → Leads LeadConversions.ConvertedBy → Users LeadConversions.TargetConnection → IntegrationConnections ScoringRuns.Lead → Leads ScoringRuns.Model → ScoringModels PriorityAlerts.Lead → Leads PriorityAlerts.Run → ScoringRuns PriorityAlerts.Owner → Users ConsentEvents.Lead → Leads AuditEvents.Actor → Users IntegrationEvents.Connection → IntegrationConnections UsersmasterTerritoryManagerUserID TerritoriesmasterTerritoryCodeManagerRoutingCursor TerritoryStatesmasterTerritoryStateWorkspaceKey LeadSourcesmasterSourceCodeNameCategory ScoringRulesmasterRuleCodeStatusAppliesToSource ScoringRuleValuesmasterRuleValueWorkspaceKey RoutingRulesmasterRuleCodeStatusTerritory ListsmasterListCodeOwnerName ListMembershipsmasterListLeadAddedBy LeadSettingsmasterMQLThresholdRecycleAfterDaysDuplicateMatchScore ScoringModelsmasterModelNumberStatusPreparedBy IntegrationConnectionsmasterConnectionNumberStatusOwner DuplicateMemberslineClusterLeadCandidateRevision ScoringEventstransactionEventNumberStatusLead LeadstransactionLeadNumberStatusSource LeadActivitiestransactionActivityNumberStatusLead LeadNotestransactionRecordNumberStatusLead LeadAssignmentstransactionRecordNumberStatusLead DuplicateClusterstransactionClusterCodeStatusResolvedBy LeadConversionstransactionConversionNumberStatusLead ScoringRunstransactionRunNumberStatusLead PriorityAlertstransactionAlertNumberStatusLead ConsentEventstransactionConsentNumberStatusLead AuditEventstransactionEventNumberStatusActor IntegrationEventstransactionEventNumberStatusConnection
Data modelTable names and relationships

How the model is organised

Lead capture

Leads, LeadSources, LeadNotes, DuplicateClusters. Bring incoming prospects into a consistent qualification queue.

  • Leads
  • LeadSources
  • LeadNotes
  • DuplicateClusters

Scoring and AI

ScoringRules, ScoringRuleValues, ScoringModels, ScoringRuns, ScoringEvents. Explain why a lead deserves attention before the team acts.

  • ScoringRules
  • ScoringRuleValues
  • ScoringModels
  • ScoringRuns
  • ScoringEvents

Routing and alerts

Territories, RoutingRules, LeadAssignments, PriorityAlerts. Put the next lead with someone who can act on it.

  • Territories
  • RoutingRules
  • LeadAssignments
  • PriorityAlerts

Outreach and preferences

LeadActivities, LeadNotes, Lists, ListMemberships, ConsentEvents. Coordinate useful follow-up while respecting contact preferences.

  • LeadActivities
  • LeadNotes
  • Lists
  • ListMemberships
  • ConsentEvents

Qualification and handoff

Leads, LeadConversions, IntegrationEvents. Give account executives the context to accept a qualified lead.

  • Leads
  • LeadConversions
  • IntegrationEvents

Funnel analysis

ScoringRuns, ScoringEvents, LeadAssignments, LeadConversions, PriorityAlerts. Learn which sources and signals lead to accepted opportunities.

  • ScoringRuns
  • ScoringEvents
  • LeadAssignments
  • LeadConversions
  • PriorityAlerts

Keys and references

Preserve workspace-scoped identities, source references and current record revisions. Child records inherit parent scope. Retried commands and provider events resolve to their original occurrence.

Migration order

  1. 1 Configure workspace identities and role scopes.
  2. 2 Import reference records and resolve duplicates.
  3. 3 Import current customer work with its actual state and ownership.
  4. 4 Reconcile historical decisions and external references.
  5. 5 Test a complete handoff before enabling automated commands.

Tables

25 tables
UsersWorkspace membership maps authenticated PrincipalId values to this app’s role and territory scope. A common person may map into different authorized roles in a connected CRM; no shared physical Users table or automatic cross-app permission is assumed.master
FieldTypeRequiredDetails
UserIDtextyes
FullNametextyes
Emailtextyes
RoleselectyesAdmin, Marketing Operations, Sales Manager, Sales Development Rep, Account Executive, Viewer
Territoryreference→ Territories
Managerreference→ Users (self)
RoundRobinEligiblebooleanyesWhen true, eligible for round-robin routing
OutOfOfficebooleanSkip in routing while true
Activebooleanyes
PrincipalIdtextyesUnique authenticated subject within WorkspaceKey; not inferred from Email.
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
TerritoriesGeo or named-account territories used by `RoutingRules` to scope which Leads land in which rep's queue. US-centric: state, multi-state region, named-account list, or industry segment.master
FieldTypeRequiredDetails
TerritoryCodetextyes
Nametextyes
TypeselectyesState, Region, NamedAccount, Industry, Segment
Managerreference→ Users
Activebooleanyes
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
RoutingCursorreference→ Users; Server-maintained cursor for atomic eligible-owner rotation.
TerritoryStatesUS-state coverage list for `State` / `Region` Territories. One row per state in the territory.master
FieldTypeRequiredDetails
Territoryreferenceyes→ Territories
StateselectyesTwo-letter US state code (AL, AK, AZ, AR, CA, CO, CT, DE, FL, GA, HI, ID, IL, IN, IA, KS, KY, LA, ME, MD, MA, MI, MN, MS, MO, MT, NE, NV, NH, NJ, NM, NY, NC, ND, OH, OK, OR, PA, RI, SC, SD, TN, TX, UT, VT, VA, WA, WV, WI, WY, DC)
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
LeadSourcesChannel taxonomy: where every Lead originated. Drives attribution reporting, scoring weights (an inbound web demo request scores higher than a cold tradeshow scan), and source-specific routing.master
FieldTypeRequiredDetails
SourceCodetextyes
Nametextyese.g. WebForm, Webinar, TradeShow, ContentDownload
CategoryselectyesInbound, Outbound, Referral, Partner, Event, Content
ChannelselectyesWebForm, Webinar, TradeShow, ContentDownload, ColdOutbound, Referral, Partner, ChatBot, PaidAd, Other
BaseScorenumberDefault contribution to Lead score on capture (0–100)
RequireDoubleOptInbooleanIf true, Subscribable defaults false until confirmed
Activebooleanyes
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
ScoringRulesDeclarative rules that compute a Lead's score. Each rule is an attribute or behavior predicate plus a point value. Examples: "Title contains 'Director' → +20", "Visited pricing page → +15", "Email opened 3 times → +10". Rules stack additively per Lead.master
FieldTypeRequiredDetails
RuleCodetextyes
Nametextyes
CategoryselectyesFirmographic, Demographic, Behavioral, Engagement, Negative
AttributeOrEventselectyesTitle, Industry, EmployeeCount, AnnualRevenue, Source, PageVisit, EmailOpen, EmailClick, FormFill, ContentDownload, MeetingBooked, Unsubscribe
OperatorselectyesEquals, NotEquals, Contains, NotContains, GreaterThan, LessThan, Between, In, NotIn
ComparisonValuetextSingle value as text; for In/NotIn list operators use child ScoringRuleValues table
Pointsnumberyes+/- contribution
AppliesToSourcereference→ LeadSources (null = all sources)
PrioritynumberyesLower fires first
Activebooleanyes
Versionnumberyes
StatusselectyesDraft, Submitted, Approved, Retired
PreparedByreferenceyes→ Users
ApprovedByreference→ Users
EffectiveFromdatetimeyes
EffectiveUntildatetime
MaximumOccurrencesnumberyesPer lead and configured time window.
WindowDaysnumberyesExplicit scoring window; zero means once per lead.
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
ScoringRuleValuesThe list of comparison values for a ScoringRule whose `Operator` is `In` or `NotIn`. One row per value in the list.master
FieldTypeRequiredDetails
Rulereferenceyes→ ScoringRules
ValuetextyesOne member of the In / NotIn comparison list
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
ScoringEventsImmutable audit trail: one row per Lead per ScoringRule fire. Reproduces "why is this Lead scored 73?" by listing every rule that contributed, when, and with what point value. Frozen at write — corrections come via new compensating events, never edits.transaction
FieldTypeRequiredDetails
Leadreferenceyes→ Leads
Rulereferenceyes→ ScoringRules
PointsnumberyesSnapshot of Rule.Points at fire time
MatchedValuetextThe actual value that matched (e.g. "VP of Engineering")
FiredAtdateyes
TriggerActivityreference→ LeadActivities (when fire was an activity event)
ReversedbooleanSet when a compensating event neutralizes this one
EventNumbertextyes
Runreferenceyes→ ScoringRuns
SourceEventIdtextyesUnique per lead, rule version and upstream occurrence.
RuleVersionnumberyes
ExpiresAtdatetime
StatusselectyesRecorded, Reversed, Expired
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
RoutingRulesDeclarative routing rules evaluated in priority order on Lead create and on MQL handoff. First match wins. Examples: "Territory.State IN (CA,OR,WA) → Round-robin SDR pool 'WestSDR'", "Industry = Healthcare → AE 'jdoe'", "EmployeeCount > 1000 → Enterprise team".master
FieldTypeRequiredDetails
RuleCodetextyes
Nametextyes
MatchTypeselectyesTerritory, Industry, CompanySize, AccountOwner, Source, ScoreThreshold, RoundRobin
MatchValuetextComparison anchor (e.g. "Healthcare", ">=500", state code)
Territoryreference→ Territories (when MatchType = Territory)
AssignToTypeselectyesSpecificUser, RoundRobinPool, Manager, AccountOwner, UnassignedQueue
AssignToUserreference→ Users (when AssignToType = SpecificUser)
RoundRobinPoolTerritoryreference→ Territories (pool = users with this Territory + RoundRobinEligible)
FallbackOwnerreference→ Users (used when no matching round-robin user is available)
PrioritynumberyesLower fires first
Activebooleanyes
StatusselectyesDraft, Submitted, Approved, Retired
PreparedByreferenceyes→ Users
ApprovedByreference→ Users
EffectiveFromdatetimeyes
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
LeadsThe unqualified person record. Captures every prospect from every source. The pivot of the app: scored, routed, worked, and eventually converted, disqualified, or recycled.transaction
FieldTypeRequiredDetails
LeadNumbertextyes
FirstNametextyes
LastNametextyes
EmailtextyesMasked for Viewer role
PhonetextMasked for Viewer role
Mobiletext
CompanytextPre-account text; conversion resolves to an Account
Titletext
IndustryselectTechnology, Financial Services, Healthcare, Retail, Manufacturing, Professional Services, Education, Government, Nonprofit, Energy, Real Estate, Media, Other
EmployeeCountnumberEnriched on capture when possible
AnnualRevenuedecimalDecimal amount in the parent currency. Enriched on capture when possible
StateselectTwo-letter US state code
Sourcereferenceyes→ LeadSources
Territoryreference→ Territories (resolved by routing)
StatusselectyesNew, Working, MQL, Submitted, SQL, Converted, Recycled, Disqualified
Ownerreference→ Users (null while in unassigned queue)
ScorenumberyesDerived 0–100 from the latest completed ScoringRuns; direct edits rejected.
SubscribablebooleanyesEmail opt-in flag, honored across outbound
DoNotCallbooleanyesTCPA flag, honored across SDR dialer
DisqualifyReasonselectBadFit, NoBudget, NotNow, NoResponse, Duplicate, Unsubscribed, BadData
DuplicateOfreference→ Leads (self) — set by duplicate-detection workflow
ConvertedAtdateStamped by conversion workflow
CreatedAtdatetimeyesServer creation timestamp.
LastActivityAtdateRolled from LeadActivities
AssignedAEreference→ Users
QualificationReasonlongtext
QualifiedByreference→ Users
QualifiedAtdatetime
LatestScoringRunreference→ ScoringRuns
ContactPolicyselectyesUnknown, Permitted, Restricted, Withdrawn
ContactPolicyEvidenceattachment
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
QualificationSubmittedByreference→ Users
LeadActivitiesCalls, emails, meetings, web visits, page views, content downloads, form fills, and unsubscribes against a Lead. Both human-logged (SDR call) and machine-logged (web tracking, campaign engagement). Drives behavioral scoring rules.transaction
FieldTypeRequiredDetails
Leadreferenceyes→ Leads
TypeselectyesCall, Email, Meeting, Task, PageVisit, EmailOpen, EmailClick, FormFill, ContentDownload, ChatTranscript, Unsubscribe
Subjecttext
Ownerreference→ Users (null for machine-logged events)
StartAtdateFor meetings, calls
DurationMinutesnumber
DueDatedateFor tasks
CompletedAtdate
StatusselectyesPlanned, InProgress, Completed, Cancelled
OutcomeselectConnected, NoAnswer, LeftVoicemail, MeetingBooked, Bounced, Replied, OptedOut
ContentURLtextThe page URL or content asset for web-tracked rows
ActivityNumbertextyes
StartTimedatetimePlanned meeting start in UTC.
EndTimedatetimePlanned meeting end after StartTime.
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
LeadNotesFree-text notes against a Lead. Markdown body, author, pinned flag for the SDR's "next time you call this person, mention X" sticky note.transaction
FieldTypeRequiredDetails
Leadreferenceyes→ Leads
BodytextyesMarkdown-friendly
Authorreferenceyes→ Users
CreatedAtdatetimeyesServer creation timestamp.
PinnedbooleanPin to top of Lead page
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
RecordNumbertextyes
StatusselectyesRecorded, Superseded
LeadAssignmentsHistorical record of every Owner change on a Lead — initial routing, manual reassignment, MQL handoff to AE, stale recycle back to the queue. Append-only audit. Sales Manager uses this to spot rep-shopping and unfair lead distribution.transaction
FieldTypeRequiredDetails
Leadreferenceyes→ Leads
AssignedToreference→ Users (null when assigned to UnassignedQueue)
AssignedByreference→ Users (system actor for workflow assignments)
AssignedFromreference→ Users (prior Owner; null on initial routing)
Rulereference→ RoutingRules (null on manual reassignment)
ReasonselectyesInitialRouting, MQLHandoff, ManualReassign, StaleRecycle, OutOfOffice, TerritoryRealignment, DuplicateMerge
AssignedAtdateyes
Notestext
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
RecordNumbertextyes
StatusselectyesRecorded, Superseded
ListsSaved segments of Leads — used for outbound cadences, event invites, and bulk operations. A List is a named container; its membership is in `ListMemberships`.master
FieldTypeRequiredDetails
ListCodetextyes
Nametextyes
PurposeselectyesOutboundCadence, EventInvite, NurtureSync, AdAudience, Suppression, Other
Ownerreferenceyes→ Users
MemberCountdecimalyesServer-derived; fx: COUNT(ListMemberships where List = self AND Active = true)
Descriptiontext
Activebooleanyes
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
ListMembershipsOne row per Lead per List. Tracks when a Lead joined the List and (for suppression / outbound) the cadence step they're on.master
FieldTypeRequiredDetails
Listreferenceyes→ Lists
Leadreferenceyes→ Leads
AddedAtdateyes
AddedByreference→ Users
CadenceStepnumberFor OutboundCadence purpose Lists
ActivebooleanyesSet false when removed without deleting the row
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
DuplicateClustersAuto-detected groups of Leads suspected to be duplicates of one another. Surfaced in the Duplicates To Merge view for Marketing Operations or Sales Manager review. The merge action picks a survivor and rewrites references on losing rows.transaction
FieldTypeRequiredDetails
ClusterCodetextyes
MatchKeyselectyesEmailExact, EmailDomain, PhoneExact, CompanyFuzzy, NameAndCompany, EnrichmentMatch
MatchScorenumberyes0–100 confidence
LeadCountnumberyesNumber of Leads in the cluster
StatusselectyesDetected, Submitted, Resolved, Rejected
ResolvedByreference→ Users
ResolvedAtdate
SurvivorLeadreference→ Leads (set on Merged)
DetectedAtdateyes
PreparedByreference→ Users
ResolutionReasonlongtext
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
RecordNumbertextyes
LeadConversionsOne durable CRM handoff intent per qualified lead. Pending and Unknown represent an unresolved external action; successful target identifiers and conversion facts are stored only after authenticated correlated acknowledgement.transaction
FieldTypeRequiredDetails
Leadreferenceyes→ Leads
ConvertedByreferenceyes→ Users; Account executive who created the intent; identifies initiator before completion.
ConvertedAtdatetimeRequired only when Status is Succeeded; server records the verified success time.
AccountReftextAcknowledged target account ID; required for Succeeded.
AccountActionselectMatchedExisting, CreatedNew; required only when Status is Succeeded after target acknowledgement.
ContactReftextAcknowledged target contact ID; required for Succeeded.
OpportunityReftextAcknowledged target opportunity ID; required for Succeeded.
OpportunityNametext
OpportunityAmountdecimalDecimal amount in the parent currency. Initial estimated amount on conversion
Notestext
StatusselectyesDraft, Pending, Succeeded, Failed, Unknown
FailureReasontextSet when Status = Failed
ConversionNumbertextyes
CommandKeytextyesOne durable conversion intent per lead; retries reuse it.
TargetWorkspacetextyes
TargetConnectionreferenceyes→ IntegrationConnections
AcknowledgedAtdatetime
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
RequestedAtdatetimeyesServer timestamp when the authorized conversion intent is created.
LeadSettingsSingle-row global configuration for the lead-management engine — the MQL promotion threshold, stale-lead-recycle window, and duplicate-detection match score floor. One active row at a time.master
FieldTypeRequiredDetails
MQLThresholdnumberyesLead score crossing this triggers MQL promotion
RecycleAfterDaysnumberyesDays before stale-lead-recycle fires (default 30)
DuplicateMatchScorenumberyes0–100 threshold for dedup (default 85)
Activebooleanyes
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
ScoringRunsReproducible score calculation at an input revision and model version.transaction
FieldTypeRequiredDetails
RunNumbertextyes
Leadreferenceyes→ Leads
InputRevisionnumberyes
RuleSetDigesttextyes
Modelreference→ ScoringModels
StatusselectyesQueued, Running, Completed, Failed, Superseded
RuleScorenumberyes
SuggestedScorenumberOptional model suggestion; does not override policy.
AppliedScorenumberyes
Explanationlongtextyes
StartedAtdatetimeyes
CompletedAtdatetime
FailureReasonlongtext
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
ScoringModelsApproved optional model configuration and allowed feature policy.master
FieldTypeRequiredDetails
ModelNumbertextyes
Nametextyes
ProviderReferencetextyes
Versiontextyes
AllowedFeatureslongtextyes
ExcludedFeatureslongtextyes
ScoreUseselectyesExplanationOnly, BoundedContribution
MaximumContributionnumberyes
PreparedByreferenceyes→ Users
ApprovedByreference→ Users
StatusselectyesDraft, Submitted, Approved, Retired
EffectiveFromdatetimeyes
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
PriorityAlertsDeduplicated actionable score and follow-up notifications.transaction
FieldTypeRequiredDetails
AlertNumbertextyes
Leadreferenceyes→ Leads
Runreferenceyes→ ScoringRuns
Ownerreferenceyes→ Users
AlertTypeselectyesThresholdCrossed, FollowUpDue, ConversionFailure
StatusselectyesOpen, Acknowledged, Resolved
DueDatedateyes
AcknowledgedAtdatetime
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
ConsentEventsEvidence for contact policy changes and withdrawal.transaction
FieldTypeRequiredDetails
ConsentNumbertextyes
Leadreferenceyes→ Leads
ChannelselectyesEmail, Phone
DecisionselectyesPermitted, Restricted, Withdrawn
Purposetextyes
Evidenceattachment
OccurredAtdatetimeyes
SourceEventIdtextyes
StatusselectyesRecorded, Superseded
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
AuditEventsAppend-only evidence of commands and independent decisions.transaction
FieldTypeRequiredDetails
EventNumbertextyes
CommandKeytextyesUnique workspace/action replay key.
RecordTypetextyes
RecordIdtextyes
Actiontextyes
Actorreferenceyes→ Users
OccurredAtdatetimeyes
BeforeStatelongtextyes
AfterStatelongtextyes
StatusselectyesRecorded, Superseded
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
IntegrationConnectionsExplicitly configured connector boundaries and credential references.master
FieldTypeRequiredDetails
ConnectionNumbertextyes
Nametextyes
Providertextyes
SecretReferencetextyes
StatusselectyesDisabled, Configured, Paused
Ownerreferenceyes→ Users
LastCheckedAtdatetime
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
IntegrationEventsIdempotent external delivery and reconciliation evidence.transaction
FieldTypeRequiredDetails
EventNumbertextyes
Connectionreferenceyes→ IntegrationConnections
ProviderEventIdtextyesUnique per connection when supplied.
CommandKeytextyes
RecordTypetextyes
RecordIdtextyes
ExternalReferencetext
StatusselectyesPending, Accepted, Confirmed, Failed, Unknown
OccurredAtdatetimeyes
FailureReasonlongtext
WorkspaceKeytextyesServer-enforced workspace scope.
RevisionnumberyesCompare-and-swap version; never client incremented.
CreatedAtdatetimeyesServer creation timestamp.
DuplicateMembersFrozen candidate membership for an independently reviewed duplicate resolution.line
FieldTypeRequiredDetails
Clusterreferenceyes→ DuplicateClusters
Leadreferenceyes→ Leads
CandidateRevisionnumberyes
ProposedSurvivorbooleanyes
WorkspaceKeytextyes
Revisionnumberyes
CreatedAtdatetimeyes
ERP•AI workspace

Start now CRM with Lead Scoring

Create your ERP.AI account and get started with Proto.

Start now Download agent
Previous · reference 2 of 6Reports and analyticsNext · reference 4 of 6Integrations

Customize CRM with Lead Scoring. With Proto, your desktop AI agent.

Ask Proto to help you customize CRM with Lead Scoring.

Customize
CRM with Lead Scoring.
Ask: “Adapt Lead capture.”
ProtoYour desktop AI agent
Download nowFree install · ~1 GB · AI usage extra
macOSWindowsLinux

Bring your first idea to Proto.

Keep this page open while you install Proto. Connect your account and model, then paste this into a new chat.

AI usage is paid separately. You can edit the prompt before copying.

ERP.AI

Business apps and the Proto desktop agent.

  • Business Apps
  • Proto
  • Workflows
  • Headless SaaS
  • Enterprise
  • Pricing
  • Contact
  • Terms of Service
  • Privacy Policy
  • Cookie Policy
© 2026 ERP•AI. All rights reserved.
System status

Your Privacy, Your Choice

We use essential cookies to run the site and optional cookies for features, analytics, and relevant content. See Cookie policy

Manage Your Cookie Preferences

We use cookies to enhance your experience, analyze site traffic, and serve relevant content. By clicking "Accept All," you agree to our use of cookies. You can customize your preferences at any time.

Learn more about how we use cookies

These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.

These cookies enable additional features that enhance your experience, such as live chat, video playback, personalized content recommendations, and remembering user preferences.

These cookies help us understand how visitors interact with our site by collecting anonymous usage data. This allows us to measure performance, detect issues, and continuously improve the user experience.

These cookies allow us and advertising partners, including X, to deliver ads tailored to your interests. They track browsing habits across sites to provide relevant advertising and measure ad effectiveness.