---
title: "A 24/7 AI agent needs to know what day it is"
description: "An automatic follow-up set to 48 hours can go out on a Sunday with nobody there to answer. What to configure on day one so that never happens."
url: https://studiochat.io/blog/un-agente-24-7-necesita-saber-que-dia-es-hoy
locale: en
translations: { es: https://studiochat.io/es/blog/un-agente-24-7-necesita-saber-que-dia-es-hoy.md, pt: https://studiochat.io/pt/blog/un-agente-24-7-necesita-saber-que-dia-es-hoy.md }
site: https://studiochat.io
---

[ Back to blog](/blog)

A reminder set to 48 hours goes out on a Sunday at ten in the morning. The customer replies right away, because on a Sunday morning people have time. On the other side there's nobody until Monday, and by Monday that conversation has gone cold. It's a real case a customer told us about, from an automation that predates us, and it's one of the most common mistakes there is.

## [Why does a 48 hour follow-up land at the worst possible moment?](#why-does-a-48-hour-follow-up-land-at-the-worst-possible-moment)

Because almost every automation counts in calendar days and almost every business runs on business days. They're two different clocks and nobody reconciles them at configuration time.

A lead who writes on a Friday afternoon gets the follow-up on Sunday. One who writes on the Thursday of a week with a Monday holiday gets theirs when the store is closed. The agent did exactly what it was told. What was wrong was the unit of time.

## [What is WhatsApp's 24 hour window and why does it matter here?](#what-is-whatsapps-24-hour-window-and-why-does-it-matter-here)

When a person messages a company on WhatsApp, a 24 hour window opens during which the company can reply with ordinary messages. If the person writes again, the window resets. Once those 24 hours pass with no activity, the company can no longer pick the thread back up with a free-form message: it can only do so with a template approved in advance. That's the platform's rule, documented by Meta.

This is where the two problems meet. The automatic Sunday message opens a conversation nobody on the team will be able to attend that day. When somebody sits down to reply on Monday, if the customer answered early Sunday and never wrote again, that window may be closed. Picking it back up stops being writing a message and becomes sending a template, which also has to have been approved beforehand.

## [What gets lost when you have to reopen with a template?](#what-gets-lost-when-you-have-to-reopen-with-a-template)

You don't lose the customer, you lose the conversation. A template is fixed text, approved earlier, with none of the context of what was being discussed. Somebody who on Sunday was asking about a specific product gets a generic message on Monday that looks nothing like their conversation.

It also carries a real operating cost: somebody has to write the templates, submit them for approval and maintain them. All of that is work that only appears because the timing was configured wrong.

## [What has to be defined on day one so this doesn't happen?](#what-has-to-be-defined-on-day-one-so-this-doesnt-happen)

Five things, and none of them is technical.

The real hours when humans are available, which are almost never the ones on the website. The holidays of the country being served, actually loaded rather than assumed. Whether the business works Saturdays, because plenty do and the default configuration assumes they don't. The unit follow-ups get counted in, which should be business days rather than rolling hours. And what the agent does when somebody writes out of hours, which is not the same as doing nothing.

That last one deserves its own decision. An agent can answer at three in the morning and resolve what it can resolve on its own. What it shouldn't do is open a topic that needs a person and leave it open until Monday without saying so.

## [So is round-the-clock availability worth it or not?](#so-is-round-the-clock-availability-worth-it-or-not)

It is, but two things that get sold together have to be separated: being available to answer and being available to resolve. The first is real 24 hours a day. The second depends on which part of the process needs a person, and on when that person exists.

An agent that knows what day it is answers on Sunday all the same, resolves what it can, and says precisely when somebody will be there for the rest. That's more honest than a "we'll get back to you shortly" sent at ten on a Sunday morning.

How many of the automations running at a company today count in business days? It's a question almost nobody has checked.

Frequently asked questions

### Can you message a customer on WhatsApp at any time?

Not with a free-form message. Outside the 24 hour window that opens when the customer writes, a company can only pick the conversation back up with a template approved in advance by the platform. Inside that window, the conversation is normal.

### Is it better to switch the agent off outside business hours?

Generally no. It's better for it to keep answering what it can resolve and to be explicit about what will have to wait for business hours, rather than leaving the impression that somebody might reply at any moment.

### How do holidays get configured if the company operates in several countries?

With one calendar per operation, not a single shared one. The same agent covering Argentina and Mexico needs both calendars loaded, because a local holiday turns a correct follow-up into a message nobody will be there to answer.

Share [ X](https://x.com/intent/post?text=Why%20an%20AI%20agent%20available%2024%2F7%20needs%20to%20know%20what%20day%20it%20is&url=https%3A%2F%2Fstudiochat.io%2Fblog%2Fun-agente-24-7-necesita-saber-que-dia-es-hoy) [ LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fstudiochat.io%2Fblog%2Fun-agente-24-7-necesita-saber-que-dia-es-hoy) [ WhatsApp](https://wa.me/?text=Why%20an%20AI%20agent%20available%2024%2F7%20needs%20to%20know%20what%20day%20it%20is%20https%3A%2F%2Fstudiochat.io%2Fblog%2Fun-agente-24-7-necesita-saber-que-dia-es-hoy)Copy link

Cristian Pereyra

Cristian Pereyra · Co-founder · Engineering, StudioChat

Want agents like these working for your team?

[Talk to us now](https://cal.com/studiochat)
