The GoHighLevel WhatsApp customer service window determines what your business can send after a contact messages you. While the window is open, your team can normally send conversational, free-form replies. Once 24 hours have passed since the customer’s most recent message, outbound messages generally need to use an approved WhatsApp template.
GoHighLevel does not define or extend this period. WhatsApp and Meta apply the messaging rules, while GoHighLevel provides the conversation and workflow layer through which your team sends messages. The practical challenge is therefore not just knowing that a 24-hour rule exists. Your team must know the conversation state, choose the correct message type, and assign responsibility for the next action.
A reliable operating approach is simple: check whether the window is open, use a free-form reply when it is, use an appropriate approved template when it is not, and record what should happen next. This prevents agents and automations from treating every WhatsApp contact as if it were in the same communication state.
What the GoHighLevel WhatsApp customer service window means
The customer service window is a rolling 24-hour period that starts when a WhatsApp user sends a message to your business. A new user message can open or reset the period. During that open period, the conversation can generally continue with normal replies that are not restricted to a pre-approved template.
When 24 hours pass without another message from the user, the window closes. At that point, a business-initiated message must normally use a WhatsApp-approved template that is suitable for the purpose of the communication. This is not a GoHighLevel preference or a timer that an administrator can change. It is a messaging rule enforced through the WhatsApp and Meta platform.
A WhatsApp conversation has two different states: an open support window for conversational replies and a closed window where outbound re-engagement requires an approved template.
The distinction matters because a contact can still exist in your CRM, remain assigned to an agent, and have an active opportunity while the WhatsApp window is closed. CRM ownership and WhatsApp messaging permission are related operational concerns, but they are not the same state.
How the 24-hour timing works
The timer is based on the user’s most recent WhatsApp message, not on the time your agent last replied. If a customer sends a new message, the relevant 24-hour period starts again from that user message. Your reply does not, by itself, create a new customer service window.
- User sends a WhatsApp message: the customer service window opens or resets.
- Team responds: free-form conversation is generally available while the window remains open.
- No further user message arrives for 24 hours: the window closes.
- Business needs to follow up: an appropriate approved template is normally required.
- User replies to the re-engagement: a new customer service window can open, allowing the conversation to continue normally.
Timing should be treated as a business control, not just a technical detail. If a support queue depends on an agent replying before the window closes, then response ownership and escalation need to be visible. If a sales workflow depends on a later follow-up, the workflow should account for the fact that the message type may need to change.
The last customer message is the key timing event. Measuring only from the last agent reply can create false confidence that a free-form message is still allowed.
Free-form messages and WhatsApp templates
Free-form replies while the window is open
When the window is open, an agent can generally answer questions, clarify requirements, provide support, and continue a normal conversation through WhatsApp. This is the appropriate state for solving the customer’s immediate issue rather than forcing every response into a fixed notification format.
Free-form access does not remove the need for good process. Teams still need message ownership, escalation rules, and a clear record of the outcome. An open window makes a conversational reply possible, but it does not determine what the reply should say or who should send it.
Templates when the window is closed
When the window is closed, a business-initiated WhatsApp message generally needs to use an approved template. Templates are structured messages reviewed through the WhatsApp messaging process and may contain defined variables, buttons, or other supported elements depending on the template configuration.
Common operational uses include a follow-up on an unresolved support matter, a service reminder, a delivery or appointment update, or a request for the customer to continue a conversation. The template should match the real purpose of the message. A generic template that does not make the next action clear can produce more failed follow-ups and more manual work.
Template approval and conversation timing are separate controls. Having an approved template does not mean every customer should receive it. The team still needs a reason to contact the person, a clear owner, and a relevant next step.
Continue the conversation
Use a normal reply to answer the user’s message, resolve the issue, or gather the information needed for the next business step.
Use controlled re-engagement
Select an approved template that accurately reflects why the business is contacting the user and what response is needed.
How to check the window in GoHighLevel
The exact GoHighLevel interface and labels can change, so teams should use the WhatsApp conversation view and any current status indicators available in their account rather than relying on an old screenshot or fixed menu path.
- Open the relevant contact or opportunity in GoHighLevel.
- Open the WhatsApp conversation rather than relying only on a general contact activity feed.
- Review the latest inbound WhatsApp message and its timestamp.
- Check the conversation status or message controls that indicate whether a free-form reply is available.
- If the window is closed, select an approved template and confirm that its purpose fits the planned follow-up.
If the interface does not make the state clear, the latest inbound timestamp is still an important diagnostic signal. It can help an operations owner determine whether the conversation is inside the 24-hour period, although teams should also account for the status information and delivery behavior shown by their connected WhatsApp setup.
A useful internal rule is to make the state visible before an agent starts writing. Do not ask an agent to compose a detailed response and only then discover that the channel requires a template. That sequence creates avoidable rework and inconsistent customer experiences.
A practical operating sequence for support and sales teams
The WhatsApp rule works best when it is built into an operating sequence rather than left to individual memory.
This sequence separates a channel rule from a business decision. The channel rule answers what type of message can be sent. The business decision answers whether sending a message is useful, who owns it, and what should happen if the customer does not respond.
How to reopen a closed conversation
There are two practical ways to continue after the 24-hour window has closed.
Wait for the customer to message again
If the user sends another WhatsApp message, the conversation can move back into an open customer service window. The team can then respond conversationally, subject to the normal behavior of the connected WhatsApp account.
Send an appropriate approved template
If the business needs to contact the user first, an approved template is normally required. In GoHighLevel, the process generally involves opening the contact’s WhatsApp thread, selecting the relevant template, completing any required variables, checking the recipient and message purpose, and sending it.
The template should not be used as a workaround for unclear ownership. For example, if a support issue has not been investigated, sending a reminder template may create another customer response without resolving the original problem. The better sequence is to clarify the internal status first, then choose the message that matches it.
Hypothetical scenarios
A support conversation nearing expiry
Suppose a customer reports a billing problem at 10:00 on Monday. An agent replies at 10:20 and marks the case as waiting for finance. If the customer sends no further message, the customer service window may close at 10:00 on Tuesday, even though the agent replied recently. A later update may therefore need to use an approved template, while the internal case remains assigned to the finance or support owner.
A sales follow-up after inactivity
Suppose a prospect asks for a quotation and then stops replying. The opportunity can remain active in GoHighLevel, but that does not mean a free-form WhatsApp follow-up remains available indefinitely. The sales workflow should identify when a template is needed, define the permitted follow-up, and stop or escalate the sequence if the prospect does not respond.
Workflow and CRM controls that reduce avoidable mistakes
A CRM should represent the business state around the conversation, not pretend that the WhatsApp window is the entire process. Useful fields or workflow conditions may include last inbound WhatsApp time, assigned owner, conversation purpose, support status, template eligibility, next action, and escalation status.
Automation can help surface aging conversations, create internal tasks, route replies, and remind owners about work that is approaching a deadline. It should not send messages merely because a timer expired. The automation needs a defined decision, a valid message path, and a clear stop condition.
If GoHighLevel is part of a wider sales or service stack, document which system is authoritative for each state. A CRM may own the opportunity stage, a support process may own the case status, and WhatsApp may determine the available message type. Treating those as one field can produce incorrect reporting and unsafe automation. ConsultEvo’s CRM consulting services can help teams clarify ownership, pipeline states, and connected workflow logic.
- What was the latest inbound WhatsApp message, and when did it arrive?
- Is the customer service window open or closed?
- Does the message need to be free-form or template-based?
- Is the selected template relevant to the customer’s actual situation?
- Who owns the next response if the customer replies?
- What should happen if there is no response?
Operational observations for GoHighLevel WhatsApp teams
A CRM stage should describe the customer’s business state, while the WhatsApp window describes the channel’s available message state.
A template is a controlled message type, not a substitute for a clear reason to contact the customer.
Automation should detect the messaging state before creating an outbound action, not after a delivery attempt fails.
The most reliable setup is usually the one with the fewest ambiguous states. Define what counts as an active conversation, who owns an unanswered message, when a template is appropriate, and when a workflow must stop. Then configure GoHighLevel around those decisions instead of expecting the platform to create the process automatically.
For broader workflow integration, ConsultEvo’s Zapier automation services may be relevant where approved systems need to exchange tasks, contact data, or status changes. The integration should support a defined operating process rather than add another disconnected notification layer.
Frequently asked questions
What is the WhatsApp customer service window in GoHighLevel?
It is the rolling 24-hour period that begins when a WhatsApp user sends a message to your business. During the open period, normal conversational replies are generally available. After 24 hours without another user message, a business-initiated message generally needs an approved WhatsApp template.
Does replying to a WhatsApp message reset the 24-hour window?
No. The timing is based on the user's most recent inbound message. A new message from the user can open or reset the window, but an agent reply does not normally create a new 24-hour period.
How do I message a GoHighLevel WhatsApp contact after the window closes?
Use a relevant approved WhatsApp template through the contact's conversation, assuming the account and template are configured for that message. If the user replies, the conversation can move into a new open customer service window.
Can GoHighLevel extend the WhatsApp 24-hour window?
No. GoHighLevel works within the messaging rules applied by WhatsApp and Meta. It can help expose conversation status and control message actions, but it cannot extend the platform-defined window.
Should every closed WhatsApp conversation receive a template automatically?
No. A closed window only describes the message type available for business-initiated contact. The team still needs a valid business reason, an appropriate template, a clear owner, and a defined next action before sending.
Build a WhatsApp workflow around clear ownership
If your GoHighLevel conversations, templates, and follow-ups are difficult to manage, ConsultEvo can help clarify the process, CRM states, and automation rules behind the channel.
