Entitlement exception referral brief template: a fill-in form for customer platform consultants, with one completed example

Short answer

A company introduction about entitlement exception handling needs one page of metadata: company size, the business task, which systems hold plan histories, permission changes and support resolutions, how many years they cover, roughly how many exceptions a year, any dated access event, who owns each system, and the CEO, who can authorize a licensing discussion. Nothing else. No tickets, log extracts, customer names or screenshots. Below are a blank template, notes on each field and one completed Illustrative brief.

Visual briefFull-size diagram
A blank referral brief form with eight fields, company size, task, records, systems, years, volume, access event and authorized contact, filling in one by one with Illustrative values for a 400-person software company.
Illustrative values. Every field is metadata; no record content belongs in the brief.

This template is part of exception handling records for AI agents. Use it once you have had the conversation and are ready to write the introduction.

When to write the entitlement brief

Write it after you have heard, from the person who runs support, how the company handles customers whose entitlements conflict. The usual moments are a helpdesk migration, a billing consolidation after an acquisition or a customer platform rebuild. Three conditions should hold:

  • The customer support director, or someone with equal standing, agrees you may describe their records to SourceX in general terms.
  • You know who sits above them and can approve a licensing discussion: the CEO, often with the COO or CFO as sponsor.
  • You can fill most fields from what you were told. If you would need to log in to find out, ask instead.

The brief replaces a long email thread. The sponsor should be able to forward it upward without edits, and SourceX should be able to decide from it whether a first call makes sense. For timing during a helpdesk change, see the helpdesk migration introduction plan.

The blank brief

Copy this into a document and fill in the right-hand column. Keep each entry under twenty words: a description, a range or a name.

FieldWhat to write
Company sizeFull-time employees at peak, contractors excluded
Business taskThe exception in one line, such as resolving conflicting entitlements after an account merge
RecordsRecord types that exist: plan histories, add-on and discount changes, group or app memberships, tickets with approvals
SystemsEach system by category and the year it went live: billing, identity platform, helpdesk, CRM, legacy billing
Years of historyEarliest usable year per system, and any gap from a migration
Record volumeRough exceptions per month or year, and whose estimate it is
Access eventAny dated change set by the company: retirement, migration cutover, contract end
Record ownerWho runs each system or knows where the records are kept
Open questionThe one thing nobody could answer yet
Authorized contactThe CEO, who can approve a licensing discussion, plus a working contact

There is no field for record content, file names or sample exports. That is on purpose.

Notes on each field for SaaS entitlement records

Company size. The baseline is 50+ full-time employees at peak, contractors excluded. Outsourced support agents do not count. After an acquisition, count the combined company if the acquired team has joined it. On location: 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.

Records. Name what exists. Billing platforms record plan changes as events; in Stripe Billing, changing a plan or applying a discount triggers a subscription update event. Whether the company kept those events beyond the platform's window is a separate question, so "current plans" and "plan history since 2019" are different entries.

Systems. Use categories and plain text names. Note whether identity events are streamed to an external store. Okta, for example, offers log streaming to external platforms, and companies that use it often have years of permission history that the platform itself no longer shows.

Years of history. Tickets usually reach back furthest. Zendesk archives most tickets about 120 days after closing, but they stay reachable through search and the API, so archived does not mean lost.

Access event. Only a dated, documented event counts: the acquired billing system's retirement, a helpdesk cutover, a vendor contract ending. Do not invent urgency. The entitlement retention timeline explains which records age out first.

Open question. Pick one. One clear question shows you listened; three make the brief look unsure.

Authorized contact. Name both the CEO and the working contact. The who-can-license decision tree explains the other roles.

A completed brief (Illustrative)

Fictional company, invented for this page. A 400-person B2B software company bought a smaller competitor two years ago and is now consolidating the acquired product's plans onto its own.

FieldCompleted entry (Illustrative)
Company size400 full-time at peak, contractors excluded
Business taskResolving conflicting entitlements after acquired customer accounts were merged
RecordsPlan histories, add-on changes, group memberships, tickets with approval comments
SystemsBilling since 2018, identity platform since 2019, helpdesk since 2017, acquired billing system
Years of historyTickets from 2017; billing events in warehouse from 2020; identity events streamed since 2023
Record volumeAbout 40 entitlement exceptions a month, by the support director's estimate
Access eventAcquired billing system retires next year, per the company's integration plan
Record ownerSupport director for helpdesk; IT for identity; finance for billing
Open questionWas the approver recorded in the identity change note, or only in the ticket?
Authorized contactCEO; customer support director as working contact

Read it as SourceX would. The chain of plan, permission and resolution exists for at least three years in every system, the ticket side reaches back further, the access event is real and dated by the company, and the open question is narrow. Nothing in it is a record.

What the brief settles and what it leaves open

The brief settles which records exist, where, for how long, who owns them and who can authorize a licensing discussion. It does not settle whether they are licensable. Customer contracts may restrict account data, identity logs carry personal data, and acquired records may come with purchase-agreement terms; see why data rights matter. SourceX's current data needs, the rights review result, preparation work and any offer all stay unknown until SourceX reviews them.

Attach the brief to a short personal note to the sponsor; the warm introduction brief is a good model, and the client opportunity brief generator can help draft it. Sign the Channel Partner Agreement before you submit. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. Tell the company that any reward is paid separately by SourceX and never comes out of the company's payout.

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 your completed brief names the systems, the years and the CEO, who can say yes, register as a partner, confirm the basics on who qualifies and read the program terms before you send it.

  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

Can I attach a sample ticket or log extract to make the brief more convincing?

No. The brief is metadata only. Partners never ask for or handle raw client records; SourceX looks at records with the company directly, after agreements are in place.

What if the support director does not know the record volume?

Write a range with whose estimate it is, or leave the field as an open question. A clearly sourced estimate is more useful than a precise-looking guess.

Sources

  1. help.okta.com/oie/en-us/content/topics/reports/log-streami…
  2. support.zendesk.com/hc/en-us/articles/4408887617050-About-ticket…
  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