Quick answer

Customer identity resolution in custom software should produce trusted links between people and source records, not a pile of merged contacts. When you control the backend, start with a stable internal customer ID and reversible links. Attach activity through validated account mappings or a verified claim to the particular record. Keep shared-email people separate, represent payer and attendee roles explicitly, and demonstrate logout and correction before enabling automatic updates.

Choose a model for customer identity resolution in custom software

A parent asks about tutoring, books a child's lesson and pays using the family email. Staff need the connected story; combining the parent and child would give them the wrong one. If your business controls the custom backend and can preserve source records, commission a stable internal customer ID with explicit, reversible links.

Here, customer means a person the application needs to distinguish. An account enables sign-in; a booking, payment customer or CRM contact is a source record. Identity resolution links records to people or transaction roles. Authentication establishes the current account; permission determines what it may see or change. These are separate decisions.

Each tool identifies its own objects. Valid chat, booking and payment identifiers need not describe the same person. Staff need connected relationships showing who booked, attends and paid, with private conversations attached to their established owner.

Email-based merging offers a simple rule but cannot distinguish relatives sharing a mailbox. Deterministic application links use explicit evidence and leave uncertainty unresolved; they suit a backend whose mappings the team can operate. Segment Unify is a named alternative when sources and matching rules become difficult to manage. Its profile matching supports identifier priorities, limits and blocked values. Those controls govern Segment profiles, however, and do not establish permission to open a customer's booking or chat. Choose it for matching complexity, with the same separation and recovery requirements.

Close frontal photograph of a tablet showing an unbranded booking form with separate neutral field areas for an adult booker and child attendee.

The identity-linking decision matrix

Approve the permitted action for each evidence condition before commissioning automatic matching. The matrix below is a proposed application policy: it distinguishes continuity, control of a particular record and permission to use it. An unresolved relationship is a valid outcome, not a failed attempt to produce a complete profile.

An authoritative identifier identifies a record within its source. Check system, tenant or merchant account, object type and identifier together. A payment customer cannot stand in for the attendee. Reuse established mappings within that scope; hold a proposed link if evidence contradicts it.

Incoming evidenceWhat it establishesRequired checkAllowed linking decisionConflict or recovery action
Validated application accountCurrent signed-in accountServer validates session, stored customer mapping and permissionAttach the current action within that permissionHold contradictory links; preserve unaffected work
Scoped source record identifierA particular external recordCheck source, tenant or merchant account, object type and established mappingReuse that record's mappingStop on contradiction; operational owner reviews
Anonymous sessionProvisional guest continuityValidate server-issued context and selected activityRetain guest activity provisionallyDo not combine known people; start fresh at account switch
New registration from current guest accountPossible continuation of guest activityCredential linking succeeds; user confirms selected activityRetain selected activity with provenanceIf linking fails, preserve guest record and use separate claim route
Existing-account guest booking claimControl of a specific booking claimLogin plus valid application-issued, single-use booking secretLink that booking only, within granted permissionReject expired, consumed or conflicting claims; fresh support verification
Matching email, phone, name or deviceCandidate associationObtain account or record-specific evidenceKeep separate while unresolvedWithhold unestablished account-history access
Different booker, payer and attendeeRelated transaction rolesEstablish each person and their roleConnect the transaction without merging peopleCorrect the role relationship if disputed
Two established login identitiesRequest to combine account accessAuthenticate both accounts and obtain confirmationLink only after both checksLeave separate if either check fails; preserve recovery plan
Conflicting mappings or plausible ownersAmbiguityOperational owner reviews original source evidenceHold proposed link; continue unaffected workRecord the decision before resuming affected updates
Mistaken linkNeed for correctionTrace original decision and derived access and mappingsDisable link and rebuild from source ownershipRemove inherited access; repair downstream effects before replay
Proposed linking rules for a connected customer workflow

Mailbox verification establishes current mailbox access, not ownership of every historical lesson or conversation. Both family members may pass that check. Importing all matching-email history would convert valid evidence of mailbox control into an unsupported ownership decision.

