Clarifying authority during a returns surge

A promotion drives a spike in orders, and a spike in orders drives a spike in returns. The client calls asking for temporary agents to handle the overflow, and the pressure is on to say yes fast. But before you commit a partner team to a returns surge, you need a clear picture of what those agents can actually do versus what stays locked behind manager approval. Skip that conversation and you set up a client who assumes every return gets resolved on the first call, and a partner team that gets blamed when reality does not match that assumption.

Why this conversation goes wrong

During a returns surge, everyone wants speed. Client stakeholders remember the last time hold times spiked, and they want a resolution. Sales executives want to close the deal and show the client that the BPO can absorb the load. That shared urgency pushes both sides to gloss over the boundary between what an agent can decide and what needs a manager's sign off. The client describes the surge in terms of volume, not authority. You describe the response in terms of headcount, not process. Neither side stops to ask which contact reasons need an escalation path or which order system holds the data an agent needs to act.

The result shows up later, not in the sales call. An agent tells a customer their refund is approved, then a manager reverses it because the order came through a marketplace channel with different rules. The customer feels lied to. The client feels the BPO overstepped. And the sales executive who promised a smooth ramp now has to explain a service failure they created by skipping one clarifying conversation.

How to prepare before you get on the call

Before you propose scope, you need answers to three plain questions. What contact reasons dominate the surge. Which order system holds the information an agent needs to see the order history, the return window, and any exceptions. And how the client wants a temporary partner team introduced to customers, since some brands want no distinction while others want a partner team clearly marked as an extension of care.

Pull in the people who actually know the answers. The client's care lead knows which exceptions get escalated today. The systems owner knows whether marketplace orders live in a separate platform than direct site orders, and whether your agents will even have access to it. The quality team knows what a correct resolution looks like, so your scoring later actually matches the client's standard. Skipping this and relying on what the sales contact assumes is how you end up promising authority nobody actually has. This is close to the discovery work described in Ask the right questions about sales data accesswhere the same principle applies. Figure out what data and access actually exist before you promise what your team can do with them.

Write down the answers as a simple map. For each contact reason, note the system it touches and who owns the approval. That map becomes the backbone of your proposal, and it protects you when the client later asks why an agent could not just approve something on the spot.

What to say

Here is how that conversation can go when a client asks for broad authority upfront.

Reyna, the client's operations lead, opens with the ask. "Customers are already frustrated. Can your team approve refunds on the spot when someone pushes back."

You do not answer with a flat yes or no. "That depends on two things, the authority your policy assigns to a frontline agent, and which system the order came through. Right now, which return exceptions require a manager on your side."

Reyna explains that most direct site returns follow a standard policy an agent can apply, but exceptions like damaged high value items or repeat returns go to a manager. She adds that marketplace orders run through a separate system her team barely touches during a surge.

You respond by naming the plan instead of promising blanket authority. "We should bring your care lead, your systems owner, and your quality team into a short readiness review. We will map out exactly which tasks our agents handle directly, where the handoff to your manager happens, and what information our agents need pulled up before that handoff so it takes one step, not five."

Notice what that exchange does. You never say the partner team can resolve everything. You ask what the client's own policy allows before describing your team's capability, and you propose a specific next meeting with named roles instead of a vague promise to sort it out later. That is the difference between a proposal grounded in how the client actually operates and one built on hope.

Mistakes that undercut the deal later

The most common mistake is answering the authority question with confidence you have not earned. Saying yes on a sales call to a question about refund approval, without knowing the client's exception rules, sets a service level you cannot hit. The second mistake is treating all orders as if they run through one system. Marketplace orders, wholesale orders, and direct site orders often live in different platforms with different data available to an agent, and a proposal that assumes one system will fail the moment a real order does not match it.

A third mistake is leaving out the introduction question. If the client wants a partner team to sound like an internal extension of their own care department, but your script has agents naming your company on every call, you create a mismatch a customer will notice within the first surge week. And a fourth mistake, subtle but costly, is running the readiness review without the systems owner in the room. Sales and operations people can describe workflows from memory, but access rights and system boundaries are the systems owner's territory. Leave them out and you find out about a login restriction after agents are already scheduled to start. The same discipline about defining boundaries before a team goes live applies to other surge situations too, including the approach covered in Set safe boundaries for a storm response service.

How to practice and score it

Pick one return, start to finish, and mark the exact point where authority shifts from agent to manager. Maybe it is a dollar threshold. Maybe it is a specific reason code. Maybe it is any return from a marketplace order regardless of value. Once you can point to that moment, practice explaining it out loud to a buyer who wants a simple, sweeping answer. Say plainly what your agents can decide, what they cannot, and what happens in between so the customer is not left waiting without a reason.

A manager reviewing your practice run should check for three things. Did you name the contact types that make up the bulk of the surge. Did you identify which system each type depends on. And did you name who owns the approval when an agent cannot resolve something directly. If those three facts show up clearly in your explanation, the proposal that follows will match how the client's operation actually runs, not how you assumed it runs. Running this scenario a few times against an AI counterpart in DealSpeak, or with your own manager listening for those three facts, catches the gaps before a real client hears them. You can find more scenarios like this one among the Contact Centers practice conversations built for exactly this kind of readiness work.

Where this leaves you

A returns surge tests whether your proposal reflects the client's real rules or your best guess at them. Ask about contact reasons, systems, and introduction before you promise anything about authority, and put the readiness review on the calendar with the right people in the room. Get that sequence right and the partnership survives its first hard week instead of breaking on it.