Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mavrodi.org/llms.txt

Use this file to discover all available pages before exploring further.

Your structure is the group of participants you are responsible for. Managing it well means staying on top of pending Intents and Help Requests, keeping participant data accurate, and being reachable when someone in your group needs help. This page covers the commands you use most often as part of that daily work.

​
Viewing your participants

Start by knowing who is in your structure and what state they are in.
CommandWhat it returns
/usersActive participants in your structure
/users_allAll participants, including inactive
/users_blockedParticipants with blocked status
Use /users_all when you need to find someone who has gone quiet or check the full size of your group.

​
Reviewing Intents

When a participant in your group submits an Intent — a declaration to give a certain amount of help — it lands in your queue for approval. 
/intents @username
/intents TGID
Both forms work: use the Telegram username or the participant’s numeric Telegram ID. The command returns all Intents for that participant with their current statuses (New, Active, Partially confirmed, Fully confirmed, Rejected, Refused).
There are four Intent types you may encounter: standard (intent), bonus (bonus), re-providing (passon), and system (system). Standard Intents come from participants. Bonus and re-providing Intents are created by Guiders. System Intents are created by Thousanders and administrators only.

​
Reviewing Help Requests

Help Requests (Asks) from your group members require your approval before the system processes them. Use /asks to see what is waiting for you. 
/asks
Shows pending Help Requests from participants in your immediate (first-line) group. This is your primary review queue.

​
Setting Help Request priority

For System Help Requests, you can adjust processing priority (0–9, higher runs first): 
/ask_1234567_priority_5
You can also run /ask_1234567_priority without a number and the bot will prompt you to enter one.

​
Viewing Orders

Orders connect Intents with Help Requests and represent the actual transfer between participants. 
/orders @username   — Orders involving a specific participant
/orders my          — Orders where you are the Guider responsible
For a detailed explanation of what each Order status means and what actions you can take at each stage, see Order lifecycle.

​
Moving participants between structures

If a participant needs to be reassigned to a different Guider’s structure — because they moved, their Guider is unavailable, or for any other reason — use the /move command. The command starts an interactive flow where you specify the participant and the destination structure. 
/move
Moving a participant transfers all their pending Intents and Help Requests to the new Guider’s review queue. Confirm with the receiving Guider before moving.

​
Editing participant information

Sometimes you need to update or correct information on behalf of a participant.
CommandWhat it edits
/setUniversal field editor — opens an interactive menu to edit any supported field
/nameDisplay name
/emailEmail address
/phonePhone number
/aboutShort profile description
/cardAdd or update a payment card on behalf of the participant
/stageChange the participant’s current onboarding scenario stage
Use /set when you are unsure which specific command to use — it covers all editable fields in one place.

​
Managing statuses

To change a participant’s status (for example, to promote someone or to block a problematic account), use: 
/status
The command opens an interactive flow. Status changes take effect immediately and affect what the participant can do in the system.

​
Communicating with participants

/send
Sends a message to one or more participants in your structure. Use this for important updates or when you need to reach someone directly through the bot. 
/admin
Sends a message to an administrator. Use this when you need to escalate an issue that is beyond your authority as a Guider. 
/report
Submits a feedback report. See also /tickets_add_report below for rewarding participants who submit video reviews.

​
Connecting with participants in Telegram

To confirm or manage the bot-level link between your Guider account and a participant’s account: 
/connected_userid    — Confirm the Guider↔Participant link in Telegram
/disconnect_userid   — Sever the link between your account and the participant
These commands are useful when a participant has switched devices or Telegram accounts.

​
Managing invite codes

Your structure grows when new participants join through your invite links. To generate additional invite codes for your group: 
/invite

​
Handling lost contact

If a participant has not responded and appears unreachable, they can be reported as lost. Use the following to track these cases: 
/losts          — List of /lost claims you have submitted or that involve your participants
/losts_all      — All unresolved /lost claims across your entire structure

​
Welcome message for new participants

You can customize the message new participants receive when they join your structure: 
/intro           — Set the welcome message text
/intro_delay     — Set how many seconds to wait before sending the welcome message
A good intro message sets expectations: what the participant should do first, how to reach you, and what the system does. Keep it short and action-oriented.

​
Log chat

/set_chatlog
Connects a private Telegram group or chat as your personal activity log. Once set, the bot forwards notifications about your structure’s activity there, so you have a searchable record of approvals, rejections, and status changes.

​
Checking a participant’s financial outcome

/outcome
Shows whether a participant is in a positive financial position (they have given more than they received), negative, or has not yet provided any help. Use this when assessing whether someone’s Help Request is reasonable given their history.

​
Rewarding video reviews

If a participant submits a video review of their experience, you can grant them 2 Tickets as a reward: 
/tickets_add_report

​
Backfill: retroactive data entry

If Intents or Help Requests were created or fulfilled outside the bot (for example, in an earlier period or through a manual process), you can enter that data retroactively: 
/ia
The /ia command opens an interactive flow for backfilling Intent and Help Request records. Use it only when you have confirmed information that needs to be entered — not as a workaround for live transactions.

​
Payment methods

To view or add payment methods (banks or crypto services) associated with your structure: 
/banks       — View available payment methods
/bank_add    — Add a new payment method