Retiring a Support Channel Without a Revolt

At 17:30 on a Friday, Dana switches off the shared mailbox. Not deleted: forwarded, with an auto-reply, which is the part that matters. The mailbox has been the organization's help desk for six years. It has nine hundred and forty unread messages. By Monday its auto-reply will be the most-read e-mail the desk has ever sent. Two hundred people will see it in the first week. Every one of them will be mildly annoyed, and every one of them will be told, in two sentences, where to go instead.

Retiring a channel is the only part of channel strategy that users notice, which is why it is the part that goes wrong. Nobody revolts when a door is opened. They revolt when the door they were using is shut, and the revolt is proportional to how little warning they had. This is the third article in our Channel Strategy series. The first two explained the channels and made the case for one queue. This one is about closing a door without losing the people behind it.

It covers why channels get retired and the three retirements almost every desk does eventually. Those are the shared mailbox, direct-message support in the chat tool, and the direct line to one technician. Next come the ninety-day transition, the communication plan, and the exceptions you will be asked for. Then it covers the auto-reply that does the work, measuring the revolt by week, and ninety days at Meridian Parts. It ends with a retirement checklist to copy.

Why Channels Get Retired

A channel gets retired for one of three reasons: it is unlogged, it is unstaffed, or it duplicates a channel that is better. Unlogged means requests on it do not reach the queue without retyping, so the desk's count is wrong by its volume. Unstaffed means the hours it promises are not the hours anyone answers it. Duplicated means another door does the same job and lands in the queue by itself. The shared mailbox is usually all three.

The decision comes from the census, not from irritation. A week of counting requests by channel, with a logged count beside each, shows which doors carry load and which only cost. The worksheet is in The Support Channels, Explained. Retire the channel with the worst ratio of cost to logged requests, and only one at a time. A desk that closes three doors in a quarter has told its users that nothing is stable. Users respond to instability by using whatever door they can still find.

Retiring is not the same as rerouting, and the difference decides how much communication you owe. Pointing the shared mailbox at the ticket tool, so that mail to the same address becomes a ticket, is rerouting: the user does nothing differently. Ending the practice of humans answering from that mailbox, or of technicians answering direct messages with the fix, is retiring. The user has to change a habit, and habit changes need notice. This article is about the second kind. The first is a Tuesday afternoon's work, and it is in One Queue, Many Doors.

The Three Commonest Retirements

The shared mailbox is the first channel most desks retire, and it is demoted rather than deleted. The address stays alive, because it is in six years of signatures, bookmarks and printed guides. What ends is humans reading it. Mail to the old address is forwarded into the ticket tool, which makes a ticket and sends a receipt. The mailbox's own auto-reply tells the sender the new door. The replacement is often the same address pointed somewhere new, plus the form.

Direct-message support in the chat tool is the second. It cannot be switched off, because the chat tool is where the whole organization already is. What is retired is the practice: technicians no longer answer a direct message with the fix. They answer with a ticket number, having opened the ticket on the user's behalf. The chat tool gets a support space with the form pinned to the top. The replacement is the same message with a number in the reply, which is a smaller change than it feels like.

The direct line to one technician is the third, and the most personal. A phone extension, a personal address or a first-name habit that one person has carried for years becomes the organization's real help desk. That channel retires when that person changes role, goes on leave, or asks for it to stop. The replacement is the desk's number and address, with the technician's own voicemail greeting and auto-reply doing the redirecting, in their own words. The relationship survives. The routing changes.

Each of the three has a door that stays open and a behavior that ends. That is the whole trick of retiring without a revolt. Keep the address, keep the extension, keep the chat tool. Change what happens when someone uses them, so that the old door becomes a short corridor into the new one. That way, nobody who tries the old way is left standing in the dark.

The Ninety-Day Transition

Ninety days is the length of a retirement because it is one quarter. That is long enough for every monthly process to run once on the new door, short enough that the desk does not forget it is in a transition. The plan has five steps, dated from the announcement, and the auto-reply outlives it by another quarter.

Each step exists because skipping it produces a specific failure. Skip the announcement and the first the organization hears of the change is the auto-reply, which reads as a door slammed. Skip the run-both phase and the people who missed the announcement have nowhere to go on day two. Skip the auto-reply and the old door becomes a silence, which is worse than a closed door because nobody knows it is closed. Switch off the forwarding and a request is lost, which is the one thing a retirement must never do. Ninety days feels long to the person waiting to close the mailbox. It is short to the person on leave for three weeks in the middle of it, which is always someone.

