WhatsApp Automation

Map the customer's preferred language and requested service to a named staff owner before building menus. A booking question, a stock enquiry and a property viewing may need different next steps. Agree which details each route needs and who reviews its English, Tamil or Sinhala wording. Extra languages, departments and integrations must fit the selected package or be separately scoped.

Define who takes a new conversation, who covers an unavailable colleague and how an unresolved request is handed over. Document access permissions and the point where automation stops so two people do not send conflicting replies. The chosen inbox determines available assignment, conversation history and reporting features; we confirm those capabilities and any provider charges in the proposal.

Business App Essentials configures the standard WhatsApp Business App for staff to use manually. Menu Bot Starter and higher packages connect an official API workflow for automated menus, lead capture and human handoff.

The workflow is designed to hand the conversation to a designated person or team. We agree the handoff rules, operating hours and escalation path during scoping; the bot is not presented as a replacement for human judgement.

AI Sales & Support includes grounded Sinhala, Tamil and English support. Language scope for other packages is confirmed from the menus, templates and content supplied for the project.

Meta prices applicable delivered messages according to recipient market and message category. Its rate card may include free or discounted windows and volume tiers, but eligibility, rates, categories and policies can change. SafeNet confirms the official current rate card and any separate provider fees during scoping.

Unless included in a written proposal, exclusions are Meta messaging charges, selected inbox or BSP subscriptions, AI model usage, cloud hosting, paid third-party tools or integrations, taxes and currency-conversion differences.

Timing depends on Meta onboarding, content readiness, integrations and acceptance testing. We confirm the implementation stages and target dates in the written scope before work starts.

Yes, where the target system offers a suitable API or supported integration path. AI Sales & Support includes one standard integration; more complex or multiple integrations are scoped under Integrated Automation Pro or Enterprise.

Storage, access, retention and regional requirements are agreed for the selected architecture. SafeNet documents the data path and permissions before production access is enabled.