# Community data referral moderation: routing guide | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-community-moderator-should-route-a-question-privately
Last updated: 2026-11-05

Move a thread to a private reply when answering it in public would mean discussing one identifiable company: whether it fits, what its records hold, what its contracts allow or what it might be paid. Keep general questions about how the program works in the open, where the answer helps every member and anyone can check it against SourceX's published pages. Remove first and message second when a post exposes something no shared space should hold. A private reply is only a channel: it gives the member routes and asks for nothing.

Members post the way they talk, with company names, headcounts and the occasional screenshot. Some are registered partners who could be paid for an introduction, and sometimes the moderator is one of them. A routing rule agreed in advance keeps those facts from colliding in one thread.

## Why a thread answer becomes a statement about a company

A thread outlives the conversation: it is searchable, quotable and readable by every member, including registered partners, competitors and, in an open community, anyone with a browser. An answer posted under "we have about 140 people and twelve years of claim files, are we a fit?" stops being advice to one person and becomes the community's public verdict on a named company.

Nobody in the community can give that verdict. SourceX checks relevance to its current data needs during its own review, and its screening page counts two things among the usual misfits: material owned by a company's clients, and any introduction its decision maker never knew about. The member who posted may not even be the person who decides: under the program, the company's CEO opens a licensing discussion and signs for it. An enthusiastic reply from a moderator can therefore mislead three people at once: the poster, the poster's CEO and every reader who assumes the community has checked something.

## Three tests for every post that mentions data referrals

Run each post through three questions, in order. Each takes seconds once moderators have used it a few times.

1. **Is this about the program or about one company?** "How is the reward worked out?" is about the program. "Would our dispatch logs count?" is about one company, even when the company is not named.
2. **What does the post itself carry?** Record extracts, screenshots, customer names, contract wording, another member's details or one deal's figures should not sit in a shared space, whatever the question.
3. **Who is answering, and could they be paid?** A staff member of a registered association, or a member who is a registered partner, has an interest that readers are entitled to see next to the answer.

A post that clears all three gets a public answer. Failing the first moves the company-specific part to a private reply. Failing the second means hiding or editing the post before anything else. Failing the third means the answer stays public but carries a disclosure, or passes to a moderator who cannot be paid.

## The public-private question routing guide

Ten kinds of thread cover most of what a data-referral category produces. The examples are Illustrative.

| Thread type | Example post | Route | The moderator's move |
|---|---|---|---|
| 1. How the program works | "Is the reward a share of what SourceX earns?" | Public | Answer from the terms: it is the greater of $50,000 plus 5% and 15% of what SourceX actually pays the company, with no cap, and never a share of SourceX's fees |
| 2. Criteria in general | "What size of company does SourceX look for?" | Public | Quote the screening rule as published and add no opinion about anyone |
| 3. One company's fit | "We peaked at about 70 full-time staff; are we in?" | Private reply | Explain that nobody here can say, give the two routes, ask no follow-up questions |
| 4. One deal's money | "What would eight years of dispatch logs fetch?" | Private reply | Typical payouts are not published; pricing is a matter between SourceX and the company |
| 5. Another member nominated | "Someone should introduce the distributor in our chapter" | Hide, then message the poster | The community never volunteers a member; only that company's CEO can raise its hand |
| 6. Records posted | A screenshot of a ticket export | Remove at once, then message | Nothing is opened or kept; SourceX's first step needs no files |
| 7. Partner link, no disclosure | "Use my link, it's the quickest way in" | Edit or hide until disclosed | Ask for the disclosure and remove the speed claim; a click decides nothing |
| 8. Partner offering to message the poster | "DM me and I'll get you introduced" | Hide the offer | The poster chooses whether to ask anyone; nobody claims a poster |
| 9. A complaint | "Our application went quiet" | Acknowledge publicly, continue privately | The community does not speak for SourceX; point the member to SourceX directly |
| 10. A completed deal announced | "We licensed our archive, here is what we got" | Private reply to the poster | Note that SourceX's standard deal terms say neither side publicizes the deal, and the member's own agreement governs |

Rows 1 and 2 are where the community earns its value, since one public answer serves every later reader. Rows 5 and 6 are the only ones where speed matters more than wording. Questions about members sharing prices or plans with each other belong to the [antitrust basics for trade associations](/guides/trade-association-antitrust-guidelines), not to this guide.

**Method note.** The ten types come from the kinds of post a referral topic draws in a member community, sorted by the three tests above and SourceX's published terms, screening page, process page and sample partner agreement, read on 2026-10-27. They are a moderation yardstick, not measured frequencies; no figures on community threads have been published.

## A private reply is a channel, not an intake form

The risk in routing privately is that the private channel quietly collects what the community refused to collect in public. Headcounts, system names and record types travel easily in a direct message, and none of them should travel to the moderator. The member can give them to SourceX itself, whose first step is a few questions with no files and no records shared.

A private reply carries five things and nothing else:

- **Why the thread moved.** One sentence: the answer depended on facts about one company.
- **The published rules.** Links to the screening page and the terms, so the member reads them in SourceX's words.
- **Two routes the member can take alone.** Apply to SourceX directly, or have the company's CEO ask the association in writing for an introduction, if the association is registered.
- **The interest, if there is one.** Whether the association or the person replying could be paid, that SourceX funds any reward itself and that none of it comes out of the member's compensation.
- **A way to stop.** One line the member can send to end further messages on the subject.

