Skip to main content

Customer Comms Tracker

Keeps one list of customers your team owes a reply, and flags who's overdue on request or a verified morning schedule.

One of the five in Customer Comms. They share one customer list, and none of them sends unless you turn on auto-send.

Every customer who’s waiting on you, in one morning list

Gmail
Google Calendar
Slack
Circleback
Granola
Fireflies
Help Scout
Your data
Customer Comms Tracker
What it finds
Gmail

Customer Comms Tracker reads Gmail, Google Calendar and the rest of these, then sends what it finds through Gmail.

A morning email from GBrain to Maya, Theo and Priya titled 3 customers are waiting on a reply. Under Follow-up due, three people, each with who they are, what they asked, the teammate who owns them and when they were last contacted. Under Coming up, two more due early next week.
The morning list. Who is waiting, who they are, what they asked and who owns them. The people and companies are made up.

What it does

  • Builds the list from your email, your calendar, your meeting notes and anywhere else your team talks to customers, like Slack or a support desk: who you talked to, who they are, and who on the team owns them.
  • Checks whether each person got their reply, from any teammate, by email, on a call or wherever else you talk to them. Morning checks need an available, verified scheduler; you can also ask for a check now.
  • Flags who is overdue and who is coming up, with one line on who each person is, so nobody has to ask “who’s that?”
  • Notices when a customer writes back and puts them on the list again.
  • Answers “who do we owe a reply?” any time you ask.

The reveal

You tell it who on the team talks to customers, once. After a check there’s a short list: the three people still waiting on an answer, who each of them is, when they last heard from you, and who owns them. The follow-up that would have slipped for a week goes out the same day.

Configuration

  • Your team: who talks to customers, and which inboxes to watch.
  • Other places: anywhere else you talk to customers, like a shared Slack channel or a support desk. Email is the default.
  • Reply window: how quickly a reply should go out. Two business days unless you say otherwise.
  • Delivery: here, an approved email to the team, or their daily recap. Automatic morning delivery requires a verified scheduler.

What it doesn’t do

  • It doesn’t write to your customers. It tells your team who’s waiting; a person sends the reply.
  • It doesn’t track bugs. What customers report can go straight to your team’s tracker with User Chats to Issues.

Triggers

Answers whenever you ask who’s waiting on a reply. With a verified scheduler, it can also run on weekday mornings at the time you approve. Otherwise, resume saved checks manually.

Put Customer Comms Tracker to work

Keeps one list of customers your team owes a reply, and flags who's overdue on request or a verified morning schedule.