How a request is handled

Who is this for

Sales people and partners who work the requests in the Telegram group. No technical knowledge needed.

TL;DR

A request from the landing page appears in the sales group as a card with buttons, within seconds.
Take it by pressing In work; update the status as you go. Every press is recorded with your name and time.
A card nobody touched for two hours gets one reminder during working hours; every morning at 10:00 there is a digest.
A message that starts with “⚠️” is a fallback request: it is real, but it is not in the database and has no buttons — handle it by hand and tell the team.
If a person asks to delete their data, an admin runs one command.

What the organiser does

Opens the landing page at pack.eventtalks.uz in Russian, Uzbek or English.
Fills in the form: name, Telegram username and phone are required; event date, approximate number of guests and a comment are optional.
Sees “Request sent”. The same browser can send a new request a day later.

Under the button the form states that sending it means agreeing to the processing of contact details in order to reply.

What appears in the group

A card looks like this (texts are in Russian in the real group):

🆕 Request #stickers_42 · AI Sticker Pack

👤 Guest Name
✈️ @example_user
📞 +<digits>
📅 mid-December, evening
👥 200–300
💬 Company party, we want a branded station

🌐 ru · utm_source=instagram
🕒 date and time, Tashkent

Status: 🆕 new

Empty fields are not shown.
#stickers_42 is a hashtag: search the group for it to find the card again.
The username is a link; the phone number is tappable in Telegram clients.
The line with the globe shows the page language and the advertising source, if the visitor came from a tagged link.

Under the card there are five buttons.

Button	Status	Use it when
🔧 In work	`in_work`	You are taking this request
📞 Contacted	`contacted`	You have spoken or written to the person
✅ Deal	`deal`	The event is agreed
❌ Refused	`refused`	The person declined or it is not a fit
🚫 Spam	`spam`	Not a real request

The five statuses can be changed to one another in any order; there is no way back to “new”. The card shows the current status and the last changes with names and times.
Only people on the lead-admin list can press. Anyone else gets “no access” and nothing changes.
Pressing the status that is already set changes nothing.

Working rhythm

When	What the bot does	What you do
A request arrives	Posts the card	Press In work, contact the person, press Contacted
A card stays new for 2 hours	Replies to it once: nobody has taken it yet. Only Monday–Friday, 09:00–21:00 Tashkent time; a night or weekend request is reminded at the next working 09:00	Take it
Every day at 10:00 Tashkent	Posts a digest: new requests in the last day, cards still without a status, packs generated. Skipped when all numbers are zero	Clear the “without status” list
The same person writes again within 24 hours	No new card. The existing card is updated with a “repeat request” block showing what changed, and the bot replies to it	Read the new details on the same card

Commands for lead admins

Typed in the group. Choose them from the bot’s menu, which group admins see.

Command	Result
`/stickers_new`	The list of requests still without a status, oldest first, with contacts
`/stickers_lead <number>`	Posts that card again with its buttons. Without a number: pick from the last five
`/stickers_stats`	Totals by period, status, language and advertising source, plus packs generated
`/stickers_export`	Sends a spreadsheet file of all requests to your private chat with the bot. Open the bot and press Start once beforehand, or it cannot write to you
`/stickers_forget <number>`	Removes the person’s data from that request. Without a number: pick from the last five

Full reference: Bot commands.

Fallback requests

If the leads server does not answer the landing page in time, the page sends the request straight into the group so it is not lost. Such a message:

starts with a warning line saying the leads server did not answer and that the request is not in the database, with its request id;
is plain text with the same fields, without buttons;
is not counted in statistics, reminders, the digest or the export.

What to do:

Handle it like any request — contact the person.
Reply to the message in the group with what you did, since there is no status.
Tell the engineer: a fallback message means the server was unreachable for at least a moment. Runbook: Leads missing or arriving as fallback.

Occasionally a card and a fallback message appear for the same request, with the same request id. It is one request; work the card.

Deleting a person’s data

If someone asks to delete their request data, a lead admin sends /stickers_forget <number> in the group.

Name, username, phone and comment are erased at once; the card is replaced by “data deleted”.
The request stays in statistics as an anonymous row.
Copies in server backups disappear as the backups rotate, within 14 days.
Without any action, requests are anonymised automatically 12 months after their last status change; spam after 30 days.

Who sees the contact data

Everyone in the group, including other products’ bots that are able to read group messages. Keep the group membership tight. The spreadsheet export goes only to the admin who asked for it.

From request to event

First contact: collect the points listed in How to sell.
Check feasibility with the engineer for anything above one station or a few hundred guests: Scaling scenarios.
Agree venue responsibilities and branding: Venue requirements and branding.
Hand over to the operator, who follows the Event playbook.
Mark the card Deal.

Where to go next

Client FAQ.
Lead submission flow — the technical view.
Playbook: new product — how another product joins the same group.

Last verified: 2026-11-13 against ai-sticker-pack@b715418 and ai-stickers-landing@e350ff5.