Weak evidence stays weak in a chain. Maya sharing an email with Leo, and Leo sharing a browser with a relative, does not make them the same person. Leo's validated account mapping attaches his current action without importing Maya's history. Hold a disputed historical claim while allowing unrelated work to continue.

Permissions need the same precision as links. A parent may manage a particular lesson without receiving the child's unrelated history. A payer relationship need not grant booking management. Require a demonstration of permitted customer actions, not just records appearing together on a staff screen.

Combining login identities changes account access. Authenticate both accounts and obtain confirmation; Auth0 recommends authentication of both in its linking workflow. Control of the current account alone cannot justify joining another.

Close-up of a reception tablet showing separate adult and child participant portraits, selection controls, and a payment-card area in natural light.

Follow one family from guest chat to a booked lesson

Consider an illustrative tutoring business using Firebase Authentication, Intercom Messenger, Stripe Checkout and a CRM, with a custom backend retaining source identifiers. These components have separate jobs; no bundled integration is assumed. Maya and her child Leo share a family mailbox and laptop. Maya books and pays; Leo attends.

The team initially proposes merging matching-email records. But the booking names Leo as attendee and Maya as booker. Keep distinct people linked by roles. Here Maya explicitly may manage this booking, without either person gaining the other's unrelated private history.

Maya chats as a visitor and drafts a lesson request belonging to her current guest context. Firebase's anonymous-account credential-linking route can retain access to that account's protected data after successful registration. The application shows the selected draft and asks her to confirm it. Successful linking retains that draft, without importing everything associated with the family mailbox.

If Maya already has an account or credential linking fails, preserve the guest booking and let her sign in. Under this illustrative application policy, claiming uses an unpredictable, single-use booking secret with a 24-hour expiry and a protected stored verifier. Login, a valid secret and confirmation permit linking that booking. Expired, consumed or conflicting claims grant no account-history access; support must perform fresh booking-specific verification. Email matching cannot rescue a rejected claim.

Assume Maya has an established Stripe Customer mapping. The backend creates Checkout with the internal booking reference and that payer mapping; Stripe supports both. It retrieves the returned session server-side to reconcile the booking and payer. Browser-supplied identifiers or email cannot decide ownership. This connects Maya's payment record to Leo's lesson; it does not establish payment success, which requires a separate payment-status decision.

Retain the CRM identifier when creating a contact for a known person. An imported same-email contact stays separate until the operational owner establishes ownership. Authorized staff then see the lesson, Maya as booker and payer, Leo as attendee and established CRM context together. A connected transaction need not become a combined person.

For an external-booking variation, Calendly's invitee URI identifies the booking record and can match a cancellation. Preserve it, but do not treat it as application ownership proof. Without a trusted mapping or specific claim, keep the booking usable through its existing channel while withholding account-history access. Cancellation updates the appointment, leaving people and payment history distinct.

Then Maya logs out of the shared laptop and Leo signs in. End Maya's chat and guest continuation context first. Proposed copy: “You are signed out. Sign in to your own account to view your bookings and conversations.” Resolve Leo through his own mapping, despite the familiar browser and mailbox.

Intercom uses a stable user identity in a server-signed token; shut down Messenger before starting another authenticated user. It also documents absorption of same-device logged-out activity at authenticated startup. Demonstrate that Leo sees none of Maya's conversations. If ambiguous anonymous activity enters his history, stop that rollout path and keep it outside authenticated history until the boundary works.

Child lesson registration card, payment receipt and appointment slip arranged separately on a worn wooden reception counter in strong daylight.

Prove correction works before automatic updates begin

A reversible link needs preserved source ownership and a traceable reason for the decision. Give ambiguous cases to an operational owner, implementation and repairs to the technical lead, and customer-visible acceptance to the product owner. Do not let destructive CRM cleanup become a hidden prerequisite for connecting the journey.

Preserve the original source record, ownership, linking evidence and decision. The technical lead must trace views, permissions and downstream mappings derived from that decision. A final combined profile alone loses the information needed for separation. Keep imported field values attributable to their sources.

