Customer / Account Relationship

Supplier-qualified relationship identity record

Customer relationship record for supplier-qualified relationship identity, qualified by seller, source and effective scope; not remastered party or billing truth.

1. Which master namespace and identifier distinguish this customer relationship from its party identity? identity
2. Which selling organization, business unit or service scope defines the relationship? relationship
3. Which aliases and external customer IDs identify this same scoped record rather than another account of the party? evidence

Account kind and participant roles record

Customer relationship record for account kind and participant roles, qualified by seller, source and effective scope; not remastered party or billing truth.

1. Does the source record represent a customer role, CRM account, individual contact or billing account? classification
2. Which parties act as buyer, payer, user, bill receiver or representative in this relationship? relationship
3. Which authority evidence limits what each related contact can request without assuming purchasing power from a contact link? authority

Customer recognition and onboarding references record

Customer relationship record for customer recognition and onboarding references, qualified by seller, source and effective scope; not remastered party or billing truth.

1. What evidence distinguishes a prospect record from an established customer relationship under the owner's definition? evidence
2. Which onboarding or agreement records establish the current relationship without importing their workflows? process
3. Which prerequisites remain unknown or unmet without turning that state into an automated eligibility or credit decision? constraint

Commercial state and temporal history record

Customer relationship record for commercial state and temporal history, qualified by seller, source and effective scope; not remastered party or billing truth.

1. Which source-qualified lifecycle state and reason describe this relationship at the effective time? state
2. When were activation, dormancy, closure or reactivation observed and recorded, distinct from source effect? temporal
3. Does record closure mean ended commercial relationship, CRM deactivation or data retirement, and which obligations remain elsewhere? lifecycle

Account grouping and hierarchy record

Customer relationship record for account grouping and hierarchy, qualified by seller, source and effective scope; not remastered party or billing truth.

1. Which parent, group or subsidiary links are CRM organization conveniences versus legal-party relationships? relationship
2. What scope, cardinality and validity qualify a group roll-up without assuming the source's one-parent rule is universal? composition
3. Which measures or records must not be double-counted or shared merely because accounts are grouped? constraint

Account responsibility and service routing record

Customer relationship record for account responsibility and service routing, qualified by seller, source and effective scope; not remastered party or billing truth.

1. Who stewards this relationship and which team or role owns each service responsibility? ownership
2. Which assignment, territory or handover evidence limits the responsible person's authority and valid interval? authority
3. Where are unresolved support requests routed without duplicating case or grievance ownership? process

Billing, agreement and entitlement references record

Customer relationship record for billing, agreement and entitlement references, qualified by seller, source and effective scope; not remastered party or billing truth.

1. Which billing accounts, contracts, subscriptions or service entitlements are related, with which master systems? relationship
2. Which account or payment status can be displayed as an attributed snapshot but must not be interpreted as relationship truth? provenance
3. Which operations remain exclusively with billing or service masters rather than the customer context record? constraint

Contact channels and preference evidence record

Customer relationship record for contact channels and preference evidence, qualified by seller, source and effective scope; not remastered party or billing truth.

1. Which contact points and address roles are valid for this relationship and purpose, rather than global party attributes? relationship
2. Which preferences or suppression flags are expressed, inferred or system defaults, and from which evidence? provenance
3. Which separate consent or policy authority must be consulted before contact, regardless of a permissive default flag? authority

Interaction and assessment context record

Customer relationship record for interaction and assessment context, qualified by seller, source and effective scope; not remastered party or billing truth.

1. Which interaction, complaint or purchase references inform the customer relationship without copying their payloads? evidence
2. Which classification or relationship-health assessment has a named method, time and uncertainty instead of an unexplained score? measurement
3. Which information is excluded from profiling and downstream automated decisions under the governing policy? privacy

Duplicate, merge and split lineage record

Customer relationship record for duplicate, merge and split lineage, qualified by seller, source and effective scope; not remastered party or billing truth.

1. Which evidence identifies duplicate relationship records while preserving distinct seller or service scopes? identity
2. Which authorized merge/split decision maps old identifiers and fields to surviving or new records? decision
3. How can a mistaken merge be corrected without losing source lineage, preferences or unrelated customer accounts? exception

Mastership, access and retention record

Customer relationship record for mastership, access and retention, qualified by seller, source and effective scope; not remastered party or billing truth.

1. Which CRM is authoritative for each relationship field and which caches are stale or conflicting? ownership
2. Which actors may read or update which fields without gaining access to private billing or identity data? access
3. What retention and correction rules keep necessary history while avoiding unnecessary personal-data copies? retention

Versioned mapping and agent acceptance record

Customer relationship record for versioned mapping and agent acceptance, qualified by seller, source and effective scope; not remastered party or billing truth.

1. Which exact TMF629, CRM or billing-customer schema mappings preserve the declared record kind? interoperability
2. What identifiers, role meanings, hierarchy rules or preference defaults are lost or changed in a round trip? quality
3. Which authorized record operations and negative fixtures prevent contact, charging or eligibility changes as unintended effects? validation