How to protect member trust when applications are declined: a member support response playbook that prepares members before anyone applies, asks each CEO at the yes how to follow up and answers a no without relaying it

Short answer

Protect member trust before anyone applies. Every notice should say that the association cannot tell a member it qualifies, that SourceX reviews and the member's CEO decides, and that a no can come at several stages for reasons the association cannot see. When a member reports a decline, reply once, keep the outcome private, point to SourceX's published reasons, offer a way to give feedback, and never argue the member's case with SourceX.

Visual briefFull-size diagram
Four storyboard panels: before, a notice saying nobody is promised a yes; at the yes, a speech bubble asking the CEO how to follow up; if declined, an envelope going to the CEO while a dashed line to the association is crossed out; afterwards, one reply and a chart with no member names.
The four moments follow the member support response playbook on this page; the panels show a sequence, not any real member's case.

A decline stings more when it arrives after a recommendation from a trusted body. The member heard about SourceX because the association mentioned it, perhaps in its newsletter or at an event, and a no can read as the association's judgment, or worse, as the association having spent the member's time for its own benefit. Most of what decides how that feels was written months earlier, in the first notice.

Why a decline lands on the association's desk

Three things make a member blame the messenger. The first is implied endorsement: if the notice sounded like a recommendation, the decline sounds like the association was wrong. The second is the incentive: a member who later learns the association could have been paid may wonder whose interest the notice served, which is why the newsletter disclosure guide puts the reward in the notice itself. The third is surprise: a member that expected a size check and got a no on something else feels misled.

SourceX's own pages give the association honest language for that third point. Its screening page calls itself screening guidance rather than an eligibility promise and says requirements follow SourceX's current data needs. Its process page says SourceX weighs ten fit signals, not just company size, and that qualifying does not guarantee an offer. A notice that says this plainly before anyone applies has already done most of the work this page describes.

What the association sees, and what stays with the member

What the association can know depends on how the member reached SourceX, and in neither case does it include the reasons for a decline. The terms say partners never receive access to applicant documents, and the partner agreement gives a partner only what it reasonably needs to follow its own referral, in generic stages or reference codes.

How the member reached SourceXWhat the association seesWhat it does with it
The member applied on its own, with no partnerNothing, unless the member tells itWaits to be told; never asks members whether they applied
The association introduced the member as a registered partnerGeneric stages or reference codes for that referral, never applicant documentsTreats any stage as the member's private business and acts on it only as the CEO asked at the yes
The member already had contact with SourceX before the association's introductionThat the introduction is not creditedSays nothing to the member about it: the member was not declined, the association simply earns no credit

Four kinds of no, and one that is not a no

Members say "we were turned down" about very different events, and the association's reply should not depend on knowing which one. Still, the association's own staff should understand the difference, because the last row is a no only for the association.

What happenedWhere the outcome sitsWhat the association says if the member raises it
The member decided not to take partWith the member; it was its own choiceThanks, and confirms the member will not hear about it again unless it asks
SourceX did not take the application forward after the fit checkBetween SourceX and the companyThe reply below, and the published reasons a referral can be declined
SourceX's review found a rights or program-fit problemBetween SourceX and the companyThe same reply; the reasons a well-documented company can still be declined explain why paperwork alone does not decide
A deal did not closeSourceX's no-deal notice, to the companyThe same reply; the association does not ask what was offered
The association's introduction was a duplicateWith the association alone, because nothing happened to the memberNothing: the credit question is the association's, not the member's

The member support response playbook

The playbook has six moments, and the first two happen before any decline exists. The reply lines below are written to be used as they are or adapted, and none of them asks the member for anything.

Complaint handling has its own published guidance. ISO 10002, in our paraphrase of ISO's description, covers complaints about an organization's products and services from planning through improvement, for organizations of any type or size, and leaves out disputes referred outside the organization. The line is a useful one here: a complaint about how the association described the program is the association's to handle and learn from; a disagreement with SourceX's decision belongs to the member and SourceX.

  • When a member reports a decline. "Thank you for telling us. The decision and its reasons are between you and SourceX, and we will not pass this on. If anything we said about the program set the wrong expectation, we would like to hear it."
  • When a member asks the association to intervene. "We cannot speak for your company or ask SourceX to revisit an application. If you want to pursue it, your CEO can contact SourceX directly."
  • When a member is angry with the association. "You heard about this from us, so your view of how we described it matters. Here is how to tell us, and here is who reads it."
  • When a member asks whether it will be eligible next time. "SourceX says a company that does not fit one program may fit another later. We cannot predict whether that applies to you."