The Communication Plan

A communication plan is a list of who hears about the change, when, from whom and in what words. It exists because "we sent an e-mail" is not a plan. People miss e-mails. The plan assumes every person needs to hear the change three times, by two routes. It assumes the third time will be the auto-reply, at the moment they try the old door.

Managers hear first because a manager who learns about the change from their team has been made to look uninformed, and will resent it on principle. Heavy users hear personally because their habit is strongest and their goodwill matters most. The notes cost twenty minutes for the whole list. Reception hears because reception is where people ask. Shifts and sites hear on paper because the all-staff e-mail does not reach a terminal in a warehouse, and never has.

The Exceptions You Will Be Asked For

Three exceptions arrive within a week of the announcement, from the same three places at every organization. The answer to each has the same shape: yes to the need, no to the old door, and here is how the new door meets the need better.

The executive assistant asks for the old address to keep working for the executives' office, because the executives will not use a form. The need is real: speed and discretion for a small group with no patience for process. The answer is that the executives' office never has to touch the form. The assistant sends mail to the support address exactly as before. It becomes a ticket with a number, and the desk treats that requester group as priority. They lose nothing and gain a number to quote when they chase, which assistants value more than anyone.

The warehouse asks to keep phoning the technician's direct line, because the warehouse has gloves, a shared terminal and no time. The need is a door that works with gloves on. The answer is the desk's number, answered the same way, with the ticket opened by the technician during the call. The answer also includes a printed card at the terminal with the number and the hours. Nobody in the warehouse has to type anything. They never did.

The night shift asks what happens at 02:00, when the old mailbox was the only thing that answered. The old mailbox never answered at 02:00 either; it just looked as if it might. The answer is the form, which takes the request at any hour and gives a number at once. The answer also includes a written statement of when a human will see it, plus the out-of-hours number for the one category that cannot wait. That is more than the night shift ever had, and the first time anyone has written it down.

The Auto-Reply That Does the Work

The auto-reply is the most important text in the whole retirement, because it is the only communication that reaches every user at the exact moment they need it. An announcement is read by the people who read announcements. The auto-reply is read by the person who just used the old door, which is the person who missed the announcement. Write it for them: short, warm, specific, with nothing to decide.

Three rules. Lead with the thing they want, which is confirmation that their request is not lost. Give one new door, not three; a list is a decision, and a decision is a reason to stop reading. Say when the old door stops being read, with a date, so nobody is surprised twice. No apology, no history of the decision, no explanation of what a ticket system is.

Subject: Received, and the support address has moved

Thanks for your message. It has been logged as a support ticket, and
the ticket number will arrive in a separate e-mail within a minute.
You do not need to do anything else for this request.

For your next request, please use the support form:
    support.example.com/new
or e-mail helpdesk@example.com. Both give you a ticket number at once
and a page where you can follow progress.

From [date] this address is no longer read by a person. Mail sent here
is still forwarded to the help desk, so nothing is lost, but it is the
slow way in.

The IT Help Desk
Hours: 08:00 to 18:00, Monday to Friday
Urgent, out of hours: 555-0100

