How We Handle Special Requests: A Guide for Clients

Special requests are welcome—when they’re handled with clarity. If you’ve ever wondered how a team figures out what’s possible (and what needs a little extra planning), this guide walks you through the process step by step.

Here are 4 questions clients usually ask when they’re searching for “how special requests are handled”:

• What counts as a special request?
• What happens after I submit one?
• How will I be kept updated?
• Can you share examples of requests that worked well?

When requirements change or go beyond standard options, the best outcomes come from good communication and clear expectations. According to guidance on change management and customer communication, aligning on scope early reduces friction and misunderstandings (see Atlassian: Change management) and improves service reliability (see Nielsen Norman Group: Customer service emotions).

Below, you’ll learn what qualifies as a special request, the exact steps we take to evaluate and confirm it, how communication works during the process, and several real-world examples of requests that were successfully accommodated.

What qualifies as a special request

A special request is anything that differs from the standard or “default” options you’d normally choose. It might be a preference, a constraint, or an added requirement that affects planning.

Common examples include:

• Timing changes: a preferred date/time window or a shorter lead time than usual.
• Specification updates: materials, sizing, quantities, formatting, or other details.
• Custom bundling: combining options that aren’t listed as a single standard package.
• Accessibility or communication needs: specific requirements for how you’d like to be contacted or what information you need upfront.
• Handling or delivery preferences: particular instructions for setup, packaging, or coordination.

Quick boundary: If a request involves safety, regulatory, or technical limitations, we’ll still review it—but we’ll be honest about what can’t be guaranteed. The goal is clarity, not surprises.

Steps involved in handling special requests

When a special request comes in, we treat it like a mini project: confirm the ask, assess feasibility, then document the final plan. Here’s what that looks like.

1) Intake: capture the full request (not just the headline)

We start by confirming the request details so we don’t miss anything important. That typically means collecting:

• What you want (the outcome)
• What’s different from the standard option
• Any deadlines or dates that matter
• Relevant constraints (size, quantity, budget range if applicable)
• Preferred communication method

2) Feasibility check: what’s doable and what affects scope

Next, we assess how the request changes the work. Some requests are straightforward “preference swaps,” while others require more planning—like coordinating timing, adjusting materials, or reserving capacity.

If we foresee friction (for example, limited availability or a dependency on other requirements), we’ll flag it early so you can decide the best direction.

3) Confirmation: align on the final plan and expectations

Once we know what’s possible, we confirm:

• What will be included
• Any trade-offs or limitations
• When you should expect updates
• What happens if priorities or timing shift

4) Execution: carry the confirmed details through the process

After confirmation, we use the agreed details as the reference point during execution. This is how we prevent “it sounded different” moments.

5) Handoff and wrap-up

When the request is complete, we share a clear wrap-up and invite feedback. If anything didn’t match expectations, it’s easier to fix when we have shared documentation up front.

Helpful tip: If you’re not sure what to include, start with our FAQ and then send the details you know. For fastest processing, the Contact form is the best starting point.

Communication during the process

Special requests require coordination, so communication needs to be predictable. Here’s the communication style you can expect.

What you’ll receive

• Initial acknowledgement: confirmation that your request has been received and is being reviewed.
• Feasibility notes: what looks workable, what might require adjustment, and why.
• Clear confirmation: the final understood plan (so both sides share the same version).
• Progress updates: based on milestones rather than random timing.

How to help communication go smoothly

• Reply with specifics: if we ask a question, answering it fully prevents rework.
• Share constraints early: deadlines, access limits, or “must-haves” should be mentioned up front.
• Use one main channel: it’s easier to track decisions when everything is in the same thread.

What happens if plans change

If something shifts—timing, quantity, priorities—tell us as soon as you can. We’ll review what needs to be updated, explain the impact, and confirm the revised expectations.

Examples of successful special requests

Here are a few example scenarios that typically go well when clients communicate early and clearly.

Example 1: A tighter timeline with a clear trade-off

A client requests an earlier date than the standard option. Instead of treating it as a simple yes/no, we confirm the feasibility and discuss what would change (for example, scheduling adjustments or prioritized elements). Because the expectations are aligned, the request can still be delivered successfully.

Example 2: Specification updates that are fully described

Another client needs a specific combination of features (not just “different”). When we receive the full requirement set—dimensions, materials, usage scenario, and constraints—we can map the request into a practical plan and confirm it confidently.

Example 3: Communication preferences for coordination

Some clients need updates in a particular way (for example, email-first communication or a specific timing for check-ins). When those preferences are stated up front, it reduces back-and-forth and makes the process calmer for everyone.

Example 4: A custom bundle built from existing building blocks

Occasionally, the “special request” isn’t a totally new item—it’s a custom mix. When we understand the goal, we can often assemble the solution while keeping the process stable and predictable.

Key takeaways

• Special requests are welcome—especially when requirements and constraints are clearly described.
• We review feasibility and confirm the plan before execution.
• Communication is milestone-based, not guesswork.
• If plans change, we update expectations transparently.

Next step: Gather the details you have and reach out through Contact. If you’re unsure where to start, the Services overview can help you describe what you need in the right terms.