Hire an AI event follow-up planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• Follow-up groups: people grouped by what they asked for, with the reason to write to each group
• A promise register: each promise with owner, due date and the note it came from
• One unsent email draft per group or promise, with its source
• A hold list: people not to contact, with the reason
• A hand-back summary with one next step

How it does the job well

• Attendance is not permission for unrelated marketing. A person who did not agree to contact and asked for nothing goes on the hold list.
• Never invent a promise, an attendee request, a date or a number. Use the notes only.
• Every draft states what was promised or asked, and one next step. Do not attach a file or link that was not supplied.
• Keep private details out of the files unless they are needed for the draft.
• Write for one named audience and one action. Each asset has a single job.
• Use the customer's own words from reviews, calls or surveys before inventing language.
• Every claim needs proof the business can show. Leave unproven claims out or mark them.

Mistakes it avoids

• Generic copy that could fit any brand.
• Comparing periods or campaigns that are not comparable, such as different dates, budgets or tracking.
• Calling a test winner before there is enough data.

What a good result looks like

An example, not your task: You came back from a trade show or conference with a pile of cards and notes and promised to send things

• Follow-up groups. Attendees grouped by what they asked for, with the reason to write to each group.
• action-register.csv. Each promise with an owner, due date, status and the note it came from.
• follow-up-drafts.md. One unsent draft per group or promise, with subject, body and source.
• draft-ledger.csv. The version and state of each draft, so you know what is still unsent.
• Hold list. People not to contact, each with the reason.
• Hand-back summary. Files saved, MISSING facts, checks not done and one next step.

How the work is checked

• Every draft names what was asked or promised, and has one ask.
• Every promise in a draft is in the register, with an owner and a source.
• Every recipient has permission or asked for follow-up. The rest are on the hold list.
• Nothing is marked sent. Every draft is labelled as a draft.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Event marketing planner. Groups follow-up needs around the event goal and what each attendee asked for. It hands on the groups and the reason to contact each one.
• Executive action register keeper. Pulls every promised file, introduction and follow-up from your notes, with the note it came from. It hands on a register with owner and due date.
• Due task follow up drafter. Writes a draft for each supported promise or group. It does not send, and it lists missing facts and approvals. It hands back drafts and a ledger.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id plan-an-event-follow-up-that-earns-a-reply only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/plan-an-event-follow-up-that-earns-a-reply/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your attendee list with names, emails, what each person asked for and whether they agreed to be contacted (a consent column)
• Your dated notes from the event: who you met and what you promised
• The event name, date and goal, from the agenda or invitation
• How each person prefers to be contacted (optional)
• A past follow-up email in your voice (optional)

Helpful context (optional)

• Photos or typed notes of business cards, with the date you met.
• A teammate who can confirm who promised what.

Tools and access

• Claude, ChatGPT or Gemini with file support: They read your list and notes and draft emails. They draft only. You review and send from your own mail.

Functions and deliverables

• Event follow-up planner: Share attendee requests, promises and contact preferences. Get follow-up groups, a commitment list and message drafts for review.
  • Follow-up groups: people grouped by what they asked for, with the reason to write to each group
  • A promise register: each promise with owner, due date and the note it came from
  • One unsent email draft per group or promise, with its source
  • A hold list: people not to contact, with the reason
  • A hand-back summary with one next step
• Event marketing planner: Turn your event role, goals, audience, and budget into an outreach and follow-up plan.
  • Event plan with before, during and after steps
  • Target list approach
  • Outreach message ideas
  • Follow-up sequence
  • Ways to judge event return
  Source: Corey Haines.
• Action item tracker: Share meeting notes or email threads. Get action items with owners, deadlines and unresolved commitments.
  • action-register.csv: id, task, owner, due_at, timezone, status, depends_on, source_id
  • clarifications.md
  • proposed-task-changes.md
• Task follow-up writer: Share dated tasks and their message threads. Get recipient-specific follow-up drafts, missing facts and a clear draft/sent status.
  • follow-up-drafts.md with task ID, thread ID, recipients, subject and body for each draft
  • draft-ledger.csv with the version, state and message ID of each draft
  • A list of missing facts and approvals you still need to give
  • A short close with source coverage and one next step
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one

Tasks you can use it for

• You came back from a trade show or conference with a pile of cards and notes and promised to send things
• You hosted a webinar or workshop and want replies from the people who asked questions
• You told three people "I'll introduce you" and want to be sure that happens
• A teammate met the leads, and you need to follow up from their notes, not from memory

Limits to check before starting

• You have no event, only tasks due from email threads. Use Task follow-up and voice editor.
• You want a multi-email sequence over weeks, after the first reply. Use the Follow-up email sequence writer.
• You want to plan the event itself, before and during. Use the Event marketing planner.
• You want to write to people who did not attend but showed interest. Use Information offer and lead follow-up writer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the handoff pack. It is a zip with HANDOFF.md and every skill file this workflow uses.
• Give the folder to Claude, ChatGPT or Gemini and say "Follow HANDOFF.md".
• Share the attendee list and your notes. Add a consent column if your list has none.
• Read the promise register first. Fix any wrong owner or date, and finish the ones that depend on you.
• Edit the drafts in your voice and send them yourself. Nothing is sent for you.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/plan-an-event-follow-up-that-earns-a-reply for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.