MomentThe association doesThe association never doesWhat it records
Before any noticeStates that it cannot say who qualifies, that SourceX reviews and each member's CEO decides, that a no can come at several stages, and whether it could be paidCalls members good candidates, lists sectors as likely fits or calls SourceX its partner without written authorizationThe approved notice text and date
At a CEO's yes, if the association introducesAsks how the CEO wants to hear from it after the introduction: never, only if the CEO raises it, or a single check-inPromises progress, or tells the member a signature or an estimate makes a deal certainThe CEO's dated yes and stated contact preference
When a member asks "are we a fit?"Points to the published screening page and the company's own applicationGives a yes, a likely or a probablyNothing about the member
When a member reports a declineSends one reply, keeps it private, offers the feedback routeAsks for the reason, contacts SourceX, compares the member with othersThat a reply was sent, with no reason attached
When a partner stage changesFollows the contact preference the CEO gave at the yesReaches out first when the CEO asked not to be contactedNothing beyond the stage itself
When reporting to the boardCounts notices sent, replies, complaints and opt-outsNames members, applicants or declinesTotals only

An education path for members who never apply

Some members will want to understand the idea without applying, and a short education session serves them without creating a single decline. It explains what SourceX looks for in its own published words, that a no can come at the fit check, in review or at closing, that the member's CEO decides, and that the association does not see outcomes. It sells nothing and collects nothing. The member education brief gives the association a sentence-by-sentence source map for that session, and the member list guide keeps the invitation itself opt-in.

A small pilot with a decline route and a feedback route

Start with members who ask to hear more, not with the whole roster. Give every message two exits: a one-line way to stop hearing about the program, and a feedback route that goes to a named person at the association and can be used anonymously. After 90 days, read four numbers: complaints about how the association described the program, members who used the stop line, members who said the information helped whatever the outcome, and members who would want the association to keep offering it. A pilot where declined members still say the association was straight with them is working; a pilot where they feel steered is not, whatever the number of introductions. SourceX has not published acceptance or decline rates, and none are given here; the pilot's numbers are the association's own.

If the association is a registered partner, it signs the SourceX Channel Partner Agreement before introducing anyone. Any reward is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, paid by SourceX separately, with nothing taken from the member's compensation.

Where the playbook can still fail

  • The first notice was already written. If earlier messages implied that members would qualify, the playbook cannot undo it. Send a corrected notice before the next one.
  • Silence can feel like indifference. A member that hears nothing after a decline may decide the association did not care. The contact preference asked at the yes is the guard against that.
  • Small networks talk. In a tight trade community, members compare notes. The association cannot stop that, but it can make sure none of the information came from its own staff.
  • The incentive shadow. Even a disclosed reward can make a declined member wonder. An association that never registers, leaving members to apply on their own, removes the question; whether a registered partner can turn its reward down is not settled in the published terms and goes to SourceX in writing.
  • Program changes. SourceX's criteria follow its current programs, so a reply that was accurate last quarter may need rechecking against the screening 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.

Before the association's next notice goes out, register if it will introduce members, quote the screening facts on who qualifies rather than paraphrasing a promise, and keep the program terms beside the response playbook.

  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 association ask SourceX to reconsider a member's application?

No. The application and its outcome are between the member and SourceX, and an association arguing the case would be speaking for a company it does not control. If the member wants to pursue it, the member's CEO contacts SourceX directly.

Will the association learn why a member was declined?

Usually not. A member that applied on its own tells the association only what it chooses to. If the association introduced the member, the partner agreement limits what it receives to generic stages or reference codes for tracking its own referral, and the terms rule out access to applicant documents.

Does a decline mean the member can never be considered again?

Not necessarily. SourceX's screening page says programs differ and a company that does not fit one may fit another later. The association can say that once, without predicting that it will happen.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. refer.sourcex.si/who-qualifies
  4. sourcex.si/how-it-works
  5. iso.org/standard/71580.html

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