Choose a useful chatbot workflow for your business
Start with a recurring customer question and a clear next step your team can support. A retailer may need product comparisons; a service business may need a complete enquiry; a multi-location company may need accurate branch guidance. Configure the knowledge and action around that job.
Planning guidance for retail and service businesses. These are workflow suggestions, not customer case studies or measured results.
Retail: help a shopper compare options
Prepare current catalogue descriptions, meaningful differences, prices and delivery or collection policies. Ask customers about the intended use and relevant preferences, then help them compare suitable offerings using those supplied facts.
Offer an approved product or checkout destination for the next step. Confirm that the selected page belongs to the intended item. A website import or saved stock field is not proof of live inventory, a reserved item or a completed order.
Services: gather a useful quote or callback request
Define the service scope, areas covered, pricing basis and the details staff need before following up. Explain which work has a published price and which requires assessment. Configure a short set of useful questions rather than requesting unnecessary personal information.
Enable the appropriate enquiry flow and check the submitted request in the workspace. Make clear that a quote request is not an accepted quotation or a commitment to perform the work. Assign a team contact and a realistic follow-up process.
Consultations: guide an eligible appointment request
Configure the consultation slots and explain what the appointment covers. Test an available slot, one that has already been taken and an incomplete form. Only report confirmation after a successful submission.
If native booking management is enabled, verify the private management link and the available rescheduling or cancellation options. A V7 consultation is separate from an appointment in another calendar unless an actual integration connects them.
Multiple locations: point customers to the right branch
Keep branch names, opening hours, contact paths and applicable delivery or service areas current. Distinguish a physical location from a service area, and state when a rule applies only to one branch.
Test a customer who names a branch, one who provides only an area and one outside your coverage. The assistant should ask for the missing detail or use the configured contact route instead of inventing a location or promising service.
Measure completion and review failures
Choose an outcome you can verify: opening the correct product page, receiving a complete enquiry or confirming an eligible native booking. Review the conversation, recorded request and usage cost together. A button click is evidence of navigation, not a sale.
Keep failed questions and incomplete handoffs in a short review list. Correct the relevant source or workflow, then repeat the check. Expand to another use case once your team can maintain the first one reliably.
Retail example: compare two products before checkout
A visitor asks, "Which jacket is waterproof and under £80?" Load current catalogue prices, waterproof ratings, sizes and a delivery policy. Test the same question with one product out of stock and with a lower budget. A useful answer states the supported differences and links to the matching product page; it does not invent stock or complete a purchase.
Then ask, "Will it arrive by Friday?" Keep delivery estimates and dispatch cut-offs in a reviewed policy. If the necessary location or deadline is missing, the assistant should ask or route the question to your team. Check the actual product link, answer accuracy and processing cost in your own test conversation. This is a fictional test scenario, not a customer result.
Service example: qualify an enquiry without promising a booking
For a vehicle-detailing business, supply service areas, package descriptions, starting prices, exclusions and a working contact destination. Test an enquiry for a large vehicle with heavy staining. The assistant should explain the relevant package, request the details your team needs for a quote and distinguish a starting price from a confirmed quote.
Ask for a specific appointment next. Unless an authorised booking integration actually confirms availability and saves the booking, the response should offer a contact or enquiry route and describe it as a request. Submit the form, find the saved lead and complete the human follow-up before launch. This example is illustrative and does not promise more sales.
What to check before launch
Results depend on your information, configuration and team follow-up. V7 does not guarantee sales, staff savings or successful outcomes, and additional business-system operations need an implemented connection.