Daily

Get a daily summary of customer conversations

Each evening you get one email on what customers asked about today and what's still open.

Runs: Daily
Apps: Intercom
AI: Yes, uses the built-in AI allowance
Access: read conversations

Send this to your assistant

Create a ClickRuntime automation: every weekday at 6pm, summarise today's Intercom conversations by topic and list the ones still open, then email it to me.

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

The head of support wants to know what customers talked about today, but the only way to find out is to open Intercom and read. There are 150 conversations a day, so nobody reads them all, and the picture comes from whichever threads happened to catch an agent's eye. A confusing checkout error that hit forty customers is only recognized three days later, when somebody mentions it in a meeting.

Each day, ClickRuntime searches Intercom for conversations updated today, passes their content to built-in AI, and emails you a summary of the main themes, notable complaints and common questions. You get a readable picture of the day in a few minutes without reading individual conversations.

Support managers, product managers and founders who want to hear the voice of the customer without reading every thread will use it most.

What you get out of it

Recurring problems show up within a day
A bug or confusing screen that hits many customers appears as a theme in the summary. You can alert engineering the same day, instead of discovering the pattern after another round of complaints.
Product decisions use real customer language
Product managers get a daily sense of what people ask for and what confuses them. That grounds the roadmap in actual questions instead of in the loudest internal opinion. They can bring concrete examples of customer wording into planning meetings the very next morning.
Leaders stay close to customers
Founders and executives rarely read support threads, but they can read a short email. A daily summary keeps them informed about customer sentiment and avoids the disconnect that grows when leadership is far from the front line.
Shifts and teams stay aligned
When support is spread across time zones, the summary tells the next shift what happened earlier. People start work knowing which issues are active instead of reconstructing it from the inbox.
Knowledge base gaps are exposed
If the summary keeps mentioning the same how-to question, there is a missing or hidden help article. Writing it reduces the number of conversations the next day. Each one costs the team repeat conversations every day until somebody writes the missing article and links it in the messenger.

How it works

What happens, step by step

Every day, ClickRuntime collects the Intercom conversations updated that day.
AI groups them by topic, such as billing questions or login issues, and notes how many are still open.
You get one email with the summary.

Before it runs live

Connect Intercom

What you get

RunsDaily

Get a daily summary of customer conversationstoday, 9:00Succeeded

Email · Intercom todayBilling questions (12), login issues (7), feature requests (4) Still open: 5

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
Change what the AI looks for, or how it writes the result
Add another app, for example also send it to Slack
Combine it with other Intercom 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_ai_summary_of_conversations.pyexample

import re, time
from clickruntime import on_trigger, http, credentials, ai, notify

def intercom(method, path, **kw):
    r = http.request(method, f"https://api.intercom.io{path}", headers={
        "Authorization": f"Bearer {credentials.secret('INTERCOM_TOKEN')}", "Intercom-Version": "2.11"}, **kw)
    r.raise_for_status()
    return r.json()
INBOX = "https://app.intercom.com/a/inbox/_/inbox/conversation/"

@on_trigger
def run(event):
    since = int(time.time()) - 86400
    convos = intercom("POST", "/conversations/search", json={
        "query": {"field": "created_at", "operator": ">", "value": since}, "pagination": {"per_page": 150}})["conversations"]
    lines = [f"{c['id']} [{c['state']}] {re.sub(r'<[^>]+>', '', c['source']['body'] or '')[:300]}" for c in convos]
    summary = ai.generate("Group today's support conversations by topic with counts:\n" + "\n".join(lines),
                          max_output_tokens=500).text
    still_open = "\n".join(f"{INBOX}{c['id']}" for c in convos if c["state"] == "open")
    notify.email_me(f"Intercom today: {len(convos)} conversations", f"{summary}\n\nStill open:\n{still_open or 'none'}")
    return {"conversations": len(convos)}

FAQ

Common questions

Does the summary contain customer names or personal details?

The AI is asked to describe themes and issues, but it reads the conversations to do so, so some details might appear. If the summary goes to a wide audience, ask for it to leave out names and emails, and review the first few before sharing widely.

How many conversations can it summarize in a day?

It reads the conversations Intercom returns for the day, which handles a typical support team's volume. For very high volumes, it can sample or focus on specific tags or teams, so ask if your daily count is in the thousands.

Can I get a summary for just one team or tag?

Yes. You can limit the search to conversations assigned to a team, carrying a tag such as billing, or from a certain channel. Several versions can run side by side, each sent to the person who cares about that topic.

What permissions does it need?

read conversations. Nothing else in your accounts is used.

Does it need AI?

Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly AI allowance.

How many runs does it use?

One run each time it runs (daily). 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.

DailyAI