Entitlement exception records across systems: a map of CRM, billing, identity and helpdesk keys

Short answer

Reconstructing an entitlement exception takes three joins across four systems: the CRM account to the billing plan, the plan change to the identity event that changed permissions, and the identity event to the helpdesk ticket that asked for it and confirmed it. The keys are usually an account or customer ID, a user or group ID with a timestamp, and a ticket number typed into a change note. Each join can break, most often after an acquisition.

Visual briefFull-size diagram
Four system nodes in a row, CRM, billing, identity platform and helpdesk, with three linking keys traveling between them: account ID, user and group ID with a timestamp, and the ticket number, joining into one case.
Each key is a join a reviewer needs. Illustrative layout; real systems and keys vary by company.

This system map is part of exception handling records for AI agents. It answers one question for customer platform consultants: where does each record sit, and what ties them into one case?

The four systems behind one entitlement case

An entitlement exception touches more systems than most people expect. Each holds one part of the story, and none holds all of it.

SystemRecord it holdsLinking key outUsual owner
CRMAccount, contract and the order form that sold each featureAccount ID, customer ID in billingSales operations or revenue operations
Billing or subscription systemPlan history with effective dates, add-ons, discounts, renewalsCustomer ID, subscription ID, plan codeFinance or billing operations
Identity platformGroup and app memberships, who changed them and whenUser ID, group ID, timestamp, change noteIT or identity administrator
HelpdeskThe complaint, the approval comment, the resolutionTicket number, requester, organizationCustomer support director
Legacy billing (after an acquisition)The acquired product's plans and contractsOld account IDOften nobody, once retired

The last row is the one that causes trouble. An acquired product arrives with its own customer IDs, plan codes and contract history, and the join from those IDs to the buyer's systems is a mapping table somebody built during integration.

Join by join: the keys that hold a case together

Join 1: account to plan. The CRM account carries a customer ID that billing recognizes. When accounts merge, the surviving account keeps one ID, and the other becomes an alias or disappears. A reviewer needs the mapping, or the legacy plan history cannot be attached to the customer.

Join 2: plan change to permission. In Stripe Billing, a plan change, a discount or a renewal triggers a customer.subscription.updated event. Okta's System Log records a user added to or removed from a group, or assigned to or removed from an app. When provisioning is automated, the two events share a user and a timestamp a few seconds apart. When an administrator grants an exception by hand, there is no billing event at all, and the identity event stands alone.

Join 3: permission to ticket. The strongest link is a ticket number in the identity change note. The weaker link is time: the same users, the same day, the same organization. Zendesk ticket audits keep a read-only history of every update to a ticket, with previous and new values, so the moment of approval can be placed against the identity event.

One fully joined case (Illustrative)

Invented for this page. A fictional 400-person software company has merged an acquired customer's two accounts, and 14 users lost a reporting module the legacy contract had included. Here is the same case seen through each key.

StepSystemRecordKey that links it to the next step
Legacy contract sold reportingCRMOrder form on the old accountOld account ID mapped to new customer ID
Accounts merged on March 3BillingSubscription update; legacy plan closedCustomer ID, subscription ID
Users lose reportingIdentity platform14 group removals the same dayUser IDs, timestamp within minutes of the merge
Customer complains on March 5HelpdeskTicket from the customer's operations leadOrganization matches the customer ID
Exception approved on March 7HelpdeskApproval comment naming the approver and end dateTicket number
Reporting restored on March 7Identity platform14 group adds, change note citing the ticketTicket number in the note
Priced at renewal on September 1Billing and identitySubscription update; 14 group removalsSubscription ID, group ID

Every row joins to the next one with a key a reviewer can check. Remove the ticket number from the change note and the restore looks like an unexplained grant. Remove the old-to-new account mapping and the complaint looks unfounded. The worked exception case tells the same story as a sequence of decisions.

Where the joins break after an acquisition

Four gaps come up again and again.

  • Old IDs with no mapping. Integration teams map active customers. Churned or merged accounts may never get a row in the mapping table.
  • Manual grants with no billing event. Exceptions are granted by hand by definition, so join 2 is often missing exactly where it matters.
  • Change notes left blank. If the administrator did not cite the ticket, join 3 depends on timing.
  • Retention windows. Okta's System Log query returns 90 days of events. Older identity history exists only if the company streamed or exported it. Zendesk's list-all-audits endpoint excludes archived tickets, which are read ticket by ticket instead.

One system alone rarely makes a licensable record set; is one system's data enough for licensing explains why. The post-merger integration data migration guide covers how mapping tables usually get built.

Questions for the customer support director

Stay at metadata level. Ask about systems and keys, not about records.

  • Which systems hold plans, permission changes and tickets, and since when?
  • Does the company keep a mapping from acquired account IDs to current ones?
  • Do identity administrators cite ticket numbers when they grant exceptions?
  • Are identity events kept beyond the platform's own window?
  • Who owns customer data and contracts, and could authorize a licensing discussion? The CEO authorizes; the COO or CFO often owns the records and prepares the case.

The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Customer contracts may limit how account data is used, and identity logs carry personal data, so why data rights matter applies here. What is licensable stays unknown until SourceX's rights review. Partners never ask for or handle raw client records. For the support side in general, see customer support workflows, and when the map is clear, the entitlement referral brief template turns it into one page.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client's billing, identity and helpdesk records still join into whole cases, register as a partner, check the company on who qualifies and read the program terms before you introduce its decision-maker.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is a helpdesk export on its own enough to show how exceptions were handled?

Usually not. The ticket holds the complaint and the conversation, but the entitlement and the permission change live in billing and identity. Without the keys that join them, a reviewer sees requests without the decisions.

What if the identity change never cited a ticket number?

Then the join depends on user, account and time proximity, which is weaker but sometimes workable. A partner simply notes how the company links them; SourceX assesses whether it is enough.

Sources

  1. developer.okta.com/docs/reference/system-log-query
  2. developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits
  3. docs.stripe.com/billing/subscriptions/webhooks
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment