“My appointment setter just quit” — what to do this week

Cover the live conversations first and hire second. Booked calls are the safest thing you own; mid-thread conversations decay in days. Replacing the seat takes roughly 19 weeks — SHRM puts 2025 median time-to-fill at about a month and a half, and The Bridge Group puts average SDR ramp at 3.0 months.

At a glance: the first week after “my appointment setter just quit”

• Today: secure access, redirect the inbox and phone, pause anything still sending from their mailbox, and list every conversation that had a reply in the last 7 days.
• Within 24 hours: personally confirm every booked call in the next 14 days from a named human, and put an owner on inbound.
• Days 2–7: work the open threads in decay order, not arrival order. Reassign every dated follow-up to a person, not a queue.
• Don’t panic-hire: about a month and a half to fill plus 3.0 months to ramp is roughly 19 weeks before a replacement is at full output — and that is before any notice period they owe.
• Not us, them: final pay, notice, restraint clauses and data they may have taken are questions for an employment lawyer or your workplace regulator, not a lead-gen vendor.

Is it as bad as it feels? What actually breaks when an appointment setter quits

Less than you think this week, and more than you think next month. Sales development output is lagged: the meetings on your calendar right now were created by work your setter did three to six weeks ago. The hole does not appear the week they leave — it appears four to six weeks later, when the meetings they would have booked simply do not exist.

So the panic about this week’s calendar is usually misplaced. Booked calls do not evaporate because the person who booked them resigned; they fail at the reminder step, when a confirmation that used to come from a named human stops arriving. That is a 20-minute fix you can do yourself tonight. What genuinely breaks is the middle: the half-finished conversations that lived in one person’s inbox and head. Nobody else knows those people said “call me after the 20th.”

The first 24 hours: seven moves that cost nothing

None of these require a vendor, a budget or a decision. Do them before you write a job ad.

1. Export before you revoke. Pull their CRM activity, sent folder and call log to a file you control, then change credentials. Revoking first is how businesses lose their own conversation history.
2. Redirect the channels. Forward their email to a shared inbox and their extension or mobile number to a person who will answer. A prospect who rings a dead line is gone.
3. Pause anything still sending. Sequences firing from a departed mailbox generate replies nobody reads and bounces that damage your sending domain.
4. List every thread with a reply in the last 7 days. That is your week-one work list, and it is usually shorter than people fear.
5. Confirm the next 14 days of booked calls by hand, from a named person, with a one-line reason the meeting still matters.
6. Put a name and a time on inbound. Every form fill, ad enquiry or chat needs an owner before close of business — response speed works the same whether you have a setter or not, as our guide to the 5-minute speed-to-lead rule sets out.
7. Ask them for a handover list. Most leavers will write one if you ask decently in the first 48 hours. Almost nobody asks.

Where we are not the answer: notice periods, final pay, withheld pay and restraint-of-trade clauses are legal questions. In Australia the Fair Work Ombudsman publishes the rules on minimum notice and final pay when an employee resigns; in the US, start with your state labor department. If client data left with them, that is a lawyer on day one. General information only, not legal advice.

Which conversations must not drop in week one

The decay-order rule: work the conversations in the order they go cold, not the order they arrived. Inboxes are chronological; decay is not. A form fill from this morning outranks a warm reply from last Tuesday, which outranks a quote sent in July — and an inbox sorted by date gives you exactly the wrong sequence. The decay windows below are the operating rule we run on our own campaigns, not a published study; adjust them to your sales cycle.

Work down from the top three rows, and do not open the dormant database until the live conversations are covered. Reactivating an old list is a good move, but it is a month-two move; doing it in week one is how people avoid the harder job of answering the people already talking to them.

Days 2–7: covering the gap without panic-hiring

Run the arithmetic on doing it by hand before you decide. A realistic week-one load: 200 open threads × 2 touches each × 3 minutes per touch to read the history and write a reply a human would answer = 1,200 minutes, or 20 hours. Add inbound, and that is one person’s entire week. Substitute your own numbers — the shape rarely changes.

Three ways people cover it:

