Clay logo, go to homepage

Search Marketplace

Browse all Skills

Webinar Followup Router

The webinar-followup-router skill efficiently routes webinar and event registrants into tailored follow-up branches based on attendance, account qualification tier, and account status.

About this Skill

When to use it

This skill is essential when you need to follow up on a webinar or event and want to ensure that each registrant receives the appropriate communication based on their attendance and account status. It helps avoid the common pitfalls of generic follow-up emails that fail to consider the nuances of each registrant's situation. Use this skill to segment your event registrants accurately and draft personalized outreach that reflects their engagement and account status.

What it delivers

The skill produces a detailed draft for each registrant, including their attendance status, account qualification tier, and account status. It unlocks the decision-making process for who should send the follow-up emails and what the content should be, ensuring that each email is relevant and appropriately addressed. The boundaries of this skill are defined by the exact field reads it requires, ensuring that no assumptions are made about the data.

SKILL.md preview

Sign in to install and view the complete SKILL.md

Illustrative preview. Sign in for the actual file.

How someone would prompt this

Please follow up on my webinar and segment the event registrants accordingly.

Other ways to ask

Inputs & outputs

What someone provides before the Skill runs, and the reviewable artifacts it returns.

Inputs

  • 01The registrant list
    • Provide one row per person from the event, including an email and an account or company identifier
    • if missing, there is nothing to route.
  • 02Event context
    • Include session title, date, recording or replay link, and key topics covered
    • if missing, the copy will be generic and the deliverable will be worthless.
  • 03Attendance field
    • Specify which field distinguishes attended from registered-no-show, and which values mean each
    • if missing, every email will open with a false claim about attendance.
  • 04Qualification field, and the disqualifying values
    • Identify the field holding the account's tier or qualification band, and specify disqualified values
    • if missing, the skill will ask for clarification.
  • 05Account-status source
    • Provide how net-new, open-opportunity, and existing-customer statuses are determined
    • if missing, the owned-account arm cannot be separated from the rep arm.
  • 06Sender per arm
    • Specify for each arm either a named mailbox or a per-account lookup
    • if missing, there will be no default sender.
  • 07CC per arm, and why
    • Identify who is copied on each arm and the reason
    • if missing, the output will indicate which arms have no CC.
  • 08Precedence between account status and tier
    • Clarify which takes precedence when an existing customer is in a disqualified tier
    • if missing, the skill will check account status first.
  • 09The messaging source of truth
    • Indicate where the event's messaging already exists
    • if missing, the copy will be built from the event context.
  • 10Segments that get no email
    • Specify which segments, if any, are handled differently
    • if missing, the skill will assume every segment gets an email.
  • 11Where the copy lands
    • Indicate where drafts will be sent for review
    • if missing, the skill will default to drafts for review.

Outputs

  • 01Routed Registrant ListA detailed list of each registrant, including their attendance status, qualification tier, account status, and the assigned follow-up sender.
  • 02Drafted Follow-Up EmailsPersonalized email drafts for each segment, tailored based on attendance and account status, ready for review before sending.
  • 03Held Rows ReportA report detailing any registrants that could not be processed due to missing information, including reasons for holding each row.
  • 04Sender and CC AssignmentA summary of who is assigned to send the follow-up emails and who is copied on each email, based on the defined routing logic.
  • 05Precedence Order SummaryA statement of the precedence order used for routing, clarifying how account status and qualification tier were evaluated.

Representative output

Routed Registrant List

EmailAttendanceQualificationAccount StatusSender
john@example.comattendedqualifiedcustomeraccount_owner@example.com
jane@example.comno_showdisqualifiednet_newshared_mailbox@example.com

Drafted Follow-Up Emails

EmailSubjectBody Preview
john@example.comThanks for Attending!We covered X, Y, and Z. Let's connect!
jane@example.comSorry We Missed YouHere’s the replay link for your review.

Held Rows Report

EmailReason for Hold
unknown@example.comMissing account match
no_tier@example.comMissing qualification tier

Sender and CC Assignment

ArmSenderCC
owned_accountaccount_owner@example.comaccount_manager@example.com
net_new_qualifieddevelopment_rep@example.comnone

Precedence Order Summary

  • Account status was checked before qualification tier.

How the Skill runs

Follow the steps in order. Each row includes the full instruction.

01
Confirm the platform, and say where the work runs

Confirm the platform and specify where the work runs, ensuring that the workspace is identified before proceeding.

Step
02
Segmentation logic, and the exact fields it reads

Clarify the segmentation logic by identifying the exact fields that will be used to segment the registrants.

Step
03
Expected behaviour for each segment

Define the expected behavior for each segment, including who sends the emails and what the email asks for.

Step
04
Copy per segment, from their source of truth first

Determine the copy for each segment based on the source of truth before writing any emails.

Step
05
Read the axes off fields, and let unknown be an answer

Read the axes off fields to ensure accurate segmentation, allowing for 'unknown' as a valid response.

Step
06
Collapse to routing arms; first match wins, in this order

Collapse the data into routing arms based on the defined precedence, ensuring that held rows are reported.

Step
07
State the cost, and wait

State the cost of prose generation and obtain approval before generating the emails.

Step
08
Generate the copy: attendance sets the opening, the arm sets the ask

Generate the copy for each routed row, ensuring that the content aligns with the established parameters.

Output
09
Deliver one row per person, with the reason attached

Deliver one row per person, including all relevant details and a coverage report for review.

Step
10
Hand off; never send

Hand off the drafts to the specified location without sending any emails.

Action

Connections required

Clay CLI / agent pluginRequired connection
CRMRequired connection

Install Clay and run it

Sign in once, install the Skill, then run the prompt.

  1. 1Install ClayUse the connector or official plugin in your coding-agent environment.
  2. 2Sign up or log inAuthorize Clay access and return when the connection is ready.
  3. 3Install the SkillRun the one-line install command from the Add this Skill card.
  4. 4Run the SkillPaste the example prompt and review the result.

Version history

Version 3From submitted SKILL.mdCurrent

Related Skills

Related searches