Register
An affiliate submits their details and receives a unique referral link.
Internal release room / tester guide
SV Affiliate connects a referral from first click to collected revenue and payout. Your job is to test that chain, capture evidence, and help us separate release blockers from ideas for later.
Every test should make that answer clearer.
01 / Why this exists
SV Affiliate is the operating system for Scale Virtually affiliate referrals. It gives affiliates a trackable link, gives the team a traceable lead record, and gives finance a defensible path from collected revenue to commission payout.
02 / Current workflow
The lead submission and Zoom redirect are early signals. Only verified webhook data confirms the appointment.
An affiliate submits their details and receives a unique referral link.
A lead opens the referral link, submits their details, and is redirected to Zoom.
A verified Zoom webhook confirms the appointment. A redirect alone is not confirmation.
Operations and sales move the record through attendance, qualification, conversion, and collection.
Finance reviews the commission ledger and creates a payout from eligible collected revenue.
03 / MVP boundary
Test the promise we made for the initial release, and record everything else as a future enhancement.
04 / Test guide
Stakeholder testing should start only after DevOps acceptance evidence is complete in the target environment. Use a fresh test email where possible. Record the exact environment, IDs, time, expected result, actual result, and a screenshot when the visual state matters.
https://affiliate.scalevirtually.com/https://book.scalevirtually.com/https://book.scalevirtually.com?ref=<affiliate_id>https://admin.scalevirtually.com/loginhttps://admin.scalevirtually.com/admin/https://admin.scalevirtually.com/admin/affiliates/https://admin.scalevirtually.com/admin/bookings/<booking_id>https://admin.scalevirtually.com/admin/commissions/https://admin.scalevirtually.com/admin/reconciliation/Register a new affiliate using a working email address, then confirm the unique affiliate ID and referral link.
Affiliate ID, confirmation screen, and referral link.
Submit a referred lead and confirm the record is saved as a lead, not a booked appointment.
Lead ID, affiliate ID, attribution status, and timestamp.
Submit a direct lead and confirm no referral language appears when no referral code is present.
Lead ID, direct status, and visible copy.
Confirm Zoom redirect occurs after lead submission.
Redirect URL, lead ID, and timestamp.
Start scheduling and abandon the Zoom flow. Confirm no appointment is created.
Booking status and absence of an appointment record.
Send a valid Zoom scheduled-event message and confirm one appointment is created or updated.
Webhook event ID, booking ID, appointment ID, and status.
Send the same Zoom delivery twice and confirm no duplicate appointment is created.
Provider event ID and one appointment record.
Send Zoom cancellation and confirm booking and appointment status are updated.
Cancellation event ID, booking status, and appointment status.
Mark attendance as completed and no-show, and confirm the lifecycle status changes.
Appointment ID, status before and after, and timestamp.
Create opportunity and signed client records, then confirm the sales lifecycle is traceable.
Opportunity ID, client ID, and won or signed status.
Record full collection, partial collection, refund, and chargeback events.
Revenue transaction IDs, amounts, statuses, and parent references.
Confirm eligible revenue creates commission and refunds or chargebacks create negative reversals.
Commission entry IDs, basis amount, rate, status, and reversal link.
Approve commission and confirm only approved, unpaid, positive entries are eligible for payout.
Commission status and eligible entry IDs.
Create a payout from approved unpaid entries and confirm the payout items link to exact commission entries.
Payout ID, payout item IDs, payment reference, and total.
Try to pay an already allocated commission entry twice and confirm the second payout is blocked.
Original payout ID, attempted entry ID, and error message.
Confirm unauthorized admin access is blocked, then review reconciliation exceptions and CSV exports.
Access result, exception records, export files, and timestamps.
05 / Evidence desk
Submit one report per finding. A useful report lets someone else reproduce the issue without needing a second conversation.
The system is wrong or broken.
It works, but the experience needs attention now.
Useful, but not urgent for the MVP.
Reports are timestamped and stored with their evidence for review.