“Can you get this to me today?” is a request for a deadline. It does not tell you what happens if the answer is tomorrow.
That missing information matters. A broken delivery link may stop a customer from using work you already promised. A new version may only be needed for a launch next week.
Both can arrive with “urgent” in the subject line. They do not necessarily need the same response.
You can take a customer seriously without putting every request at the front of the queue. The useful question is what is at risk, by when, and what the business has already committed to do.
Ask what the deadline protects
Imagine a product photography studio. Its team receives three requests on a Tuesday morning.
One customer’s final image files will not download, and their scheduled launch begins that afternoon. Another wants a new background color by the end of the day. A third asks which images were included in a delivery from last week.
If the studio works in arrival order, or answers the loudest sender first, it may miss the request with the most at stake.
The team needs a few facts before deciding:
- What is the customer unable to do?
- When does that cause a meaningful problem?
- Is there a workable alternative until the full request is completed?
- What has the studio already promised?
Ask naturally. “Is this blocking today’s launch, or would tomorrow morning still work?” is more useful than a long questionnaire.
The answer may change your first judgment. A background change could be a preference, or it could correct a studio error that makes the files unusable.
Separate a response from a resolution
Customers should know when they will hear from you and when they can expect the work. Those are different promises.
A fast acknowledgment can confirm that the request has reached the right person. But “We’re on it” leaves both the customer and the team guessing about what happens next.
The studio could instead reply:
“We have the request. We’re checking whether the new background affects all twelve images or just the three selected for the campaign. We’ll confirm the scope and delivery time by 2 p.m.”
Make that 2 p.m. promise only if the team has time to check. The reply tells the customer what is being checked and when they will hear next. It does not quietly commit the production team to finish everything today.
If AI helps draft these replies, decide who can make the promise before one goes out.
Choose response windows your team can support, not ones borrowed from a competitor. A small team can offer dependable service without offering every service at every hour.
Use consequences to set priority
Keep the internal rules simple enough to use on a busy morning. For the studio, they might look like this:
| What is happening | Priority decision |
|---|---|
| Delivered work cannot be used, and a customer deadline is close | Check it now, find a workaround and set a time for the next update |
| An existing commitment is close to its agreed deadline | Protect the promised work and flag any risk early |
| A customer asks for extra work by a new deadline | Check scope and capacity before accepting the date |
| Nothing is blocked if the request waits | Put it in the normal queue |
The purpose is consistent judgment. Exceptions will still happen, so name who can decide them. When one changes the queue, explain why so the rest of the team understands the tradeoff.
Name what a rush request would displace
The studio may have room for the new background color. If it does not, “yes” creates another decision: whose work moves?
Work that out before agreeing to the deadline. A rush fee does not create production time, and an important customer’s enthusiasm does not change another customer’s promised date. If the same customer keeps asking for rushes, look at what the account costs your week.
Offer choices you can actually deliver. The studio might finish the three selected images today and the other nine on Thursday, or deliver all twelve on Thursday. If neither option works, it can say so before the customer builds a plan around an impossible promise.
Do not make existing customers absorb a hidden delay. If a priority change affects them, tell them. The team should not have to discover on Wednesday that Tuesday’s quick “yes” made Wednesday’s work impossible.
Check whether your rules create the pressure
If everything arrives as urgent, look at the expectations the business has set. Your own promises may be creating the rush.
Start with three causes the business controls:
- Unclear delivery dates. Customers who never get a clear date may keep chasing.
- Inconsistent revision promises. One person may promise same-day changes while another schedules several days ahead.
- No acknowledgment. Customers may have learned that “urgent” is the only way to get a reply.
Check a few recent urgent requests against these causes, then fix the one that keeps coming up.
The next time a customer asks for today, find out what today changes for them. Then give an answer the whole business can stand behind.
