A texting setup is ready when you can send a message, receive the reply on the right CRM record and give its owner a clear next step. Installing an extension is only part of that test.
Choose your route around the countries and numbers you need, whether you work in real estate or a nonprofit. Then verify the conversation history before automating messages to customers.
Choose the texting route that fits your region
Zoho Voice supports two-way local SMS in the USA and Canada. Its cited international SMS offering is outbound-only. If replies are essential, do not treat those routes as equivalent.
Voice charges SMS by usage. Obtain a quote for the countries, number and expected activity you need. For any Marketplace tool, check its own documentation rather than assuming the same coverage or charging model.
Use this shortlist for each candidate:
| Check | Evidence to request |
|---|---|
| Countries | Supported destination and sender countries |
| Number | Eligible number type and reply capability |
| Conversation history | Where sent messages and replies appear in CRM |
| Access | Which users can send and view the conversation |
| Cost | Subscription, number and usage charges |
| Stops | How the route records and applies opt-outs |
Choose a provider only after it can support your actual reply and record-history requirements. A tool that sends an outbound text may still fail your shared inbox process.
Check your number and account prerequisites
The Voice extension documentation requires a compatible CRM plan, a compatible Voice plan and a purchased Voice number. It also requires completed 10DLC registration for US and Canadian local numbers used for SMS/MMS.
Check those prerequisites before troubleshooting a missing send button. Confirm the sending number, its owning account and the CRM users who need access. Keep the person responsible for the Voice account involved in the pilot.
Use the selected provider's current instructions to establish consent and opt-out handling. Record where your team will see permission to text and how sending stops. A field labelled “consent” is not proof that the provider suppresses a message.
Country and registration requirements depend on the route. Check Zoho's help docs and the chosen provider's requirements for your exact numbers rather than reusing a setup from another region.
Install and connect the chosen integration
Use the Zoho Voice CRM SMS extension for this walkthrough. It supports sending and receiving messages inside CRM. Confirm the prerequisites on its documentation page, then follow the linked CRM installation guide for your account.
Have the authorized administrator install the CRM extension and review the requested access. The Voice account owner should complete any Voice-side number or registration work. Confirm that authorization connects the intended organisation.
Within CRM, check access for a pilot user and identify the intended sending number. Open a test contact before adding a workflow. If the extension does not appear, inspect installation scope and permissions before trying another install.
Voice supports templates and scheduled messages through the extension. Prepare a short test template with an identifiable purpose. Do not schedule customer messages while you are still checking which number and contact the extension uses.
Send a message and verify the reply on the contact
Use a recipient who has agreed to help test. Confirm the complete phone number, including country code, and search CRM for other records containing that number.
Send a plain message that asks for a simple reply. Record the contact identifier and the sending number. Then inspect the CRM conversation rather than relying only on a notification.
Your acceptance test should confirm:
- The outgoing text belongs to the intended contact.
- The recipient receives it from the expected number.
- A reply appears against the same contact.
- The responsible user can find and read the conversation.
- Delivery information is understandable to the person following up.
- An ambiguous number does not silently attach the reply to the wrong person.
Can you send and receive from the same CRM contact record? The Voice extension provides in-CRM sending and receiving, but your pilot must establish the actual record association. Resolve duplicate or shared numbers before using replies as workflow inputs.
Use contacts without email or phone to find missing contact details before expanding the recipient list.
Automate a useful follow-up
Start with a narrow requirement: when an eligible lead becomes qualified, prepare the agreed text and give the owner a follow-up task after a reply. Confirm that your chosen provider exposes the events and actions needed before configuring this design.
Write down the stop conditions first. Exclude missing or ambiguous numbers, withdrawn permission, already completed conversations and leads outside the pilot. Define how your team handles a reply that needs a person immediately.
Separate “message requested,” “message sent” and “reply received.” A successful CRM field update does not establish delivery. Ask the provider how failures and opt-outs reach CRM and test those paths.
Prevent repeat sends on unrelated edits. If the connector cannot support the required stop or reply logic, keep that step manual until you have a supported design.
Have the Zoho CRM AI Assistant run the setup
The Zoho CRM AI Assistant can configure the CRM side of your texting process, prepare fields and templates, inspect records and build follow-up automation on request. It waits for approval before applying texting-related CRM changes or sending a test message.
Inspect our CRM texting setup for the selected Voice route. Check pilot contacts for missing or shared phone numbers. Propose the CRM configuration, message template, permission fields and reply task. Show the changes for approval. Then help test a message and verify its CRM history, using only the connected CRM actions that are available. Stop if a provider-side step is required.
The assistant configures the texting workflow through the available CRM controls. It does not operate a third-party SMS provider, purchase a number or complete external registration. Have the account owner perform those steps.
After the pilot, use leads without a first response to review missed enquiries and deals without a next step to find conversations needing action. Confirm that the available CRM history supports your interpretation.
Troubleshoot missing messages and histories
If a message never leaves, check number eligibility, registration and account access. Capture the provider's error before retrying. Repeated clicks can create several sends if the first request was accepted.
If the recipient replies but CRM shows nothing, verify the route supports inbound messages for that number. Then check the connected account, user access and number matching.
If history appears on the wrong record, inspect shared or duplicate numbers. Decide which record owns the conversation before moving or changing CRM data.
Finally, test the stop path using the provider's documented procedure. Confirm that the CRM reflects the result and that your automation respects it. Expand only when send, reply, logging and stopping all produce the expected evidence.