# \[SOLVED\] Points Wagering Flaws- Teams select "All" but not all are wagered **URL:** \ **Category:** Bugs\ **Tags:** trivia, features\ **Created:** [April 27, 2022, 4:20pm UTC](https://community.crowdpurr.com/t/solved-points-wagering-flaws-teams-select-all-but-not-all-are-wagered/418 "2022-04-27T16:20:25Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![RossN](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.crowdpurr.com/rossn/32/74_2.png) [@RossN](https://community.crowdpurr.com/u/RossN)\ **Post date:** [April 28, 2022, 1:54pm UTC](https://community.crowdpurr.com/t/solved-points-wagering-flaws-teams-select-all-but-not-all-are-wagered/418/4 "2022-04-28T13:54:43Z")
Hi @gregstudley, rest assured we take all bugs seriously. We know how important it is to have a live event go off seamlessly and of course that many of customers make businesses out of using our app. Just an FYI, capturing an email is your choice. You can turn this off at **Experience Dashboard → Leads → Lead Capture Settings → Crowd Lead Capture Settings**. However, if you’re using it as a means to allow Basic Teams to sign back in or use multiple devices, then you need to leave it enabled. > [@gregstudley](#): > > It should be as simple as scanning the QR, entering the same team names and the phones are linked. First answer in is the one that’s recorded. For Basic Team Mode, unfortunately we can’t make it this simple. If you could enter the Basic Team you want to join, not only would there be problems matching up errors in how players enter the team names, allowing a “first one to answer gets recorded” would be disastrous if someone wanted to sabotage another team (which happens). Imagine someone signing into a Basic Team and instantly answering with the wrong answer each time. I looked up ZSFLI and it’s currently showing that **It’s Carol’s Birthday** won. When I export your **Crowd Activity** with the raw votes, it appears that you had more than one “It’s Carol’s Birthday” team actually playing, as there’s answers/points rows for a **It’s Carol’s Birthday** with an email and a **It’s Carol’s Birthday** with no email, for the same question. So this probably explains the confusion with the team thinking they couldn’t wager all their points, they didn’t have enough points, etc. Perhaps you deleted one of the duplicate teams listed in the rankings? As of now, [Basic Team Mode](https://crowdpurr.zendesk.com/hc/en-us/articles/360015360111-Team-Trivia-Explained) is designed to have _one_ device playing with other team members assisting not using their devices. It’s not meant to for multiple devices and adding additional devices will result with duplicate team names, unless **Allow Participants To Sign Back In** is used correctly. This isn’t recommenced though and we’re currently working on a more robust solution. For now, if you limit Basic Teams to a single device, per its design, you won’t have this issue. If you want everyone to play on their device on a team, use [Advanced Team Mode](https://crowdpurr.zendesk.com/hc/en-us/articles/360015360111-Team-Trivia-Explained). This is what this is designed for. There’s another thread going here where we’re discussing a solution to the duplicate teams issue with Basic Team Mode, [Improved Basic Team Mode - Follow Along Participants](https://community.crowdpurr.com/t/improved-basic-team-mode-follow-along-participants/285). --- _[View the full topic](https://community.crowdpurr.com/t/solved-points-wagering-flaws-teams-select-all-but-not-all-are-wagered/418)._