The shared inbox problem in company referral tracking: a six-step identity check that turns info@ into one legal company, one group and one CEO

Short answer

A shared inbox breaks referral tracking because an email address identifies a mailbox, not a company or a person. An introduction sent to info@ reaches whoever reads it that day, a reply from it does not show who agreed, and the company may already have written to SourceX from that same address. Before you introduce, resolve the address to one legal entity, its group and a named CEO who has replied personally, then record the company, domain, method and timestamps in your submission.

Visual briefFull-size diagram
A left-to-right chain that resolves an email address in six steps: mailbox type, domain operator, legal entity, group, CEO reply and history question, ending in one recorded introduction, with a warning branch where a shared mailbox answers instead of a person.
Illustrative addresses. The six steps follow the program terms, the Channel Partner Agreement sample and the who-qualifies page, checked 2026-10-26.

The problem runs both ways: a company's role address hides who said yes, and your own team mailbox hides which partner account introduced the company. The fix is the same: get from a mailbox to a person, and from a domain to an entity, before anything is submitted.

Three places a shared mailbox hides the facts you need

The company's role address. RFC 2142, the Internet specification for common mailbox names, lists business mailboxes such as INFO, MARKETING, SALES and SUPPORT for reaching an organization's personnel by role. Microsoft's guide to creating a shared mailbox describes the same pattern from the inside: a group of people monitor and send from one address, and a member's reply appears to come from the shared mailbox, not from the individual. So "Yes, go ahead" from info@ shows that someone is interested, not that the CEO knows. Under the program the CEO authorizes a licensing discussion, and an introduction made without the decision maker's knowledge is usually not a fit.

The company's earlier contact with SourceX. Section 3 of the terms counts any earlier lead, account or email correspondence between SourceX and the company as a relationship, however it began, and a company SourceX already knew is not credited to a later partner. A question someone typed into a form or sent from the company's general mailbox last spring counts the same as a call with the CEO. SourceX checks its own records before inviting an introduced company. You cannot see those records, but you can ask the CEO whether anyone has written to SourceX before.

Your own team's mailbox. If introductions leave your firm from a shared address such as referrals@, the email shows your firm, not the partner account that introduced the company. The terms require an approved partner account with accurate identity details and credit one partner per company. The partner agreement asks every introduction record to identify the company, its domain, the partner, the opportunity, the introduction method and the timestamps. A team mailbox fills in none of the partner field.

Domains add a fourth complication. One domain can serve several entities in a group, and one company can run several domains after a rebrand or an acquisition. The domain field in a record is a clue to the entity, not the entity itself.

Sort the thread by sender, mailbox type and date

Before any submission, lay the email thread out in date order and mark each message's mailbox type. This Illustrative thread for a 210-person property management company shows a shared inbox being resolved into a person.

DateFromToMailbox typeWho is identifiedWhat it establishes
2026-08-03The partner firm's insights@ addressThe company's info@Shared to roleNobodyA broadcast mention, not an introduction
2026-08-05The company's info@The partner firm's insights@Role, reply sent by an unnamed memberNobodySomeone is interested
2026-08-11The account lead's own addressThe CEO's own addressPersonal to personalThe CEOA request for a short call
2026-08-14The CEO's own addressThe account leadPersonalThe CEOThe decision maker knows and wants the conversation
2026-08-14The account lead's partner accountThe SourceX portalAuthenticated submissionThe partner and the companyThe recorded introduction, with company, domain, method and timestamp
2026-08-26The CEO, through the applicationSourceXPersonalThe companyThe verified application, day 12 of 90

The first two rows feel like progress and establish almost nothing. The record starts on 11 August, when two named people write to each other.

The company-identity verification workflow

Six steps, in order. Each ends with something written down, and each has a point where you stop rather than guess.

StepQuestionWhat you recordStop or escalate when
1. Classify the addressIs it a person's mailbox, a role or shared mailbox, or a free webmail account?The address and its typeIt is a role or shared mailbox: find the named person first
2. Find who runs the domainWhich entity operates the website and email on this domain?The legal name shown in the company's own terms page, invoices or contractsSeveral brands or entities use the domain: list each one
3. Pin the operating entityWhich entity's employees created the records, and which holds them today?Legal name, jurisdiction, registration number if known, date checkedYou cannot tell which entity: ask the CEO rather than guess
4. Map the groupIs there a parent, a sister company or a recent acquirer?The parent and the entities under itAnother group entity was introduced or contacted SourceX: note it for duplicate review
5. Name the authorizerWho is the CEO, and has the CEO replied personally?The CEO's name and the date of that personal replyOnly a shared mailbox has answered: wait
6. Ask the history question, then submitHas anyone at the company written to SourceX before, from any address?The CEO's dated answer, then the portal submission with company, domain, method and timestampsThe answer is yes or unsure: say so in the submission

