Webinar Follow-Up Email: 4 Templates for B2B Teams

A webinar follow-up email should deliver what the recipient expects from the session and use only the context you can verify. Send a replay to a registrant who missed the event. Give an attendee the material you promised. If someone asks a specific question or requests a conversation, reply to that request directly. Each of those emails has a different job.

Here are four templates for a B2B webinar, plus the handoff a salesperson needs to continue the discussion. The fictional examples follow a session on reducing duplicate purchase orders. Change the names, facts and resource links before sending.

Start with the action the recipient took

In Great Events, Mastercam’s Sarah Jordan Usher describes a post-webinar recap that gives the revenue team context from questions, chat and audience segments such as owners and software users. She also describes a separate thank-you email with the recording. Her team was still working on connecting event activity to pipeline outcomes at the time of the interview. The episode explains the process and its limits; it gives no reliable conversion estimate for these templates.

You can adapt the distinction with a short decision list:

1. Registered and missed it. Offer the recording and point to a useful section. Leave room for attendance data to be incomplete.
2. Attended, with no request. Deliver the promised material. Thank the person for attending only if the record supports it.
3. Asked a question. Answer the question, mention any uncertainty and offer a way to clarify it.
4. Requested a conversation. Arrange the conversation on the topic they named. Use the existing account owner if there is one.

For each person, check what contact and event data you may use before you send anything. A roster identifies an event relationship. It does not settle whether a promotional sequence is appropriate. Keep event delivery and any later prospecting in separate queues so people can review them independently.

Template 1. Replay for a registrant who missed the session

Subject: Replay: preventing duplicate purchase orders

Hi Jordan, the recording from our purchase order webinar is ready. The walkthrough on identifying a duplicate starts at the reconciliation example. It shows the fields we used to tell two orders apart.

You can watch the replay here: REPLAY LINK.

Thanks for registering,
Casey

Use a chapter link or an accurate timestamp when you have one. If attendance is ambiguous, “Thanks for registering” works without calling anyone a no-show. Check that the person can open the replay and that the link points to this session.

Template 2. A thank-you with the promised worksheet

Subject: The worksheet from the purchase order webinar

Hi Sam, thanks for joining the session on duplicate purchase orders. Here’s the worksheet we showed: WORKSHEET LINK.

Start with a single supplier and check whether the same order can arrive through two different channels. The first column records the source so you can see where the duplication starts.

Thanks,
Casey

Mention one thing the person can do with the resource. A long recap can bury the attachment. If you never promised a worksheet and do not have one, point to the useful part of the replay. Avoid implying the attendee showed interest in a specific product feature simply by watching.

Template 3. An answer to a question

Subject: Your question about amended purchase orders

Hi Taylor, you asked how to tell a revised order from a duplicate. In our example we keep the original order ID and look for a separate revision field. That works when the purchasing system preserves both values.

If your export reuses the same row for each revision, the example may need a different check. Does your export include a revision number?

Thanks,
Casey

The answer comes first. The final question helps resolve the remaining uncertainty. Check the original wording before referring to it. If the question was anonymous, share the answer in a general recap rather than guessing the author. If a reply concerns an existing support issue, route it to the team that can resolve it.

Template 4. An explicitly requested conversation

Subject: A short walkthrough of your purchasing export

Hi Morgan, thanks for asking to walk through the order revision example. We can spend a short call looking at the export columns and decide whether the worksheet fits your process. Is Tuesday morning or Thursday afternoon better for you?

Thanks,
Casey

Confirm what the person asked for. A poll response such as “send me the slides” calls for the slides. A request to discuss a workflow can justify an invitation. Both may sit next to each other in the export, so preserve the wording that makes the difference.

Give sales a reason to write

For a requested conversation, write one row with the event, contact, observed action, exact request, existing owner, open question and proposed next action. For example: “Purchase order webinar, Morgan, asked for a walkthrough of an export, account owner Casey, revision field unknown, offer a short call.” If the action came from someone else at the same company, name that person separately. Company fit can help decide who owns a follow-up. It does not tell you which employee asked for it.

Set a deadline your team can actually meet. Deliver replay and promised resources once they are ready. Assign an owner when a question needs an answer. You can acknowledge a request before a specialist has the answer. If marketing and sales will both write, put the sending owner and purpose on each task so they do not ask for the same thing twice. The lead nurturing guide covers longer paths once the event follow-up is complete.

Measure the next action you can observe

Separate replay sends, questions answered, requested conversations booked and conversations held. Use the number of people eligible for each action as its denominator. A booking count divided by all registrations can hide whether the team responded to people who actually requested help. If contacts later enter a pipeline, check that you can link the records and distinguish an event touch from evidence of what caused the purchase.

Before you start a new outreach sequence, review the outcome of the first message. If the promised resource was delivered and the recipient asked for nothing else, you have completed a useful follow-up. For contacts who agree to explore a real problem, use discovery questions to plan the next conversation.