How should an AI worker hotline use WhatsApp after a phone call?
A practical workflow for consent, message templates, minimal confirmations, worker replies, delivery failures and one traceable case record.

The short answer
Use WhatsApp as a controlled continuation of the same worker case, not as a second inbox. After the call, send only the confirmation the worker needs: who sent it, what was received in neutral terms, the case reference, the next step, a realistic response expectation and a simple way to correct the information or ask for help.
Link the outbound message, every reply and each delivery event to the original case. If the worker has not agreed to receive WhatsApp messages, the correct template is unavailable or delivery fails, use the approved fallback. A phone call alone does not give the business permission to start an unrestricted WhatsApp conversation.
A phone call does not open the WhatsApp service window
WhatsApp's 24-hour customer service window starts when the person sends the business a WhatsApp message. A worker calling the hotline by voice has not opened that window. A business-initiated confirmation after the call therefore needs the required approved message template, even if it is sent one minute later.
Design this before launch. Create a small set of utility templates for receipt, status update, action needed and closure. Prepare each supported language separately, control the variables that can be inserted and record the template version used for the case. Do not rely on improvised free text that may be rejected by the channel or drift from the approved process.
Record permission for the channel and assess GDPR separately
WhatsApp policy requires the person to provide the mobile number and opt in to receive messages from the named business. The agency should be able to show when, where and for which message categories that permission was obtained. It also needs a clear opt-out route that works inside and outside WhatsApp.
Channel opt-in does not settle every GDPR question. The agency still determines the purpose, lawful basis, notice, recipients, access, retention and safeguards for the worker data in this workflow. Keep the channel permission, privacy notice and employment process aligned, but do not treat one checkbox as approval for any future use of the number.
Confirm the case without copying it into the notification
A useful confirmation can identify the agency or branch, state that a request was received, show a reference and explain what happens next. Add a time or shift only when it helps the worker detect an error. The worker should not need to guess whether the report reached the right operation.
Keep sensitive detail out of the notification preview. A sickness reason, payroll amount, housing access code, identity document or full transcript does not belong on a lock screen merely because it appeared in the call. Put protected detail in the authenticated case and use WhatsApp to point to the next action.
Return every reply to the same case
A worker may reply with a correction, an attachment or a new fact. The system should match that reply to the case, preserve the original report, add the new event and show the current owner what changed. If the reply cannot be matched safely, create a review task instead of attaching it to the nearest record.
Do not let WhatsApp become a private parallel history on a coordinator's phone. Use the approved business sender, route inbound messages into the operational workflow and keep the case status in the system the team already owns. Recheck identity before disclosing protected information or making a change that affects a shift, payment, accommodation or another person's data.
Track delivery without confusing it with resolution
Messaging providers can report stages such as sent, delivered, undelivered and, where available, read. Store those events with the case because they help the team see whether the chosen channel worked. A failed or undelivered message should trigger the agreed alternative, such as SMS, a call or a task for the coordinator.
Delivered does not mean understood. Read does not mean accepted, and it does not prove that a worker will attend a shift. Keep communication status separate from operational outcome. A case closes only when the approved workflow reaches its real end state, not when two ticks appear beside a message.
Give failures and sensitive replies a safe route
Plan for an old number, a shared device, a worker without WhatsApp, a rejected template, a late reply after the service window, a language mismatch and repeated delivery failure. The fallback must preserve the same case reference and must not send the same sensitive content through every available channel.
If a reply reports danger, coercion, a medical concern, harassment or another issue outside the approved chat flow, stop routine automation and route it under the relevant human procedure. The system may acknowledge receipt and preserve the facts. It should not judge credibility, medical severity, absence validity or employment consequences.
Test the whole path before workers depend on it
Run the test from the real call through template selection, language choice, delivery callback, worker reply, case update and human handoff. Include duplicate callbacks, replies from an unexpected number, wrong-case references and unavailable integrations. Check what the worker sees on a locked phone as well as what the coordinator sees in the case.
Agree the release measures in advance: correct recipient, correct language, successful case matching, delivery-failure recovery, time to owner and number of manual corrections. AI may choose an approved template, populate allowed fields and route a reply. People remain responsible for message categories, privacy settings, escalation rules and every decision about leave, work, pay, safety and discipline.
FAQ
Does a worker's phone call open the 24-hour WhatsApp service window?
No. The window starts when the worker sends the business a WhatsApp message. A business-initiated confirmation after a voice call normally needs the required approved template and valid channel opt-in.
Can the AI confirm a sickness report through WhatsApp?
It can confirm that the report was received and explain the next step. It should not say that the absence is approved, valid or free of consequences unless an authorised person and the agency's policy have established that outcome.
Should WhatsApp become the source of truth for the case?
No. Messages, replies and delivery events should attach to the same operational case. The ATS, CRM or case system chosen by the agency should hold the current status, owner and audit trail.
Sources and further reading
- WhatsApp Business Messaging Policy
- Twilio: WhatsApp Business Platform overview and opt-in requirements
- Twilio: WhatsApp customer service windows and message templates
- Twilio: outbound message status callbacks
- European Commission: principles of the GDPR
- EDPB: Guidelines 02/2021 on virtual voice assistants

