This page is for the operations lead whose firm introduces companies to SourceX and who decides what gets sent when a referral stops moving. The stalled-or-closed rules say whether a quiet record is still open; the next-step owner register finds who holds the step. This page governs the messages themselves.
A repeat, defined, and what it buys
A repeat is a message to the same recipient, asking the same question, with nothing new in it. "Just checking in", "bumping this to the top of your inbox", a reminder whose only new content is the date, a copy of the same note sent to someone senior at the company, and the next step of an automated sequence are all repeats.
These are not repeats: a message to a different and correct recipient, a message that opens with a new fact, a reminder the recipient asked for on a date they chose, a resend after a bounce, and the receipt confirmation a formal notice clause requires. A single reminder date set when a question was first asked, as on a board of questions waiting on the company, belongs to that question; a second reminder is a repeat.
A repeat buys nothing on paper. Section 7.7 of the unsigned sample Channel Partner Agreement reads: "A website update, dashboard edit, unanswered message or one-time exception does not amend this Agreement or waive another obligation." Credit does not move either: under section 2 of the terms the 90-day window does not extend, and SourceX may talk to the company directly without affecting a valid attribution. What a repeat does change is the CEO's view of you. A no said politely tends to become a firmer one.
Three kinds of escalation, and the one to switch off
Atlassian's guide to escalation policies sorts escalation into three types: hierarchical, by seniority; functional, by expertise; and automatic, set off by a rule such as an alert nobody acknowledged in time (our paraphrase). A referral uses the first two, each in its own place, and should never use the third on a person outside your firm.
- Hierarchical, inside your firm only. Relationship owner, then operations lead, then the firm's principal. At the company there is no rung above the CEO. Writing to a board member, an investor or a deputy to move the CEO is going around the decision-maker, not escalating.
- Functional, across to whoever can answer. The CEO for the company's own step, SourceX for your referral's status or your reward, and the dispute route for a decision you contest.
- Automatic, off. A sequence that resends on silence is the repeat this page exists to prevent. Keep automation for internal reminders to your own colleagues.
The message ledger every escalation is sent from
Every message about a referral starts from one line in a ledger. The line exists before the message does.
| Field | What goes in it | Rule |
|---|---|---|
| Question ID | A short code such as Q3 | One question per line |
| Recipient | One person or one route | The CEO, the relationship owner, the operations lead, SourceX's partner contact, or the dispute route |
| Question | One sentence | Something this recipient can actually answer |
| Threshold | The dated event that justified sending | No threshold, no message |
| Carries | The new fact or the evidence attached | A reference code, a dashboard label with the date you read it, or the CEO's own words shared with permission |
| Sent and answered | Two dates | "None" is an allowed answer |
| State | Open, answered or closed unanswered | One open line per recipient per topic |
Before anything goes out, check for an open line with the same recipient on the same topic. If one exists, do not send. If you have a genuinely new fact, close the old line and open a new one whose message states that fact in its first sentence. The ledger never holds the company's files, the CEO's private reasons or anything about another partner; the agreement gives a partner no authority to share a company's records in any case (section 4.2).
The escalation threshold and contact map
Each row names one stuck question, the event that justifies one message about it, the only person who receives that message, and what happens if nothing comes back.
| Stuck question | Threshold for one message | The one contact | What the message carries | If nothing comes back |
|---|---|---|---|---|
| 1. A step at your firm is overdue | Its due date has passed | The operations lead | The line, its owner and its date | Reassigned the same day; nobody outside the firm hears about it |
| 2. Nobody at the company is taking its next step | The date the CEO gave has passed, or no holder was ever named | The CEO, from the relationship owner | One question: who will take the step, or would the company rather pause | The silence stands; outreach stops, and the record closes on day 90 if no application arrives |
| 3. Did the introduction reach SourceX? | Two dashboard readings on different days show no record of an introduction you submitted | SourceX, about your own referral | Submission date and method, the company's legal name, your reference | A second message only with a new fact, such as a portal confirmation |
| 4. The CEO says SourceX has not been in touch | The CEO tells you so | The CEO, with SourceX's own starting point | SourceX's process begins with the company's own short application; nothing about the company goes to SourceX from you | Nothing more to send; the step is the company's |
| 5. The status has not moved for weeks | None: elapsed time alone is never a threshold | Nobody | Nothing to send | Read the dashboard on your set day |
| 6. Not credited, and you disagree | A decision on the dashboard, and dated introduction evidence in your file | The dispute route in section 7 of the terms | The referral details and all supporting evidence, in one message | SourceX reviews and communicates its decision; your signed agreement sets what follows |
| 7. The reward reads Paid and nothing has arrived | Paid displayed, funds not received | SourceX, about your own reward | Your reference, the reading date and the payment details on file | A second message only with a new fact, such as your bank's confirmation |
| 8. The reward figure does not match your arithmetic | A recorded reduction, or a figure you cannot reconcile | SourceX, asking for an explanation of your own reward | Your calculation: the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, with no cap | If the explanation does not settle it, row 6 |
| 9. Another partner says they introduced the company | You learn of the overlap | Neither the company nor the other partner | Your dated evidence, kept ready | Only one introduction can be credited, and SourceX settles overlaps in duplicate review; act through row 6 only if a decision goes against you |
Row 5 deserves its own note. SourceX's company process page says commercial feedback "usually takes 7–14 days; that is a target, not a promise". That target belongs to a company that has reached that step of its own deal. A partner cannot see when the step begins, so it is never a deadline to escalate against. Thresholds come from events you can see: your own dates, dates the CEO gave, and dashboard labels you read and dated. Partners follow their referral through generic stages or reference codes (section 4.6 of the agreement), and no amount of asking makes those stages more detailed.
Before row 7, check your own side. SourceX's rewards page describes Processing as a payout under way once the required tax and payment details have been completed. An Approved reward that has not reached Processing often means your own details are missing.
Never on the map: the company's board members, its investors, a deputy approached behind the CEO's back, the company's staff, SourceX asked to carry a message to the company, and another partner's clients.
Who sends what
Three people share the work, and each sends only one kind of message.
- The relationship owner is the only person who writes to the CEO. One question per threshold, with an easy way to pause or say no. The answer-led follow-up library helps when the CEO has asked something.
- The partner of record, who signed the Channel Partner Agreement before submitting the introduction, is the only person who writes to SourceX about the referral or the reward.
- The operations lead keeps the ledger, approves each new line and closes lines that have run their course.
For disputes, the sample agreement's Schedule A lets a partner ask for an explanation of its own reward or dispute a decision with supporting evidence, and says SourceX provides reference codes, status information and redacted calculations without disclosing other partners' records (paragraph 8). The agreement also sets thirty days of written notice and discussion before arbitration (section 7.4). Read your signed agreement with your own counsel before relying on either; this page is not legal advice. Disputes between investors over who introduced a company follow their own escalation path.
One referral, handled twice (Illustrative)
Illustrative. One generic company and invented days, shown once with repeats and once with the map.
| Day | Repeat version | Escalation version |
|---|---|---|
| 0 | Introduction submitted | Introduction submitted |
| 14 | "Just checking in" to the CEO | Nothing: the CEO said the COO would apply by day 21 |
| 21 | A second check-in to the CEO | The date passes; one question to the CEO, row 2 |
| 23 | A note to the CFO asking her to nudge the CEO | The CEO names the COO, who confirms |
| 28 | A third check-in, copying a board member | The company applies |
| 35 | A request to SourceX to remind the company | Nothing to send: the dashboard shows the application |
| 60 | Two emails to SourceX asking why the company is under duplicate review | Nothing to send: review is SourceX's work, row 5 |
| 75 | A third email to SourceX | The dashboard shows not credited; one dispute message with the dated introduction record, row 6 |
The repeat version sent eight messages, none with a new fact, and two of them went around the CEO. The escalation version sent two, each to a different recipient and each justified by a dated event. SourceX's decision on the dispute is the same kind of event in both versions; the difference is what the CEO thinks of your firm afterward.
Closing questions instead of repeating them
A ledger line ends in one of two ways: answered, or closed unanswered once the next threshold passes, such as day 90 for a company that never applied. Closed-unanswered lines stay in the ledger as a record that you asked once; they are never sent again.
Once a month, count three things: repeats sent (the target is zero), lines closed unanswered, and messages by contact type. No benchmarks have been published for any of them, so compare your own months with each other. Keep messages that evidence an introduction or a dispute, which the agreement's return-or-delete clause allows for reward accounting and dispute evidence (section 4.4); other notes follow your firm's retention policy.
Where a no-repeat rule bends
- A bounce or a wrong address. Resend; the first message never arrived.
- Formal notices. Under the sample agreement, email notice takes effect on acknowledged receipt, and an automated send event alone is not acknowledgment (section 7.5). Confirming receipt of a notice is procedure, not a repeat.
- A reminder the CEO asked for. A message on the date the CEO chose is requested, not repeated.
- Many introducers. A firm whose referrals come through many people may also need one escalation owner for the whole network.
- Unmeasured effect. Whether the map shortens anything or protects relationships is untested. Log every line for two quarters before judging it, and see when to stop following up on an inactive referral for the point where asking ends altogether. Dashboard stages are explained on where a partner sees the current stage, and more operations guides sit in 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.
Set up the ledger before the next introduction leaves your firm: register as a partner so rows 3, 6, 7 and 8 have a signed agreement behind them, screen each company against who qualifies, and keep section 7 of the program terms and the reward statuses beside the map.