Test the auto-reply against an out-of-office before day forty-six. An old mailbox that auto-replies while forwarding into a ticket tool that also sends receipts can, with one vacationing sender, produce a loop that fills the queue overnight. Most ticket tools have heuristics for this (QuerySolv's mail screening recognizes bounces and auto-replies for exactly this reason). But the only proof is a test message from a mailbox with an out-of-office set, and a look at the queue ten minutes later.

Measuring the Revolt

The revolt is measured as the number of requests that still arrive by the old door, counted by week. The number should fall by about half every two or three weeks. Count them by hand if you must: every message to the old address, every DM answered with a number, every call to the old extension. Put the weekly figure on one line in the desk's notes. The shape of that line says whether the retirement is working and whether anyone is being left behind.

Acme's two-person desk retired direct-message support in the chat tool, and Sam counted. Week one, after the announcement: sixty-three DMs, every one answered with a ticket number and the pinned form link. Week three: forty-one. Week five, with the support space live and the status text pointing at the form: twenty-two. Week seven: twelve. Week nine, the week of switch-off: six. Four of them were from the same person in the warehouse. That person was handed a printed card with the desk number and has phoned ever since. Week twelve: three. Nobody at Acme was ever told "we don't do that anymore". They were told a number, sixty-three times in week one, and the number did the rest.

Two things in the line matter more than the slope. A week where the count rises after falling means a group has just discovered the change, usually a shift or a site the plan missed. That group needs the message in person. A long tail of the same few names means a real need the new door is not meeting. That needs a conversation, not another announcement. The tail at Acme was one person with gloves and no keyboard, which is a need, not a habit.

Ninety Days at Meridian Parts

Meridian Parts retired its shared support mailbox with a ninety-day plan. This followed a census showing that the mailbox received more requests than every other channel combined and that a third of them were never logged. Priya announced the change to managers on a Monday, to all staff on the Tuesday, and to the twenty heaviest senders by personal note on the Wednesday. The ticket tool was already reading the mailbox so that every message became a ticket from that week. The auto-reply went on at day forty-six, pointing to the form and the new address. Human replies from the mailbox stopped at day ninety. In the first month the auto-reply went to four hundred and six senders. In the second it went to eighty-eight; in the third, eleven. Seven of those were automated reports from a system that had been e-mailing the support address for years without anyone noticing. Nobody lost a request, because the forwarding never stopped. The one complaint that reached the IT manager was about the change itself, attached to a request that had been answered faster than the old mailbox ever managed. The address is still alive, still forwarded, and still auto-replies, to about one person a month.

I have retired a mailbox with no plan, once, over a weekend. The Monday was long. By Wednesday I had turned the mailbox back on, which taught the whole organization that announcements from the desk are provisional. Do not do that.

Switch-Off Day and the Quarter After

Switch-off day is an anticlimax if the plan worked, and that is the measure of the plan. The forward into the ticket tool stays. The auto-reply stays. What changes is that no technician opens the old mailbox, the old extension's voicemail gives the new number, and the chat tool's status text is permanent. Remove the old address from every signature, template, page and guide the desk controls. That search was started on day one and will now turn out to be unfinished.

Keep the auto-reply for a full quarter after switch-off, because the people who use a channel once a quarter meet the change for the first time then. Those include the month-end people, the auditors, and the person back from long leave. After the quarter the auto-reply can go or stay. It costs nothing, and it still catches someone.

The quiet risk after switch-off is the old door reopening by habit, from the inside. A technician on a busy day replies from the old mailbox because it was open, or answers a DM with the fix because the user is a friend. The organization learns, correctly, that the old door still works if you know whom to ask. The one-queue rule applies here with more force: reply with a ticket number, or do not reply. The channel is retired when the desk stops using it, not when the users do.

The Retirement Checklist

The checklist below is the whole plan in order, for one channel at a time. Do not announce until every "before" item is ticked, because the announcement is the one step you cannot take back.

CHANNEL RETIREMENT CHECKLIST
Channel being retired: ______________   Replaced by: ______________
Owner: ______________   Announce date: ________   Switch-off: ________

BEFORE (week 0)
[ ] Census done: requests per week on this channel, and how many logged
[ ] New door works end to end: request in, number back, reply threads
[ ] Old door forwards into the queue (mail), or the on-their-behalf
    habit is agreed for it (DM, phone, hallway)
[ ] Test message sent from a mailbox with an out-of-office: no loop
[ ] Auto-reply text written, dated, read by someone outside IT
[ ] Communication plan filled in: managers, staff, heavy users,
    reception, shifts and sites
[ ] Exceptions decided: executives' office, warehouse, night shift

ANNOUNCE (day 1)
[ ] Managers told first, then all staff, then heavy users by name
[ ] New door published: desktop link, signatures, intranet, voicemail,
    chat tool support space
[ ] Weekly count started: requests still arriving the old way

RUN BOTH (days 1 to 45)
[ ] Every old-door request logged on the user's behalf and answered
    with a ticket number and the one-line reminder
[ ] Weekly count falling; a rising week investigated (which site?)

AUTO-REPLY (day 46)
[ ] Auto-reply on; forwarding continues; receipt still within a minute
[ ] Second all-staff notice sent

SWITCH OFF (day 90)
[ ] Human replies from the old door stop
[ ] Old address removed from every signature, template, page and guide
[ ] Old extension's voicemail gives the new number and hours
[ ] Chat tool status text made permanent

AFTER (days 90 to 180)
[ ] Auto-reply kept for a quarter; weekly count continues
[ ] Long tail reviewed: same names? real need? talk to them
[ ] Desk reminded: reply with a ticket number, or do not reply

Signed off: ____________________   Date: ________

Dana's auto-reply will go out two hundred times in its first week and perhaps once a month by spring. Every one of those messages will say the same two things: your request is safe, and here is the door. That is all a retirement is. Not a door closing, but a door becoming a sign.

Frequently Asked Questions