Client problems

What to do when a client wants a service that is not offered: 32 ways to help without overpromising

When a client asks for a service that is not offered, clarify the outcome they need, explain the service boundary, and offer a relevant next step. That may be an existing alternative, a clearly scoped assessment, an appropriate referral, or a polite decline. Do not accept unfamiliar work simply because it sounds close to the usual service.

A useful refusal is specific. “We do not do that” becomes more helpful when the client understands whether the issue is capability, capacity, tools, location, or the type of work involved. Keep those reasons accurate and avoid implying that a different service will produce the same result unless it genuinely can.

These examples are suggested wording for ordinary service inquiries. Referrals and partnerships require the relevant person’s permission before private project details are shared. Specialized, regulated, or safety-critical work needs appropriately qualified support.

What to do first when a request falls outside the service

1. Ask what result the client needs and what prompted the request.
2. Check whether an existing service actually meets that need, rather than merely sounding similar.
3. Identify the boundary: the task is not offered, cannot be delivered in the requested form, or needs specialist capability.
4. Offer a suitable route with clear limits. Do not invent an available partner or promise another provider’s timing.
5. Confirm whether the request changes an existing project or remains a separate inquiry.

What to do when the requested service is unclear

Start with the intended outcome. A client may use a different name for something already offered, or may request a familiar-sounding task that requires a substantially different capability.

1. What to do when a client asks for a service using unfamiliar terminology

Ask the client to describe the result and where it will be used. A service label alone may not establish the scope. Give a simple example of what the business does offer, then check whether that matches the intended need.

Do not claim to understand a specialist term just to keep the conversation moving. Equally, avoid rejecting a suitable inquiry because the client uses informal wording. Summarize the task in plain language before deciding whether it is within the service.

• “What result do you need from that service?”
• “Could you describe how the finished work will be used?”
• “The service I offer covers this specific outcome.”
• “Let us confirm whether that matches the request before discussing the next step.”

2. What to do when a client sends an example and asks for the same thing

Ask which aspects of the example matter: appearance, functionality, process, or deliverable. An example can communicate a goal without defining the complete work. Do not assume the client wants a literal copy or that every visible feature belongs to the offered service.

Explain which elements can be addressed and which need another capability. Respect the original creator’s material and avoid promising an identical reproduction. The next step should define an original, suitable deliverable with clear boundaries rather than copying an example without understanding it.

• “Which features of this example are important to the intended result?”
• “I can help with the content structure, but not the specialist implementation.”
• “The project would need its own agreed scope and original materials.”
• “Let us separate the supported work from the elements requiring another provider.”

3. What to do when a client describes a goal instead of a service

Translate the goal into possible tasks without pretending the business can own every part. Ask about the intended audience, output, and constraints that affect the choice. A goal such as “improve the launch” may involve several disciplines.

Explain the contribution the offered service can make and the gaps it cannot cover. If an assessment would help, define its limits before offering it. Avoid positioning a narrow service as a complete solution to a broad business problem merely to secure the booking.

• “Which part of the launch needs the most help?”
• “My service can address the messaging and content deliverables.”
• “The technical setup would need a separate provider.”
• “I can help define the content scope without claiming to manage the entire launch.”

4. What to do when a client assumes a related service is included

Identify the connection the client is making and explain the actual boundary. Designing a document does not necessarily include translation; creating content does not automatically include running a campaign. Use the specific project rather than a broad statement about how the industry works.

Review any wording that may have created the expectation. If the proposal was unclear, acknowledge that and clarify the next step. For an active project, keep included work distinct from the unsupported addition so the client knows what will still be delivered.

• “The proposal covers the document design, while translation is a separate task.”
• “I understand why those services may seem connected.”
• “Let us check whether the earlier wording made that boundary clear.”
• “The agreed design work can continue once the approved translated text is available.”

What to do when an existing service may offer a partial alternative

An alternative is helpful only when its limitations are clear. Explain what it achieves and what remains unresolved. Let the client decide whether the narrower outcome is useful.

5. What to do when a simpler service meets the immediate need

Ask whether the client’s immediate objective can be met by a service already offered. A static document may suit an initial presentation even if a more complex interactive tool was requested. Explain the supported result without calling the two services interchangeable.