• Absorb it internally. Free and immediate, and it costs your closers selling time. Works for two to three weeks; beyond that you are funding coverage with lost close rate.
• Contract or temp setter. Days to start, no product ramp. Quality is a lottery, and they leave when the replacement lands.
• Hand the top-of-funnel to a service or an AI agent. Starts in days rather than months and does not resign, which is the entire point in this situation. It still needs your offer, your qualification rules and your calendar, and it still has a ramp of its own — set out plainly in how long AI outbound takes to ramp. Anyone who says it is instant is selling. The mechanics are on our AI appointment setting page; across our own campaigns that model has booked 50,769+ sales appointments since 2017.

My SDR resigned — what does replacing them actually take?

Longer than the budget spreadsheet assumes. Two independent benchmarks bracket it:

So “I’ll just hire someone” is a correct answer to a different question: it solves month five, not this month. The honest wrinkle in the other direction: if you already have a known candidate or an internal mover, time-to-fill can collapse to a fortnight. The ramp does not collapse — that 3.0-month average is the lowest The Bridge Group has recorded since 2010 and it still assumes a functioning onboarding process. The same study puts median annual SDR attrition at 40%. The full-cost version of the hire-versus-buy decision is in AI appointment setting vs hiring SDRs.

Cover it in-house or hand it over? The crossover point

These conversation-volume thresholds are our own operating rule for when coverage stops being absorbable in-house. They are not a published benchmark — move them to fit your sales cycle and your team’s spare capacity.

That last row matters: if your sales development rep quit because the offer was hard to book, replacing the person changes nothing. No service, human or AI, converts an offer the market does not want.

The fix that stops this happening again

With median annual SDR attrition at 40%, a single-setter team is not unlucky when it loses its setter — it is on schedule. The structural fix is not loyalty, it is making the capacity legible:

• Conversations live in the CRM, not a mailbox. Every touch logged, every promise a dated task with an owner. If a resignation can delete your context, the context is in the wrong place.
• Written qualification rules. Budget, timing and fit criteria on a page, so anyone can apply them the same way on day one.
• Sequences owned by the business, sending from a role address rather than a person’s name.
• A second source of booked calls that is not a human seat, so no single resignation empties the calendar.

Do those four and the next resignation costs you a week, not a quarter. Across clients who supplied both numbers we publish a 7x average sales lift at month six, and the same methodology page discloses that the median is closer to 4x — an average is not a promise. This page sits in our cluster of sales-emergency triage guides, alongside the ones on an empty pipeline, leads that dried up overnight, and a closer resigning mid-quarter.

Common questions

My SDR resigned — what do I do first?

Export their CRM activity and sent folder before you revoke access, forward their inbox and phone to a person who will answer, and pause any sequence still sending from their mailbox. Then list every conversation that received a reply in the last 7 days — that list, not the job ad, is your week-one work.

Should I hire a replacement appointment setter straight away?

Start the search, but do not treat it as coverage. SHRM’s 2025 recruiting benchmarking found median time-to-fill is roughly a month and a half for both executive and nonexecutive positions, and The Bridge Group’s 2025 SDR report (351 B2B companies) puts average SDR ramp at 3.0 months. That is about 19 weeks to full output, before any notice period.

How long before my pipeline shows the gap?

Four to six weeks, in most sales cycles. Sales development output is lagged, so the calendar looks normal for a month and then thins out. Two quiet weeks after a resignation is arithmetic, not a collapse — six quiet weeks is a trend, and by then the cause is 30 days old.

Can I just ask my closers to cover the setter’s work?

For two to three weeks, yes. Run the numbers first: 200 open threads at two touches each and three minutes a touch is 20 hours in week one, before inbound. Past about three weeks you are funding coverage with your closers’ selling time, which is the most expensive hour in the business.

We lost our appointment setter and they took the contact list. What now?

That is a legal question before it is a sales one. Get advice on your employment contract and any confidentiality or restraint clause — the Fair Work Ombudsman’s resignation guidance covers notice and final pay in Australia, and a lawyer covers the data. Separately, rebuild from your CRM export, which is why you take it before revoking access.

Should I restart the cold sequences under someone else’s name?

Not in week one. Replies land with a stranger who has no context, and a new sending identity on a cold domain harms deliverability. Pause, cover the live conversations, and relaunch outbound deliberately once someone — or something — owns it properly.