---
name: gmail-customer-feedback-digest
description: "Every Friday: the customer feedback that arrived by email this week, sorted into feature requests, bugs and praise, with short quotes. Use when the user asks for this, or when it runs on a schedule."
---

# Gmail customer feedback digest

Every Friday: the customer feedback that arrived by email this week, sorted into feature requests, bugs and praise, with short quotes.

Not every customer opens a ticket. Plenty reply to an onboarding email, write to the founder directly, or answer a newsletter with two paragraphs about what annoys them. That feedback lands in Gmail and stays there, out of reach of the product team and of whoever runs the support queue.

Once a week the agent searches the inboxes or aliases you name, skips newsletters and automated mail, and sorts what customers wrote into feature requests, bugs and praise. Each item keeps a short quote and the sender's company, so a PM knows who to follow up with.

## Two ways to get the data

Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used.

## Route A: API or MCP server

### What you need

- Read access to the Gmail inbox or shared alias where feedback arrives: a Gmail connector, or an OAuth client with the `gmail.readonly` scope.
- The addresses or label that collect feedback (for example `feedback@` or a `customer-feedback` label).

If something is missing, say what and stop; do not invent numbers.

### Steps

1. **Search the week's mail** (Gmail): Call `users.messages.list` with a `q` such as `newer_than:7d (to:feedback@example.com OR to:hello@example.com OR label:customer-feedback) -category:promotions -category:social -from:me`, paging with `pageToken`.
2. **Read and filter** (Gmail): Fetch each message with `users.messages.get` (`format: "full"`), take the plain text part and drop quoted replies and signatures. Skip auto-replies, receipts and anything with a `List-Unsubscribe` header.
3. **Classify and merge**: Sort each email into feature request, bug report, praise or other. Merge emails that ask for the same thing and count how many customers asked for it.
4. **Check for replies** (Gmail): Use `users.threads.get` to see whether someone on your side already answered in the thread, and note the sender's company from their email domain rather than their address.
5. **Write the digest**: Counts per group, then items with the most customers first, each with a quote under 30 words. Anything that sounds like an outage or a billing error goes to the top, whatever its count.

## Route B: the browser

### What you need

- Signed in to Google in the mailbox that receives feedback, or an account the shared alias is delegated to; delegated mailboxes open from the account menu.

If something is missing, say what and stop; do not invent numbers.

### Steps

Start at https://mail.google.com/. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.

1. **Search the week**: Pick the account or shared mailbox where feedback arrives. In the search box type `newer_than:7d (to:feedback@example.com OR to:hello@example.com OR label:customer-feedback) -category:promotions -category:social -from:me` and press Enter.
2. **Open and read each thread**: Open each result, read the newest message from the customer only (click the three dots to expand trimmed quoted text only when the new part is unclear). Skip auto-replies, receipts and newsletters, which show an **Unsubscribe** link next to the sender.
3. **Classify and merge**: Sort each email into feature request, bug report, praise or other. Merge emails that ask for the same thing and count the customers behind each item.
4. **Check for a reply**: In the same thread view, see whether a message from your side follows the customer's. Take the company from the sender's domain (hover over the name to see the address), not from the signature.
5. **Write the digest**: Counts per group, then items with the most customers first, each with a quote under 30 words and the company. Anything that sounds like an outage or a billing error goes to the top.

Note: Gmail shows 50 threads a page by default, so a busy week means paging. The `label:` operator only matches labels on this account; a shared alias forwarded into several inboxes needs the search run in each.

## The report

- **Counts** of feature requests, bug reports and praise this week.
- **Grouped items**, most customers first, with a short quote and the sender's company.
- **Unanswered**: feedback nobody on your side has replied to.
- Bugs that sound like an outage or a billing error, at the top.

## Post it to Briefkin

When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on.

```bash
[ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env
curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \
  -H "authorization: Bearer $BRIEFKIN_TOKEN" \
  -H "content-type: application/json" \
  -d @- <<'JSON'
{
  "v": 1,
  "event_id": "gmail-customer-feedback-digest/<date of this run, e.g. 2026-10-16>",
  "item_key": "gmail-customer-feedback-digest",
  "project": "Acme",
  "source": "Gmail customer feedback digest skill",
  "kind": "update",
  "title": "27 feedback emails: 12 requests, 9 bugs, 6 praise",
  "summary": "**27** customer emails this week. The most asked-for feature is **two-way calendar sync** (5 customers). One bug report describes duplicate invoices and has no reply yet.",
  "widget": [
    {
      "type": "Grid",
      "props": {
        "columns": 3
      },
      "children": [
        {
          "type": "Stat",
          "props": {
            "label": "Feature requests",
            "value": 12
          }
        },
        {
          "type": "Stat",
          "props": {
            "label": "Bug reports",
            "value": 9,
            "tone": "warn"
          }
        },
        {
          "type": "Stat",
          "props": {
            "label": "Praise",
            "value": 6,
            "tone": "ok"
          }
        }
      ]
    },
    {
      "type": "Table",
      "props": {
        "columns": [
          "Type",
          "What they wrote about",
          "Customers",
          "Replied"
        ],
        "align": [
          "left",
          "left",
          "right",
          "right"
        ],
        "rows": [
          [
            "Bug",
            "Duplicate invoices after a plan change",
            1,
            "0 of 1"
          ],
          [
            "Request",
            "Two-way calendar sync",
            5,
            "3 of 5"
          ],
          [
            "Bug",
            "Mobile app logs out every day",
            4,
            "2 of 4"
          ],
          [
            "Praise",
            "The new onboarding checklist",
            4,
            "4 of 4"
          ],
          [
            "Request",
            "Export reports to PDF",
            3,
            "1 of 3"
          ],
          [
            "Bug",
            "Reminders show the wrong time zone",
            3,
            "3 of 3"
          ],
          [
            "Request",
            "More granular user roles",
            2,
            "2 of 2"
          ],
          [
            "Request",
            "Dark mode",
            2,
            "0 of 2"
          ],
          [
            "Praise",
            "A support reply from Aisha",
            2,
            "2 of 2"
          ],
          [
            "Bug",
            "Search misses archived items",
            1,
            "1 of 1"
          ]
        ]
      }
    },
    {
      "type": "Callout",
      "props": {
        "text": "\"We were charged twice after upgrading and both invoices went to our accountant.\" Lucerne Publishing, no reply yet.",
        "tone": "bad"
      }
    }
  ]
}
JSON
```

Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report.

## Run it on a schedule

Suggested: Fridays at 15:00 (`0 15 * * 5`). From cron, with the agent signed in on that machine:

```bash
0 15 * * 5 claude -p "Run the gmail-customer-feedback-digest skill"
# Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run
```

Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/gmail-customer-feedback-digest#schedule

Source: https://briefkin.dev/skills/gmail-customer-feedback-digest
