How a training session works
เนื้อหานี้ยังไม่มีในภาษาของคุณ
When someone sends /train, they get a session — a couple of minutes of work with a clear start and a clear end. Not a whole lesson dumped in one message.
The rule
A session is capped at six pieces. Coming back tomorrow is how it’s meant to work.
How it works
- The bot opens with what’s coming: “Wine service · 2 min · 3 questions”, and a Start button. Your team knows what they’re agreeing to before anything arrives.
- An idea arrives on its own — 40 to 80 words, one point, nothing else. They press Got it when they’ve read it.
- Then a question about that idea. They tap an answer and the message turns into the verdict, with the reason.
- Two or three more of those, then a closing card: their score, and what’s left in the course.
Nothing arrives until they’re ready for it. Pressing Got it is what brings the next piece — so a session moves at their pace, standing at the pass, not all at once.
Good to know
- Questions come in three shapes now — pick the answer, true or false, and “which of these is wrong”. Mixing them makes guessing much harder.
- They can stop any time. Send /train again within twelve hours and it picks up exactly where they left off.
- Nothing is asked twice. A question they’ve already answered never comes back in a new session.
- A course takes several visits, on purpose. That’s how things are actually remembered.
- Everything they’ve already done under the old style still counts — nobody restarts.
Related features
- Writing a course — where the lessons and questions come from.
- Reading the results — how your team is doing.
- The morning nudge — the gentle reminder that opens a session.