Choose one conversation type
WhatsApp can carry sales, support and booking requests, but each path has a different owner and permission boundary. Choose one first. For example, answer routine product questions from approved information, then route a qualified purchase request to Sales. Keep complaints, sensitive requests and exceptions on a visible human path.
Write down the customer’s starting question, the information needed to answer it and the tool result that proves completion. A friendly response does not prove a booking was placed or a refund was approved.
Confirm channel access and consent
Before sending or automating messages, verify your business account, provider access, permitted message categories and the lawful basis or opt-in required for your audience. Provider APIs, template rules and pricing change; use the current provider documentation for the exact requirements. The Eyeleven connection guide describes the workspace setup path, and the Terms describe messaging responsibilities.
Do not upload contact lists to a live workflow until you have checked permissions, opt-outs and ownership of the data. An internal test number or authorized test account is enough to validate the first route.
Design for a confirmed handoff
An incoming question can be classified, answered from approved knowledge, and escalated when confidence or authority is insufficient. The next step may be a draft quote, a proposed appointment or a support case. Each should carry the source conversation and the reason for escalation. Before the system reports completion, check the destination system or a human confirmation.
- Keep a record of what the customer asked and what the system used to answer.
- Use explicit states for drafted, sent, accepted, failed and handed over.
- Stop automation when a person takes over or the customer opts out.
- Review a sample of real outcomes before increasing volume.
Track outcomes and costs
Measure response quality, verified next steps, opt-outs, provider failures and human review time. Include provider charges and implementation effort in the cost view. A high reply count is not useful if requests do not reach the right owner or customers receive unwanted follow-ups.
The 2026 regional cost guide explains the cost layers, while the ROI framework helps measure verified outcomes. For a deployment, confirm the current provider terms and the connected services in your workspace.
Continue with the platform
Explore OmniForces, review the documentation, or contact Eyeleven about a specific workflow.