Method note. The workflow applies the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the record fields in the unsigned Channel Partner Agreement sample (version 2026-10-19) and the who-qualifies guidance, read on 2026-10-26, with RFC 2142 and Microsoft's shared mailbox guide for how role addresses behave. It identifies entities and people; fit with a program is decided in SourceX's review. SourceX has not published how often duplicates trace back to shared mailboxes, so this is a prevention method, not a measured fix.

Step 4 is where partners most want a rule and the terms give only half of one. A parent and its subsidiaries count as one company for the USD 50,000 floor, which applies once to the group's first qualifying transaction; that is settled. Whether a sister company's earlier introduction, or a parent's earlier contact with SourceX, affects credit for the entity you introduce is not settled. SourceX decides it in duplicate review, so the right move is to name the whole group in the submission and promise nothing.

Step 6 is the cheapest step: one dated question to the CEO can save a month of work on a company that was never new to SourceX.

Four inbox timelines and the term behind each (Illustrative)

Illustrative. Generic companies and invented dates.

A. The info@ yes. On 1 July an introducer writes to a 150-person dental lab group's info@ address. A reply from info@ on 2 July says "go ahead", and an operations manager applies through the partner link on 10 July. The CEO never hears of it. The CEO authorizes, and an introduction made without the decision maker's knowledge is usually not a fit; step 5 would have stopped it.

B. The April email. The company's info@ asked SourceX about data licensing on 7 April. On 14 August a partner introduces the CEO, who applies on 26 August. Section 3 of the terms decides it: earlier email correspondence is a relationship however it began, so the company is a duplicate. Step 6 would have surfaced it first.

C. One domain, two companies. A holding company runs a 300-person logistics operator and a 60-person freight brokerage on one domain. Another partner introduced the brokerage on 12 May. On 2 September your introducer writes to the logistics operator's CEO. No published rule settles whether the brokerage's introduction affects credit here; SourceX decides it in duplicate review. The floor is settled: the USD 50,000 element applies once across the group, on its first qualifying transaction.

D. The team mailbox. Two consultants at one firm each hold their own partner account. On 8 September one emails a CEO from the firm's referrals@ mailbox and submits nothing. On 15 September the other submits the same company from their own account. Only one partner is credited per company, and the 8 September email names no partner account. The firm should have chosen its partner of record first; now SourceX weighs the dated records.

CaseWhat the mailbox hidGoverning termRoute
AWhether the CEO knewWho-qualifies screening guidance; the CEO authorizesDo not introduce until the CEO replies personally
BThe company's earlier contact with SourceXTerms section 3Duplicate, not credited
CWhich entity behind the domain was introducedNot settled for credit; one floor per groupDuplicate review, group named
DWhich partner account introduced the companyTerms section 2: one partner per companyDuplicate review on dated records

What to send SourceX when identity is the question

If a case reaches review, email hello@sourcex.si with the referral details and:

  1. The legal name and jurisdiction of the entity you introduced, and every domain it uses.
  2. The group structure: the parent, and the other entities you know of.
  3. The CEO's name and role, and the date of the CEO's personal reply.
  4. Your written introduction, unedited, and the date of the portal submission.
  5. The CEO's dated answer to the history question.

Do not export or forward the company's shared inbox, its internal threads or anything about its staff. A review does not need them, and partners never receive other partners' records in return. If the company's support or sales mailbox history is itself a record set worth discussing, that is a licensing question for the company and SourceX, covered on sourcex.si in exporting shared inbox history from Front and Help Scout.

Where an identity check cannot help

What the portal records for each introduction is outlined in the partner portal explainer, and earlier SourceX contact is tested in whether an existing relationship affects credit.

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.

When a company's interest arrives through a shared address, run the six steps before the link goes out: register for a partner link under the person who will be the partner of record, check the entity against who qualifies and read sections 2 and 3 of the program terms. More attribution cases are in the guides library.

  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 introduce a company whose only reply came from info@?

Wait for a personal reply from the CEO first. A reply from a shared mailbox appears to come from the mailbox, not the person who wrote it, and under SourceX's screening guidance an introduction the decision maker never knew about is usually not a fit.

Does an old email from the company's shared address to SourceX matter?

Yes. Under the terms a relationship includes any earlier lead, account or email correspondence the company had with SourceX, whatever started it, and a company SourceX already knew is not credited to a later partner. Ask the CEO whether anyone has written to SourceX before, from any address.

Is a company's shared inbox history itself licensable data?

It can be a separate question from the referral. Years of customer conversations may be a record set, but whether the company can license it depends on its rights and SourceX's review; the referral step only asks what exists, never for an export.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. refer.sourcex.si/who-qualifies
  4. rfc-editor.org/info/rfc2142
  5. learn.microsoft.com/en-us/microsoft-365/admin/email/create-a-sha…

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