Give WhatsApp follow-ups a clear next action.

Start with a real enquiry or request. Agree what information is needed, who receives it, when it should be escalated and what counts as a completed follow-up. A fast acknowledgement is useful only if the work continues correctly.

For example, a workshop enquiry could collect the job reference and a short description, create an item in a review queue and assign it to the right person. The person checks the request and prepares the quotation; an approved reminder can follow if the customer has not replied. This illustrates a possible scope, not an existing client result.

A consumer chat account, the WhatsApp Business app and the Business Platform have different capabilities. We inspect the account, provider, number setup, messaging rules and integration options before proposing a build.

Meta policies, template requirements, messaging charges and provider fees affect what can run and what it costs. We use supported interfaces and agree how failures, opt-outs and handover to a person will work.

Agree the purpose for processing information, the records required, the responsible person and how requests or complaints reach a human. Marketing and service messages should be assessed separately under the applicable rules.

Only connect the information needed for the workflow. Define access, retention and the systems that receive it. Your organisation remains responsible for its decisions and legal obligations; an integration does not certify compliance.

Aitsa implementation uses a fixed fee agreed upfront for the scope, with a 50% deposit on acceptance. Acceptance checks, remaining payment, documentation, handover and initial support are defined in the proposal.

The client pays software, hosting and usage costs. Messaging charges depend on the current provider arrangements and the messages sent. We assess these before you commit, rather than advertising a universal package price.