Describe what the simpler option cannot do and whether the missing capability matters now. Do not steer the client toward it solely because it is easier to sell. If it fits, write the scope around that actual deliverable so expectations remain clear.

• “A simpler document may meet the immediate presentation need.”
• “It would not provide the interactive functions originally mentioned.”
• “Are those functions essential at this stage?”
• “If the simpler outcome is useful, I can scope that service accurately.”

6. What to do when only part of the requested project can be delivered

List the supported tasks and the tasks requiring another provider. Explain any dependencies between them, such as receiving approved technical information before writing the final content. Avoid accepting responsibility for the whole project through vague coordination language.

Ask whether the client wants separate scopes or an appropriately assessed collaboration. Confirm who will manage the remaining work and approvals. A partial engagement needs a clear handover point so neither provider nor client assumes that the missing piece is being handled elsewhere.

• “I can deliver the content portion of the project.”
• “The integration work needs a separate specialist.”
• “Who will coordinate that part and provide the required inputs?”
• “My scope will identify the handover and dependencies explicitly.”

7. What to do when the alternative changes the client’s expected outcome

Explain the difference before asking the client to approve. A reduced service may be useful while producing a narrower result. Show which requirement would remain unmet and ask whether the revised goal is acceptable.

Do not hide the change in a technical description or assume that a lower price compensates for a missing essential function. If the client needs the original outcome, acknowledge that another route is necessary. The alternative should support an informed choice, not obscure a capability gap.

• “This option delivers a narrower result than the original request.”
• “The missing capability is the automated update process.”
• “Would the manual version still meet the immediate need?”
• “If automation is essential, this service is not a suitable substitute.”

8. What to do when a client wants an unsupported workaround

Ask what the workaround is intended to achieve and assess whether it is appropriate within the service. Do not promise that an improvised route will be reliable, compatible, or safe without the necessary basis. A workaround may introduce more uncertainty than it resolves.

Explain the specific limitation and offer a supported route if one exists. For specialist or safety-critical tasks, direct the client toward qualified help. Avoid treating the request as permission to bypass technical protections or professional boundaries. A clear refusal can be more useful than a fragile substitute.

• “I need to assess whether that workaround is suitable for the intended use.”
• “It is not a supported part of the service I provide.”
• “The appropriate route requires the relevant technical capability.”
• “I can help with the supported portion once that requirement is resolved.”

What to do when a client asks for work beyond current capability

Be accurate about competence and the service offered. Curiosity about learning a skill does not make a live client project an appropriate training environment. Do not confuse willingness with readiness to deliver.

9. What to do when a client asks to make an exception

Ask what exception they need and explain the specific boundary. If the issue is merely scheduling, an assessment may be possible. If the task requires a capability the business does not have, an exception does not remove that limitation.

Avoid a vague “maybe” that encourages the client to plan around unsupported work. State what can be considered and what cannot be offered. If the service genuinely changes later, it can be discussed through a new assessed scope rather than an informal promise made under pressure.

• “I understand why an exception would be convenient.”
• “This is a capability boundary, so I cannot confirm the requested service.”
• “I can still help with the related work already within the offer.”
• “The unsupported portion needs an appropriate provider.”

10. What to do when a client says the task looks easy

Explain the relevant requirement without turning the conversation into a lesson about how difficult the profession is. A task may look simple while needing specialist knowledge or a workflow the business does not support. Keep the explanation specific and proportionate.

Do not argue over the client’s estimate. State whether the service is offered and identify a useful next step. If the task is actually within capability but outside the standard package, assess it as a scope question rather than using a refusal that is not accurate.

• “The visible result is simple, but this task requires a workflow I do not provide.”
• “I cannot offer it as part of this service.”
• “A provider working in that area would be a better fit.”
• “I can clarify the related input they would need from this project.”

11. What to do when a client asks to learn the missing skill during the project

Explain whether the project can tolerate an assessed learning or experimental phase. For ordinary exploratory work, a clearly defined test may be appropriate if honestly described. Do not present uncertain work as an established service or accept specialist responsibilities without the necessary competence.

