On a schedule

Get yesterday's chat numbers each morning

A morning email with total chats, satisfaction and first response time.

Runs: On a schedule
Apps: LiveChat
AI: Not needed
Access: reports_read

Send this to your assistant

Create a ClickRuntime automation: every day at 8am, email me yesterday's LiveChat total chats, satisfaction rating and average first response time.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A support manager running a LiveChat team needs to know each morning how yesterday went: how many chats came in, how customers rated them and how long they waited for a first response. Pulling those figures from LiveChat's reports section takes several clicks every day, and when the team is busy it is skipped. Problems that could be spotted on Tuesday are then discovered on Friday.

Each morning, ClickRuntime queries LiveChat's Reports API for the previous day and emails you a summary with the number of chats, the satisfaction ratings and the average response time. The same figures arrive in the same layout every day, so a change is easy to see.

Support leads and owners of small businesses who run chat themselves will find it handy. The figures are the same ones you would find in LiveChat's own reports.

What you get out of it

A bad day is noticed on the next one
If response time doubled yesterday, you know before the day starts and can adjust staffing or find out what caused a surge. Waiting for a weekly report hides problems for days.
Staffing decisions use real numbers
Daily chat volume and response times show when the team is stretched. That is the evidence you need to add a person, change shifts or add self-service answers. That makes the case for headcount much easier to make.
Customer satisfaction is tracked daily
Ratings reported each morning show whether quality is holding. A drop after a change to scripts or tools is noticed early, when it is simple to reverse. That awareness helps you protect the quality of your support.
Reporting costs no time
Nobody needs to open reports, choose a date range and copy figures. The email arrives before the team meeting, and the manager can start with the discussion. Time returned to the team goes toward helping customers.
A history builds in your inbox
A folder of daily emails gives you a ready record of volume and response times through the year. It makes seasonal patterns and the effect of changes easy to see.

How it works

What happens, step by step

Every morning ClickRuntime pulls yesterday's reports from LiveChat.
It gets the total number of chats, how many were rated good or bad and the average first response time.
You get one email with the chat count, the share of good ratings and the response time in seconds.

Before it runs live

Connect LiveChat

What you get

RunsOn a schedule

Get yesterday's chat numbers each morningtoday, 9:00Succeeded

Email · LiveChat daily reportChats: 186 · Satisfaction: 94% good (52 rated) · Avg first response: 38s

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other LiveChat steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

daily_chat_report.pyexample

from datetime import date, timedelta
from clickruntime import on_trigger, credentials, http, notify

@on_trigger
def run(event):
    y = date.today() - timedelta(days=1)
    h = {"Authorization": f"Bearer {credentials.connection('livechat', 'work')}"}
    body = {"filters": {"from": f"{y}T00:00:00Z", "to": f"{y}T23:59:59Z"}, "distribution": "day"}
    def report(name):
        r = http.post(f"https://api.livechatinc.com/v3.5/reports/chats/{name}", json=body, headers=h)
        r.raise_for_status()
        return next(iter(r.json()["records"].values()), {})
    total = report("total_chats").get("total", 0)
    ratings = report("ratings")
    rated = ratings.get("good", 0) + ratings.get("bad", 0)
    good_pct = ratings.get("good", 0) / rated * 100 if rated else 0
    frt = report("first_response_time").get("first_response_time", 0)
    notify.email_me(f"LiveChat {y}", f"Chats: {total}\nSatisfaction: {good_pct:.0f}% good ({rated} rated)\n"
                                     f"Avg first response: {frt:.0f}s")
    return {"chats": total}

FAQ

Common questions

Which figures are in the email?

The default report has the total number of chats, the count of good and bad ratings and the average first response time. You can add others that LiveChat's reports provide, such as chat duration or the number of missed chats, by naming them. The email can be sent to several people if the whole team wants it.

Does it cover weekends?

It runs on the schedule you choose. Many teams run it every day, and a zero-chat Sunday is simply reported as such. If your team is not open on weekends, you can limit the schedule to weekdays, so Monday's email covers the whole weekend instead.

Can I get it for each agent separately?

Yes. LiveChat's reports can be broken down by agent, so the email can include a short table per agent. Use that carefully, since people often react badly to being ranked. It is more useful for identifying who needs support than for comparing them.

What permissions does it need?

reports_read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (on a schedule). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

The moment it happens