Bot commands in the WhatsApp group
Full reference of Torneyo's commands in the class group: /vou, /lista, /sortear, /placar, /gol, /ranking, /pix, /novo and the rest, with who can use each one.
After connecting the group with a code, Torneyo answers commands typed in the group. A command is any message that starts with / or !, in any letter case (/VOU, !vou, /nãovou). The bot also accepts a mention in front (@Torneyo /vou), the /vou@bot suffix and trailing punctuation (/vou!). Text that doesn’t start with / or ! is ignored.
Who’s who to the bot
The bot identifies each person by the phone number on their class registration, never by name or by the text of the message.
| Role | Who | What they can do |
|---|---|---|
| Participant | Anyone in the group, registered or not | /proxima, /ajuda, /cadastro, /vincular |
| Linked athlete | Phone number matches an active enrolment in the class | Everything above, plus attendance, list, teams, rankings, /pix and /devo |
| Organizer | Organization manager on Torneyo (owner, administrator or manager, matched by the user’s phone number) or admin of the WhatsApp group | Everything above, plus the management commands |
Anyone not registered receives, once per hour, the public session link to answer by name. If the same phone number appears in more than one registration (a parent with two children, for example), the bot asks them to use the link.
By default, a WhatsApp group admin can use the operational commands (/sortear, /fechar, /abrir, /novo, /cor, /convidado), but /placar and /gol, which feed the rankings, require an organization manager. The platform administrator can enable permissive mode.
Attendance
| Command | Who | What it does |
|---|---|---|
/vou | athlete | Confirms attendance for the next game. Honors spots, waiting list, an active suspension and pending rulebook acceptance. With no argument, keeps your current position; on the first confirmation, anyone registered as a goalkeeper takes a goalkeeper spot. |
/vou goleiro | athlete | Asks for a goalkeeper spot (/vou linha asks for an outfield spot). |
/vou churrasco, /vou jogo, /vou tudo | athlete | Picks the event when there is more than one on the day. Just /vou with two open events returns a numbered menu; reply 1, 2 or 3 within 2 minutes. |
/naovou (/nao vou, /nao) | athlete | Marks you as not coming, even while suspended. If there was a waiting list, the first in line moves up and the group is told. |
/lista (/list) | athlete | Confirmed players numbered with the time, goalkeepers, waiting list, spots left, pending, who’s not coming and the link. /lista churrasco details one event. Repeated within 60 s, it’s ignored. |
/meus (/status) | athlete | Your status in each event of the day. |
/proxima (/proximo, /next) | anyone | Date, time, venue, confirmation deadline (or “confirmations closed”) and the session link. |
/ajuda (/help, /comandos, /ayuda) | anyone | Lists the commands; the organizer also sees the management ones. |
/vou with text the bot doesn’t understand (for example /vou can't make it) does not confirm: the bot asks whether you meant /naovou.
Registration
| Command | Who | What it does |
|---|---|---|
/cadastro First Last (/registro, /register) | anyone | Requests your own registration in the class. It becomes a request under Pending registrations for the manager to approve. Letters only in the name; the phone number comes from WhatsApp. |
/cadastrar | organizer | Replies in the group with the number of pending registrations and the dashboard link. If anyone else sends /cadastrar Name, it counts as /cadastro. |
/vincular CODE | whoever has the code | Links the group to the class. It’s the only command accepted in a group that isn’t linked yet. |
Game and post-game
| Command | Who | What it does |
|---|---|---|
/sortear [n] | organizer | Draws 2 to 6 teams (default 2) from the confirmed players of the current game, balanced by teammate ratings and attendance. Same confirmed players = same draw. Only in pickup-game or standalone-class types. |
/times (/teams) | athlete | Reposts the latest draw and the score, if already recorded. |
/cor <team> <color> | organizer | Shirt color of a team (/cor 1 azul, /cor time2 sem colete). With no arguments, lists the colors. Palette: white, black, blue, red, green, yellow, orange, vest, no vest, or a free-form name. |
/fechar [nickname] | organizer | Locks confirmations for the current game (or for the event with that nickname). Applies to the group and to the link. With the list closed, the waiting list promotes nobody. |
/abrir [nickname] | organizer | Unlocks confirmations and re-evaluates the line. If the original deadline has already passed, the bot says so. |
/convidado Name | organizer | Adds someone without a registration to the game, by name only. Gets in if there’s a spot; otherwise joins the waiting list. Stays out of rankings and billing. |
/placar 3x2 | organization manager | Records the score on the reference draw (one number per team, in team order). A different score already saved is only replaced with /placar 3x2 confirmar. |
/gol Name [assist OtherName] | organization manager | Logs a goal and, optionally, an assist on the day of the reference draw. With repeated names, the bot asks “Which João? 1) … 2) …” and you reply with the number within 2 minutes. |
/craque (/mvp) | athlete | Link to the MVP vote for the latest game (open from kickoff until 48 h later). |
The current game for /sortear, /fechar and /abrir is today’s game that started less than 4 hours ago (or is still to start); failing that, the next one. The reference draw for /times, /placar and /gol is the most recent one up to today (3-day window); if there is none, the nearest upcoming one.
Opening a list from the group
| Command | Who | What it does |
|---|---|---|
/novo [day] [time] [nickname] | organizer | Opens the list for a game (/novo sexta 20h, /novo 12/10 19h30) or for an extra event (/novo churrasco sábado 14h). With no day or time, opens the next slot in the schedule. Synonyms: /novalista, /novoencontro, /abrirlista, /encontro, /nova. Future dates only, up to 60 days ahead; at most 2 games and 3 extra events per day. |
Rankings and money
| Command | Who | What it does |
|---|---|---|
/ranking [type] [mes|ano|tudo] | athlete | Top 5 of a class ranking: presenca, palavra, artilharia, assistencia, vitorias, aproveitamento, craque, parceria, evolucao. With no type, this month’s attendance. |
/artilharia [ano|tudo] | athlete | Top 5 scorers of the month. |
/devo (/owe) | athlete | Privately: what you owe in the class (items, overdue, total). The group only sees “I sent it to you privately”. |
/pix | athlete | Privately: the copy-and-paste Pix for what you owe, with the class’s key. With no key set up, it tells you to talk to the organizer. |
Limits and privacy
- Each person can send up to 6 commands per minute; the group receives at most 40 replies per minute. Beyond that, the bot goes quiet.
- Commands delayed by more than 3 minutes (WhatsApp with no signal, for example) are ignored so nobody is confirmed out of time.
/vincularwith a wrong code 5 times blocks that sender for 15 minutes.- The bot never posts phone numbers, amounts owed or suspension reasons in the group. The text of a command isn’t stored, even with message reading turned on.
- Replies come out in the organization’s language (Portuguese, English or Spanish).
FAQ
I sent /vou and the bot replied with a link. Your phone number isn’t on the class registration, or it’s on more than one. Ask the manager to check under Group members, or just confirm through the link.
The bot stopped answering. Check the connection status on the Sessions screen. If the group is paused (“Pause posts”) or unlinked, the bot stays silent. The class keeps working through the link.
Does pausing posts also silence the commands? Yes. Pausing turns off everything Torneyo does in that group.