A prospect messages a service business: "We need someone to manage our social media. How much will it cost?" The question sounds straightforward, but the work is not defined. Do they need content writing, design, ad campaign management, or someone to reply to customers? Giving a firm number now can either turn away a suitable buyer or win a contract that is difficult to deliver.
The right response is neither to refuse to discuss pricing nor to send a twenty-question form. Answer what you already know, identify the few missing details that actually change the scope, and decide whether an approved indicative price is possible or a scoping call is needed before a final quotation.
Turn "we need this service" into a request you can price
Service firms sell a mix of time, expertise, and deliverables. Two clients asking for the same named service may need very different work. Separate incoming requests into three practical states:
General inquiry: The buyer wants to know whether you offer the service or what it includes. Answer directly using approved information.
Scope needs clarification: The buyer has a real requirement, but a missing variable could materially change the effort or price. Ask about that variable rather than collecting every detail at once.
Ready for quotation review: The expected deliverables, exclusions, timeline, and necessary approvals are clear enough for an authorized person to review a proposal.
This is more than message organization. Atlassian's scope of work guidance recommends documenting objectives, deliverables, inclusions, exclusions, constraints, and timing. Asana's project scope guide, updated February 15, 2026, similarly emphasizes clear boundaries, deliverables, and deadlines. These are general project management references, not Egyptian market statistics or claims about Mr. AI features.
A six-field scoping card, not a long questionnaire
Create a short internal record for each service request, even if the team initially uses a simple document. The aim is for the person preparing the quotation to understand the request without replaying the entire conversation.
- Desired outcome: What does the buyer want to achieve? "Organize content for our business page" is more useful than "We need marketing."
- Deliverables: What will actually be supplied? Designs, reports, consulting sessions, scheduled maintenance, or something else?
- Volume and frequency: How many branches, accounts, visits, deliverables, or service periods are involved? Ask only about factors that affect the work.
- Boundaries and exclusions: What is included and what requires a separate agreement? For example, does an ad management fee include the advertising budget itself?
- Timing and approvals: When does the work need to start? Who reviews and approves the scope and price?
- Quote status and next step: Is there a published fixed price, an approved indicative estimate, a review requirement, or a final authorized quote? Who owns the next action and when?
Do not ask the prospect for all six fields in the first message. Some information should already come from your service catalog or company policies. Gather the rest progressively.
Example: a marketing agency receives a WhatsApp inquiry
This is an illustrative scenario, not a real customer conversation.
Prospect: "We need social media management. What's the price?"
Instead of quoting an arbitrary package, the agency might respond: "We can help. Content management and paid ad management are different services. Are you looking for content for your pages only, or do you also need ad campaigns?"
If the answer is content, the next question might concern the number of pages or required output volume. If the buyer also wants campaigns, explain that advertising spend and the agency's management fee are separate items unless the approved offer states otherwise.
Once the key details are clear, send a summary the buyer can correct: "Our understanding is that you need content management for two pages, without paid campaign management for now. We'll review the required deliverables and return with a quote that clearly states inclusions and exclusions."
Notice what this response does not do. It does not promise a final price or delivery date before approval, but it also does not leave the buyer without an answer or a next step.
When is an indicative price appropriate?
If your business has a published fixed-price package with clear limits, share that approved price and explain exactly what it includes. If the amount depends on workload, an indicative range is appropriate only when the business has authorized that range and its assumptions.
When a quotation depends on missing specifications, a third party, a site visit, or technical assessment, say that the team will review the details and confirm the offer. Do not invent a number just to keep the conversation moving. Discounts, contractual commitments, and delivery promises must stay with the person authorized to make them.
For on-site requests, see our guide to qualifying technician visits before confirming appointments. For companies issuing formal quotations, the B2B WhatsApp quotation workflow covers versioning and approvals in greater detail.
Measure clarity, not the number of quotes sent
Over a two-week period, review four signals from new inquiries: the share that reached a clear scope, the number of quotes that needed rework because information was missing, the share of requests with an owner and next step, and the number of times buyers had to repeat details they had already provided.
Compare similar services and request sizes. Sending more quotations does not by itself prove higher conversion or profitability. Not every qualified request will become a sale.
A practical test: Open your last ten unresolved service inquiries. Could a new team member identify the expected deliverables, exclusions, and next step from the record? If not, the intake process needs work before response speed becomes the main concern.
Where Mr. AI can help, and where human approval remains essential
According to Mr. AI's current FAQ, the platform helps teams respond using company knowledge across WhatsApp, Messenger, and website chat. It also supports follow-up, conversation summaries, and handing conversations to staff when needed. These capabilities can help clarify approved service information, preserve the buyer's context, and make the next step visible to the team.
Mr. AI is not a replacement for a pricing manager or project manager. Do not assume it calculates custom project costs, produces binding contracts, or automatically approves delivery scope. Your business must define the scoping card, pricing rules, and approval responsibilities.
Start with one service that attracts frequent inquiries. Identify the one or two questions that genuinely change the price, test how your team handles them, and then book a Mr. AI demo to discuss customer conversation handling and follow-up.
