WhatsApp Customer Service in Malaysia: Understanding the 24-Hour Window and Template Messages

article summary：WhatsApp customer service teams in Malaysia need a clear way to decide when they can reply normally, when a template is required, and how category and pricing rules affect the next step. This guide explains the rolling customer-service window, template review, message categories, and a practical decision flow. It also provides 12 proposed template examples and an operating routine that helps agents avoid avoidable sending errors, protect customer context, and keep service communication relevant across routine and complex customer requests.

WhatsApp customer service can appear simple from the customer side: a person sends a question and expects a helpful reply. For the business, the next message depends on policy state. Is there an open customer-service window? Is a free-form reply permitted? If the window has closed, does the business have an approved template that matches the real purpose of the message?

These questions matter for any team handling support, order updates, appointments, account access, or follow-up. The platform rules are set by WhatsApp, while applicable charges depend on Meta's current pricing documentation, the message category, the recipient market, and the account arrangement. This article uses Malaysia as the operating context but does not assume a fixed local rate or a local market behaviour.

Check the customer's last message

The customer-service window is a rolling 24-hour period measured from a customer's most recent WhatsApp message to the business. During that period, a business may send free-form replies as part of the service conversation. Each new customer message refreshes the timer.

This is why an agent should check the last inbound message before writing a detailed response. A reply that is appropriate in a current service conversation may not be permitted as free-form text once more than 24 hours have passed. The right next step then changes from composing a normal reply to selecting an approved template, if a compliant business-initiated message is appropriate.

A sent template does not itself refresh the customer-service window. The customer must send a message back. That distinction prevents a common mistake: treating a template delivery as permission to continue with an unrestricted conversation.

Make a send decision in the right order

The following flow is a simplified operating guide. It describes the decision order for a service team. It is not a substitute for Meta's current documentation, template status, delivery controls, or applicable rate card.

Permission, approval, delivery, and charging are separate checks. A template can be approved yet still be unsuitable for a particular use. A correctly categorized template can still face delivery limits. A message that is permitted may have a charge determined by current Meta rules. Keep these checks separate in the agent guide and in automation logic.

Check the pricing condition separately

The WhatsApp 24-hour rule controls when a business can use a free-form service reply. It is not a complete pricing calculator. Starting 1 July 2025, Meta moved to a per-template-message pricing model. Current charges can vary by template category and recipient market, and Meta may change the applicable commercial terms.

Within an open customer-service window, free-form service responses are the normal support path. Meta's published pricing treatment also distinguishes utility templates delivered within such a window from utility templates delivered outside it. Do not reduce this to "all messages are free for 24 hours." Marketing and authentication messages follow their own category and pricing conditions, while an individual business account may also have provider fees outside Meta's rate card.

For a Malaysia operation, the safe practice is to use the current Meta documentation and rate information for the recipient's country code before forecasting spend. This article deliberately avoids giving a Malaysian monetary rate because rates and terms can change.

Build the cost check into the workflow before launch. The person approving message content may not be the person who reviews campaign spend. Make the template category, expected recipient market, provider charge, and Meta rate reference visible in the same release check. That reduces the risk of treating an operational deadline as a reason to bypass a pricing or policy decision.

It is also useful to separate internal cost tracking from customer-service quality. A low template cost does not prove that a follow-up is useful. Review replies, opt-outs, complaints, and repeat contacts beside message volume. A template that is technically deliverable but routinely confuses customers should be revised or retired.

Match the template to the real message purpose

Message category should follow what the message actually does. Writing a promotional sentence inside an order update does not turn it into a utility message. Category fit should be reviewed before the template is submitted, not after an agent needs to send it.

Utility messages for agreed transactions

Utility templates support a specific request, transaction, or ongoing service update. Suitable examples can include an order confirmation, delivery update, appointment confirmation, refund-status notice, or return instruction. The content should be relevant to the customer's existing relationship or action.

Keep the message factual and focused. If the business wants to add a product recommendation or a discount, assess that material separately. Combining unrelated promotion with a transaction update can change the policy assessment.

Authentication messages for account access

Authentication templates support identity or account-access processes, such as a one-time passcode for sign-in, registration, or account recovery. They should not become a place for customer-service commentary, sales information, or broad account marketing.

