Link player branch accounts
Connect a mobile player identity to the right branch customer record so balances, activity, rewards, and session history stay useful.
Returning customers have one useful branch identity instead of scattered records across guest sessions and mobile activity.
Before you start
- The player has or can create a mobile account.
- The branch has a player record or can create one safely.
- Staff know how to search before creating duplicate records.
Find the branch record
Search first. Linking works best when staff connect the mobile identity to the existing record with the correct history.
- Search by the branch identifiers your staff use.
- Confirm with the player before linking.
- Avoid linking to a guest or wrong customer record.
Complete the link
After confirming identity, complete the linking flow and tell the player which features now use that branch account.
- Link the mobile identity to the branch player record.
- Confirm balance, debts, rewards, or history if the branch uses them.
- Ask the player to refresh mobile branch activity if needed.
Maintain clean accounts
Account linking reduces duplicate records only when staff keep the branch data clean.
- Review duplicate player records during quiet hours.
- Train staff to search before creating players.
- Escalate mistaken links to an owner or trusted supervisor.
Verify it worked
- The player sees the expected branch relationship in mobile.
- Staff can find the linked player account in the Controller.
- Future sessions, requests, and activity use the same player context.
Troubleshooting
The player has duplicate branch records.
Choose the record with correct history and train staff to search before creating another account.
The link was made to the wrong account.
Escalate to a supervisor and review history before making corrections.