Disable a wrong link and affected automatic updates. Remove inherited access and invalidate affected sessions or cached permissions. Suspend derived mappings and pending actions that could recreate the error. Rebuild views from original ownership, repair downstream mappings and replay only reviewed updates after approval. Check customer accounts too: old sessions must no longer expose another person's history.

Application reversal is not universal rollback. HubSpot merges cannot be unmerged; replacement contacts require reconstruction and do not restore the original state. Before destructive cleanup, the responsible owner must establish that records represent the same entity and accept the destination's recovery limits. Matching contact details cannot settle this.

  1. Identify the people and transaction roles the workflow must distinguish, including who can manage a booking and whose private history stays separate.
  2. Have the technical lead preserve scoped source mappings, original ownership and the evidence behind each link before adding automatic downstream writes.
  3. Apply the matrix to a complete staging journey, then add the distinct new-registration and existing-account claim routes and shared-device session boundaries.
  4. Demonstrate shared email, different payer and attendee, repeated booking events, cancellation, contradictory ownership and wrong-link reversal using the proposed systems.
  5. Have the product owner accept the resulting relationships and private-history separation. Require no duplicated relationships after retries and restored source ownership after correction before enabling affected writes.

Stop automatic linking and affected writes on unexplained conflict or failed reversal; preserve incoming records for review. Run Maya's journey, switch to Leo, then revoke a deliberately mistaken link and inspect both accounts. After settling these identity outcomes, use the workflow automation testing checklist to extend acceptance-test coverage.

Side view of a standing tutoring-centre worker comparing an appointment slip with a contact folder beside an open records cabinet.

Carry the resolved booking into website video calling

If the booked service happens by video, consultation entry is the next place these relationships must hold. The attendee, booking manager and payer can be different people. Accepting a connected booking does not by itself decide which of them may enter the lesson.

Request a prototype showing the resolved account entering the correct booked consultation and the role granting entry. Include Maya's booking management and Leo's attendance as distinct outcomes, plus the shared-family cases that must stay separate. Check that payment ownership has not silently replaced attendance permission.

This gives the development discussion observable behavior to assess. The immediate result is a concrete prototype scope and acceptance conditions covering account, scheduling and access relationships.

Wide view of a modest tutoring classroom where a tutor arranges lesson papers beneath a wall-mounted monitor and fixed video camera.

Scope the consultation entry prototype

Website Video Calling compares simple embeds with API and SDK integrations and describes Scrile Stream custom development with authentication, roles, scheduling and session-access options. Use the guide to compare routes. If your workflow needs custom consultation entry, take the accepted identity matrix to the page's Scrile Stream contact route and request the scoped prototype above. The result to seek is a concrete development scope for the correct account entering the correct booked session; the guide does not supply a ready-made identity-resolution engine.

Frequently asked questions

What is identity resolution?

It decides which source records belong to the same customer and which relate through roles. It does not replace account authentication or permission checks.

Can email alone identify a customer?

No. Shared mailboxes can represent different people. Verification establishes mailbox access, not ownership of every historical record using it.

How does a new guest register?

Successful credential linking can retain the current guest account's selected activity. Show what will continue and confirm it, without importing unrelated history.

How does an existing customer claim a booking?

Require login and a valid booking-specific claim secret. Reject expired, consumed or conflicting claims and use fresh booking-specific support verification.

Can payer and attendee differ?

Yes. Keep their people records separate and connect them to the booking through explicit roles, each with its own permissions.

What happens on shared-device logout?

End the previous chat and guest continuation context before another person begins. Demonstrate that the next account cannot see the previous person's conversations.

What happens to ambiguous CRM contacts?

Keep them separate until source evidence establishes ownership. Their existing channel may remain usable without granting unestablished account-history access.

Can an incorrect merge be reversed?

Preserved application links can be corrected along with derived access and mappings. Destructive external merges have separate limits; HubSpot has no native unmerge.