121 CRM playbook · Event follow-up

Continue an event conversation with relevant context, permission and a useful next step.

A fictional training event sends attendees the promised resource, then offers an optional discussion related to the session. This playbook turns that kind of situation into an owned sequence with explicit stop points, exceptions and measures. Use only channels, data and capabilities approved for your setup.

Subscribe to 121 CRM Seller, billing and cancellationRead the automation guide

Customer Thread

Event follow-up: the working sequence

Illustrative example

Reconcile attendance
Distinguish registered, attended, cancelled and no-show records before messaging.
Segment by genuine context
Use session, question or stated interest rather than broad assumptions.
Close the event workflow
Respect opt-outs and move active conversations to named owners.
Human review
A person checks the outcome and any exception.
Human decision

Illustrative playbook — names, organisations and activity are fictional.

Fictional workflow demonstration

Event follow-up, with controls and handovers visible

The coded interface shows an example sequence using fictional data and does not expose a live CRM account.

121 CRM · Customer thread

New enquiry09:12

Northstar Joinery

Website · Commercial enquiry

“We need a clearer way to coordinate enquiries between the office and site team.”

Owner

Amina K.

Next action

Discovery call

Enquiry
Website form
01
Conversation
Reply recorded
02
Owner
Amina assigned
03
Review
Suitability check
04
Next action
Call on Thursday
05

Illustrative exampleFictional customer and activity. Exact fields, channels and stages depend on configuration.

What supports the playbook

See what the CRM can coordinate — and where your team steps in.

The CRM can organise the sequence, but the business still sets the rules, checks consent and handles the moments that need human judgement.

Capability 01

Event calendars

Creates hostless bookable events with their own availability and restricted external-sync behaviour.

How it works: Applies configured availability, booking rules and connected-calendar settings to eligible appointments.
Why use it: Fits shared seminars and events where the event matters more than an assigned staff member.
Plan for: Sync, meeting-link and resource behaviour varies by calendar type and external provider. Dynamic Zoom, Google Meet and Microsoft Teams links are not supported for hostless Event Calendars; external sync is restricted.
Your team owns: Staff must handle exceptions, incorrect availability and bookings that need judgement.

Capability 02

Email campaigns

Creates and sends configured email campaigns to eligible audiences using connected sending infrastructure.

How it works: Runs an approved campaign, publishing or reputation process through connected channels and profiles.
Why use it: Lets a business communicate with a defined customer group and measure supported engagement.
Plan for: Platform policies, connection expiry, delivery, public responses, usage and add-on charges can vary.
Your team owns: A person must approve content and handle negative feedback, policy issues and publishing failures.

Capability 03

Smart lists

Builds reusable contact views from saved filters and relevant record conditions.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Lets teams focus on a working group without maintaining separate copies of the same contacts.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 04

Tasks

Creates assigned, dated and optionally recurring actions against contacts or opportunities.

How it works: Tracks a potential deal, stage, owner or task using configured pipeline and record rules.
Why use it: Turns the next step into owned work instead of leaving it inside notes or inboxes.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

Entry criteria

Begin with a valid trigger, enough context and one owner

Attendance or registration is confirmed and the planned follow-up basis is documented. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook.

Trigger

Attendance or registration is confirmed and the planned follow-up basis is documented.

Practical scenario

A fictional training event sends attendees the promised resource, then offers an optional discussion related to the session.

Human decision retained

Accountable owner

Name the person or queue that accepts the work, monitors exceptions and can stop the sequence.

The sequence

Run the event follow-up playbook step by step

Each step should leave evidence a colleague can understand. Timing and channels should follow the customer context rather than a generic high-pressure cadence.

1. Reconcile attendance

Distinguish registered, attended, cancelled and no-show records before messaging.

2. Deliver what was promised

Send slides, recording or next steps only when approved and available.

3. Segment by genuine context

Use session, question or stated interest rather than broad assumptions.

4. Invite a proportionate next step

Offer reply, booking or subscription choices clearly.

Close the loop

5. Close the event workflow

Respect opt-outs and move active conversations to named owners.

Owner, timing and exception

Make the operational state easy to review

The supporting view keeps the next action and human checkpoint visible around the automated steps.

121 CRM · Connected operations

Book discovery

October · illustrative availability

MTWTFSS1234567891011121314

11:3014:00

Appointment sequence

Booked

Calendar entry created

1 day before

Reminder scheduled

Exception

Owner reviews a reply

Journey summary

New

Illustrative

Owned

Illustrative

Due

Illustrative

Website

Referral

Direct

Illustrative exampleAll dates, counts and workflow states are fictional. Availability and behaviour depend on the agreed setup.

Exception paths

Stop the normal route when the facts change

Exceptions are part of the process, not failures to be hidden. Route them to a person with the authority and context to decide what happens next.

Human review

Attendance uncertain

Avoid claims such as “thanks for joining” until the record is reconciled.

Human review

Question needs expertise

Assign it to an appropriate person instead of answering automatically.

Human review

Resource delayed

Send an honest update rather than a broken or invented link.

Operational review

Measure whether the work became safer and clearer

Use measures that reveal ownership, service quality and control. Counts of messages, tasks or workflow runs are supporting signals, not proof of customer value.

Promised resources delivered successfully

Check failures and access issues.

Questions with named owners

Track service completion.

Opt-outs or complaints

Review relevance and pre-event expectations.

Questions about this page

Useful answers, without the sales fog.

1. When should the event follow-up playbook start?

Attendance or registration is confirmed and the planned follow-up basis is documented. Confirm the record is eligible and that a named owner or monitored queue is available before allowing customer-facing action.

2. Which channels should the event follow-up playbook use?

Use only configured channels that suit the purpose, customer preference and consent position. Give each channel a distinct role and check provider availability and usage charges before launch.

3. When should event follow-up automation stop?

Stop when the purpose is complete, the customer responds or opts out, the data conflicts, or an exception needs judgement. In this playbook, pay particular attention to attendance uncertain, question needs expertise, resource delayed.

4. How should we judge whether event follow-up works?

Review promised resources delivered successfully, questions with named owners, opt-outs or complaints. Combine the numbers with sampled records and customer context; do not treat activity volume as a business outcome.

Read all CRM questions

Continue the journey

Calendar management Email marketing Contact segmentation Inbound-call handling

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing