CRM Responsibilities

How the Product Area Is Divided

CRM keeps the customer's people and organizations and the work done around them. Entities is the core: it owns the people, the organizations, the ties between them and the safeguards that protect and explain every change. Around it, other CRM modules each own one concern and work through Entities' records or react to their changes: data quality finds and merges duplicates, regions assign people and organizations to geographic or organizational regions, data jobs run bulk updates and imports, and activities and tasks record the work staff do with people. Entities, Data Quality and Regions are designed so far; the others are named here so the boundary is clear, and each gets its own section when its design is drafted.

Entities

Entities is the record owner for contacts, organizations and contact-owned affiliations and role periods. Its safeguard model covers versions, customer locking, independent Rhythm protection, archive metadata, contact and organization revisions, and workspace CRM defaults. Classification catalogues remain within this ownership even though a separate function hosts their routes.

The module exposes record creation, reading, editing and removal, dedicated archive and customer-lock actions, history reads, disconnected-detail resolution, date settlement, compliance scans and notice preview. It also exposes permission-filtered presentation defaults and classification maintenance. The structured operation list is the boundary inventory.

Changed contact and organization transactions capture aggregate revisions and events. Independent handlers perform compliance and projections after commit. Accepted notice pointers commit with the compliance transition and deduplicate recipient batches; Platform owns delivery outcomes. The guarantee references point to the object invariants and their enforcement evidence.

Implementation qualifications distinguish that boundary: deletion is unversioned, classification records lack record history, unchanged type writes can advance versions, and legacy contact-role saves can bypass lock audit. Complete replacement, stale no-op handling, explicit relationship operations and deployment activation still need implementation or product resolution.

Data Quality

Data Quality identifies possible duplicate people and organizations and supports an authorized decision to combine them. Its duplicate service owns matching keys, candidate pairs, review groups, workspace rules, creation exceptions and rechecks. Its merge service owns plans, attempts, durable-job links and forwarding aliases.

Detection runs after committed record changes. Pair decisions rebuild affected groups in their transaction, while replacing matching keys and writing new pairs can use separate transactions. Creation blocking applies to ordinary creation; an authorized exception is recorded alongside the admitted record.

Merge execution encloses participating database changes in one transaction. A rolled-back running claim remains queued until separate failure settlement; a caught execution error normally produces a failed attempt rather than an automatic business retry. The originals remain in merge outcomes, and forwarding aliases preserve absorbed identities, although deleting a survivor can leave their destination absent.

Ordinary survivor saves and participant deletion call Entities. Merge-owned persistence also rewrites references, moves affiliations and prepares organization parentage, while other applications supply their own participant functions. The module declares no custom-field support and publishes no operations to Submissions.

Regions

Regions owns the catalogue, geographic policy, recalculation runs and automatic placement decisions. Entities owns the contacts and organizations that store regional values and permits authorized staff selections. Regional processing reads and writes the record’s placement facet through Entities persistence rather than storing another copy.

The regional surface provides catalogue maintenance, complete-policy saving, individual-rule operations, saved-policy preview and recalculation reads and start. Twelve hosted import operations delegate file execution and controls to the Data Job Engine. Those routes require both regional bulk and update authority; other protected operations use their declared regional keys.

Committed address and override changes reach common reconciliation through captured events. Organization address changes also revisit linked contacts. Policy saves update generations without moving existing records; staff request recalculation when they want changed coverage applied. Traversal commits placements and progress batch by batch, preserves overrides and update locks, and continues through its own captured events.

The boundary has important qualifications. Policy reads do not lock settings and criteria into one consistent snapshot, first policy writes can collide, and whole-list saves reset retained rule versions. Replacement clears omitted optional fields, unchanged updates advance versions, and ordinary requests still manage locks without regional history. Recalculation failure settlement is best effort, so exhausted delivery can leave a run stuck in running. New reference checks preserve workspace integrity while older regional references remain tolerated.

Activities and Tasks

Activities and Tasks owns interaction records, outstanding work and the computed timeline for each related CRM record. Activity owns its categories, results, associations and supporting-file entries. Task owns its categories, shared queues, routing and closing attribution. The two service contracts define their record and operation boundaries.

The module provides interaction creation, correction, removal and revision reads; configuration maintenance; and contact and organization timeline reads and summaries. Task operations cover work persistence, routing, claiming, release and lifecycle commands, with a separate service dispatcher for workflow callers. Platform executes general workspace views over registered datasets. The local declarations include activity history capture, overdue-task attention and shared queue responsibility.

Interaction persistence and requested follow-up insertion commit together. Task checks maintain its lifecycle and routing stamp pairs, and claim arbitration admits at most one committed holder. Enabled attention participates in task transactions, while separately read reconciliation pages can publish older details without a repair deadline. Related-record deletion retains interactions and tasks but can remove all interaction links. Task revision history, assignment eligibility, role-offer discovery and external integration readiness remain unresolved in their existing planning records and examination findings.

What Is Delegated to Platform and Other Areas

Platform defines customization and presentation metadata, evaluates security, owns search projections and communication delivery, and supplies attention, files, numbering and shared work engines. Entities stores the CRM values and selects applicable definitions. Its communication seam includes a narrow insert-only submission grant and bounded request-object write; that exception does not grant general Platform table ownership.

Other CRM modules own data quality, regions, bulk work and activities. They use Entities persistence or react to captured events without acquiring another ownership home for its records. Submissions owns future intake processes, and the scoped Entities contracts declare their operations unpublished.

Data Quality uses Platform for change dispatch, durable execution, portal identity, attention and workspace lifecycle coordination. CRM supplies the duplicate and merge lifecycle participants. A merge invokes application-owned reference functions inside its execution transaction; external retry and recovery policies require evidence from their owners.

Regions uses Entities for stored placements and the Platform Data Job Engine for file execution. Shared libraries supply captured-change dispatch and queue retry; regional handlers retain responsibility for their decision and failure-settlement behavior.