Updated October 17, 2026. DinkTourney helps pickleball hosts create events, organize divisions and courts, record results, and share live information with players. Learn a small bracket first, then match the paid event tools to the host's real needs.
Find the host's actual problem
Good prospects include a club volunteer running regular play, an instructor organizing a clinic, a tournament director managing multiple divisions, and a recreation organizer who needs players to see live results. The buyer is usually the person responsible for setup and event operations, rather than every spectator who opens the live board.
Ask how they collect names, how many divisions and courts they use, whether registration must happen online, whether entry fees are collected, how often they host, and what happens when venue Wi-Fi fails. Also ask who records scores and who needs the public viewing link.
A simple evening draw can begin with a free bracket. A full event with online registration and multiple divisions may justify one paid tournament. Someone hosting repeatedly may prefer annual Pro. Avoid promising that software replaces volunteers, provides courts, supplies referees, or automatically fills registrations.
DinkTourney's rating features should not be described as automatic synchronization to every external pickleball rating system. Explain the actual displayed system and event type. Do not promise official sanctioning or compliance with a particular association merely because a bracket can be created.
Current customer prices and limits
The current full-event choices are $49 for one complete tournament or $99 per year for Pro, which supports unlimited complete tournaments. An eligible previous one-tournament buyer can be offered a $49.99 upgrade to twelve months of Pro. The upgrade depends on eligibility shown in the account; it is not a universal public coupon.
There is no current monthly Pro checkout and no Pro trial. The Residual Apps catalog also carries a monthly Pro reward; current DinkTourney checkout offers an event purchase, annual Pro, and an eligible upgrade. Do not pitch a monthly plan unless the actual current checkout offers it.
Free quick brackets use a free host account, manual rosters, and a private viewing link. The current default limit is three free quick brackets per rolling 24 hours, subject to the displayed limit. A free bracket does not include the complete event's online registration, entry-fee collection, multi-division workflow, or offline controller. Repeated free brackets should not be sold as an equivalent full-event package.
Clinic or camp creation has a separate free path. Do not assume that every event called a clinic consumes a tournament credit, or that creating a clinic makes a later full tournament free. Choose the actual event type matching what will happen.
A tournament purchase supplies creation entitlement. It is distinct from player entry fees and their payout arrangements. Billing for a newly created event is checked during creation; the event's right to run is retained on that event. Do not promise that a paid host can create unlimited new events after a one-event credit is used.
Lesson 1 — Create the correct host account
Have a new customer open your own current DinkTourney share link from Residual Apps. Sign in or create the host account before event creation so the tournament belongs to an account they can return to. Use the real organizer's own email and password and complete the email confirmation before activation; an affiliate does not need their credentials or verification code. Check spam and the address entered if confirmation is missing.
The host dashboard is the place to return to owned tournaments and billing-related event rights. Confirm the signed-in account before buying an event or annual Pro. Purchasing under one email and attempting creation under another can make rights appear missing.
A player opening a public live board is taking a different path from a host creating an event. Keep the host account, public tournament code, staff PIN, and affiliate link distinct. None of those is a substitute for the others.
If the host already has an account, use that account rather than creating a duplicate to obtain a different offer. For password or verification problems, use the site's current recovery route or contact support from the account email.
Lesson 2 — Build a small free bracket
Choose the simple bracket path and enter a clear event name. Paste the players or teams one per line; read the count and check for accidental blank lines or duplicates. A practice demonstration might use “Demo Pair A,” “Demo Pair B,” “Demo Pair C,” and “Demo Pair D.”
Review the available format and scoring controls. Where offered, single elimination, double elimination, and round robin create different schedules and amounts of play. Select only a format actually enabled for that creation path. Set the game length, winning margin, match configuration, and court count shown by the form.
Create the bracket, wait for the confirmation, and retain the event link or code. Inspect the draw before sharing it. A generated bracket is not proof that the roster is correct or that every match has been assigned the intended court.
Use this first bracket to learn the difference between viewing and scoring. Open the live board as a spectator and return to the host's control path to record a practice result. Do not publish a fictional paid or rated event into real discovery simply to demonstrate the software.
Lesson 3 — Set up a complete tournament
Choose the complete tournament builder when the event needs the full workflow. Confirm that the host has a purchased tournament credit or active Pro before expecting the new event to be created. A failed validation should be corrected in the form; do not keep buying credits when the issue is a missing field.
Enter the event identity, date and location, and the signup arrangement. The current builder supports opening online signup before finalizing divisions, as well as a host-managed roster. Choose the path that fits how the director will collect names.
Define division names, formats, and relevant capacity or roster details. Review the event-wide courts as a shared physical resource; several divisions do not create additional real courts. A division's capacity and an event's total capacity should be understood before publicizing registration.
For online signup, inspect the public registration view and the division choices before inviting participants. For a manual roster, confirm each participant or team is entered in the correct division. Preserve the distinction between an interested person, a completed registration, check-in, and a player placed in a finalized draw.
Finalize divisions only when their real roster and setup are ready. If someone withdraws or the format changes, use the appropriate director control and review resulting matches before proceeding. Do not promise that an arbitrary mid-event change can be made without consequences to schedules or results.
Lesson 4 — Share the right access
The event or tournament's six-character code and public link let players find the live board. A staff PIN grants operational access to the relevant scoring or check-in tools. The PIN is not a tournament code. The host's private account and owner access should stay private.
Show players the public link or QR. Give staff access only to people the director authorizes. Before an event, have a staff member demonstrate finding the event, opening Score desk or Judge, and entering the correct PIN where required. Never post operational access publicly just to simplify a demo.
An event hub can bring divisions together and provide a shared staff PIN. Check which division is selected before entering results. A score recorded for the wrong division is not fixed by recording another unrelated score elsewhere.
The affiliate referral link is used when recommending DinkTourney to a prospective paying host. The tournament link serves that host's players. Sharing a live event with many spectators does not itself produce affiliate commissions.
Lesson 5 — Scores, courts, and results
Open the correct event and match through the host or authorized staff controls. Confirm both sides, game or match number, and court before entering a result. Read the selected scoring settings, since one game's target and winning margin may differ from another event's rules.
Use Score desk for the relevant result-entry workflow and Judge for the available live scoring workflow. Check the saved score and progression on the bracket or live board. A displayed score on one local screen does not always prove it has synchronized to every viewer.
Correct mistakes through the available correction controls. Downstream matches can depend on earlier winners, so stop and review the effect before overriding a result after later play has begun. Escalate a confusing state to support instead of repeatedly changing winners until the draw looks plausible.
Court assignments need to reflect actual available courts. Review waiting matches, active matches, and completed matches. The app organizes entered information; staff still confirm that players are ready and that a court is physically free.
Printouts are useful backups. Open the real print preview and inspect division names, page breaks, and readable brackets before relying on the copy at the venue. The software cannot guarantee that a printer is connected or supplied with paper.
Lesson 6 — Prepare offline operation in advance
The full tournament's offline controller is prepared on one designated laptop while online. This is not a promise that every visitor's phone can independently run the entire event offline. Use the offline preparation and readiness controls before traveling to a venue with unreliable connectivity.
Read the readiness results for the saved tournament, cached scoring/bracket/print pages, and storage. A control that says pages are not cached or preparation has expired needs attention before relying on it. Do not assume that simply opening the homepage prepares the event.
During disconnection, the designated laptop can control the prepared event and queue changes. Watch the status: cloud connected, offline controlling, synchronizing, or needs review are materially different states. Public remote viewers cannot receive fresh cloud scores while those changes remain only on the laptop.
Reconnect and synchronize before closing the laptop or clearing browser data. Review conflicts deliberately rather than discarding one side without checking it. Keep queued data intact until resolved. A practice readiness check before event day is more useful than discovering at check-in that a different laptop was prepared.
Lesson 7 — Reuse setup and handle money correctly
On an owned tournament in the dashboard, Copy setup reuses its configuration for a new event. It does not copy participant identities, registrations, payments, results, schedules, or staff credentials. The new event is a fresh instance with its own runtime information.
A previous one-time buyer can inspect and reuse owned setup, but creating the new full tournament still needs a new credit or active Pro. This is a useful repeat-host conversation: reuse saves setup effort, while the billing decision depends on how often the host will run events.
Web purchases use the site's checkout. Review whether the customer is buying one tournament, a renewing annual subscription, or an eligible upgrade. Manage a web subscription through its billing route. Do not invent a universal store purchase or restore path for every installed wrapper; the controls actually offered in that version determine the route.
Entry-fee payouts are separate from affiliate commissions and Pro billing. The host should follow the dashboard's payment setup, fee disclosure, and refund controls for registration payments. Never describe player registration revenue as money paid to the referring affiliate.
A five-minute host demonstration
Use a practice account and clearly fictional participants in a non-customer practice event. Do not charge entry fees, send real invitations, or alter a customer's active competition.
- Ask how often the person hosts and whether online signup or multiple divisions are necessary.
- Create a small free bracket with four demo sides and one court.
- Show the public code and explain why a staff PIN is different.
- Enter one practice result through authorized controls and show the corresponding live-board change.
- Point out the full event's division, registration, print, and offline preparation workflow, using an entitled practice environment when needed.
- Compare $49 once with $99 annually based on the host's actual plans.
- Let the host open your disclosed personal referral link for their own account and purchase decision.
A successful first result is an organizer who understands how to return to a saved event and publish the right viewing link.
Sales language and objections
Introduction: “How do players find their next match and see updated scores at your events? DinkTourney gives the host a saved event and players a live board. We can start with a small free bracket, then compare full-event registration and divisions if you need them. I'm an affiliate and may earn a commission on a qualifying purchase through my link.”
Invited follow-up: “Did the four-player practice bracket match the way you run play? The next choice is whether your event needs online signup and several divisions, and how many complete events you expect to host.” This is example copy, not an outgoing campaign.
“I only run one event.” Compare the $49 one-tournament purchase with the recurring annual option; do not force a subscription pitch.
“Does Pro cost $4.99 per month?” That is an older offer. Current checkout is annual, with no monthly plan or trial.
“Can players just use the code?” They can view the event with the public code. Authorized scoring requires the proper staff or host access.
“Will it work without internet?” A full event can use a properly prepared single-laptop controller. Preparation and later reconciliation matter; live cloud viewers will not receive unsynced changes.
“Does Copy setup reuse last week's players?” No. It reuses configuration, leaving the new event's registrations and results fresh.
“Why can I open my old tournament but not create a new one?” An existing paid event retains its operational entitlement. A new complete event requires current Pro or a new credit.
Commissions, support, and readiness
Published qualifying rewards are $40 for annual Pro, $20 for a one-tournament purchase, and $20.20 for the eligible upgrade. These relate to the software sale, not participant entry-fee volume. Annual renewal rewards depend on continued qualification and payment; they are not monthly commissions. Gross published rewards can be affected by program fees, refunds, and attribution.
Use the current DinkTourney link or QR from your own Residual Apps card, disclose the relationship, and have a new customer begin there before registration. A click, free bracket, clinic, or player registration does not itself prove a paid affiliate conversion. Check the dashboard rather than estimating income from event attendance.
For product support, use support@dinktourney.com. Include the host email, event code, division and match, device/browser, exact error, and whether an offline queue is pending. Keep staff PINs, private host access, passwords, and payment details out of public screenshots. Referral questions go to support@residualapps.com with relevant dashboard evidence.
Readiness quiz: Is current Pro monthly? Does one $49 credit mean unlimited new events? Is the PIN the public code? Does an offline laptop instantly update remote spectators? Does an entry-fee payment create the same commission as a Pro sale? Answers: no to all five. Demonstrate setup, viewing, authorized scoring, and a correct plan comparison before promoting the product.
Official reference links
DinkTourney, create an event, Pro and event purchase, terms. Published affiliate rewards: Residual Apps apps and payouts. Program conditions: Residual Apps terms. Review current checkout and dashboard terms before quoting a purchase or reward.
Current tools — Pool seeding and optional DUPR CSV
For exactly two equal round-robin pools, the automatic proposal ranks each pool separately and interleaves its places into bracket seeds. Played opening matches cross the pools. In a ten-team example, A4 plays B5 and B4 plays A5, while each pool’s top three receive byes. A team with a bye may meet its own pool in a later round. Unequal pools and other formats do not receive this same guarantee. Directors review the proposed seeds; an already confirmed manual order is preserved. Show the current seeding criteria rather than inventing tiebreak rules.
The director’s event hub now offers an optional DUPR tool. Select the division, enter the actual individual players’ DUPR IDs (both people for doubles), choose singles or doubles, and review actual match dates and game scores. Missing IDs or other incomplete data hold affected matches. Synchronize and release any offline controller before preparing the export.
Review eligibility and exclusions, then download the division’s CSV. An authorized club organizer uploads it manually through DUPR’s own dashboard and inspects its preview before accepting. This is CSV preparation, not automatic API reporting or automatic rating synchronization. Actual acceptance of this new CSV by DUPR has not been verified in this training. A download is not an upload; previously downloaded matches are omitted by default to reduce duplicates. Deliberately include them again only when appropriate, and correct already imported results through DUPR’s process.
Use the app and help us improve it
Use the app yourself before recommending it. Complete one useful workflow in your own account or an authorized demo, then find the saved result again. A paid subscription is not required to become a partner; use the free option or an available preview and be clear about what you have actually tried.
If you use this app, tell us what works, where you get stuck, bugs you can reproduce, and what you wish it did next in Partner Care. Include the app, web/iOS/Android, installed version or browser version, steps, expected result, and what happened. Say whether it affects your own use or a demonstration. Please report unclear training or a screen that differs from this guide too.
Keep customer names, email addresses, medical records, payment details, passwords, and sign-in codes out of feedback. Use fictional examples and remove private information from screenshots. Urgent account or billing problems still belong with the product support route above.