## TL;DR
First-response goals should match the channel's promise: chat is seconds to a couple of minutes, phone is immediate, email is hours, social is under an hour. Set targets from your actual distribution, not from a blog post: take your current median, shave it 20 percent, and staff to that. A goal the team hits 90 percent of the time beats an aspirational goal they hit 40 percent of the time.

## The query

```text
first-response time goals by channel
```

## Use this when

- Setting SLAs or internal targets for the first time
- Leadership asks why email is slower than chat
- Staffing the team to a response target
- One channel's response time is clearly broken

## Not for

- Resolution-time targets (different metric)
- SLA contract language with customers
- Individual agent performance plans
- 24/7 coverage decisions

## Steps

### 1. Start from channel norms, then adjust to your data

Reasonable starting points: chat under 2 minutes, phone answered immediately, email under 4 business hours, social under 1 hour. Then pull your actual medians per channel. If email's median is 9 hours, a 1-hour goal is fiction.

Expected output: starting goals plus your actual medians side by side.

### 2. Set the goal at a reachable stretch

Take the current median and target 20 percent better, with 90 percent attainment. Goals exist to be hit reliably, not to decorate a slide. Tighten quarterly as the team improves.

Expected output: a goal per channel with an attainment target.

### 3. Separate business hours from the clock

Email "4 hours" means 4 business hours, and everyone must know the business hours. Publish them. Chat outside hours should say "we reply in the morning" instead of silently queueing.

Expected output: published hours attached to every goal.

### 4. Staff to the goal, not the other way around

A chat goal of 2 minutes needs enough concurrent agents for peak volume. Model it: arrivals per hour, average handle time, target wait. If the math does not work, change the goal or the staffing, not the agents' effort.

Expected output: a staffing model per channel.

### 5. Review monthly and tighten slowly

Track attainment weekly. When a channel holds 95 percent attainment for a month, tighten the goal 10 to 15 percent. Never tighten two channels in the same month.

Expected output: a monthly review cadence.

## Template: the goals table

```text
Channel | Goal | Attainment target | Hours | Notes
Chat | < 2 min | 90% | 8am-8pm ET | bot deflects first, human on escalation
Phone | < 30 sec | 90% | 9am-6pm ET | callback offered at 2 min queue
Email | < 4 business h | 90% | 9am-6pm ET, M-F | auto-ack immediately
Social | < 1 h | 85% | 8am-10pm ET | triage only, move to DM/ticket

Review: first Monday monthly. Tighten rule: 95% attainment for a month, then -10%.
```

## Variant phrasings

### support response time benchmarks

Step 1. Norms plus your own medians.

### SLA for first response by channel

Steps 1 through 3. Goals, attainment, and published hours.

### email response time too slow

Steps 1, 2, and 4. Measure, set a reachable goal, staff to it.

## Why it works

First response is the customer's first signal that they have been heard. Channel-appropriate goals respect what each channel promises: nobody expects a 2-minute email reply, and nobody tolerates a 4-hour chat wait. Reachable goals keep the team honest; impossible goals teach everyone to ignore the metric.

## Edge cases

- VIP tiers: separate, tighter goals. Do not average VIPs into the general number.
- After-hours: the goal clock pauses, but the auto-acknowledgment must state when a human replies.
- Seasonal spikes: set a separate spike goal rather than blowing the normal one.
- Bot-handled chats: measure human first response separately from bot first response.

## Provenance

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