A business with a season

The two dials, and the third that is not one#

The last row is the point of the page. Suppression, do-not-contact, the single send boundary and the three layers of workspace isolation are not things you relax under pressure. A season is a volume problem, and every mechanism that would be tempting to loosen is one whose failure costs more than the season is worth.

What actually limits you at peak#

Simultaneous calls

ring refuses not_ready when every live worker is over a one-minute load of 0.85 per core — the same number the worker gives its own admission control, so the gate and the fleet agree rather than fighting. A refused call is recorded and appears in Needs You; it is not a silent drop.

The daily allowance

When it is spent, work is held rather than dropped and the mail read cursor deliberately does not advance. That is the difference between a backlog and permanent loss.

The voice budget

budget_refusal is asked before an outbound call and before answering an inbound one. A refused inbound gets the spoken closed-line message rather than silence — worth knowing before your busiest Saturday.

Model availability

A 429 or a revoked key opens a breaker: scheduled work is skipped and a caller already on the line is still attempted. The priority ordering there is deliberate.

Call length

Sessions are capped, and sweep_stale holds every provider to the configured cap from the engine tick as well as the worker heartbeat — because a browser call has no worker, and one once sat active for 24.78 hours.

Before the season, in order#

1. Load the season's Knowledge — this year's dates, prices you publish, what changes, what does not.

   Result Answers are grounded in the current season rather than last one's document, and anything unsupported is refused rather than improvised.

2. Rehearse on draft_only a fortnight early.

   Result Connect writes what it would send against real traffic and asks nobody. You read a week of genuine replies before widening anything.

3. Extend line hours and check the line answers on each number.

   Result Hours live on channel_routes rather than in an instruction, so this is a configuration check with a definite answer.

4. Widen autonomy channel by channel, narrowest scope last.

   Result Exceptions you have set against particular contacts keep winning, because the narrowest applicable scope always does.

5. Watch Needs You and the usage screen daily for the first week.

   Result Refusals, held work and line health are all visible in one queue, and the real shape of the peak is measured rather than guessed.

After it ends#

The tempting mistake is to leave everything wide because it worked. A quieter month with autonomous still set on every channel is when an unusual message gets an automatic answer that nobody reads until a customer complains. Narrow the scopes back, or set the seasonal channel to off — which disables it without deleting anything — and keep the records, memory and follow-ups exactly where they are for next year.

Questions#

Related#

• Prepare for a busy period
• Capacity and admission control
• The daily email allowance
• Turning Connect on and off
• Business hours and the closed line
• Usage and allowances