If you are the first point of contact in an office, interruptions come with the role. People walk up to your desk, call the main line, send chat messages, and forward emails marked “quick question.” Each one is reasonable on its own. Together they leave little time for the work that needs sustained attention, such as minutes, travel arrangements, reports, and the schedule changes that hold a team together.
This article sets out how to minimize interruptions at work as an administrative assistant without becoming unreachable. The method has three parts: sort requests into tiers, give each tier a channel and a response time, and tell people how it works in words that keep the relationship warm.
Why admin roles get interrupted more, and what it really costs your day
Admin staff are interrupted more often because they sit at the junction of information. You know where the room booking is, who approves the expense, and when the executive is free. Colleagues ask you because you are the fastest route to an answer, and the cost of asking you feels low to them.
For you the cost is higher. Every interruption pulls you out of the task in front of you, and picking it back up takes time. Detail work suffers most: a reconciled spreadsheet, a long email to a client, a calendar with six conflicting commitments. Mistakes in those tasks tend to appear after the interruption, when you resume from memory and miss something.
There is also a cumulative effect on how the day feels. When every request is treated as equally pressing, you end the day busy and unsure what you completed. And a bit frustrated. A tiered system addresses that by deciding in advance which requests deserve an immediate response and which do not.
Sort requests into three tiers: urgent, same-day and whenever
Start by listing the requests you received over the last week or two. Check your chat history, sent email, and any notes you keep. Then sort each one by the consequence of waiting.
Tier 1, urgent. Waiting causes harm or a missed deadline within the next hour or two. Examples: an executive about to walk into a meeting without a document, a client arriving at the wrong location, a system outage that stops the team working, a safety issue.
Tier 2, same-day. The request matters and has a deadline today, but a delay of a few hours changes nothing. Examples: a room booking for tomorrow, a document that needs formatting before end of day, a question about a policy.
Tier 3, whenever. The request has no deadline this week, or the deadline is far enough away that it can join your normal queue. Examples: supply orders, filing, next month’s travel, a request to update a template.
Most of the list will land in tiers 2 and 3. That is expected. The point of the exercise is to show how few requests are urgent, and to give you a shared definition of urgent that you can state out loud.
Assign each tier a channel and a response window
A tier works only when it is tied to a way of making contact. Otherwise people choose whichever channel is nearest, and everything arrives in the same place at the same volume.
A workable starting arrangement:
- Urgent: phone call or a walk-up. Response within 10 to 15 minutes. These are the only contacts that may break into your focus time.
- Same-day: chat message or a shared request list. Response within two to three hours, usually at the end of a focus block.
- Whenever: email or a request form. Response within one working day, or within two days for large items.
Adjust the times to your office. A front-desk role with constant phone traffic needs shorter windows than a coordinator who supports a single team. What matters is that the windows are written down and that you consistently meet them. People will trust a slow but reliable channel more than a fast one that sometimes goes quiet.
If email is the channel that feels most out of hand, the posts on email overload management strategies for admins and setting up urgent email alerts cover the inbox side in more detail. This article deals with what happens across all channels at once.
Block focus hours that your team and executive can plan around
Focus hours are scheduled periods in which only tier 1 contacts reach you. Put them on your calendar as busy, with a clear label such as “Focus block: urgent only by phone.”
Choose the times by looking at when your work is most demanding and when requests are lightest. Many admin roles have a natural quiet window, often early morning before executives are active or mid-afternoon after the lunch period. Start with two blocks of 60 to 90 minutes a day rather than a full morning. A shorter block is easier for colleagues to accept, and you can lengthen it once it holds.
Between blocks, set open periods for answering. Check chat and the request list at the start of each open period, work through same-day items, and then return to the queue. Visible, predictable availability is what makes the focus hours acceptable to others. Colleagues will wait if they know when you will respond.
For the executive you support, share the blocks and ask them to build around them. If the executive’s calendar and yours are already coordinated, the weekly calendar organization post may help you fit the blocks into a weekly structure.
Scripts for saying “not right now” in a professional, warm tone
The words you use matter as much as the system. A good script acknowledges the request, gives a time, and does not apologize for having priorities. Adapt these to your voice.
To a colleague at your desk during a focus block:
“I want to give this proper attention, and I’m in the middle of something right now. Can you send it by chat? I’ll reply by 2 p.m.”
To a colleague who sends an unmarked request by chat:
“Thanks for sending this. I’ll get to it this afternoon. If it needs to be done before then, give me a call and I’ll switch.”
To an executive who adds a request mid-block:
“I can take that. I’m finishing the board pack until 10:30. Would you like me to start on it right after, or does it need to jump the queue?”
To someone who calls a routine item urgent:
“Understood that it matters to you. Is there a deadline today that I’m not seeing? If not, I’ll add it to tomorrow morning’s list and confirm when it’s done.”
To a repeated interrupter, in private:
“I’ve set up a system to protect time for detailed work. If you have several small items, send them as one list and I’ll work through them together. That gets you faster answers overall.”
Each script offers a next step. The person leaves knowing when to expect help, which is what they wanted when they interrupted.
How to roll it out to your manager and team without friction
Begin with your manager, before anyone else. Present the system as a way to improve accuracy and turnaround, not as a boundary dispute. Bring a one-page summary: the three tiers, the channels, the response windows, and the proposed focus blocks. Ask for specific agreement on two points: that the executive will use the tiers, and that your manager will support the system if someone pushes back.
Then brief the team in a short message or at a regular meeting. Keep it brief:
“Starting Monday, I’m trying a simple system to make sure requests get handled quickly and correctly. Urgent items: call me. Same-day items: message me and I’ll respond within a few hours. Everything else: email, and I’ll reply within a day. I’ll be in focus time from 9 to 10:30 and 2 to 3, so phone only for emergencies during those. I’ll review how it’s going in two weeks and welcome your feedback.”
A short trial period lowers resistance. People accept a two-week trial more easily than a permanent rule. Putting the channels in your email signature and chat status reinforces the system without repeated explanation.
Handling the exceptions: emergencies, executives and walk-ups
No system works without exceptions, and planning for them keeps the rest intact.
Emergencies. Define them narrowly and tell people the channel. If a true emergency arrives by chat, respond, then remind the sender of the phone route afterward. Responding to the emergency matters more than enforcing the process at that moment.
Executives. The executive you support has priority access, but that does not mean unlimited access. Agree on a signal for tier 1, such as a call or a specific phrase, and keep a short “while you wait” habit: acknowledge the request and give a time. Executives generally accept a clear time estimate more readily than silence.
Walk-ups. Walk-ups are the hardest to manage because the person is standing in front of you. Use a script that redirects without dismissing, such as the desk-side one above. A visual cue also helps: a small sign or a headset on during focus blocks signals that you are working on something. If the walk-up is urgent, they will say so, and you can respond.
Keep a note of each exception. If the same type of request keeps breaking through, either the tier definition needs adjusting or that person needs a specific conversation.
Review after two weeks and adjust the protocol
At the end of two weeks, spend 20 minutes reviewing. Look at what actually happened rather than what you expected.
- Which tier received the most contacts, and were they sorted correctly?
- Did you meet your response windows? If not, the windows may be too short.
- Which focus blocks held, and which were broken repeatedly?
- Who is still using the wrong channel, and is a short reminder enough?
- Which tasks improved in quality or speed during focus time?
Make small, incremental changes rather than overhauling everything at once. Try lengthening a response window, repositioning a focus block, or adding a request form for categories that frequently appear in chat. Once you’ve made these adjustments, share them with the team so they can see their feedback in action. A protocol that is regularly reviewed and visibly updated earns more cooperation than one handed down as a static rule. These processes are most effective when team members know they have helped shape a procedure that makes the office function better.
If you also need a way to rank the work you protect time for, the four-box system for prioritizing tasks digitally pairs well with this protocol.
Join the newsletter for a free copy of the interruption protocol template and weekly workflow tips for admin professionals.