# Shared inbox referral tracking: a six-step check | SourceX

Canonical: https://refer.sourcex.si/guides/the-shared-inbox-problem-in-company-referral-tracking
Last updated: 2026-11-05

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.

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.

| Date | From | To | Mailbox type | Who is identified | What it establishes |
|---|---|---|---|---|---|
| 2026-08-03 | The partner firm's insights@ address | The company's info@ | Shared to role | Nobody | A broadcast mention, not an introduction |
| 2026-08-05 | The company's info@ | The partner firm's insights@ | Role, reply sent by an unnamed member | Nobody | Someone is interested |
| 2026-08-11 | The account lead's own address | The CEO's own address | Personal to personal | The CEO | A request for a short call |
| 2026-08-14 | The CEO's own address | The account lead | Personal | The CEO | The decision maker knows and wants the conversation |
| 2026-08-14 | The account lead's partner account | The SourceX portal | Authenticated submission | The partner and the company | The recorded introduction, with company, domain, method and timestamp |
| 2026-08-26 | The CEO, through the application | SourceX | Personal | The company | The 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.

| Step | Question | What you record | Stop or escalate when |
|---|---|---|---|
| 1. Classify the address | Is it a person's mailbox, a role or shared mailbox, or a free webmail account? | The address and its type | It is a role or shared mailbox: find the named person first |
| 2. Find who runs the domain | Which entity operates the website and email on this domain? | The legal name shown in the company's own terms page, invoices or contracts | Several brands or entities use the domain: list each one |
| 3. Pin the operating entity | Which entity's employees created the records, and which holds them today? | Legal name, jurisdiction, registration number if known, date checked | You cannot tell which entity: ask the CEO rather than guess |
| 4. Map the group | Is there a parent, a sister company or a recent acquirer? | The parent and the entities under it | Another group entity was introduced or contacted SourceX: note it for duplicate review |
| 5. Name the authorizer | Who is the CEO, and has the CEO replied personally? | The CEO's name and the date of that personal reply | Only a shared mailbox has answered: wait |
| 6. Ask the history question, then submit | Has 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 timestamps | The 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.

| Case | What the mailbox hid | Governing term | Route |
|---|---|---|---|
| A | Whether the CEO knew | Who-qualifies screening guidance; the CEO authorizes | Do not introduce until the CEO replies personally |
| B | The company's earlier contact with SourceX | Terms section 3 | Duplicate, not credited |
| C | Which entity behind the domain was introduced | Not settled for credit; one floor per group | Duplicate review, group named |
| D | Which partner account introduced the company | Terms section 2: one partner per company | Duplicate 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](https://sourcex.si/insights/exporting-shared-inbox-history-from-front-and-help-scout).

## Where an identity check cannot help

- **SourceX's records stay out of view.** The history question relies on what the CEO remembers or can find.
- **Shared addresses outlive their owners.** After an acquisition, a role address may have been used by the previous owner's staff; the [acquisition identity mapping guide](/guides/acquisition-identity-mapping-data-licensing) covers that chain, and a renamed company is handled in the [rebrand evidence packet](/questions/company-rebrand-referral-attribution-evidence).
- **Group credit is unsettled.** The workflow flags group cases; it does not decide them.
- **Counting is a separate job.** Removing duplicates across your own lists is covered in the [canonical company identity register](/guides/how-to-avoid-counting-the-same-company-across-three-networks), and subsidiaries in [multiple subsidiaries in referral attribution](/guides/how-to-handle-multiple-subsidiaries-in-referral-attribution).

What the portal records for each introduction is outlined in the [partner portal explainer](/questions/what-is-a-partner-portal), and earlier SourceX contact is tested in [whether an existing relationship affects credit](/guides/how-to-check-whether-an-existing-sourcex-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](/register) under the person who will be the partner of record, check the entity against [who qualifies](/who-qualifies) and read sections 2 and 3 of the [program terms](/terms). More attribution cases are in the [guides library](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/who-qualifies
- https://www.rfc-editor.org/info/rfc2142/
- https://learn.microsoft.com/en-us/microsoft-365/admin/email/create-a-shared-mailbox?view=o365-worldwide
