How to end a referral thread without burning the relationship: a four-line close and a suppression record that stops your firm asking twice

Short answer

End the thread with one short message: thank them, say plainly that you will not raise it again, confirm that nothing is pending and none of their information was passed on, and leave the only way back in their hands. Then log a suppression record so no colleague asks twice: who asked, the scope, the date and who must honor it, without their private reasons. If they objected, do not schedule a check-in to see whether they changed their mind.

Visual briefFull-size diagram
Four ways a referral thread ends, a clear no, a stop request, silence and a failed fit, converge into one four-line close message and then into a suppression record whose fields are scope, date, honored by and revisit only if they raise it.
The close and the record follow the template on this page; the endings are generic, not real threads.

This guide is for channel partnerships managers at consultancies, managed service providers, agencies and accounting firms that refer across many client relationships. In a firm, one person's close has to bind everyone, because the fastest way to burn a relationship is a colleague asking the same CEO the same question a month later.

Four ways a referral thread ends, and what each close owes the company

The thread started with a reason that was about the company: its history, its systems, something its CEO said. The close should end it on the same footing, in one line that uses the company's own words, and then stop. What else the close says depends on how the thread ended.

EndingWhat you heardWhat the close doesSuppression scopeRevisit
A clear no"Not for us."Thanks them and confirms you will stopThis topic, this companyOnly if they raise it
A stop request"Please stop contacting me about this."Confirms the stop the same day and asks nothingEvery channel from your firm on this topic; the whole company if they said soNever by you
Silence after your limitNo reply to the ask or to one follow-upOne final note that makes no reply a complete answerThis topic, until any trigger they gaveOnly a dated event they named
A failed fit you foundRecords that belong to clients, or 40 full-time employees at peakStates the program fact plainly, without judgmentThis topic, until the fact changesThe fact changing

The fourth ending is the one partners skip: closing a thread yourself because a check failed. SourceX's screening page lists material that belongs to the company's clients as usually not a fit, and the size test is 50+ full-time employees at peak, contractors excluded. 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. Saying which fact failed is more respectful than going quiet, and that same page adds that missing one program's criteria does not rule a company out of a different program later on.

The respectful close and suppression template

The template has two parts: a message of four lines, and a record nobody outside your firm sees.

Part 1, the close. Four lines, in this order, and nothing after them.

  1. Thanks, with their reason in their words. One line that shows you heard them.
  2. The stop. "I won't raise it again."
  3. The loose ends. What is pending (usually nothing) and what you passed on (usually nothing). Only write what is true.
  4. The door, held by them. No date, no link, no question.
EndingLine 1Line 3Line 4
A clear no"Thanks for the straight answer on licensing your service history.""Nothing is pending, and I haven't passed your details to anyone.""If it's ever useful, you know where I am."
A stop request"Understood, and thank you for saying so.""You won't hear about this from me or anyone at our firm again."Leave it out; end on line 3
Silence"A few weeks ago I raised licensing your project archive.""I'll take no reply as a no, and that's completely fine.""If it ever becomes useful, just reply to this."
A failed fit"I checked the program's criteria against what you told me.""It looks for 50+ full-time employees at peak and you're at 40, so it isn't a fit today.""If that number changes, it may be worth a look; your call."

Part 2, the suppression record. One entry per request, written the day it arrives.

FieldWhat to writeRule
Person and companyName, role and the company's legal nameOnly the person who asked, and the company if they spoke for it
ScopeThis topic only, all outreach from your firm, this person or the whole companyUse the widest scope they stated; when unclear, take the wider one
ChannelEmail, phone, in person, or allAll, unless they named one
Date and wordsThe date, and their words in one quoted lineNo paraphrase that softens it
Honored byEvery colleague who knows the company, plus the CRM and any mailing toolApplied the same day
What we holdWhat your firm keeps about the referral, and what it deletedJust enough to honor the request
Never recordPrivate reasons: finances, health, disputes, opinions about the personNowhere, in any system
Revisit"Only if they raise it" after a stop or an objection; a dated condition only if they gave oneNo check-in after an objection
OwnerOne person who reviews the list each quarterReviews scope and spelling, never whether to ask again

Two regulators explain why the record beats deletion. The UK Information Commissioner's Office says that when someone objects to direct marketing, suppressing their details is usually preferable to erasing them, provided you keep just enough to respect their preference and mark it clearly. Its guidance adds that you cannot contact them later to ask whether they have changed their mind, and that a confirmation message must not require them to do anything. In the US, the FTC's CAN-SPAM guide says opt-out requests must be honored within 10 business days, without a fee, without asking for more than an email address and without any step beyond a reply or a single web page, and that the law makes no exception for business-to-business email. It covers messages whose primary purpose is commercial; whether a personal note about SourceX meets that test is a question for your counsel. The template meets the stricter reading either way.

An architecture practice says "please leave it" (Illustrative)

