Guides · long-form, readable, opinionated

Playbooks for teams who answer like humans.

Opinionated pieces on the craft of small-team support — channel by channel, workflow by workflow. Each guide is a self-contained essay, longer than a doc entry and quieter than a blog post. Read one with coffee. Disagree with us in writing if it helps.

EDITOR'S PICK · STRATEGY

On the cost of breaking a customer's one thread.

The one-thread doctrine: how to stop fracturing customer conversations.

Every help desk we've used assumed the ticket was the unit of work. We think the thread is. This is the case for designing support around a single continuous conversation per customer — and what it costs you when you don't.

12 min read · STRATEGY

The library

By the way you actually work.

STRATEGY

Routing without regex.

How to write rules that read like sentences and still do the job.

DISCORD

Discord as a support channel, actually.

The four lessons we learned the hard way running support inside a community server.

WORKFLOW

Macros that listen.

Writing saved replies that adapt to context, instead of pasting walls of canned text.

WORKFLOW

The Monday inbox triage.

A 20-minute weekly habit that keeps the open-conversations queue from compounding.

MIGRATIONS

From four tabs to one thread.

Migrating a small support team off a ticket portal without scaring the customer base.

CHANNELS

Slack DMs vs. shared channels.

Why the two cases need different routing, and how to set both up cleanly.

STRATEGY

The case against ticket numbers.

What you lose when every interaction starts with a six-digit ID, and what to use instead.

Field notes

Subscribe to the field notes.

One quiet guide a quarter — never more. Unsubscribe in one click.

↳ same form lives in the footer.

Docs →·Changelog →·Customers →