Automotive
Example workflow
Test Drive Request
Collect a model and preferred dealership visit window for staff confirmation.
- Model
- Branch
- Preferred date and time
Automotive · Sales
Vehicle Sales Enquiry
Prepare a vehicle enquiry around model preference, use and purchase timing.
For automotive teams handling sales conversations.
Example workflowWhat this chatbot helps with
- Prepare a vehicle enquiry around model preference, use and purchase timing.
- Clarify model preference before the team follows up.
- Organise intended use, purchase timeline into a readable enquiry brief.
- Explain what happens next and route exceptions to a person.
A conversation with a next step
Illustration only. Questions and replies must be adapted to the business’s approved process.
How the workflow works
- 01
Customer enquiry
Identify sales intent and explain the scope.
- 02
Relevant questions
Which model or vehicle type interests you?
- 03
Captured details
Model preference · Intended use · Purchase timeline
- 04
Next action
Share the request with the responsible team for review and confirmation.
Information captured
Suggested fields to review during configuration. They are not automatically required.
- Model preference
- Intended use
- Purchase timeline
Explain why a detail is needed, let the visitor correct it, and use the minimum information necessary. Ask permission before arranging a follow-up.
Knowledge to provide
- Vehicle and service information approved by the business
- Branch hours and booking process
- Sales and workshop escalation contacts
- Approved answers to “Which model or vehicle type interests you?” and “When are you considering a purchase?”
- A named team responsible for vehicle sales enquiry enquiries
Give each source an owner and a review date. Remove outdated instructions before the workflow goes live.
Integrations and limits
Stock, on-road prices and finance approval require dealer confirmation.
Without that connection, the assistant can explain the approved process and collect a request for staff. It should state what is known, what is requested and what still needs confirmation.
When staff takes over
Finance terms, trade-in valuation or an unavailable model.
Also hand over when the visitor asks for a person, information is missing or the same question remains unresolved. Pass the enquiry summary with the handoff so the visitor does not have to start again.
Set up with your team
- Discuss the workflow. Share your sales process and review the fields above with WhatsOS.
- Connect your business number. Use the existing Meta connection flow in WhatsOS and complete the account setup.
- Prepare approved knowledge. Supply service information and agree on the handoff owner. Confirm which actions your configuration actually supports.
- Test before enabling. Try normal enquiries, missing details, a request for a person and finance terms, trade-in valuation or an unavailable model.
- Review live enquiries. Use the team inbox to handle follow-ups and improve unclear answers.
Questions about vehicle sales enquiry
What does the team need from the first conversation?
Start with model preference and intended use. Collect the other suggested details only if they help the next action. When are you considering a purchase?
Can it complete this request automatically?
Stock, on-road prices and finance approval require dealer confirmation. The catalogue is an example, not a claim that the integration is already enabled for your account.
Which situations need a colleague?
Finance terms, trade-in valuation or an unavailable model. Agree on the responsible team and response expectations before launch.
Can we change the questions?
Yes. Review these prompts against your automotive process. Which model or vehicle type interests you? may need a shorter form or additional context for your customers. Test changes with staff before enabling them.