Who this is for
Clinics, consultancies, tour operators, real estate agents, schools and online stores in Nepal that receive enquiries by WhatsApp and lose some of them because nobody replied fast enough, or that spend staff hours sending the same confirmation and reminder messages by hand. It also fits businesses running click-to-WhatsApp ads who need the conversation to continue automatically after the first tap.
Two related pages cover the rest of the channel. Setting up WhatsApp Business, broadcast lists and catalogues by hand is WhatsApp marketing. Buying the conversation through Meta is click-to-WhatsApp and Messenger ads. This page is about what happens automatically once the message arrives.
WhatsApp Business App vs WhatsApp Business API
The free WhatsApp Business app on a phone cannot be automated beyond a greeting and away message, and it lives on one device. Automation needs the WhatsApp Business Platform (the API), which runs in the cloud, supports multiple agents, and can be connected to n8n, Make, ManyChat or a CRM. Getting there involves:
- A verified Meta Business account with your business documents; verification for Nepali companies typically uses the company registration certificate and PAN.
- A phone number not already registered on the WhatsApp app, or migrated from it. A Nepali +977 number works; the number must be able to receive a verification SMS or call.
- Access route. Either directly through Meta’s Cloud API or through a Business Solution Provider. Direct Cloud API access is cheaper; a BSP adds a dashboard and support. Tools such as ManyChat and GoHighLevel connect through their own integrations.
- Payment. Conversations are billed by Meta in USD, so the business needs a card Meta accepts.
- Display name approval that matches your registered business name.
I handle the application, number migration and connection as part of the setup, with your accounts in your name.
Templates, the 24-hour window and opt-in
Meta’s rules decide what is possible, so I design around them rather than discovering them after launch:
- Message templates. Any message the business sends first, or sends more than 24 hours after the customer’s last message, must be a pre-approved template in a category (marketing, utility or authentication). Approval usually takes minutes to a day; templates that look like spam are rejected. I write templates in Nepali and English and submit them with sample values.
- The 24-hour customer service window. Once a customer messages you, free-form replies and bot conversations are allowed for 24 hours. After that, only templates. Workflows are built to do the useful work inside the window and to use utility templates (reminders, order updates) afterwards.
- Opt-in. Marketing templates may only go to people who agreed to receive WhatsApp messages. The opt-in is captured on the form, the ad or in the first conversation and stored in the CRM with a timestamp. Buying a phone list and broadcasting to it will get the number blocked, and I will not build it.
- Quality rating. Meta rates the number by blocks and reports; a low rating reduces how many templates you can send per day. Frequency limits and easy opt-out are part of every flow.
- Conversation pricing. Each conversation type has a per-conversation cost that varies by country and category; the current rate card is in WhatsApp Manager. I estimate monthly volume and cost before build.
Workflows I build most often
- Lead form to WhatsApp to CRM to sheet. A website or Facebook lead form is submitted; within seconds the lead receives a WhatsApp template thanking them, confirming what they asked for and offering a time to talk; the contact is created in HubSpot, Zoho or GoHighLevel with the source and campaign; a row is appended to a Google Sheet; the salesperson receives an alert with a one-tap link to reply. If nobody replies within an agreed time, a reminder goes to the manager.
- Appointment confirmation and reminders. Booking created in the calendar or CRM; confirmation template immediately; reminders 24 hours and 2 hours before; a reply of “reschedule” opens a new slot picker. Detailed on appointment booking automation.
- Order updates for stores. WooCommerce order placed, paid, shipped and delivered each send a utility template; a “where is my order” reply returns the tracking status without a human.
- FAQ and qualification bot. A menu-based or AI-driven flow answers hours, pricing, location and eligibility questions and collects name, need and preferred time, then hands the chat to a person with a summary. The AI version is scoped under AI chatbot development.
- Click-to-WhatsApp ad hand-off. The ad’s pre-filled message identifies the campaign; the first reply is automatic and tagged; the lead lands in the CRM with the ad source so cost per lead can be reported by campaign.
- Re-engagement. Leads with no reply in 3 days receive one follow-up template; a “not interested” reply closes the record and stops all messages.
What the service includes
- API access setup: business verification, number registration or migration, display name and payment method.
- Template writing in Nepali and English, submission and approval handling.
- Workflow build in n8n, Make, ManyChat or GoHighLevel, connected to your forms, ads, CRM, calendar and sheets.
- Shared inbox setup so several staff can reply from one number, with assignment rules.
- Opt-in capture and opt-out handling across every entry point.
- Testing with real numbers, Nepali text, emoji, missed fields and duplicate submissions.
- Monitoring: failed sends, template rejections and quality rating alerts.
- Documentation and a 30-minute training for the people who will reply.
What to decide before automating WhatsApp
- Who answers when the bot hands off, and within how many minutes, including evenings and Saturdays.
- Whether the number is the one already printed on your signboard and Facebook page, and whether it is currently on someone’s personal phone.
- Which system is the record: the CRM, a sheet or the inbox. Only one can be.
- Tone and language: formal Nepali, casual Nepali, English or mixed, per audience.
- How often you will message people who have not replied. Fewer is safer for the number’s rating.
What breaks, and how I prevent it
- A template rejected after launch because it was edited; I version templates and keep the approved copy.
- Messages sent outside the window without a template, which simply fail; the workflow checks the window first.
- Duplicate contacts when a lead submits twice; the CRM step matches on phone number before creating.
- Number quality drops after a promotional blast; frequency caps and opt-out keywords are built in.
- Staff replying from the personal app after migration, which disconnects the number; part of the training.
Pricing pointer
Setup is quoted on request after scoping; a single-workflow setup (for example lead form to WhatsApp to CRM) sits at the lower end of that range, and a full inbox, bot and reminder system with CRM integration sits higher. Monthly maintenance is quoted on request, and Meta’s conversation charges and any ManyChat or GoHighLevel subscription are paid by you. Related services often bought together: lead generation automation and CRM setup and integration.
Next step
Tell me which number you use, where enquiries come from and what the first reply should say, and I will come back with the workflow diagram and a fixed price. The full list of automations is on the automation services hub.
