The 7x24 Heatmap: When Your Customers Actually Message

TL;DR: The aiSTAFF dashboard includes a 7x24 heatmap that maps every conversation by day and hour, showing the real demand pattern so you can schedule promos, staff handoffs, and ad budget around it.

What the 7x24 heatmap shows

The heatmap is a grid: seven rows for the days of the week, twenty-four columns for the hours of the day. Each cell is shaded by how many conversations happened in that hour on that day. A dark block at Saturday 8pm means Saturday evening is your busiest window. A pale strip across weekday mornings means almost nobody messages before 10am. One glance replaces a spreadsheet.

It sits inside the wider analytics view, alongside message counts, unique users, response time, fallback and escalation counts, and token usage. The heatmap is the part owners come back to, because it answers a question they could never answer before: when, exactly, do my customers want me? If you want this dashboard running on your own bot, our AI chatbot development service ships it. The full platform sits in the aiSTAFF hub.

Why timing data changes decisions

Most Georgian SMB owners run on a hunch about their busy hours, and the hunch is usually wrong. People assume midday is peak because that is when the shop feels busy in person. The chat data tends to tell a different story: a large share of Instagram and WhatsApp messages land after 7pm, when the customer is home and scrolling. If you staffed a human to answer chats from 9am to 6pm, you were covering the quiet half and missing the loud half.

Once you can see the real curve, the decisions get easy. You schedule your ad spend to land before the evening spike, not after it. You set a promo to go out an hour before the busiest window. You make sure your escalation contact is awake and reachable during the hours that generate leads. None of this is guesswork once the grid is in front of you.

How to read the grid

A few patterns show up again and again, and each one points to an action:

• An evening band. Dark cells from 7pm to 11pm across most days means your customers are night shoppers. An always-on agent earns its keep here, since this is the window a human would miss.
• A weekend peak. If Saturday and Sunday glow while weekdays are dim, your audience shops on days off. Time your weekly promo for Friday evening.
• A lunch bump. A bright column around 1pm suggests people message on their break. Short, fast answers win that slot.
• A dead zone. The hours that stay pale are where you should never schedule a campaign or expect a reply rush.

The heatmap also reads per channel. Your Telegram crowd might peak at a different hour than your Messenger crowd, so you can tune each one. That ties into running one brain across five channels while still treating them as distinct audiences, and it pairs with the per-channel KPIs that sit next to the grid.

A worked example

A cosmetics store connected aiSTAFF to Instagram and a website widget. The owner believed her busy time was midday, because that is when foot traffic peaked at the counter. After two weeks the heatmap showed the opposite: chat volume on Instagram doubled between 9pm and 11pm, with a hard spike on Sunday night. She moved her weekly discount post to Sunday 8pm, an hour before the peak, and let the agent answer the wave that followed. The same budget, pointed at the right hour, pulled more conversations and more captured leads. She did not spend a lari more, she spent it at the right time.

The agent did the answering, so the late spike was not a staffing problem. She read the grid the next morning, saw where the volume landed, and adjusted. That loop, see the pattern then act on it, is what the dashboard is for. Capturing those late leads instead of losing them is the same logic behind choosing where your bot lives.

What the rest of the dashboard adds

The heatmap answers "when." The other panels answer "how well." Response time confirms the agent is fast. Fallback and escalation counts show how often it could not answer and had to route to a person, which tells you where your knowledge base has gaps. Token usage tracks cost against your plan. Unique users separates real reach from a handful of chatty repeat customers. Read together, you get a weekly health check on the agent without reading a single transcript. For the metrics worth tracking on any bot, the broader read is in support automation efficiency, and developers wiring this data elsewhere can pull it through the Bot API or surface it next to the streaming widget on site.

Related reading

• aiSTAFF: One AI Brain Across Every Channel
• One Message Quota Across All Channels
• One AI Brain, Five Channels

FAQ

What does a 7x24 heatmap mean?

It is a grid of 7 days by 24 hours. Each cell shows how many conversations happened in that hour on that day, so darker cells mark your busiest windows.

Can I see the heatmap per channel?

Yes. The analytics view splits by channel, so you can compare when your Instagram, WhatsApp, Telegram, and website audiences message and tune each one.

What else does the dashboard report?

Messages, unique users, response time, fallback and escalation counts, and token usage, with daily trends, all split per channel next to the heatmap.

How does the heatmap help my marketing?

It shows the exact hours customers message, so you can schedule promos and ad spend to land right before the busiest window instead of guessing.