Protecting an overnight message from another country requires more than leaving a morning reminder. The organization’s time zone, the active shift, and the person responsible for a new inquiry must work together. The WhatsApp conversation window also limits the available response path. A dependable setup in Zoho therefore cannot rest on one setting or on someone noticing the message after arriving.
A sound response workflow connects three layers: organizational time, ownership and redistribution, and channel conditions. When one remains unclear, a message may be visible while responsibility stays uncertain. The objective is to decide in advance how every out-of-hours inquiry will be handled the next morning. The team can then act through shared rules for time, access, and follow-up instead of personal assumptions.
The morning after a 2 a.m. message
An inquiry arrives at 2:30 a.m. when nobody is watching the screen. At nine, three people see the same message, and each assumes someone else has answered it. Near noon, the patient writes again from another number. The message itself was not lost. What remained missing was a clear owner and an agreed first action for the visible inquiry.
Calls for greater attentiveness alone cannot resolve this pattern. Team members may all see one record, but visibility does not create responsibility without a shared handoff arrangement. A meaningful morning check needs a consistent operating approach that defines which organizational day includes the night, which team is on duty, and who holds the inquiry before individual assumptions begin shaping the response.
Set the time zone and shifts first
The organization’s time zone is defined under Locale Information in Company Details, and it affects how workflow rules calculate the day. A user’s personal time-zone setting is separate. Preserving that distinction prevents a patient’s local time from being confused with a staff member’s display preference. In Zoho, the organizational setting provides the shared reference while individuals can retain their own viewing context.
Business Hours can be established organization-wide as 24/7, 24/5, or customized by day. Shifts can represent different time zones and working patterns, with location-specific holiday lists attached. A user’s shift change may take effect immediately or be scheduled up to six months ahead. The chosen first day of the week also controls weekly calculations in reports, smart filters, and metrics.
The 24-hour window is a technical constraint
With the WhatsApp Business integration, a business cannot begin an unrestricted conversation. Sending requires a template approved by Meta. Templates are prepared in the WhatsApp Notification tab under Actions in Automation and enter Meta review when saved. They cannot be edited during review or after approval. Data from other modules may be used, but delivery goes only to a Lead or Contact record.
Every conversation has a 24-hour messaging window, during which the customer may send unlimited messages. Charging is conversation-based, belongs to Meta, and is not included in a Zoho license. Decisions about an overnight message therefore cannot depend only on staff availability. The open conversation window and the requirement for an approved template also belong in the response plan, without assuming a particular charge.
Define who takes ownership after hours
During integration setup, the party responsible for incoming inquiries can be designated in advance as a user or role, which then receives a notification when a message arrives. The Assign Owner option limited to online users makes no assignment if none of the selected users is online through the web. It appears only when users are chosen through category-based and criteria-based selection.
When no user qualifies, a record may remain with the default assignee. Assignment Threshold can redistribute such records using a frequency and maximum waiting period expressed in minutes, hours, days, business hours, or business days. When that period ends, routing can follow the assignment rule or use round robin among selected users, ordered first in, first out or by a chosen field.
Cadences for staged follow-up
Cadences provides multi-step follow-up through email, tasks, calls, and WhatsApp. Once a response is received, the record leaves the sequence. A WhatsApp step requires Business Messaging to be enabled, and the following action may use only Delivered or Failed as its condition. The sequence can therefore stop retaining a responsive record and continue according to the documented channel outcome.
Follow-up capacity depends on the plan: the create limit is 20 in Standard, 40 in Professional, 60 in Enterprise, and 70 in Ultimate, while the documented active limits are 10, 20, 30, and 50. The feature begins with Standard and is absent from Free. When planning after-hours communication, these limits should be considered before creating separate sequences for every country or team. The capacity belongs to the plan and does not imply coverage for an undocumented module.
Scheduled email is not scheduled automation
Email scheduling inside CRM is available in Enterprise and Ultimate. Its four choices are Zia’s suggested best time, one hour after creation, 8 p.m. the next day in the organization’s time zone, and a custom date and time with a specified time zone. A scheduled message appears in the record’s email related list and can be edited or cancelled before sending.
Schedules works differently: it runs only a custom function, no more frequently than daily, with at most ten schedules per organization. Manual execution is limited to twice per day, and hourly or minute-based recurrence is unavailable. The required custom function starts with Enterprise. Eksenium’s WA Mesaj Planla widget opens in a new window from a custom button on Contact, Lead, and Vendor record-detail pages in Zoho CRM. Its page and backend run on Eksenium’s own server; it is not a module installed in CRM. Users select the sender, approved template, and sending time, and no live clinic use or field success is claimed.
Visibility follows the role hierarchy
The WhatsApp integration adds a Messages module to Zoho CRM, where conversations, attachments, and the activity timeline are recorded. Access to conversations is permission-based. Users in the record owner’s role and in higher roles may see the conversation when they also have permission to view the record. Morning access must therefore be designed through ownership and role structure, not through message notification alone.
A coordinator calls according to their own clock rather than the patient’s. At the other end, the phone rings after midnight. The conversation is brief, and the record stays open. This shows that seeing a conversation does not mean knowing the correct local time. Organizational time, role access, and handoff responsibility must align, or an accessible record may still be handled at the wrong hour.
Measure what remains until morning
The thresholds should be read together. Cadences starts with Standard, is unavailable in Free, and has follow-up create limits of 20, 40, 60, and 70. CRM email scheduling belongs to Enterprise and Ultimate, while the custom function needed by Schedules starts with Enterprise. WhatsApp requires a WhatsApp Business account and Meta Cloud API rather than a stated CRM tier. The Business Hours and shift tier remains unspecified and should be verified in Setup before proposal.
The morning check should focus on records waiting with the default assignee and how long they have remained there. Redistribution can be configured in business hours, interpreted through the organization’s time zone. A monitoring view does not trigger action by itself. Its value comes from exposing pending records and showing clearly which threshold and ownership arrangement govern their eventual handoff to an eligible person.
