Bot setup and message handling are separate steps. BotFather creates and configures the bot; the Bot API delivers updates that identify the conversation and the sender.
Configure the bot
The original setup began with BotFather:
/newbotThe next commands controlled group joining and the command menu:
/setjoingroups/setcommandsDecide what the bot needs to see
The source also used the privacy setting:
/setprivacyThe old checklist disabled privacy mode and assigned administrator permissions. Those are capability choices, not requirements for every bot. Review Telegram’s privacy-mode behavior before giving a bot wider group visibility or permissions.
Distinguish conversation and sender
The original diagnostic requested getUpdates through a token-bearing Bot API URL. In an update’s message object, chat.id identifies the conversation, while from.id identifies its sender. A group conversation and a user are different identities.
The old response sample contained personal names and malformed JSON, so it is replaced here with the field explanation. Keep real bot tokens and captured user information outside shared examples. No bot or group was created for this revision.