# New Lead Response Playbook for Small Businesses | 121 CRM > Respond to a useful new enquiry quickly, establish ownership and agree the next step without rushing qualification. A fictional roofing company receives a website enquiry from Kim about a repair and assigns it to the duty estimator. 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. ## New-lead response: the working sequence Illustrative playbook — names, organisations and activity are fictional. ## Capabilities explained ### 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. ### Forms Collects structured visitor details and maps supported responses into CRM records and workflows. **How it works:** Publishes or collects information through a configured visitor-facing page, form or content experience. **Why a business would use it:** Turns an enquiry into usable data instead of an unstructured email. **Limitations:** Generated or templated content is not automatically accurate, accessible, compliant or ready to publish. **Human responsibility:** A person must review content, test the journey and explicitly publish or change live assets. ### 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. ### Opportunities Represents a potential sale or deal linked to a contact, value, owner and pipeline position. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Shows which customer conversations are active commercial work rather than general contacts. **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. ### Triggers Starts a workflow after configured contact, event, appointment, opportunity, course or other supported activity. **How it works:** Runs an ordered sequence only after its configured trigger and conditions are met. **Why a business would use it:** Lets follow-up begin from a business event instead of waiting for someone to remember. **Limitations:** Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service. **Human responsibility:** A process owner must approve, test, monitor and pause or correct faulty automation. ## Begin with a valid trigger, enough context and one owner A valid enquiry enters the CRM from an approved channel. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook. ### Trigger A valid enquiry enters the CRM from an approved channel. ### Practical scenario A fictional roofing company receives a website enquiry from Kim about a repair and assigns it to the duty estimator. ### Accountable owner Name the person or queue that accepts the work, monitors exceptions and can stop the sequence. ## Run the new-lead response 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. Validate the record Check contact details, source, consent and whether the request is genuine enough to work. ### 2. Acknowledge appropriately Confirm receipt and set an honest expectation for the next human response. ### 3. Assign an owner Route the enquiry using service, location and team-cover rules. ### 4. Review fit A person checks urgency, suitability and missing context. ### 5. Agree the next action Record a call, appointment, information request or clear close reason. ## 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. ### Duplicate or spam Suppress automation and merge or close only after an appropriate check. ### Sensitive or urgent request Move to the approved specialist or emergency route; do not leave it in routine nurture. ### No response Use a short, proportionate cadence and stop after the agreed limit. ## 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. ### Median time to owned first response Measure when a useful owner accepts the lead, not merely when an automatic message sends. ### Leads with a dated next action Review whether live enquiries have an accountable next step. ### Exception volume and reasons Use exceptions to improve forms, routing and cover. ## Frequently asked questions ### When should the new-lead response playbook start? A valid enquiry enters the CRM from an approved channel. Confirm the record is eligible and that a named owner or monitored queue is available before allowing customer-facing action. ### Which channels should the new-lead response 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 new-lead response 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 duplicate or spam, sensitive or urgent request, no response. ### How should we judge whether new-lead response works? Review median time to owned first response, leads with a dated next action, exception volume and reasons. 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/lead-management](https://121.direct/crm/features/lead-management) - [/crm/features/team-inbox](https://121.direct/crm/features/team-inbox) - [/crm/playbooks/missed-call-follow-up](https://121.direct/crm/playbooks/missed-call-follow-up) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.