State the limits, likely deliverable, and decision point before any experiment begins. If the task is regulated or safety-critical, direct it to an appropriately qualified provider. The client’s willingness to accept uncertainty does not automatically make every form of experimentation suitable.

• “This is not an established service in the current offer.”
• “A limited exploratory test would need its own clearly described scope.”
• “It would not be a promise of a finished production solution.”
• “For specialist work, the project should use an appropriately qualified provider.”

12. What to do when a client offers more money to provide the unsupported service

Separate compensation from capability. A higher fee may make a suitable expanded scope commercially viable, but it does not create expertise, authorization, or delivery infrastructure. Explain which limitation actually applies.

If a legitimate partnership could address the need, assess it before promising anything. If not, decline clearly and keep any existing work on its agreed track. Avoid accepting a large commitment because refusing feels uncomfortable. The client needs a deliverable that can be responsibly provided.

• “A higher budget does not resolve the capability needed for this task.”
• “I cannot offer the specialist portion directly.”
• “A suitable collaboration would need assessment before any commitment.”
• “The existing agreed work can continue within its current scope.”

What to do when a referral could help the client

Recommend a route only when there is a reasonable basis for it. A referral should make the next step easier without promising another provider’s quality, availability, pricing, or suitability before those points are checked.

13. What to do when a suitable provider is already known

Explain the relevant reason for suggesting the provider and the limits of that knowledge. Prior collaboration or a relevant public service listing may support an introduction, but neither guarantees that the provider can take the project now.

Offer public contact information or ask whether the client wants an introduction. Do not forward private project details without permission. Let the receiving provider assess the actual scope and availability. Keep any commercial or referral relationship transparent where it is relevant to the recommendation.

• “This provider works in the area the project needs.”
• “Availability and fit would need to be confirmed directly.”
• “I can share the public contact details.”
• “If an introduction would help, please confirm what project information may be included.”

14. What to do when no specific provider can be recommended

Say that there is no verified recommendation available and describe the type of specialist the client should look for. Provide useful selection criteria tied to the task rather than inventing a name to avoid leaving the client without an answer.

Explain the questions a suitable provider should be able to address, such as the relevant deliverable, experience, or required qualifications. Avoid making unsupported rankings or calling an unverified search result trusted. A clear search brief can still help the client move forward.

• “I do not have a provider recommendation I can verify for this task.”
• “The project needs a specialist in the relevant service area.”
• “Ask about experience with this specific deliverable and intended use.”
• “I can summarize the requirements to make the inquiry clearer.”

15. What to do when a client asks to send the brief to another provider

Confirm the intended recipient and the information the client authorizes sharing. A brief may contain private contacts, internal plans, or commercial details that are unnecessary for an initial inquiry. Use a minimized description appropriate to the purpose.

Do not treat permission to make an introduction as permission to distribute every project file. Confirm whether the client wants to review the summary first if the material is consequential. Keep the handover separate from any promise that the receiving provider will accept the work.

• “Which provider should receive the inquiry?”
• “Please confirm the project details that may be shared.”
• “A short scope summary should be enough for an initial discussion.”
• “The provider will need to confirm suitability and availability independently.”

16. What to do when a client expects a referral to guarantee the result

Explain what the recommendation is based on and what remains for the client and provider to assess. A referral may identify a relevant service without guaranteeing the final work. Avoid distancing language that obscures a real commercial relationship; be accurate about the arrangement.

Encourage the client to confirm scope, timing, and terms directly through the appropriate process. Do not guarantee someone else’s delivery or imply that an introduction replaces due diligence. If the project needs coordinated responsibility, that should be established explicitly rather than assumed from the referral.

• “The recommendation is based on the provider’s relevant service area.”
• “It is not a guarantee of the project outcome.”
• “Please confirm the scope, timing, and terms directly.”
• “If coordinated delivery is needed, that arrangement must be agreed separately.”

What to do when collaboration or subcontracting is proposed

A combined service needs clear responsibility, scope, and permission. Do not describe an informal contact as an established delivery team. Assess the arrangement before giving the client a combined commitment.

17. What to do when a client asks to bring in a specialist

Clarify whether the client will contract with the specialist directly or wants a coordinated arrangement. Explain which tasks remain within the current service and what information must move between providers. Do not assume that collaboration is automatically included in the existing price or schedule.

