Which claims need a correction, and which only need a calmer tone
Enthusiasm is not the problem; false facts are. Sort every sentence of the original into one of two piles before you write anything.
| Claim in the original | Type | Correct it? | Why |
|---|---|---|---|
| "Any business qualifies" | Eligibility overstated | Yes | The program looks for a company that peaked at 50+ full-time employees, can document its operating history, holds the rights to license and has an authorized contact |
| "Six figures" or any amount | Payout invented | Yes | No typical payout is published; a company's payout is set in its own signed agreement after review |
| "Paid within weeks" | Timing invented | Yes | Payment follows the company's agreement; partner rewards have their own conditions in the terms |
| "AI labs will buy your files" | Counterparty wrong | Yes | The company licenses its data to SourceX, which acts as its counterparty from agreement through delivery and payment |
| "I've partnered with SourceX" with no mention of a reward | Disclosure missing | Yes | A paid recommendation needs the connection stated plainly |
| "I get a share of your deal" | Reward mechanics wrong | Yes | SourceX pays the reward separately; it never comes out of the company's payout |
| "Don't miss this window" | Invented urgency | Yes | Real urgency is a documented event such as a system shutdown, not a feeling |
| "This is the most interesting program I've seen this year" | Opinion, clearly the author's | No | A personal view with no false fact in it; leave it or tone it down |
If a sentence would mislead a reasonable reader about who qualifies, what anyone is paid, when, by whom, or what the author earns, it goes in the correction. The live page on discussing a partnership without promising a payout covers how to avoid these claims next time; this page is about after they are out. Related outreach guidance is gathered in the guides hub.
One correction, written on the same company facts (Illustrative)
Illustrative. Generic people and companies, invented facts. A consultant in your partner network emailed 40 owner clients and posted the same text on a social network and in a regional business owners' chat community:
Big news for business owners: AI labs are paying six figures for old company emails and files, and any business qualifies. I've partnered with SourceX, so message me and you could be paid within weeks. Don't miss this window.
One recipient replied the same afternoon: the CEO of a 180-person regional engineering firm with 22 years of project files, who asked, "What would we get?"
The public correction, posted or sent in every channel the original reached:
Correction to my message of October 20. I overstated three things and left one out. Not every business fits: SourceX screens for 50+ full-time employees at peak, years of the company's own records, the rights to license them and a CEO who wants the conversation. Nobody can promise an amount or a timeline: any payout is set in the company's own agreement with SourceX after it reviews the records. The company licenses its data to SourceX, which is its counterparty, not to an AI lab directly. And I should have said that SourceX may pay me a referral reward if a company I introduce completes a deal; SourceX pays it separately, and it never comes out of the company's payout. The program terms are at refer.sourcex.si/terms.
The private note to the engineering firm's CEO, tied to the facts the CEO actually shared:
Thanks for replying, and I owe you a correction: my email made this sound simpler and more certain than it is. Your 22 years of project files and your 180 people are why I thought of you, and they line up with the published screening profile on history and size. Whether SourceX can use the files, and what it would pay, depends on its review and its current programs; nobody can name a figure before that, me included. SourceX may pay me a referral reward if a deal completes, separately from anything you would receive. If you would still like an introduction, I will make it. If not, this is the last you will hear from me about it.
| Wrong claim | What the correction says instead |
|---|---|
| Any business qualifies | The four screening facts, stated plainly |
| Six figures | No amount; payout set in the company's own agreement after review |
| Paid within weeks | No timeline |
| AI labs buy the files | The company licenses to SourceX, its counterparty |
| No reward mentioned | Reward disclosed, with who pays and that nothing is deducted |
| Don't miss this window | Dropped; nothing replaces it |
The correction is not an apology tour. It names each error once, gives the accurate version and points to the terms. The private note does the same in the CEO's own facts and ends with an easy way out.
Put the correction where the claim traveled
A correction only works in the place the claim was read. Each channel has its own trap.
| Channel | Where the correction goes | Edit, delete or add | Who else to tell | Done when |
|---|---|---|---|---|
| Email to people outside your firm | A new email to the same recipients, subject starting "Correction:" | Add; Outlook's recall works only when sender and recipient share one organization's Microsoft 365 or Exchange accounts, and not for outside or personal addresses | Anyone you know forwarded it | Every original recipient has the correction |
| Email inside your firm | The same correction email | Add, even if you tried a recall, because a recall can fail | Team leads who passed it on | The correction is in every inbox the original reached |
| Social post | The top of the original post, if the platform allows editing, plus a short correction post if it was reshared | Edit and add; delete only if editing is impossible, and say what was removed | People who reshared it | The original and every reshare you can reach point to the fix |
| Chat community | A reply in the original thread and a new message in the main channel | Edit the original to point to the correction | The moderators | The correction is visible without scrolling back |
| Newsletter | A correction box at the top of the next issue and a dated note on the web version | Add; fix the archive copy | The editor of any newsletter that reprinted it | The archive shows the note |
| Deck, PDF or one-pager | A replacement file at the same link, with a version date on the cover | Replace | Everyone who received the old file | The old version is withdrawn |
| Listing or web page | The corrected text with an "Updated" date | Edit | No one else; the page is yours | The page matches the terms |
A correction tucked into a comment under a post is easy to miss, so put it in the post itself. For newsletters that carry referral links, the live guide on preparing a referral link for an association newsletter shows what a clean item looks like.
The first-day correction checklist
- Save the original as sent, with its date and audience, for your own log.
- List every copy: recipients, forwards, reposts, threads, the newsletter archive.
- Sort each claim with the table above: correct, or tone only.
- Write one correction text, with the accurate terms and a link to them.
- Publish it in every channel, at least as visibly as the original.
- Ask everyone who forwarded the original to forward the correction.
- Send a private note to any company that replied or was introduced on the strength of the original.
- If a company has already applied, tell your SourceX contact what it was told, so the review starts from accurate expectations.
- Record what you corrected, where and when.
- Decide whether the author's next posts about SourceX need your approval before they go out.
Why the person who runs the channel owns the fix
Whoever runs a partner channel is the one able to find every copy and get the correction out. The FTC's guidance points the same way. Its endorsement FAQ says there is no one-size-fits-all standard for monitoring endorsers, that pre-approving posts may be the better route where regular monitoring is too much, and that monitoring should run through a contract and for a reasonable period after it. It also says anyone who plays a role in creating or spreading endorsements they know or should know are deceptive could be liable. That is the FTC's general guidance, not a ruling on any program; ask your own counsel how it applies to you, and see the referral fee disclosure question for professional rules that can add to it.
In practice, a channel manager needs three habits: the accurate terms in one place partners can copy from, a correction text ready before it is needed, and a rule for when posts need approval.
Say what SourceX does and what you earn, accurately this time
The opportunity, in one sentence: companies license their own business data to SourceX for AI training and evaluation and are paid by SourceX, which acts as their counterparty from agreement through delivery and payment. Any eligibility line in a corrected message rests on these facts: a full-time workforce that has reached 50 or more at its peak, contractors not included; an operating history with documentation behind it; rights to license; a CEO who wants the conversation; and 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. SourceX's screening page calls itself guidance rather than a guarantee of eligibility, and it does not usually see a fit in an introduction the decision maker knows nothing about.
The incentive, in one sentence: SourceX may pay the partner a reward of the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, on a referred company's first qualifying transaction, with further qualifying transactions first agreed within 12 months paying 15%; it is paid separately and never deducted from the company's payout. A lead, meeting or signed agreement alone triggers nothing; the reward becomes payable only once the conditions in the terms are met. Partners sign the SourceX Channel Partner Agreement before submitting introductions. The live guide on how to talk to companies about data and the test of the maximum-payout headline show why a figure in the first line misleads more readers than it persuades.
A private note for anyone who already replied
People who responded to the original deserve more than a public correction. Write to each one individually, restate the reason you thought of their company in its own facts, give the accurate terms, disclose the reward, and offer one choice: an introduction now, or nothing further. No deadline, no follow-up sequence. If they choose the introduction, it goes ahead on accurate expectations; if they say nothing, leave it there.
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.
Once the correction is out and any company that replied has chosen to continue, register for a partner link if you have not, check the company against who qualifies and keep the program terms as the single source your partners copy from.