For business owners and launch teams: Super Admins handle setup, billing, and permissions; Admins manage users and referrals; BDRs recruit and support partners. Launch in five days with role-specific practice. Referrers participate in tests and submit their own referrals.
Build a recognizable company profile, a reliable response promise, and a clear bonus rule. Choose a payment path supported by your plan. Checkpoint: the setup is ready or every verification/funding requirement has an owner and next check; Reactor Pay is not required for a Starter launch.
Understand the complete referral journey, define what a useful referral looks like, and prepare for a consultation and plan selection.
Referral Reactor has four permission roles. Referrer: submits referrals and views their own status. BDR: recruits referrers, manages invitation codes, and submits referrals for their referrers. Admin: views all referrals and manages users. Super Admin: has full access, including organization settings, billing, and permissions. Owner, team leader, field technician, customer, relationship manager, and business-stage personas describe people or responsibilities; they do not grant app access. Use the role assigned in the active organization. Course audience labels organize training and do not change permissions.
Practice only the actions available to your assigned role and plan. For a task outside your access, prepare the information and hand it to the authorized Admin or Super Admin. Referrers are not required to configure organization payments or send a payout to complete their learning; BDRs are not assumed to have organization-wide administration access.
You want referrals to become dependable work without becoming the person who chases every update. Start with a promise your office can keep: clear acceptance criteria, a named responder, and visible follow-through.
A referral program works best when the partner can see that someone received their lead, acted on it, and followed through. The overview shows one connected journey: a person submits a referral, the office acknowledges it, the team communicates inside the referral, and the bonus is recorded with the relationship history.
Understand the complete referral journey, define what a useful referral looks like, and prepare for a consultation and plan selection.
Set up a recognizable company profile with accurate contact information, square and wide logos, and readable brand colors.
A partner is lending you their reputation. A recognizable profile removes the first moment of doubt about who will receive their customer.
Your company profile helps people recognize the business they are joining and referring to. The setup walkthrough distinguishes your personal owner account from the company information, then shows two logo formats and the branding settings you can adjust later. If your account is already created, review the existing profile rather than creating a second company.
Set up a recognizable company profile with accurate contact information, square and wide logos, and readable brand colors.
Learn how to choose the correct bonus recipient, review the amount and payment method, and understand the recipient’s claim process.
Reliable rewards protect partner trust. A simple rule prevents a well-intended bonus from turning into a dispute over who earned it.
A bonus is only a successful experience when the right person receives the intended amount. This video walks through both sides: the business reviews and confirms a bonus, and the partner follows a Dots payout link to choose how to receive it. Dots provides the underlying payout infrastructure for Reactor Pay.
Learn how to choose the correct bonus recipient, review the amount and payment method, and understand the recipient’s claim process.
Set up a practical recordkeeping and review process for bonuses, including payments made through more than one method.
You should be able to explain every reward without reconstructing months of messages. Organize evidence while the transaction is fresh.
The tax documentation video explains why your payment method affects the work your bookkeeper needs to do. It describes tax-form collection and reporting features in the Dots infrastructure used by Reactor Pay, and contrasts those with payments recorded or handled through other methods. Your task is to establish a clear review process, not to assume every filing obligation is already handled.
Set up a practical recordkeeping and review process for bonuses, including payments made through more than one method.
Prepare your approved payment method: Reactor Pay on Pro/Unlimited, or recorded cash/check payments on Starter.
The goal is a dependable reward experience, even when account verification or funding takes longer than your five-day launch.
Choose the bonus workflow supported by your plan. Starter users can launch with manual cash/check payments recorded in Referral Reactor. Pro and Unlimited include Reactor Pay, which requires its own setup, verification, and usable funding.
Prepare your approved payment method: Reactor Pay on Pro/Unlimited, or recorded cash/check payments on Starter.
Starter view: Reactor Pay is included with Pro and Unlimited. A Starter launch can use an approved manual payment workflow. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Give each teammate appropriate access and rehearse the handoff. Checkpoint: the team can demonstrate its assigned tasks, explain the payment distinction, and identify primary and backup owners.
Invite the people who will manage the referral workflow and verify that each can do their assigned work using their own account.
A referral can sit untouched even when several people receive alerts. Ownership tells the team who acts and who covers the gap.
Your launch needs clear ownership as well as access. The setup video says teammates should have separate accounts. The Managing Referrals video also shows that what a person can see depends on their role. Use the permissions displayed in your current account to match access to each teammate’s responsibilities.
Invite the people who will manage the referral workflow and verify that each can do their assigned work using their own account.
Pilot the complete experience with clearly labeled tests and three trusted partners. Checkpoint: verify submission, acknowledgment, conversation, and any approved real bonus; track unresolved steps honestly. Manual cash/check and Reactor Pay paths are both covered.
Run one clearly labeled test referral from submission to acknowledgment and confirm both sides can identify the correct record.
A controlled test protects your first partner experience. Test the whole handoff, not just whether a form accepts a submission.
Practice first with a teammate so you can catch missing information and notification issues before inviting partners. The overview demonstrates a mobile referral with a description, address, and photo, followed by acknowledgment in the office. Use your own controlled test details and make the practice purpose obvious.
Run one clearly labeled test referral from submission to acknowledgment and confirm both sides can identify the correct record.
Focus: Manage & engage Repeat the partner experience with a new group, then give everyone a clear reason to participate. Day 4 checkpoint: Six partners have been invited in total, and your first announcement is sent.
Use what you learned from the first three partners to onboard three more with fewer questions and a consistent experience.
The next three invitations should test an improvement. Growth becomes easier when you remove the friction the first group experienced.
This round tests whether your team can repeat the experience, not just complete it once. Fix the confusion from Day 3 before inviting the next group. Reuse the invitation, notification, conversation, and bonus checks that worked, while keeping the message personal to each partner.
Use what you learned from the first three partners to onboard three more with fewer questions and a consistent experience.
Focus: Scale Bring in your next partners and make the referral routine easier to maintain. Day 5 checkpoint: Nine partners have been invited across three days, your team has practiced the workflow, and you know which follow-ups remain.
Invite the final three partners in your launch group and establish a routine your team can continue after Day 5.
The third group tests whether your process can continue after launch week. Your goal is an active relationship, not a growing count of unanswered invitations.
The target is nine partners invited across three days, with a repeatable experience your team can maintain. This round should use the improvements from Days 3 and 4. The QR-code tutorial also shows how invitation associations can help track where referrers came from when those features are available in your account.
Invite the final three partners in your launch group and establish a routine your team can continue after Day 5.
The relationship loop becomes visible: this test referral has been acknowledged. An acknowledgment is a status update, not proof that work is scheduled. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Copy and complete: We help [customer] with [problem] in [area]. Send [information] through [route]. [Person] responds during [coverage]; [backup] covers absences. We update you by [agreed next checkpoint]. Bonus rule: [condition, amount, approver].
Decide the service area, accepted work, response coverage, bonus approval limit, and weekly review owner. Calculate a test ceiling as approved bonus per person × approved recipients, plus any displayed fees. Nine invitations are a learning target, not a revenue forecast.
Ask a partner: “When you refer someone today, where does the handoff become frustrating?” Use their answer to improve your promise before discussing rewards. Explain how they will know you received the referral and what happens next.
Example referral standard: ‘A homeowner in our service area who needs restoration work, has agreed to be contacted, and has a phone number, job address, and a short description of the problem.’ Adapt this to your business before sharing it with partners.
If urgent jobs arrive outside staffed hours, agree on a separate urgent-contact route. Do not promise that submitting a referral is the same as dispatching a crew.
You can explain the referral journey in your own words, have written your referral standard and response owner, and have completed your consultation and plan selection.
Do not copy the demo’s bonus amount into your program automatically. Choose your own qualifying conditions and affordable bonus amount.
Organization Profile → Branding: the Organization Logo and Wide Logo are separate uploads. Check both formats; this example organization has only its wide logo filled in. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Example description: “We help homeowners recover from water, fire, and mold damage in [service area]. Share the customer’s contact details and a brief description so our team can arrange the next step.” Replace the services and coverage with your actual offering.
Approve one accurate company description and contact owner. Avoid promising availability or services the office cannot deliver. Keep personal login identity separate from company branding.
Open the company experience on your phone and say the business name aloud. Ask a colleague to identify the company, service fit, and contact route without explanation. If any answer is unclear, report the specific field or image to the administrator.
Ask a teammate to look at the company header at normal phone size. Can they recognize the business without zooming? Correct a cramped logo or low-contrast color combination now.
Use a legible logo with space around the lettering. Test the primary background and secondary accent together; a familiar brand color can still make small text difficult to read.
The dashboard shows the correct company, your contact information is accurate, and both logo formats are readable. Your owner account belongs to you, with separate accounts planned for teammates.
Keep personal login details, company branding, subscription billing, and bonus funding distinct. Only set up Reactor Pay if it fits your plan and approved workflow.
Give Bonus begins with Recipient. This test referral lists an Original Referrer and a Marketer; verify who earned the approved bonus before moving to Amount, Method, and Confirm. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Rule card: qualifying event [ ]; recipient [ ]; amount [ ]; approval owner [ ]; payment method [ ]; payment timing [ ]; exceptions contact [ ]. Example: a submitted lead is awaiting review until the agreed qualification condition is confirmed. This example does not establish your company’s reward policy.
Approve what counts as qualified and successful, whether those rewards are cumulative, who may approve an exception, and what evidence is required. Have the appropriate business adviser review your proposed program before making commitments.
Explain the rule before inviting someone: “Here is the event that earns the bonus, who confirms it, and how we will keep you updated.” If two people claim the same referral, pause the bonus and bring the record to the designated decision-maker.
Before any confirmation, say the check aloud: ‘I am paying [referrer] [amount] for [reason] using [method].’ If any part is uncertain, return to the referral details before proceeding.
The Give Bonus flow starts with Recipient, then Amount, Method, and Confirm. A referral may list an Original Referrer and a Marketer. Choose the recipient your approved rule identifies; do not assume the customer or first visible name should be paid.
You can identify the correct recipient, explain the difference between recording an offline payment and sending a Reactor Pay payout, and describe what the recipient does next.
Do not treat a prefilled amount or a successful send as proof that the recipient has received the funds. Check both the payment history and the recipient’s outcome.
Use one reconciliation row per payment: referral | recipient | amount | method | platform entry | independent payment evidence | difference | owner | next check. If a check was entered twice but paid once, flag the discrepancy for correction instead of treating two entries as two payments.
Choose the person responsible for reconciling platform records, bank or offline evidence, and provider reporting. Ask them to flag unresolved differences before the periodic review rather than waiting for year-end.
Record the referral reference, intended recipient, approved amount, method, date, and what remains pending. Route tax questions to the recordkeeping owner; never promise that a partner owes no tax or that every form is automatically filed.
Create a review checklist with these columns: recipient, referral, payment date, amount, payment method, provider record, and unresolved question. Use it to trace one test payment after Day 3.
Keep personal tax forms and payout credentials in the approved secure process. The course teaches the handoff and review discipline; your provider and adviser must confirm the current obligations for your setup.
A recordkeeping owner is named, the review schedule is agreed, and you know which provider tasks are automated and which still need a human review.
A recorded bonus, collected tax form, and completed tax filing are different milestones. Do not use a dollar threshold quoted in a video as a permanent rule for every payment type or year.
Cash and Check are manual payment methods. Enabling or recording them does not transfer money; arrange the actual payment and keep the record accurate. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Payment readiness card: plan [ ]; method [ ]; authorized sender [ ]; approved test ceiling [ ]; usable funds or offline arrangement [ ]; pending requirement [ ]; next check [ ]. An offline test is complete only after the actual payment and its record agree.
Starter supports recorded manual cash/check payments. Reactor Pay is included with Pro and Unlimited. Choose based on the workflow you need; assign an authorized finance owner before any setup or funding. Keep subscription spend separate from the bonus budget.
Confirm the approved method before promising a partner an electronic payout. If setup is pending, say: “Your approved bonus is awaiting [specific step]. [Owner] will check again on [date].” Do not substitute a firm arrival date you cannot substantiate.
Keep one readiness note for your chosen method. Reactor Pay: verification, available funds, remaining action, owner, and date. Manual cash/check: authorized payer, approved amount, planned handoff, recordkeeping owner, and how receipt will be confirmed.
A walkthrough without moving money is useful rehearsal, but label it rehearsal. Do not record a cash or check payment as paid when no payment occurred.
Your payment method and authorized owner are agreed, and either the manual test is arranged or Reactor Pay readiness and remaining requirements are documented.
The video describes an initial verification and funding period of roughly eight days. Treat that as the recording’s estimate, not a guaranteed arrival date; use the status shown in your own account.
The email invitation dialog explains each role. Select the role your teammate needs; the default Referrer selection shown here is not automatically correct for an internal teammate. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Handoff map: New referral → intake owner [ ] / backup [ ]; customer contact → [ ]; partner update → [ ]; bonus approval → [ ]; payment → [ ]. Agree on a daily check and an escalation time when the primary owner is unavailable.
Use the least access needed. The invitation dialog describes BDR as recruiting referrers and managing invitation codes, Admin as viewing all referrals and managing users, and Super Admin as full access including settings and billing. Confirm access through an actual teammate sign-in.
Ask who handles intake, customer contact, partner updates, and bonus approval. Your role should not depend on access to financial credentials or every company referral. Escalate a missing control to your administrator with the organization and task you were attempting.
Make a small responsibility list: ‘New-referral review — [name]; customer follow-up — [name]; partner updates — [name]; bonus approval — [name]; backup — [name].’ Share this internally with the training links in the next lesson.
Settings → First Contact configures which admins receive new-referral and user-sign-up notifications. Ask a Super Admin to review coverage, then test delivery; a configured recipient list is not proof a phone notification arrived.
Each invited teammate can sign in independently, access the tools needed for their role, and name their responsibility and backup.
An invitation sent is not the same as an active, working account. Verify sign-in and access with the person. The dedicated internal-permissions tutorial was marked ‘coming soon’ in the source guide; these steps are a launch checklist, not a walkthrough of an unseen video.
Give Admins and BDRs a shared understanding of the referral lifecycle and check that they can explain the bonus workflow.
Your team needs confidence at the moment a real referral arrives. A brief scenario reveals misunderstandings more effectively than asking whether everyone watched the video.
Sending a video link is the start of training. A short teach-back reveals whether the team knows how to act on it. The overview explains the whole relationship loop; Giving & Receiving Referral Bonuses adds the recipient checks, payment-method distinction, and claim process the office needs to understand.
Give Admins and BDRs a shared understanding of the referral lifecycle and check that they can explain the bonus workflow.
Scenario: A partner submits a water-damage lead, then asks for a reward before the customer has been contacted. Passing answer: acknowledge the referral, assign customer follow-up, explain the agreed qualification rule, and give the partner a next update. Do not promise approval based solely on submission.
Have the intake owner, BDR, and payment owner each demonstrate their part. Treat a missed step as a process fix: name the owner, clarify the rule, and repeat the scenario before expanding invitations.
Play the partner in the rehearsal. Ask: “Did you receive my referral? Who contacts the customer? When will I hear back? What earns the bonus?” The responding teammate should answer with a concrete action or an honest follow-up, not a guess.
Suggested training message: ‘Please watch these two short walkthroughs before our practice on [date]. Be ready to show how we acknowledge a referral, keep the partner updated, and verify the bonus recipient and payment method. Your role in the test is [role].’
Ready means each person can perform their role, identify the original referrer, distinguish a message from a private note, and explain why a recorded offline bonus does not send money. Rehearse any missed point once more.
Every participating teammate has both links, can answer the three practical checks, and knows their role in the practice session.
Do not assume everyone watched or understood the material because a link was delivered. Use a brief demonstration or teach-back to confirm readiness.
Use the referral queue, status updates, Conversations, and private Admin Notes to keep work moving and partners informed.
Partners remember whether you followed through. A short daily review keeps an acknowledged referral from becoming a forgotten one.
Managing referrals is a repeatable review routine. The tutorial begins with the Referrals tab’s Action needed filter, which groups new, acknowledged, and in-progress referrals. It then shows how status changes, partner-visible conversations, payment history, and internal notes serve different purposes.
Use the referral queue, status updates, Conversations, and private Admin Notes to keep work moving and partners informed.
Action Needed narrows the list. Clear or change it before searching for a completed referral; check other filters and your role visibility as well. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
For each open referral ask: What happened? What is next? Who owns it? When is the next check? What does the partner know? Example: “Customer contacted; assessment timing pending. Intake will confirm tomorrow, and I will update the partner afterward.”
Agree on what each status means operationally and who checks overdue next steps. New, Acknowledged, In Progress, Completed, and Cancelled appear in the current referral controls. Reports definitions can be configured separately, so do not assume a label automatically represents your revenue stage.
Review what changed, what the partner needs to know, and who acts next. If nothing has changed, give an honest update with the next check time instead of moving the status merely to make the queue look clean.
Partner update: ‘Thanks for the referral. We’ve received it and [name/team] will contact the customer by [time]. We’ll update you here after the next step.’ Internal note: ‘Follow-up assigned to [name]; next check [date/time].’
To locate a completed referral, clear or change Action Needed before searching. Also check date filters and role visibility. Never create another referral simply because the current view does not show the first one.
You can locate a test referral, acknowledge it, distinguish a partner update from an internal note, and find its payment history.
A missing record may be outside the current filter or your role’s visibility. Check those before creating a duplicate referral.
Use an obvious TEST name and agreed test details. Confirm the submitting referrer and the status with the receiving teammate. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Test log: submission time | correct organization | original referrer | office can find it | acknowledgment visible | notification received | next owner. If the record exists but no alert arrives, investigate notifications separately rather than submitting a duplicate.
Let the office know the test window and confirm that no dispatch or connected customer outreach should act on it. Choose a receiving teammate whose permissions cover the task; being a BDR does not establish access to every referral.
Submit from the same kind of device your partners use. Note where you hesitate and whether the destination company is obvious. Mark the name and available notes with TEST, and use only agreed contact details that your team controls.
Use a test description such as: ‘TEST — training only. Practice request for [service]. Do not dispatch or contact a real customer. Test owner: [teammate].’
Business requirements and form requirements are different. Include the contact details your team needs, but follow the required indicators in your organization’s current form; fields can be configured.
The sender and receiver can find the same test referral, the office has acknowledged it, and the sender can confirm the update or identify a specific notification issue.
Do not allow a training record to trigger a real dispatch or customer follow-up. Coordinate with the office and any connected workflow before submitting it.
Test the full bonus journey: approval, correct recipient, available funding, payment history, claim steps, and confirmed receipt.
A payout is not finished just because the sender clicked a button. Your test should show what both people experience.
A test referral is practice, but a Reactor Pay bonus can move real money. Agree on a small test amount within your approved budget. The bonus walkthrough shows the sender’s final review, while the receiving walkthrough shows why the recipient still has a part to complete.
Test the full bonus journey: approval, correct recipient, available funding, payment history, claim steps, and confirmed receipt.
Find Bonus Payments on the referral before issuing a test bonus. This example has no previous payments; inspect your own record for earlier entries before using Give Bonus. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Payment evidence log: referral | recipient | approved amount | method | sent or paid time | displayed status | recipient confirmation | next action. If the record shows sent but the recipient reports nothing, check the original transaction and claim progress before escalating.
Approve a small real test or choose a no-money rehearsal explicitly. For Reactor Pay, require available funds; for manual cash/check, arrange the actual handoff and then record it accurately. Do not pay twice to compensate for uncertainty.
Walk the recipient through the process without taking over their verification. Ask which stage they reached: message received, claim completed, or money visible in their destination. These are your tracking categories, not a promise that the app uses those exact status labels.
Track the test as three separate checks: ‘Payment recorded: [status]. Recipient claim completed: [status]. Funds received: [status].’ This makes the unfinished step visible.
For a stalled electronic payout, provide support with the transaction reference and displayed status, not passwords or verification codes. For a check, confirm delivery and reconcile with your finance owner rather than treating the app entry as proof it cleared.
The payment record matches the intended recipient and amount, and receipt is confirmed. If still pending, the test remains open with a named owner and next check date.
Do not send a second bonus merely because the first one has not arrived. Check payment history and the recipient’s claim progress first.
Invite three trusted partners, guide them through joining and notifications, and ask each to send a clearly labeled practice referral.
Your first three partners are a pilot group. Their feedback helps you build an experience worth recommending before you expand.
Start with people who will give honest feedback and are likely to encounter customers who need your services. The QR-code tutorial distinguishes an invitation link that joins someone as a referrer from a public service-request link intended for a customer’s own request. Choose the invitation route for this partner exercise.
Invite three trusted partners, guide them through joining and notifications, and ask each to send a clearly labeled practice referral.
Users → Add people distinguishes referrer invitations from internal team invitations. Choose Invite New Referrers for this partner pilot. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Pilot card for each partner: customer fit [ ]; current frustration [ ]; invitation sent [ ]; joined [ ]; test submitted [ ]; update seen [ ]; feedback [ ]; next owner/date [ ]. Ask: “What almost stopped you?” Record their words and fix the most common obstacle.
Choose people with service fit, a trusted relationship, and willingness to give candid feedback. Prefer a small responsive pilot to a large list that your office cannot support. Name the relationship owner for each person.
Try: “When your customer needs [service], I want the handoff to be easy and keep you informed. Would you try one clearly labeled test with me? You will see where it goes and how we follow up.” Ask permission to guide the first attempt; do not make them discover every step alone.
Suggested invitation: ‘We’re launching a simpler way to send and track referrals. Please join [company] using this link, choose your notification preferences, and send one clearly labeled practice referral. We’ll acknowledge it and show you how updates work.’
Use Dashboard → Invite referral partners or the appropriate Invitations controls. The Users → Add people dialog also distinguishes Invite New Referrers from Invite New Admins or BDRs. Confirm the joining route before sharing.
Three partners have been invited, and each person’s joining, test-referral, and notification status is recorded with a follow-up for any unfinished step.
A public service-request link and a referrer invitation link serve different purposes. Verify the destination before sending the same link to all three partners.
Use Conversations to acknowledge each partner, state the next step, and verify that your update reaches the right person.
A good update protects the relationship by reducing uncertainty. It tells the partner what happened and what they can expect next.
The Managing Referrals tutorial treats the conversation as the shared story of the referral. A useful update tells the partner what happened and what comes next. Admin Notes serve a different purpose: the video explicitly identifies them as internal information the referrer does not see.
Use Conversations to acknowledge each partner, state the next step, and verify that your update reaches the right person.
The shared Conversation shows referral events and provides a message composer. Add the human update—what happened, what happens next, and when you will check again. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Rewrite “Working on it” into a useful update: “Our intake team has contacted the customer and is arranging the next step. I will check back tomorrow afternoon and update you here.” Use this only when those facts and timing are true.
Agree on which events require an update and who sends it. Keep customer-sensitive details out of partner messages unless appropriate to share. Admin Notes are internal, but should still be professional and necessary.
Acknowledgment: “Thanks for the introduction. [Name/team] is reviewing it and will update you by [time].” Waiting: “We are waiting on [shareable fact]. Our next check is [time].” Closed loop: “The referral is now [accurate outcome]. The bonus review is [status under our rule]. Thank you for connecting us.”
Example: ‘Thanks, [name]—we received your practice referral. No service visit will be scheduled. Please reply “received” here so we can check the conversation. Next, we’ll walk through the test bonus once funding is ready.’
If a partner asks a question you cannot answer, acknowledge it and name who will find out. Silence and unsupported reassurance both damage trust. Never paste an internal speculation into the shared conversation.
Every partner test has a clear conversation update, the partner can find it, and you have either received a reply or assigned a follow-up.
A private Admin Note does not replace a message to the partner. Put the update in the correct place and avoid promising timing your team cannot meet.
Managing Referrals — Conversations at 3:24; Admin Notes at 5:27
Send each agreed partner test bonus when funding allows and help the recipient complete their own claim and receipt check.
Your partner should understand how to receive an approved reward without surrendering control of personal details. A calm, specific follow-up builds confidence.
Now repeat the bonus process with the partners who submitted practice referrals. Keep each payment tied to its referral and review it individually. The receiving tutorial shows the Dots link, phone verification, and payout-method selection; the faster-bonuses tutorial explains why a person’s saved default may override the organization default.
Send each agreed partner test bonus when funding allows and help the recipient complete their own claim and receipt check.
Organization Bonus Defaults apply when a referrer has no specific defaults. This example has neither amount set; confirm the approved amount rather than copying a default blindly. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Partner follow-up: “Your [amount] test bonus was [accurate action] using [method]. Please confirm when it arrives. If you are stuck, tell me the step you see; keep codes and account details private.” For cash/check, describe the agreed handoff instead of sending Dots instructions.
Set one person to resolve payment exceptions. Review individual defaults against organization defaults before each test, especially when several partners have different approved arrangements.
Ask “Which step are you on?” If no payout message, verify the original transaction and recipient information with the authorized sender. If claiming, let the partner complete verification privately. If claimed but not received, collect the displayed status and route the issue to the payment owner or support.
Partner follow-up: ‘Your test bonus has been sent through Reactor Pay. Look for the Dots payout message and complete the claim steps yourself. Please tell us when it arrives, or which step is preventing you from finishing.’
Organization defaults live in Settings → Payment Settings; user-specific defaults can override them. Defaults reduce entry work, but they do not approve a payment or resolve who earned it.
Each approved partner test bonus has a matching payment record and confirmed receipt, or a documented pending status with a specific follow-up.
Help the partner understand the steps, but let them enter their own verification codes and payout details. A test label does not make a real payout reversible.
If a pilot partner struggled to join, first check that you used the referrer invitation route. Fix the specific obstacle before inviting the next three. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Choose a learning question: Does the revised invitation explain the value? Does a different partner type understand the referral standard? Does a phone user find the update? Compare the first and second groups in your own tracker; do not claim the app automatically measures these steps.
Review where people stopped: opening the link, joining, submitting, finding updates, or receiving the agreed reward. Choose one fix and assign someone to verify it with the next group. Keep the service promise within your actual capacity.
If the objection is “I already text referrals,” say: “Keep the relationship personal. This gives us a shared place to confirm receipt and follow through. Let us try one together.” If the objection is time, offer a brief guided test and ask which step felt unnecessary.
Compare the two groups: Which joining or notification question repeated? Turn your answer into one clear sentence in your next invitation so the third group has an easier start.
Do not raise bonuses automatically to solve a confusing joining experience. Find the obstacle first. You can complete this lesson with unresolved cases if each has a specific follow-up; do not label six invitations as six active partners.
Six partners have been invited in total. The second group’s joining, test referral, communication, and payout progress is recorded, with follow-ups for anything incomplete.
Do not count an invitation as a completed onboarding. Keep separate checks for joining, submitting, seeing updates, and receiving any agreed bonus.
Write a useful launch announcement with a clear referral request, an action to take, and precise terms for any optional incentive.
An announcement earns attention when it helps a partner recognize a customer you can serve. One specific request is easier to act on than a list of everything your business does.
Give partners one timely, useful reason to participate. The original guide’s announcement video is still listed as coming soon, but the current software provides a working announcement editor. Use the verified controls below and a clear message.
Write a useful launch announcement with a clear referral request, an action to take, and precise terms for any optional incentive.
The live announcement editor: title, optional body and image, plus separate push and email choices to all users. Review the message and channel selections before Create Announcement. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Example title: “Know someone dealing with water damage?” Example body: “We help homeowners in [area] take the next step after water damage. With the customer’s permission, submit a referral with their name, phone, job address, and a brief description. Our [team] will respond during [coverage] and keep you updated here. Questions? Reply to your contact at [company].” Replace every bracket before publishing.
Confirm the service capacity, response owner, and any incentive before publishing. Current announcement controls show optional push and email notifications to all users; a targeted audience or scheduled send was not verified. Choose notification channels deliberately.
Draft the message around the partner’s customer: problem, helpful next step, and the information to include. Offer a clear route for questions. Avoid an urgent-sounding promotion if the office is not staffed to respond.
Example without an extra incentive: ‘Our referral program is ready. Know someone in [service area] who needs [service]? Submit their details through [referral link] with a short description of the work. We’ll acknowledge the referral and keep you updated in the app. Questions? Contact [team/contact].’
The editor allows a title up to 100 characters and an optional body up to 500. If an incentive needs more explanation, simplify the offer and give an approved route to full terms. Include any deadline and time zone in the text; do not assume automatic expiration.
The announcement is sent to the intended audience, its action link works, and a named teammate is ready to respond. Any incentive has clear qualifying conditions and an approved budget.
‘Extra $50 today’ leaves unanswered questions. If you use an offer like the guide’s example, add the exact end time, qualification rule, and when it is earned before sending.
Weekly partner review: invited but not joined → offer help; joined but no test → guide one; test complete but no real referral → discuss fit; real referral open → update the partner; repeat referrer → ask what made the handoff work. Assign one next action and date per person in your tracker.
Assign an ongoing relationship owner and backup. Review whether your partner mix matches the work and geography you can serve. Decide how many new partners the team can onboard while still following through with existing ones.
Use a personal reason for each new invitation. For someone who joined but never referred, ask: “Have you encountered a good-fit customer, or is something about the process unclear?” If they have no fit right now, agree on a sensible next contact instead of pressuring them for a test of activity.
Give a teammate the invitation and onboarding instructions you now use. Can they onboard the next partner without relying on you to explain each step? Note and fix any missing instruction.
If using invitation associations, verify the chosen source before sharing. Marketers Portal is an Unlimited feature. Keep a manual relationship-owner list when needed; do not promise automatic assignment behavior that you have not tested.
Nine distinct partners have been invited across Days 3–5, their progress is visible, and someone owns the next follow-up for each unfinished onboarding.
More invitations do not fix an unclear experience. Keep improving the instructions and response routine as your network grows.
Decide whether a CRM connection is needed, define the handoff, and verify a supported integration with a controlled test.
A connection is valuable only when your team knows which system owns the next action. Avoid making the same customer harder to track in two places.
A CRM connection should make the handoff easier to manage. In Managing Referrals, the presenter briefly shows a ‘convert to customer’ action and refers to the CRM, but does not demonstrate a complete integration setup. Use the supported integration instructions for your actual CRM rather than assuming the video establishes a particular sync behavior.
Decide whether a CRM connection is needed, define the handoff, and verify a supported integration with a controlled test.
Settings → CRM describes the built-in customer and job features. Turning it on does not establish an external CRM sync; verify that handoff separately. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Mapping worksheet: trigger | source field | destination field | required information | duplicate-match rule | owner of updates | failure check. Test a clearly labeled record, compare actual values in the destination, and inspect whether any outbound automation fired. Until verified, use a named manual handoff.
Choose between a manual handoff, the built-in CRM, or a verified external integration. Settings → CRM enables customer and job management; it is not proof of external synchronization. API Keys and Zapier are shown as Unlimited features.
Describe the operational handoff in plain language: “Once [event] happens, [owner] creates or updates [record], and tells [next owner] where to find it.” Preserve the original referrer and keep the partner updated even if customer work moves elsewhere.
Write a handoff rule: ‘When [event] happens, [owner or integration] creates or updates [record] in [system]. We check [fields]. If it fails, [person] follows up by [time].’
The video’s CRM moment is brief. No specific GHL, Jobber, or other external sync was verified for this course. Obtain instructions for the exact integration and plan; do not infer it from the presence of a CRM menu.
Either a supported connection has passed a controlled test, or your decision to defer it is recorded with a workable manual process and owner.
Connecting an account is not proof of a working sync. Verify the destination record and actual behavior before relying on the integration for live work.
Review the launch from invitation to payout, assign every unfinished action, and set a repeatable follow-up schedule.
A strong launch leaves the team with a routine that works after the excitement of week one. Measure follow-through before judging the size of the pipeline.
Finish with a review of what actually happened, not just what was sent or started. The tutorials show several distinct signals: an invitation, a submitted referral, an acknowledgment, a conversation, a payment entry, and the recipient’s claim and receipt. Your launch review connects those signals and gives every unfinished item an owner.
Review the launch from invitation to payout, assign every unfinished action, and set a repeatable follow-up schedule.
During the launch review, widen the referral view when needed. A record absent from Action Needed may still exist under another status. Screen captured September 9, 2026; branding and available controls may vary by organization, role, and plan.
Days 6–7: close access and test issues. Weekly through day 30: review referral ownership, partner updates, pending invitations, and payment exceptions. At day 30: compare real referral quality, response consistency, repeat participation, and program cost with your launch agreement. Decide what to continue, simplify, or stop.
At the first weekly review, separate test records from real activity in your own analysis. Review invited, joined, tested, first real referral, referrals awaiting action, and unresolved payments. These are suggested management measures; not all are native dashboard metrics.
Choose the next action for each relationship. Ask one pilot partner what was useful and what still felt confusing. Bring one concrete process improvement to the weekly review, supported by the referral or onboarding step where you saw friction.
Follow-up format: ‘[Partner/referral] — [current status] — [next action] — [owner] — [next check date].’ Example: ‘Partner A test bonus — sent, receipt unconfirmed — ask partner to complete the claim and confirm arrival — Jordan — Friday.’
A five-day course can prepare your process while verification or a payout remains pending. Track the unfinished work honestly. Before drawing conclusions from Reports, check the date range and Settings → Report Definitions so the team agrees on what the figures represent.
Every launch milestone is reviewed, every unfinished item has an owner and date, and the team knows when it will review new referrals and partner progress again.
A successful launch can still have documented follow-ups. Be accurate about what remains pending so it receives attention after the five-day course ends.
Managing Referrals — queue and payment history
Referral Reactor Overview — Reports at 4:01
Giving & Receiving Referral Bonuses
Tax Documentation in Referral Reactor
Installing Referral Reactor on Android
Submitting Referrals Across Multiple Organizations
Contact Referral Reactor support with the organization, task, and the exact step or status where you are stuck. Keep passwords, verification codes, and payment credentials private.