Assess availability, responsibilities, and handover points before promising a combined result. Keep approval authority clear for both parts. A practical collaboration can help, but only when the client knows who is delivering each task and how the dependencies will be managed.

• “Would the specialist be engaged directly or through a coordinated arrangement?”
• “My role would remain the content deliverables listed here.”
• “We need to confirm the handover and approval responsibilities.”
• “I will assess that setup before committing to a combined schedule.”

18. What to do when a client asks to manage another provider’s work

Ask what management means: scheduling, reviewing deliverables, translating requirements, or accepting responsibility for technical quality. These are different tasks and may require different competence. Do not accept a broad management role through a casual agreement to “keep an eye on it.”

Explain which coordination tasks can be offered and which judgments need the appropriate specialist. Define the scope before starting. If the role exceeds the service, decline it while clarifying the inputs that can still be provided from the existing project.

• “Which coordination tasks do you want me to handle?”
• “I can manage the content handover, but not certify the specialist implementation.”
• “Any additional coordination needs a defined scope.”
• “The technical decisions should remain with the appropriately qualified provider.”

19. What to do when a client wants one invoice for several services

Clarify whether the business actually offers a combined service arrangement. A single invoice may be convenient, but it can change responsibilities and commercial relationships. Do not promise it merely because another provider is willing to help informally.

Assess the arrangement through the appropriate business process before presenting terms. If only separate engagements are available, explain that clearly. Avoid making legal or tax claims about the best structure without suitable advice. The client should understand the available delivery model and who is responsible for each scope.

• “A combined arrangement would need to be assessed before it can be offered.”
• “At present, the services are provided through separate scopes.”
• “I can clarify the handover between those scopes.”
• “Any different commercial structure would need explicit agreement.”

20. What to do when a partner is unavailable after being suggested

Tell the client promptly once the availability issue is confirmed. Explain whether the current project depends on that provider and what alternatives can be assessed. Do not conceal the gap or imply that a replacement has already been secured.

Offer a revised route based on verified options: another suitable specialist, separate client sourcing, or a changed schedule. Keep the existing service commitment accurate. If the earlier recommendation sounded firmer than warranted, acknowledge that and correct the expectation before the client plans further work around it.

• “The suggested provider has confirmed they cannot take the project at this time.”
• “I do not yet have a confirmed replacement.”
• “We can assess another suitable route or revise the dependent schedule.”
• “The work within my current scope remains as described.”

What to do when the unsupported request affects an existing project

Separate the original commitment from the new request. Explain whether the added service changes the goal, creates a dependency, or exposes a misunderstanding in the original scope. Keep the current project status clear.

21. What to do when a client adds an unsupported task after booking

Review the original scope and explain where the new request sits outside it. Ask whether the task is essential to the agreed outcome or reflects a changed objective. Do not assume it is an optional extra before checking the promise already made.

If the project has changed, discuss the revised scope and specialist need. If the task was implicitly or explicitly promised, acknowledge the gap and seek an appropriate resolution. For a broader reset, use what to do when a client changes the brief.

• “This task was not part of the service described in the current scope.”
• “Is it required for the original outcome or a new objective?”
• “Let us review the earlier wording before deciding how to handle it.”
• “Any revised project needs a clear route for the specialist portion.”

22. What to do when an unsupported service becomes a dependency

Identify the task that cannot proceed without the missing service and explain why. A content project may need confirmed technical information, while a design may depend on a specialist production specification. Do not guess the missing input to preserve apparent progress.

Ask who will supply the dependency and when it can be confirmed. Continue independent work where useful, but keep the final schedule conditional on the necessary input. The guide on incomplete client materials helps organize the handover once the right provider is identified.

• “This stage depends on the specification from the specialist provider.”
• “Who will supply and approve that information?”
• “The independent sections can continue while it is outstanding.”
• “Final timing needs to be reviewed once the dependency is confirmed.”

23. What to do when a client expects unsupported work within the same deadline

Explain that the new service needs its own assessment and confirmed availability. Do not promise another provider’s turnaround or compress the current work to compensate for an unassessed task. Show the dependency in the project plan.