Illustrative. A 210-person architecture practice whose document management is run by the partner's IT consultancy. After one message about licensing its project records, the CEO replied: "Our drawings belong to our clients under our contracts, and I'm not comfortable with this. Please leave it."

Before:

Totally understand! For what it's worth, SourceX's review would sort out the client question, and my attribution window closes in about 60 days, so let me know if you change your mind before then. I'll check back in a couple of months in case things change. Here's the link again just in case.

That close argues with the no, makes a claim about SourceX's review nobody can support, turns the partner's credit clock into the company's deadline, schedules a check-in after an objection and repeats the ask.

After:

Understood, and thank you for telling me plainly. I won't raise it again, and nobody else at our firm will either. Nothing is pending: you didn't apply, and I haven't shared anything about your files with anyone.

FieldEntry
Person and companyThe CEO, for the architecture practice under its legal name
ScopeData licensing, whole company, all channels
Date and words14 October 2026: "Please leave it."
Honored byThe account manager, the document-management team and a CRM flag reading "no licensing outreach"
What we holdThe original email thread, nothing more
Never recordAnything about the practice's client contracts beyond the CEO's one line
RevisitOnly if the CEO raises it
OwnerThe channel partnerships manager, at the quarterly review

The CEO's concern is the same one SourceX's screening guidance raises: client-owned material is usually not a fit. The close does not need to say so. It only needs to stop.

What closing changes on the program side

Closing a thread gives up nothing that existed. A lead, a meeting or a signed agreement alone earns no payable reward; the default reward, the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap (the USD 50,000 floor applies once per referred company, to its first qualifying transaction), depends on a completed, paid transaction and the payment conditions in the terms.

The 90-day attribution window is the partner's clock, never the company's. Credit goes to the first valid introduction of a new company within that window when the company submits a verified application, and the terms say the window does not extend because contact protection under the partner agreement continues. If a company comes back on its own months later, attribution is decided from dated records, including written introduction evidence, so keep the original thread rather than a hope. If the company had already applied and now wants out, that conversation is between the company and SourceX: the terms let SourceX communicate directly with a referred company, and SourceX's process page says a deal that does not close ends in a no-deal notice, with declined data deleted. Before applying, a company shares only answers to a few questions, with no files. The terms also count any earlier lead, account or email correspondence between SourceX and a company as an existing relationship, so a company that once wrote to SourceX directly is reviewed as a duplicate whoever introduces it later.

The only next step belongs to the company

After a stop request or an objection, there is no next step for you. After a "not now" that came with a date, one note on that date is fine, as set out in the guide on following up after a company asks for more time; the live guide on handling a "not now" helps tell the two apart. After silence, the stage limits in when to stop following up decide when the final note goes. A short confirmation that you have stopped is welcome, as long as it asks for nothing.

Four things never appear in a close: a "last chance", a window that is closing, the partner link sent again, or "just checking you saw this". If the first message was built well, as in the evidence-and-questions format, the close is short because nothing needs undoing.

When the template needs adjusting

  • Long relationships. With a client of ten years, say it in person or on a call, then write the record.
  • Jurisdiction. The ICO's guidance is for the UK and CAN-SPAM is US law; the EU, Canada and others have their own rules, so take advice where you refer.
  • Small firms. A spreadsheet works, but it has to reach every colleague who might mention the topic.
  • Scope. A licensing suppression should not stop ordinary client service; write the scope precisely so nobody over-applies it.
  • No evidence yet. No data on how closes affect later relationships has been published. To measure it, note for each closed thread whether the client relationship continued at 6 and 12 months: renewals, new work, other introductions.

Method note. The template applies the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), SourceX's screening and process pages, the FTC's CAN-SPAM guide and the ICO's direct marketing guidance, all checked on 26 October 2026. The architecture practice and its messages are Illustrative. Nothing here is legal advice. For tone in earlier messages, see following up with a company owner and the guides library.

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.

With closed threads logged and your suppression list shared across the firm, register for a partner link for the next company that wants the conversation, check it against who qualifies and keep the attribution rules in the program terms to hand.

  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

Should the closing message mention the 90-day attribution window?

No. The window is the partner's clock for credit, and it does not extend however the thread ends. Putting it in a close turns your deadline into pressure on the company, which is exactly what the close exists to remove.

Is it better to delete a contact who asked us to stop, or keep them on a list?

UK regulator guidance says suppression is usually preferable to erasure after an objection: keep just enough to honor it and mark it clearly, so a later import or a colleague cannot reach the person by mistake. Take advice for other jurisdictions.

Can we check back in six months after a company said no?

Not after a stop request or an objection; the UK regulator says you cannot contact someone later to ask whether they have changed their mind. After a plain 'not now' with a date they named, one note on that date is reasonable.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/how-it-works
  4. ftc.gov/business-guidance/resources/can-spam-act-com…
  5. ico.org.uk/for-organisations/direct-marketing-and-priva…

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