# Telephony and messaging CRM integration | 121 CRM > Understand how Telephony and messaging may connect with 121 CRM, including the documented data flow, permissions, limitations, testing and ownership needed. A useful decision about connecting Telephony and messaging begins with the real data flow, not a logo on an integrations page. This Telephony and messaging guide explains the documented method, practical setup or migration sequence, important limits and the acceptance checks a small business should complete before relying on it. ## A connection with a named job Fictional example using Alder & Field; supplier capability is documented, while account availability and 121 service scope still need agreement for each customer. ## Capabilities explained ### 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. ### 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. ### Messaging and calling compliance Requires number verification, applicable registrations, consent, sender identity and opt-out handling for each channel and region. **How it works:** Handles an eligible customer interaction through a configured inbox, number or connected channel. **Why a business would use it:** Makes channel setup a governed operational task rather than just a technical connection. **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. ## How the Telephony and messaging connection currently works The provider documentation reviewed on 11 October 2026 describes this route: Connect and configure an eligible LC Phone or customer-owned Twilio route, numbers, regulatory information and channel webhooks. Treat the Telephony and messaging method as a starting boundary, because permissions, editions and configured options can change the actual result. ### What the current documentation supports Supported calls and SMS/MMS can be associated with CRM contacts and Conversations. For Telephony and messaging, this is a general supplier capability; it does not confirm availability or inclusion in a particular 121 customer account. ### Another supported part of the documented scope Call status and inbound-message events can be routed through the configured provider connection. For Telephony and messaging, this is a general supplier capability; it does not confirm availability or inclusion in a particular 121 customer account. ### A practical business question Which single customer or team action should become easier because Telephony and messaging is connected? If the answer is unclear, the business is not ready to approve access. ## A controlled way to connect Telephony and messaging Use a bounded, reversible Telephony and messaging test before any live change; this sequence is practical guidance, not a promise that 121 has access to either account or that every step is included in a 121 package. ### 1. Name the business event Start with one event that matters, such as a booking, message, payment or status change. Do not connect Telephony and messaging merely because a connector exists; apply that check to the documented Telephony and messaging route. ### 2. Grant the minimum access Use an account owned by the business, record who can reconnect or revoke it, and approve only the permissions needed for the documented flow; apply that check to the documented Telephony and messaging route. ### 3. Test both the happy path and failure Use fictional data to confirm the expected record, owner, timestamp and next action. Then revoke a permission or use invalid data in a safe test to see how the failure becomes visible; apply that check to the documented Telephony and messaging route. ### 4. Monitor the live boundary Assign an owner for failed runs, expired tokens, duplicates, provider changes and usage charges. Review the connection when either supplier changes its terms or data model; apply that check to the documented Telephony and messaging route. ## How Alder & Field could test the decision Alder & Field is a property-maintenance business. Its fictional Telephony and messaging records and narrow acceptance test demonstrate the method without implying a live connection or customer result. ### The operating need The team needs one Telephony and messaging event to create a visible, owned action without retyping or leaving credentials with an individual. ### The trial Alder & Field wants Telephony and messaging to support one clear handover. The team connects a non-production test where available, sends one fictional event through the documented path and checks the resulting contact, timestamp, owner and next action before enabling wider use. ### The evidence Alder & Field's reviewer keeps the Telephony and messaging source count, test input, mapped output, timestamps, owner, exception log and configured-permission evidence; a pass means this agreed scenario behaved as expected, not that every future scenario is guaranteed. ### The decision Alder & Field names an owner to accept, revise or reject the Telephony and messaging design; anything unexplained remains outside live use until it has a documented rule, monitoring route and human response. ## What to check before relying on Telephony and messaging Telephony and messaging documentation establishes general capability, not customer-specific availability, commercial inclusion or a 121 migration commitment; put those boundaries in the decision rather than small print after go-live. ### What the connection or export does not solve Number availability, registration, consent, country rules, carrier filtering and usage charges apply. ### A second boundary to plan around A customer-owned Twilio account requires correct number and Messaging Service webhooks; portability and history are separate checks. ### Account and commercial boundary Confirm the relevant HighLevel, Telephony and messaging and connector plans, permissions, usage charges and supplier terms in the customer's own accounts. This Telephony and messaging page does not claim that integration or migration work is included in the 121 subscription. ### Live acceptance still required Before live Telephony and messaging use, confirm an owned connection, run a representative test, reconcile results and record failure handling; no live account test was performed for this public guide, so those checks remain customer-specific implementation work. ## Frequently asked questions ### Is the Telephony and messaging integration included with every 121 CRM account? Not necessarily. The supplier documents a general platform capability, but the relevant HighLevel feature, Telephony and messaging plan, permissions, connector and usage charges must be confirmed for the customer's own configuration. ### What data moves through the Telephony and messaging connection? Supported calls and SMS/MMS can be associated with CRM contacts and Conversations. Call status and inbound-message events can be routed through the configured provider connection. The exact fields and direction should be confirmed in a test because configured options and provider changes can alter the result. ### What happens when the Telephony and messaging connection fails? The design should expose failed runs, revoked permissions, expired tokens or rejected data to a named owner. Test the failure path safely, record retry and duplicate rules, and keep a manual recovery route. ### Does 121 promise to configure or support the Telephony and messaging connection? This guide explains the documented capability and a sensible acceptance method. Any 121 configuration, migration, monitoring or support commitment must be agreed explicitly for the customer and is not created by this page. ## Related CRM pages - [/crm/integrations](https://121.direct/crm/integrations) - [/crm/security-data](https://121.direct/crm/security-data) - [/crm/guides/crm-vendor-due-diligence](https://121.direct/crm/guides/crm-vendor-due-diligence) - [/crm/integrations/cloud-storage](https://121.direct/crm/integrations/cloud-storage) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.