Ask whether a phased delivery or narrower first stage would meet the immediate need. Offer only feasible options. For the wider deadline conversation, see a client requesting earlier delivery. Confirm the revised route before the client relies on a new date.

• “The added service needs a separate assessment and confirmed provider availability.”
• “I cannot promise that it will fit the original deadline.”
• “Would a narrower first stage meet the immediate need?”
• “The revised schedule can be confirmed once the delivery route is agreed.”

24. What to do when a client asks to replace the booked service with another one

Clarify the new outcome and review what work has already been completed. A replacement request may be a substantial change rather than an equivalent exchange. Explain whether the alternative is offered at all before discussing a substitution.

If it is outside capability, discuss the current project status and a suitable next route under the actual agreement. Do not invent cancellation terms or assume the client forfeits everything. Keep the conversation focused on the completed work, remaining obligations, and the unsupported new request.

• “The replacement is a different service from the one currently booked.”
• “I do not offer that service directly.”
• “Let us review the current project status and remaining agreed work.”
• “Then we can discuss an appropriate next step for the changed requirement.”

What to do when a client challenges the service boundary

Answer the actual concern calmly and keep the boundary consistent. The client may be disappointed, confused by marketing language, or trying to simplify a complex project. Explain the available service without arguing about whether the request was reasonable.

25. What to do when a client says a competitor offers everything

Acknowledge that another provider may use a broader delivery model. Explain the current specialization and assess whether it fits the client’s needs. Do not assume that the competitor’s broader offer is low quality or that specialization is always preferable.

If the client wants a single provider for the full scope, accept that the alternative may suit them better. For a price-based comparison, use the guide to a cheaper competitor. Keep this discussion about capability and responsibility rather than defending the business in general.

• “Another provider may offer a broader combined service.”
• “My service focuses on the specific deliverables described here.”
• “If one provider for the full scope is essential, that affects the choice.”
• “I understand if a broader arrangement fits the project better.”

26. What to do when a client says the website implied the service was available

Ask which wording created the expectation and review it fairly. Marketing language may be too broad or unclear. Do not insist that the client should have understood an internal distinction that was not communicated publicly.

Clarify the service available now and address any active commitment through the actual agreement. If the wording is misleading, correct it through the appropriate process. Avoid making a promise to deliver unsupported work simply to avoid acknowledging a communication problem.

• “Which wording led to that expectation?”
• “I can see how the description may have been unclear.”
• “The service currently offered covers these specific tasks.”
• “We should resolve any existing commitment separately and clarify the public description.”

27. What to do when a client insists the unsupported task is just a small extra

Explain the capability difference, not merely the amount of time involved. A small specialist task can still require knowledge or responsibility outside the service. Do not imply that a higher fee automatically makes it acceptable.

If the request is actually within capability but outside the package, treat it as an addition instead. The guide on free extra work addresses that different situation. Keep the explanation accurate so the client understands whether the issue is scope or an unavailable service.

• “The limitation is the type of expertise required, rather than only the task size.”
• “This service does not include that specialist capability.”
• “If the request were within the offer, it could be assessed as an addition.”
• “For this task, an appropriate provider is the necessary next step.”

28. What to do when a client becomes frustrated by the refusal

Acknowledge the inconvenience and restate the supported options. The client may have hoped to avoid coordinating another provider. Explain what help can still be given, such as a requirements summary or a clear handover, without inventing a complete solution.

Avoid a defensive lecture or repeated apologies that make the boundary sound negotiable when it is not. If communication becomes abusive, set an appropriate boundary and pause the exchange if needed. The goal is a practical next step, not convincing the client to feel pleased about the limitation.

• “I understand that involving another provider is inconvenient.”
• “I cannot deliver the specialist service directly.”
• “I can provide a clear summary of the related project requirements.”
• “The supported portion of the work remains available as described.”

What to do when the inquiry needs a clear next step or closure

End with an accurate status: a supported scope, a referral to assess, a pending decision, or a declined request. Do not leave the client believing that unsupported work is being investigated indefinitely when no such service is available.

29. What to do when a client cannot choose between a partial service and another provider

Compare the practical routes against the client’s priorities. A partial engagement may preserve a preferred specialist for one task, while a broader provider may reduce coordination. Explain the trade-offs without claiming one model is universally better.