What it never carries: a request for figures, an estimate, a hint that writing privately moves a company up a queue, or a promise about SourceX's decision. The sample partner agreement gives a partner no authority to share a company's records or personal information and makes the partner an independent contractor who cannot commit SourceX to payouts, so routes are all anyone in the community can offer.

Platform tools make the move easy and the record thin. On Discourse, for example, the moderation guide describes a message option in the flag menu that opens a personal message to the poster instead of filing a flag, and that message stays out of the moderator review queue (our paraphrase). A reply sent that way does not show up in the queue the moderating team works from, so log each move in the moderators' own notes: the date, the thread, the row of the guide, and no company facts.

## When registered partners post in the community

A community with a referral program will have members who could be paid, and the rules for them belong in the pinned note, not in a moderator's memory.

- **Disclose in the post.** Any answer or link from someone who could be paid carries the disclosure in the same post. The [newsletter disclosure guide](/guides/how-to-keep-referral-incentives-transparent-in-a-member-newsletter) sets out what that sentence must say; a forum post needs the same facts beside the link.
- **Offer once, in the open.** A partner may say in the thread that they are registered and that the poster's CEO can ask them for an introduction. Following up by private message on a public question is out.
- **Credit is SourceX's call, not the community's.** Under section 2 of the terms, credit goes to the first valid introduction of a new company within the 90-day window, once that company submits a verified application, and an earlier link click alone does not decide it. Under section 3, a company that already had any lead, account or email correspondence with SourceX is a duplicate and credited to nobody. When two partners in the same community both know a member, only one introduction can be credited, and SourceX settles overlaps like that in duplicate review.
- **No "official partner" claims.** Section 4.5 of the sample agreement bars either side from publicly identifying the other as a partner without written authorization. In an open community, a post calling SourceX "our partner" is public; edit it unless SourceX has authorized the wording in writing.

The pinned note can also say that partners sign the SourceX Channel Partner Agreement before submitting any introduction. For one-to-one etiquette in a smaller group, see the [peer group introductions guide](/guides/peer-group-member-introductions-etiquette).

## Piloting the rules with members who opt in

Do not launch the routing guide across a whole community at once. Open a single data-referrals category, invite members to join it rather than adding them, and pin the three tests and the ten rows at the top. Run it for 60 days with two exits that need nobody's approval: leaving the category, and a one-line decline that stops any private messages on the topic.

Count what tells you whether members are better off: threads answered publicly and threads moved privately, with the row that decided each; members who said a private move felt like being silenced, the main cost of over-routing; partner posts missing a disclosure; complaints about unwanted private messages; and members who used the decline line, checking that nobody messaged them afterwards.

Write the decision rule before the pilot starts: keep the category if complaints stay rare and members describe the public answers as useful; tighten the partner rules if unwanted messages appear; close the category if members say they felt watched or steered. SourceX has published no figures on member communities, so every count here is the community's own. Readers who want a ready list to share instead of a moderated space can start from the [professional community checklist guide](/guides/how-to-share-a-company-referral-checklist-in-a-professional-community).

## Two threads, routed (Illustrative)

Illustrative. Invented posts and members; no outcome is implied.

**Thread A, a mixed question.** A member writes: "Has anyone licensed operating data? We're a freight broker with years of dispatch records. Would that work, and what does SourceX pay?" The moderator answers the general part in the thread, quoting the screening rule and the reward basis and noting that typical payouts are not published, then moves the company-specific part to a private reply with the five elements above. If the member's CEO later applies directly, the community plays no part, and the log holds one line with no company details.

**Thread B, an eager partner.** A member who is a registered partner posts: "SourceX pays members well. DM me and I'll fast-track you." The moderator hides it and tells the partner privately that nobody can make the pay claim, that there is no fast track and that offers belong in the open with a disclosure. The partner reposts: "I'm a registered SourceX partner and could be paid if a company I introduce completes a paid licensing deal. If your CEO wants an introduction, they can ask me here or apply directly." The second post stays.

## Where routing rules backfire

- **Over-routing.** A moderator who moves everything private empties the public record, and members can no longer check answers against each other. Rows 1 and 2 should almost never leave the thread.
- **Shadow advice.** Private messages between members sit outside the moderators' view. The rules can ask partners to stay in the open; they cannot see everything.
- **The moderator who could be paid.** Routing questions into a private channel run by the one person with a reward at stake looks like steering. Separate the roles where the community is large enough.
- **Rules that drift.** SourceX publishes new versions of its terms from time to time; check the pinned note against the current version before each review.
- **A different question entirely.** If the community is weighing whether its own posts could be licensed, that is a separate decision about [licensing forum and community content](https://sourcex.si/ai-data/text/forum-community-content-licensing), not a referral.

More playbooks for associations and member networks sit in the [guides library](/guides), and the [endorsement policy question](/questions/association-endorsement-policy-vendor) helps a board keep the community's tone educational.

## 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 category opens, decide whether the association itself will [register as a partner](/register) and say so in the pinned note, copy the screening rules for rows 1 and 2 from [who qualifies](/who-qualifies), and link the [program terms](/terms) so every public answer can point to them.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://meta.discourse.org/t/discourse-moderation-guide-part-3-managing-content/406266
- https://sourcex.si/how-it-works
