1. Define one use case
Write down the trigger, the customer audience, the team owner and the intended outcome. For example, a new property enquiry should reach the appropriate advisor with enough context to arrange the next conversation. This is more useful than a generic request for automation.
2. Review the number and account
List the business number you want to use and its current setup. Identify who controls the relevant account and business information. Ask about migration and coexistence before changing an existing service. Available routes depend on the account and provider configuration.
3. Prepare messages and permissions
Document how recipients agree to hear from you, how requests to stop are handled and which templates the first workflow needs. Keep messages specific. Check links, sample values and language before launch. Platform approval is a dependency, not a date the website can guarantee.
4. Configure the team and handover
Assign responsibility for new enquiries, working hours and escalations. Decide how automation hands over to a person. Test unexpected answers, duplicate enquiries and requests for help so the workflow works beyond its ideal path.
5. Launch in a controlled scope
Use a small, appropriate audience and review the process with the people who answer replies. Check that customer details reach the right place and that the promised follow-up actually happens. Expand only once the workflow is understood.
What to bring to your demo
Have your use case, team size, number of business numbers, current CRM or store, recipient countries and expected messaging activity ready. The goal is a clear setup and cost discussion, not a rushed migration.
A growing retail or D2C team
A campaign attracts product questions and order enquiries. Separate buying advice from existing-order support, while keeping the conversation visible to the right team.
Bring your preferred customer language and current business tools. Your India quotation will state the billing currency and implementation scope.