Give a recommendation based on the confirmed requirements and ask for a specific decision. If indecision continues, use what to do when a client refuses to choose an option. Do not start partial work before the client understands the remaining gap.

• “The partial service keeps this scope here but requires separate coordination.”
• “A broader provider may handle the combined delivery through one arrangement.”
• “Which priority matters most for this project?”
• “Please confirm the chosen route before the supported work begins.”

30. What to do when a client asks to be contacted if the service becomes available

Clarify what follow-up the client wants and use the business’s appropriate process. Do not promise a future launch date or enroll them in unrelated marketing. A request about one service does not authorize a broad campaign or repeated messages.

If there is no plan to offer the service, say so. Where a suitable notification process exists, record the limited preference accurately. Keep the current inquiry closed rather than implying the project has entered a waiting queue for a service that may never be introduced.

• “There is no confirmed plan to offer that service at present.”
• “If an appropriate notification option is available, it can be limited to this topic.”
• “That would not place the project in a production queue.”
• “For the current need, another provider remains the practical route.”

31. What to do when a client accepts the supported part of the service

Confirm the exact deliverables and exclusions, including the task another provider will handle. Name the dependencies and approval points so the partial engagement does not quietly become responsibility for the whole project.

Ask for the inputs required to begin and explain the handover. Keep the language positive and concrete, without repeating a long list of everything the business does not do. The scope should make the client’s next steps visible and support a smooth collaboration.

• “The agreed scope covers the content and layout deliverables listed here.”
• “The technical implementation will be handled separately.”
• “These inputs are needed before the first review.”
• “The handover will identify the approved materials for the implementation provider.”

32. What to do when there is no suitable service or referral to offer

Decline clearly and respectfully. Explain the boundary briefly and avoid inventing an alternative that does not meet the need. A concise requirements summary may still be useful, but do not offer extensive unpaid consulting merely to soften the refusal.

Close the inquiry with an accurate status and no misleading promise to keep searching unless that work is genuinely agreed. If there is an existing project, handle its remaining scope separately. The client should know that this request is not proceeding and can seek another route without waiting.

• “I cannot offer a suitable service for this request.”
• “I also do not have a verified referral for the specific requirement.”
• “The key capability to look for is the specialist task described in the brief.”
• “This inquiry will not proceed through the current service.”

What to avoid when declining an unsupported service

Do not accept work beyond capability to preserve a sale, promise an unconfirmed partner, or describe a partial solution as equivalent to the requested result. Do not share private client information through a referral without the relevant permission.

Avoid unsupported judgments about competitors or broad claims that another provider will solve the problem. Keep scope, responsibility, and availability separate. If the issue involves an existing disputed commitment, review the actual agreement and seek appropriate advice instead of improvising legal conclusions.

Frequently asked questions about services that are not offered

What to do when a client asks for a service that might be introduced later?

Describe the current offer accurately and avoid a speculative launch commitment. If an exploratory assessment is genuinely available, give it a clear scope and limits. Otherwise, explain that the client should use a provider offering the required service now. Future interest does not create current delivery capability.

What to do when a client asks whether the refusal is about price?

Explain the actual limitation. If the task is outside capability, a larger budget does not resolve that. If the task is within capability but outside the standard package, assess it as additional scope. Avoid using a capability refusal to conceal a pricing decision or suggesting that money can remove every professional boundary.

What to do when a client asks for a referral but no provider has been checked?

Do not present an unverified name as a recommendation. Describe the type of specialist needed and the criteria relevant to the project. If research is offered as a separate task, define it clearly. A public search result should not be described as trusted without a basis for that claim.

What to do when a client asks to keep the current provider involved after a referral?

Clarify the role they want and whether it is available. Providing existing project materials differs from managing the other provider or approving specialist work. Agree on responsibilities, permissions, and any additional scope before participating. Do not let an informal introduction become an undefined management commitment.

What to do when a client asks for a one-sentence refusal?

Use a clear boundary and a relevant next step: “I do not offer that specialist service, but I can clarify the project requirements for an appropriate provider.” Only include the second part if that help is genuinely available. Avoid vague wording that leaves the client expecting a later acceptance.