# Event Follow-Up CRM Playbook | 121 CRM > 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. ## Event follow-up: the working sequence Illustrative playbook — names, organisations and activity are fictional. ## Capabilities explained ### 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 a business would use it:** Fits shared seminars and events where the event matters more than an assigned staff member. **Limitations:** 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. **Human responsibility:** Staff must handle exceptions, incorrect availability and bookings that need judgement. ### 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 a business would use it:** Lets a business communicate with a defined customer group and measure supported engagement. **Limitations:** Platform policies, connection expiry, delivery, public responses, usage and add-on charges can vary. **Human responsibility:** A person must approve content and handle negative feedback, policy issues and publishing failures. ### 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 a business would use it:** Lets teams focus on a working group without maintaining separate copies of the same contacts. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### 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 a business would use it:** Turns the next step into owned work instead of leaving it inside notes or inboxes. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ## 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. ### Accountable owner Name the person or queue that accepts the work, monitors exceptions and can stop 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. ### 5. Close the event workflow Respect opt-outs and move active conversations to named owners. ## 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. ### Attendance uncertain Avoid claims such as “thanks for joining” until the record is reconciled. ### Question needs expertise Assign it to an appropriate person instead of answering automatically. ### Resource delayed Send an honest update rather than a broken or invented link. ## 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. ## Frequently asked questions ### 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. ### 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. ### 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. ### 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. ## Related CRM pages - [/crm/guides](https://121.direct/crm/guides) - [/crm/guides/customer-follow-up-automation](https://121.direct/crm/guides/customer-follow-up-automation) - [/crm/features/calendar-management](https://121.direct/crm/features/calendar-management) - [/crm/features/email-marketing](https://121.direct/crm/features/email-marketing) - [/crm/features/contact-segmentation](https://121.direct/crm/features/contact-segmentation) - [/crm/playbooks/inbound-call](https://121.direct/crm/playbooks/inbound-call) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.