The operating check is direct: if the recipient cannot understand why a code arrived or what account action it supports, the workflow needs review. The template, triggering event, and secure verification path should tell one coherent story.

Marketing messages for promotional outreach

Marketing templates are for offers, announcements, recommendations, invitations, and other promotional outreach. They need a clear promotional purpose, appropriate customer permissions, and respect for WhatsApp limits and customer responses.

Do not use a marketing template as an informal support follow-up merely because a utility template is unavailable. The message category is not a workaround for a closed window. It is a policy classification that must match the content and context.

Submit templates with usable review context

WhatsApp template messages are submitted for Meta review before use. A proposed template may be approved, rejected, paused, reclassified, or need revision. No copy in this article is pre-approved. Each example below is a policy-aligned proposal only, and its final category and approval status remain Meta's decision.

Review templates as a small content system. Give each one a defined triggering event, a category, an approved language variant, owner, variables with realistic sample values, and a fallback path for an agent. This makes it easier to identify a template that no longer matches the real workflow.

Language versions also deserve a separate check. English, Malay, Chinese, or Tamil wording should preserve the same transaction or authentication purpose. A translation that adds promotion, changes an instruction, or obscures the reason for contact can create a different review risk.

Work from a purpose-based template register

The following 12 examples are proposed templates requiring Meta review before use. Use placeholders only where the underlying data is accurate and necessary. A team should submit only the templates that reflect its genuine customer journeys.

The table is a template-purpose register, not a list of universal approval outcomes. For example, the support-case follow-up must relate to an existing customer request; adding a sales message would require a fresh category assessment. Marketing examples should be sent only under an appropriate permission and engagement strategy.

Before submitting a template, test the variables against ordinary and edge-case records. A missing order number, a very long product name, or a translated customer name can make a message unclear even when the approved structure is valid. Give agents a safe fallback: pause the outbound send, correct the source data, or move the issue to a human review queue rather than sending a misleading update.

Recover safely after an expired window

Closed-window errors often begin with an unclear handoff between the inbox and the policy owner. Create a simple routine that agents can follow without guessing.

1. Confirm the last customer-message time. Use the message timestamp rather than an agent's memory of the conversation.
2. Classify the next message. Decide whether it is a service reply, transaction update, authentication event, or promotional outreach.
3. Use a reviewed template when required. Check its current approval status, language, category, variables, and business reason.
4. Record the outreach reason. A brief case note makes later review possible and helps another agent understand why a template was sent.
5. Reassess after any customer reply. The inbound reply changes the service-window state; it does not erase other policy or quality checks.

For teams managing campaigns as well as service, Udesk WhatsApp Customer Service supports dynamic content templates, scheduled sending, bulk import, and reporting for delivery, read, click, and response activity. Those functions can support a controlled template library, but they do not determine whether a message is allowed by Meta. The WhatsApp policy decision must remain separate from campaign execution.

Assign control for template changes

Keep governance simple and visible. Assign an owner for template requests, define who checks category fit, and give agents an escalation route when a needed template is missing. Review rejected templates, category changes, failed sends, opt-outs, and mistakes around window status.

Use customer language and transaction context together. A translation may be clear yet still be wrong for the underlying booking, order, or account action. Keep source content, variables, and local customer details under the same change control. This is especially useful when one central team prepares templates for several languages.

The goal is a library agents can use with confidence. Each message needs a clear reason, an accountable owner, and a known next action when the customer replies or does not reply.

FAQ

Q: Does sending a WhatsApp template reopen the 24-hour window?

A: No. A customer's message refreshes the customer-service window. Sending a template alone does not permit unrestricted free-form replies.

Q: Are WhatsApp template messages automatically approved?

A: No. Meta reviews submitted templates. A template can be rejected, paused, reclassified, or require changes before it can be used.

Q: Can a business send a normal WhatsApp reply after 24 hours?

A: After the customer-service window closes, a business generally needs an appropriate approved template rather than a free-form reply.

Q: Is a utility template always free in Malaysia?

A: No. Check Meta's current pricing rules, delivery context, category conditions, and Malaysia rate information before making a cost assumption.

The article is original by Udesk, and when reprinted, the source must be indicated：https://my.udeskglobal.com/blog/whatsapp-customer-service-in-malaysia-understanding-the-24-hour-window-and-template-messages.html