Answer the question behind the enquiry
A visitor may ask about price while trying to understand whether the service fits. Provide the facts your business has approved: what is included, who the offer suits, and what changes scope. If the work is custom, explain the information needed for a team quotation.
Avoid inventing scarcity, discounts, availability, or customer results to encourage contact. An accurate first answer gives your team a better conversation to continue. An aggressive prompt that collects a number but leaves the visitor confused may add little value.
Ask qualification questions with a purpose
Choose one question that helps the team decide the next step. For a project, that might be the outcome the customer wants. For an appointment, it might be the topic to discuss. The question should be relevant before you ask for budget or timing.
Visitors can share a preferred contact method when they want follow-up. Keep consent and expectations clear. A captured enquiry does not authorise unrelated marketing or guarantee the visitor is ready to buy.
Keep quotes and commitments under human control
Supplied pricing information can guide an answer when the business has enabled that feature. A custom quote still needs the responsible person to review the requirement and terms. Do not teach the assistant to invent a price from general market knowledge.
The same applies to delivery promises, appointment confirmation, and contract scope. Use precise wording about requests and reviews. If the source does not contain the answer, the assistant should say it cannot confirm rather than present a guess as business policy.
Example sales discovery flow
Visitor: I want to improve my business website. Assistant: [Explain the verified service.] What would you like the website to help customers do? Visitor: Request quotations for our products. Assistant: Our team can review that goal and discuss scope. Would you like to leave your preferred contact method? Team: Review the requirement and prepare an authorised next step.
Prepare the follow-up workspace
Use the saved enquiry and conversation to personalise the response. Review any score as a prioritisation aid, not a substitute for reading the requirement. Configure tags or tasks only when someone will act on them.
Decide who handles urgent or ambiguous requests and how to avoid duplicate contact. Check the team and resource allowances before scaling the installation. A high volume of chats can increase staff work if the questions and next steps are poorly defined.
Measure sales outcomes separately
Track confirmed opportunities and sales through your own business process. Conversation volume and captured leads are intermediate signals. Account for traffic campaigns, seasonality, and staff response when comparing periods.
The product does not guarantee a conversion increase or verified return on investment. You can use the free ROI tool to explore assumptions, but its result is a scenario, not a forecast. Start with useful answers and review the outcomes you actually observe.
Review a request that does not fit your offer
Test a visitor asking for a service you do not provide. The assistant should acknowledge the limit rather than widen your offer to secure a lead. A contact request may still be appropriate if the team can clarify, but it should not imply acceptance of the unsupported work.
Also test a visitor who wants a price before giving personal information. Provide published pricing guidance where available and explain when scope review is necessary. Do not replace that answer with an invented discount or a compulsory lead form.
Have a salesperson review the resulting conversation and identify the next action. If the person cannot tell what the visitor wants, improve the discovery question. If the visitor already received a clear answer and needs no follow-up, respect that outcome. A useful sales assistant should improve understanding rather than treat every conversation as a target to convert at any cost.
A controlled trial to adapt
Example to adapt: a prospect describes a project whose scope is not covered by your published package. The assistant may explain the verified package and invite a team review, but it should not silently add work or invent a new price. Ask a follow-up about timing and check the same boundary. Have the responsible salesperson read the saved conversation and state the next action. If the proposed wording implies that the project has already been accepted, revise it before publishing. This is a sample evaluation, not a promised customer outcome.