A WhatsApp Business Information Checklist Before You Add AI

Adding AI to customer conversations begins with a straightforward question: can your team agree on the information customers should receive? A business may already have a website, social profiles, brochures and a shared drive, yet still lack one dependable set of answers.

This checklist helps you prepare that foundation for a WhatsApp AI assistant. Use it as an internal working document, assign owners to the open items and test a focused set of enquiries before widening use. It describes preparation practices, not an assurance that every listed item can be imported or automated in any particular Engage AI setup.

1. Confirm business identity and locations

Write the customer-facing business name, a brief description of what you do and the approved website or contact links. For each branch, record the address, general service area, contact route and any location-specific differences that affect an answer.

Check that your material distinguishes a physical shop from a service coverage area. A business that visits customers in a city does not necessarily operate a walk-in branch there. If customers need directions, use an approved location link and confirm it opens the correct destination.

• Which name should appear in customer answers?

• Which locations are open to visitors?

• Which areas receive on-site service?

• Which facts differ between branches?

2. Describe services and their limits

Create a short description for each service or product group. State who it is suitable for, what is included, what is excluded and which requirements need assessment. Use the terms customers use, while preserving the distinctions staff need to make.

Hypothetical example: a business offers residential wall-mounted air-conditioning cleaning. Its information should say whether repairs, commercial systems, high-access installations and replacement parts fall outside the standard service. “Air-conditioning services” alone leaves too much room for an overbroad answer.

Where suitability depends on a model, site condition or another detail, record the question staff would ask first. Do not collect a full address or detailed customer history when a general area or equipment type is enough for the initial check.

3. Prepare prices, conditions and quotation rules

For each price, identify the currency, unit, service scope and effective date. Explain the difference between a fixed price, a starting price and an estimate. Include relevant minimum quantities, exclusions and any applicable charges using wording approved by the business.

If an exact quote requires assessment, list the minimum information needed and identify who approves the quote. Do not let a list of sample amounts become a universal price promise. Remove expired promotional material from the active answer source or clearly mark it as historical and unavailable for current offers.

Ask the price owner to resolve discrepancies between the website, a PDF and a staff spreadsheet. More documents do not help when they contain competing answers.

4. Separate different kinds of hours

Record shop opening hours, staff response hours and appointment or delivery windows separately. Include the relevant location and timezone where ambiguity is possible. Clarify whether messages can be received when staff are unavailable, and avoid suggesting a person will respond immediately outside support hours.

State how holiday closures and temporary changes will be approved and updated. Appointment availability is a separate question from operating hours: an open business may have no remaining slots. Only describe a booking as confirmed when the actual business process establishes that confirmation.

5. Document policies customers need to understand

Gather the current booking, cancellation, rescheduling, refund, delivery and warranty information relevant to your business. Record the conditions and the responsible owner. When a case depends on an individual review, describe the review route without promising its outcome.

Keep policies readable. A short approved explanation may help answer common questions, but it should not silently change the formal terms. Have the responsible person review any simplified version. Retain a link to the relevant approved policy if the customer needs full details.

Avoid including unrelated confidential procedures or sensitive customer records in a general FAQ collection. Prepare only the information needed for the intended customer questions.

6. Define human contact and handover routes

Decide where customers should go when information is missing, a complaint needs judgement or they explicitly ask for a person. Identify the team, its response hours, the details it needs and a realistic next step.

A useful handover plan answers four questions: who receives the enquiry, what context they need, when they are available and how the customer knows what happens next. If those decisions are unresolved, mark them as open work rather than filling the gap with a reassuring but unsupported promise.

Document any proposed routing rule separately from the product capability that implements it. Test the actual workflow available in your setup before relying on it.

7. Check links, files and language versions

Open each customer-facing link from a normal browser session. Confirm the destination, page title, contact details and access requirements. Avoid relying on staff-only documents as customer links. Use a clear filename for an approved source and retire outdated duplicates from the active collection.

For multiple languages, identify a reviewer and keep the underlying facts consistent. Dates, prices and exclusions should match across versions. Record when a translation was reviewed so a later policy update does not leave one language behind.

8. Give every important fact an owner

A preparation sheet is easier to maintain when each item includes an owner, source, approval state and review date. The owner should be able to resolve uncertainty, not merely forward the question elsewhere. Define what triggers an immediate update, such as a revised price, holiday closure or service withdrawal.

Use practical states such as “approved”, “needs confirmation” and “retired”. Keep unconfirmed information out of the approved answer collection. Preserve a simple change record so reviewers can see which facts changed and why.

A compact readiness worksheet

For each service, complete the following fields:

• Customer question: the decision the customer needs help making.

• Approved facts: the answer, conditions and exclusions.

• Source and owner: where the facts came from and who approves them.

• Missing details: what must be clarified before proceeding.

• Next step: an approved enquiry, booking or human-help route.

• Review trigger: the date or business change that requires another check.

• Test result: expected and actual answers for a realistic question.

Connection is the beginning of readiness

Once a channel or information source is connected, run a realistic enquiry from start to finish. Test a straightforward question, an ambiguous request, an out-of-scope need and a request for a person. Check whether the customer receives accurate information and a workable next step.

Resolve missing facts and broken contact routes before expanding the scope. A completed checklist is useful because it makes decisions visible; dependable service comes from checking those decisions against the way your business actually operates.

Use the Engage AI product overview alongside this business-preparation checklist.