# Email Enquiry Management Playbook | 121 CRM > Turn an incoming email into a visible, owned question with a useful response and next action. A fictional accountancy practice receives Noor’s email about bookkeeping support and assigns it to the new-business queue. 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. ## Email-enquiry handling: the working sequence Illustrative playbook — names, organisations and activity are fictional. ## Capabilities explained ### Email conversations Sends and receives supported email messages against the customer conversation and contact record. **How it works:** Handles an eligible customer interaction through a configured inbox, number or connected channel. **Why a business would use it:** Keeps email context visible to authorised colleagues rather than one private mailbox. **Limitations:** Delivery, message types, geographic coverage, approval and charges vary by channel and provider. **Human responsibility:** A person must own sensitive conversations, failed delivery and any situation outside the approved script. ### Conversations inbox Brings supported connected message threads into a shared operational inbox. **How it works:** Handles an eligible customer interaction through a configured inbox, number or connected channel. **Why a business would use it:** Helps a team see the customer history and coordinate replies from one working view. **Limitations:** Delivery, message types, geographic coverage, approval and charges vary by channel and provider. **Human responsibility:** A person must own sensitive conversations, failed delivery and any situation outside the approved script. ### Contacts Stores a person or lead with contact details, activity, ownership and related records. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Gives a team one place to understand who a customer is and what has happened. **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 A configured business inbox receives a genuine customer enquiry. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook. ### Trigger A configured business inbox receives a genuine customer enquiry. ### Practical scenario A fictional accountancy practice receives Noor’s email about bookkeeping support and assigns it to the new-business queue. ### Accountable owner Name the person or queue that accepts the work, monitors exceptions and can stop the sequence. ## Run the email-enquiry handling 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. Triage the message Identify customer, purpose, urgency and whether the email contains sensitive attachments. ### 2. Assign ownership Route by service and authority, with cover for absence. ### 3. Respond in context Answer the question or explain the next step without asking for information already supplied. ### 4. Link related work Connect the thread to the contact and opportunity where appropriate. ### 5. Resolve properly Close only after the answer or follow-up action is owned. ## 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. ### Sensitive attachment Move it to the approved secure process and restrict access. ### Several recipients reply Set one owner and prevent conflicting responses. ### Unclear or suspicious message Use the security and spam process before opening links or files. ## 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. ### Enquiries with one accountable owner Audit unassigned and multiply assigned threads. ### Time to substantive response Do not count automatic acknowledgements as resolution. ### Reopened conversations Use them to identify incomplete answers. ## Frequently asked questions ### When should the email-enquiry handling playbook start? A configured business inbox receives a genuine customer enquiry. Confirm the record is eligible and that a named owner or monitored queue is available before allowing customer-facing action. ### Which channels should the email-enquiry handling 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 email-enquiry handling 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 sensitive attachment, several recipients reply, unclear or suspicious message. ### How should we judge whether email-enquiry handling works? Review enquiries with one accountable owner, time to substantive response, reopened conversations. 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/email-marketing](https://121.direct/crm/features/email-marketing) - [/crm/features/team-inbox](https://121.direct/crm/features/team-inbox) - [/crm/features/customer-management](https://121.direct/crm/features/customer-management) - [/crm/playbooks/multi-channel-follow-up](https://121.direct/crm/playbooks/multi-channel-follow-up) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.