Skip to content
LET'S TALK
EN▾

← the board · internal pilot · klar

INBOX TO ACTION MAIL TRIAGE

In an internal pilot, Klar joined five PILLAR, Betsa and GrandMa mailboxes into one flow: AI sorted threads, created tasks and sent digests while people kept control of replies.

  • industryB2B operations / internal product
  • faderAutomation & AI
  • countryMulti-market (UA / DE ops)
  • periodPilot · Jun–Jul 2026
  • leakjourney

inbox chaos → structured work.

Klar — MAIL TRIAGE

the starting point

FIVE INBOXES. ZERO SINGLE VIEW.

Working mail for PILLAR, Betsa and GrandMa arrived in five separate accounts. Important threads mixed with lower-priority messages, and the next action depended on manual review. The team lacked one layer that turns incoming mail into priorities, tasks and regular summaries.

what we built

ONE TRIAGE LAYER FOR SHARED MAIL.

Klar sits above connected mailboxes as one operational layer: it classifies threads with AI, routes required actions into tasks and sends scheduled digests. People keep control of replies while the system carries the path from incoming mail to a structured next action.

  1. 01

    CONNECT

    Five accounts across three companies in one triage workspace.

  2. 02

    CLASSIFY

    561 AI results applied to 426 threads from 615 messages.

  3. 03

    TASK & DIGEST

    91 tasks created; 148 digest sends between 13 Jun and 8 Jul 2026.

results

MEASURED THROUGHPUT.

615Messages triaged

426Threads processed

561AI classification results

91Tasks created

148Digest sends

5Mail accounts / 3 companies

five inboxes became a measurable flow of tasks and digests — without a dedicated coordinator.

Klar dashboard — overview with unanswered queue and AI work
proof, as recorded
Klar dashboard — German locale overview
proof, as recorded

the footnote

ONE VISIBLE
MAIL FLOW.

The pilot sorted 615 messages across five mailboxes, created 91 tasks and sent 148 digests.

measured period
Повідомлення, треди та AI-результати: 12–26 червня 2026; задачі й відправлення дайджестів: 13 червня–8 липня 2026
source
public case on grandma.agency, numbers as recorded in the account — no rounding beyond what the label says

who this is for

FOR TEAMS DROWNING IN INBOX.

Operations and leadership teams that share multiple mailboxes and lose time sorting, forwarding and chasing follow-ups manually.

  • Multiple accounts, one place to see what matters
  • AI classification you can route into tasks and digests

timeline

HOW THE PILOT RAN.

  1. 12–26 Jun 2026

    615 messages ingested; 426 threads; 561 AI classification results.

  2. 13 Jun–8 Jul 2026

    91 tasks tracked; 148 digest sends to keep teams aligned.

asked about this case

Does Klar replace your mail client?

No — it sits on top of connected accounts, classifies threads and outputs tasks and digests. Humans still decide on replies.

Which companies were in the pilot?

Five accounts across three companies: PILLAR, Betsa and a GrandMa internal pilot — multi-market UA/DE operations.

What period do the numbers cover?

615 messages / 561 AI results: 12–26 Jun 2026. 91 tasks and 148 digests: 13 Jun–8 Jul 2026. Source: Klar production metrics for the pilot period.

Can this run for a single company inbox?

Yes — the same triage → task → digest loop scales from one account to a shared multi-company setup.

What was broken?

Mail for PILLAR, Betsa and GrandMa arrived in five accounts. Important threads mixed with noise; next actions depended on manual review. No single layer turned mail into priorities, tasks and summaries.

Leak: journey (handoff / ops).

What we did

Klar as one triage layer above connected mailboxes: AI classifies threads → routes actions into tasks → scheduled digests. People keep control of replies.

One number that moved

615 messages triaged (also: 426 threads, 561 AI classification results).

91 tasks created; 148 digest sends.

5 mail accounts / 3 companies (PILLAR, Betsa, GrandMa internal).

Periods: messages/threads/AI results 12–26 Jun 2026; tasks & digests 13 Jun–8 Jul 2026.

Boundaries:

  • Internal pilot, not client revenue proof.
  • Throughput metrics only — not “hours saved,” not reply automation, not CRM deals.
  • AI does not send customer replies in this story; humans decide.
  • Secondary on Automation service page only with this pilot label.

What we refused

Replacing the mail client. Letting AI quietly answer customers. Claiming client P&L from an internal pilot.

FAQ

Replace mail client? No — sits on top; humans reply.

Who was in the pilot? Five accounts / three companies as above.

Periods? As stated.

Single-company? Same loop scales from one account up.

CTA

How many inboxes and follow-ups are manual? → hello@grandma.agency / /contact/. Related: /services/automation-ai-systems/.

write to us

WANT INBOX
WITHOUT CHAOS?

Show us how many inboxes and team follow-ups you handle manually. We will design the shortest path to triage, tasks and regular digests.

No calls, no newsletter. A reply from a person, usually within one working day. Prefer chat? Telegram · hello@grandma.agency

GrandMa in an armchair, answering on her phone
A person from the team replies.

PREFER MESSAGING?

write where it's easier for you.

The same team, the same written answers, in the channel you already use. Usually within one working day.