By Nudge team
Build guide for owners and developers
Updated
Choose the first job
Choose one job first: answer product questions, collect enquiry details, book a time or send a payment link. Write down what must happen before you tell the customer it is done. A booking, for example, needs a successful calendar entry.
Begin with a small set of questions and one action. Test them before adding more. The AI should answer about your business using information you approved, and ask a person when that information is missing.
For a broader view of the operating model, read the WhatsApp AI automation guide.
Use the official WhatsApp Cloud API
Build on Meta's official Cloud API and a properly configured WhatsApp Business Account. Unofficial browser automation is not recommended. It depends on a consumer interface, is difficult to operate reliably and does not give you the platform controls a production business workflow needs.
Use the current Meta WhatsApp Cloud API documentation as the source of truth for setup, authentication and supported behavior. Keep access tokens, app secrets and verification values in server-side secret storage. Never place them in browser code, article examples, screenshots or source control.
Receive messages through a verified webhook
A webhook is the URL where Meta sends new messages. Use HTTPS, check the request signature and reject invalid requests. Acknowledge valid messages quickly, then put the AI work in a queue so slow replies do not hold up delivery.
Meta may deliver the same event again. Save its message ID and process it only once. Developers call this idempotency. Without it, one customer message could trigger two replies or two bookings.
Reference flow
- 01A customer sends a WhatsApp message
- 02Meta delivers a signed webhook event
- 03The application stores and deduplicates the event
- 04Business knowledge and lead state shape the reply
- 05A narrowly authorized action runs when needed
- 06The reply, action result and next step are recorded
- 07A person takes over when policy or judgment requires it
Use your business information for replies
Start with current services, prices, hours, locations and policies. Add instructions for questions that need a person. Give someone responsibility for keeping this information up to date.
For each question, give the AI only the relevant business information. If the answer is missing, it should say a teammate will check. Keep enough information to trace a wrong answer back to its source.
CustomerCan I book a call tomorrow afternoon?
BusinessI’ll check the calendar for tomorrow afternoon. What time zone are you in?
Check live availability before offering a time. Save the calendar result before confirming.
Give the AI narrow business actions
Give the AI specific actions, such as “check available times” or “create a payment link”. Each action should accept clearly defined inputs. Your server must check the business account, permissions and inputs before running it.
The AI can suggest an action, but your application must decide whether it is allowed. Recheck the time before saving a booking and save the result. Do not give the AI unrestricted database access or the ability to run arbitrary code.
Track conversation and lead state
Save customer details and actions in your database, outside the AI conversation. Include the business, contact, latest customer message, consent, assigned teammate and next step. A chat summary is helpful, but cannot replace a booking or payment record.
Use clear labels such as new, waiting for customer, waiting for staff, booked and closed. Record why a label changed. Every database query and action must be limited to the correct business, with database permissions as a second check.
Enforce the 24-hour service window
Derive the free-form reply path from the latest customer message. When the customer service window is open, the assistant can answer within the business's approved scope. Outside the 24-hour service window, a business-initiated follow-up must use an appropriate approved message template rather than a free-form AI message.
Enforce that choice in the sending code, not only in a prompt. Follow-up also requires valid consent. Store consent evidence, block contacts without the required opt-in and process STOP as a permanent opt-out that queued work or later imports cannot undo. Read the WhatsApp lead follow-up guide for the operating workflow around those controls.
Check the current WhatsApp Business Messaging Policy before launching or changing a live messaging workflow.
Use our business knowledge checklist and plan when a person should take over.
Design human handoff before launch
Define handoff triggers before the first live conversation: explicit requests for a person, low-confidence answers, complaints, payment problems, policy exceptions, sensitive topics and actions the automation is not allowed to perform. Tell the customer when a person is taking over instead of leaving them in silence.
A handoff needs a destination, an owner and enough context to act: customer intent, facts already collected, actions attempted and the unresolved question. Pause automated replies while a person is in control, and make resuming automation an explicit decision.
Test the complete system safely
Build a simulation mode that exercises message intake, retrieval, model routing, business actions, follow-up decisions and dashboard state without real credentials or external sends. Then run user acceptance testing with test contacts and reversible actions before enabling production traffic.
- Verify webhook challenges, signatures, retries and duplicate events.
- Test known questions, unknown questions and deliberately conflicting knowledge.
- Confirm every business action checks permissions and validates its inputs.
- Exercise opt-in, STOP, open-window replies and approved-template re-engagement.
- Force each handoff condition and confirm an owner receives the full context.
- Run the journey in simulation before enabling any live send or write action.
Include failure cases: timeouts, stale knowledge, unavailable calendars, duplicate webhooks, rejected templates and a human who does not answer immediately. A demo path is not production-ready until the unhappy paths are visible and recoverable.
Decide whether to build or buy
Build your own system if you have developers to maintain it, handle failures and keep up with Meta changes. A managed product is worth considering when your team wants to run the business and have a provider maintain the software.
| Decision area | Build internally | Use a managed AI Front Desk |
|---|---|---|
| Control | Maximum implementation control | Control through configured workflows and policies |
| Ownership | Your team owns hosting, updates and incidents | The provider operates the platform; you own business decisions |
| Best fit | A staffed product team with a unique use case | A business that wants setup and an operating outcome |
Neither path removes the business's responsibility for consent, correct knowledge and staff escalation. The honest comparison is where the technical and operational work will live—not whether it exists.
For an education consultancy, map the architecture against the education consultant enquiry workflow and the Shopify WhatsApp automation workflow. Compare how student qualification and counselling bookings differ from live order lookup and product questions. Both need clear customer context and a person responsible for exceptions.
Turn the architecture into a working front desk
Nudge uses the official Cloud API and connects business knowledge, real actions, compliant follow-up and human handoff. We help set up the workflow; your team remains in control of the business.
For an education consultant, follow a student enquiry through qualification and counselling booking. For a Shopify store, see an order or product question answered from connected store data.
Book a free demo