# Inbound Call Handling CRM Playbook | 121 CRM > Answer, identify, route and record inbound calls without losing the customer’s purpose or next action. A fictional property firm receives Alex’s call about a viewing and routes it to the available enquiries team. 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. ## Inbound-call handling: the working sequence Illustrative playbook — names, organisations and activity are fictional. ## Capabilities explained ### Call handling Supports configured inbound and outbound calling, routing, voicemail and related call records. **How it works:** Handles an eligible customer interaction through a configured inbox, number or connected channel. **Why a business would use it:** Makes call activity part of the customer history rather than a separate phone log. **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 call reaches an approved business number during or outside configured hours. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook. ### Trigger A call reaches an approved business number during or outside configured hours. ### Practical scenario A fictional property firm receives Alex’s call about a viewing and routes it to the available enquiries team. ### Accountable owner Name the person or queue that accepts the work, monitors exceptions and can stop the sequence. ## Run the inbound-call 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. Set the opening context Identify the business and, where relevant, explain recording or privacy information. ### 2. Understand the purpose Capture a concise reason and verify identity only to the level needed. ### 3. Resolve or route Answer within authority or assign the call and context to the right person. ### 4. Record the outcome Use meaningful outcomes rather than “spoke to customer”. ### 5. Create the next action Confirm booking, call-back, information request or closure. ## 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. ### Caller at risk or in distress Use the approved emergency or safeguarding route, not a routine script. ### Identity cannot be verified Limit disclosure and arrange a secure next step. ### No suitable person available Give an honest call-back window and named queue. ## 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. ### Calls with a meaningful outcome Audit vague and missing records. ### Transfers with context retained Reduce customer repetition. ### Promised call-backs completed Compare actual service with stated expectations. ## Frequently asked questions ### When should the inbound-call handling playbook start? A call reaches an approved business number during or outside configured hours. Confirm the record is eligible and that a named owner or monitored queue is available before allowing customer-facing action. ### Which channels should the inbound-call 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 inbound-call 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 caller at risk or in distress, identity cannot be verified, no suitable person available. ### How should we judge whether inbound-call handling works? Review calls with a meaningful outcome, transfers with context retained, promised call-backs completed. 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/call-tracking](https://121.direct/crm/features/call-tracking) - [/crm/features/team-inbox](https://121.direct/crm/features/team-inbox) - [/crm/features/tasks-activities](https://121.direct/crm/features/tasks-activities) - [/crm/playbooks/web-chat](https://121.direct/crm/playbooks/web-chat) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.