← WhatsApp Business Automation
0/15 complete

Module 01 · WhatsApp Business Foundations

Introducing WATI: Your No-Code Automation Layer

20 minfocused lesson5practical steps4grounded questions5source links
Open lesson + course map

On this lesson

Course outline

WATI is one possible solution-provider layer for the WhatsApp Business Platform. Its current help center documents a team inbox, contacts, attributes, campaigns, chatbots, assignments, APIs, and webhooks; availability varies by plan. Treat it as a replaceable operating tool, not the source of customer truth and not an exemption from WhatsApp rules.

After this lesson, you can create a safe WATI workspace model, a minimal contact schema, and an acceptance test before customer launch.

// concept

Define the System of Record

Choose where each fact lives:

FactRecommended authorityWATI’s role
consent evidenceconsent ledger or CRMcopy current permission state for filtering
customer identityCRM/customer databaseconversation address and limited attributes
order and paymentcommerce/payment systemdisplay reference, never decide paid status alone
conversationteam inbox/platform recordworking communication history
automation versiondocumented flow repositoryexecute the currently released flow
analytics eventevent store/reporting sheetcontribute timestamps and outcomes

If an agent edits an order amount in a contact attribute, that must not silently overwrite the commerce record. Define direction and conflict rules for every integration.

// concept

Build the Smallest Useful Schema

Start with attributes that drive a named decision:

// prompt — copy me8 lines
preferred_language: en | roman_urdu
city: controlled list
lead_stage: new | qualified | human_review | won | lost
interest_code: catalog identifier
consent_marketing: true | false
consent_source: page/form/click-to-chat identifier
order_reference: non-sensitive external ID
assigned_team: sales | support | operations

Do not store card data, banking secrets, OTPs, full CNIC values, medical details, or long free-text personal profiles in attributes. WATI documents plan-specific attribute limits; more importantly, a field without a purpose creates privacy and synchronization risk.

// concept

Configure Ownership Before Automation

Create company-controlled administrators, separate operator accounts, and teams with explicit queues. Write definitions for New, Open, Pending, Solved, Expired, and Blocked states based on the current inbox behavior. An automated assignment is successful only when a real team can see, accept, and resolve it.

Name flows with versions:

// prompt — copy me3 lines
PK_SALES_INBOUND_v1_2
PK_ORDER_STATUS_v1_0
PK_HUMAN_HANDOFF_v1_1

Keep a release note: owner, change, approval, test contacts, release time, and rollback version. No-code systems still need change control.

// worked_example

Worked Example

A Rawalpindi tutoring service creates Sales and Student Support teams. It stores city, grade band, preferred language, lead stage, consent source, and assigned team. The chatbot may update lead_stage only after a customer answers the qualification questions. It cannot mark a fee as paid; an integration must confirm a payment-provider event and attach a non-sensitive reference.

The acceptance test uses internal numbers. One user selects Roman Urdu, asks for Grade 9, then requests a person. The contact is assigned to Sales, the preference persists, the agent sees the transcript, and the timer begins. A second user types STOP; the campaign permission becomes false and the test confirms suppression. A third sends an unknown phrase; the bot offers a menu and human route instead of looping.

// failure_cases

Failure Cases to Diagnose

7 cases to diagnose

  • Tool is treated as the database for everything

    assign an authoritative system per fact.

  • Tags and attributes duplicate each other

    define controlled values and their purpose.

  • One shared administrator login

    create individual identities and recovery ownership.

  • Flow edited live without tests

    version, test, approve, release, and retain rollback.

  • Plan-specific feature assumed

    verify the live plan before promising assignment or attribute behavior.

  • Bot can set `paid=true`

    only a trusted payment confirmation may change payment state.

  • No opt-out suppression test

    campaign readiness is incomplete.

// pakistan_angle

Pakistan Angle

Use city and service-area codes that match how the business actually fulfills orders. Rawalpindi/Islamabad as one vague value can hide different delivery charges or appointment coverage. Keep phone values in a consistent international format while displaying familiar local formatting to agents where useful.

Small Pakistani teams often share devices or accounts for convenience. That destroys accountability and increases offboarding risk. Give each operator an identity, remove access promptly when roles change, and ensure the company—not an outside agency—controls the business account, recovery email, phone ownership, and billing relationship.

// hands_on

Hands-On Exercise

5 steps

  1. Assign a system of record for consent, identity, orders, chat, flows, and analytics.

  2. Create no more than eight purposeful contact attributes.

  3. Define teams, inbox states, response ownership, and escalation time.

  4. Write a versioned flow naming and release-note convention.

  5. Run internal happy-path, unknown-input, opt-out, handoff, and duplicate-event tests.

// completion_rubric

Completion Rubric

6 checks — tick as you verify

0/6

// sources

Sources

5 official sources — check every claim yourself

// check_yourself

Check yourself

4 questions · answers and options are taken word-for-word from this course

0/4

  1. 1 / 4 · diagnose

    Your work shows this failure mode: “Tool is treated as the database for everything.” What does the lesson tell you to do about it?