## TL;DR
Canned responses in a shared inbox need three things: one shared library everyone pulls from (not personal collections), a naming convention so agents find them, and an owner who keeps them current. Set permissions so anyone can use but only leads can edit. Review quarterly. Personal snippet collections in a shared inbox are how five different answers to the same question happen.

## The query

```text
how to set up canned responses in a shared inbox
```

## Use this when

- A team shares an inbox and answers inconsistently
- Setting up a new shared inbox
- Canned responses drift out of date
- New agents do not know the responses exist

## Not for

- Chatbot automation
- Personal email templates
- Help-center authoring
- Marketing email templates

## Steps

### 1. Create one shared library

Every canned response lives in the shared library, visible to the whole team. Ban personal collections for customer-facing answers. One library, one truth.

Expected output: a single shared library, personal stashes migrated or deleted.

### 2. Set use-anyone, edit-leads permissions

Any agent can insert a response. Only team leads can create, edit, or retire them. Open editing in a shared inbox produces duplicates and contradictions within weeks.

Expected output: permissions configured.

### 3. Apply a naming convention

Category-first names (billing: refund status, accounts: password reset) so agents find responses by search. Without naming, the library becomes a scroll-and-hope list.

Expected output: the library renamed to the convention.

### 4. Build the starter set from real tickets

Top 20 ticket intents from the last 90 days. Write each response once, well, with personalization slots ([Name], [order ID]). A starter set grounded in volume gets used; a guessed set does not.

Expected output: 20 responses covering the top intents.

### 5. Assign an owner and a review cadence

One person owns the library: quarterly review, updates after product changes, retirement of dead responses. Put the review on the calendar. Libraries without owners rot.

Expected output: a named owner and a quarterly review date.

## Template: the setup checklist

```text
SHARED INBOX CANNED RESPONSES
[ ] Shared library created; personal collections retired
[ ] Permissions: all agents use, leads edit
[ ] Naming convention applied (category: intent)
[ ] Starter set: top 20 intents written with [slots]
[ ] Owner named: __
[ ] Quarterly review scheduled: __
[ ] New-agent onboarding includes a 15-min library tour

RULES: one current version per intent. Personalize the slots, not the structure. Suggest improvements to the owner; do not fork your own copy.
```

## Variant phrasings

### shared inbox templates setup

Steps 1, 2, and 4. Library, permissions, starter set.

### team email canned responses

Full sequence. The owner in step 5 is what sustains it.

### agents giving inconsistent answers

Steps 1 and 4. One library built from real tickets.

## Why it works

Shared inboxes fail on consistency: five agents, five answers. The shared library fixes the source of truth, permissions protect it, naming makes it findable, and ownership keeps it alive. The starter set from real tickets ensures day-one usefulness instead of an empty library nobody opens.

## Edge cases

- Multiple brands in one inbox: prefix names by brand (acme: billing: refund). One library can serve several brands with naming discipline.
- Languages: one response per language, linked by naming (billing: refund: es). Do not mix languages in one response.
- The owner leaves: reassign immediately. An ownerless library starts rotting the same quarter.
- Agents bypassing with personal text: usually means the library is missing intents. Ask what they are writing by hand and add it.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst__DNx9E3_SLDo5UEHmdgTJg