Guankeyun
When a livestream has many reservations but few attendees, do not assume that everyone who missed it has lost interest. Separate reservations, actual viewing, interaction, and follow-up responses, then send one useful message based on what each person has actually done. A reservation is a signal of interest, not a promise to attend. The purpose of follow-up is to make it easy to catch up or ask a question, not to keep pressing the viewer.
Count reservations and attendance separately
At minimum, record the number of reservations, actual room entries, the viewing-time measure you use, viewers who interacted, and later inquiries or purchases. First confirm the definition and scope of each figure. A reservation may come from a Mini Program subscription, a registration form, or a group list; actual viewing should come from the session data available in the current admin interface. Delivery of a group message, a link click, and entry into the livestream are different actions.
Guankeyun’s materials describe Mini Program subscription reminders, a livestream data dashboard, and user tags. The fields, export options, and update timing available to a particular account still need to be checked in the current admin interface. If a data point is not available, mark it as unknown in your operations sheet rather than estimating it. Review the livestream launch tools and user operations features, then use a test session to verify what is actually available.
Group viewers by actions that actually occurred
The first group entered the livestream and watched at least part of it. If a replay exists and the current viewing permissions allow it, share the replay link with a short guide so viewers can find the relevant section. Do not promise that a replay will always be available, and do not send its link to every registrant before checking its access settings.
The second group reserved a place but did not enter the room. Send one concise recap describing the session topic, whether a replay is available, and the approximate timing of the next event. Offer clear choices such as “send me the replay,” “tell me about the next session,” or “not needed for now.” If the person does not respond, stop following up. A third group consists of people who asked a question or requested contact. Route each request to an owner, note what has already been answered, and avoid duplicate outreach from several colleagues.
Base these groups on observed behavior, not a guess about motivation. Someone may miss a session because of a schedule conflict, an unseen reminder, an unexpected commitment, or a mismatch with the content. One absence does not reveal the reason. If the team uses tags, record states such as “reserved, did not attend” or “watched and asked a question” only when the current account supports those fields. Otherwise, a controlled internal sheet is enough; restrict access and remove stale information regularly.
Make the follow-up useful on its own
A message should contain only information relevant to the session: a one-sentence recap, a verified replay or inquiry link, and an easy way to express the viewer’s preference. Avoid combining a long sales pitch, several links, and the next promotion in one message. If no replay was created or it cannot be shared, say so and offer a written summary or the next event time instead.
Your team can choose a follow-up cadence that fits its service process—for example, finishing the first review on the next business day. That is an operational suggestion, not a platform rule. Record and respect a clear request not to be contacted. Avoid setting an automation to repeatedly message every registrant regardless of their choices; the larger the list, the more important it is to check the audience, content, and opt-out handling first.
Use the next session to evaluate the follow-up
Do not judge the process only by the number of messages sent or replay clicks. Track how many invited viewers actively choose to watch later, ask a specific question, reserve the next session, or decline further contact. Compare sessions using the same definitions. With a small sample, record the change without rushing to a causal conclusion. If the topic, time, and reminder process all changed at once, you cannot tell which change made the difference.
Keep a one-page review after each session: reservation source and definitions, attendance, known feedback from people who missed it, what you sent, the responses, and who owns the next step. Store only what is needed to complete the follow-up. This helps the team improve scheduling and reminders without turning one absence into repeated unwanted contact.