Automotive
Example workflow
Vehicle Sales Enquiry
Prepare a vehicle enquiry around model preference, use and purchase timing.
- Model preference
- Intended use
- Purchase timeline
Automotive · Appointments
Vehicle Service Request
Capture a workshop request with vehicle model and service reason.
For automotive teams handling appointments conversations.
Example workflowWhat this chatbot helps with
- Capture a workshop request with vehicle model and service reason.
- Clarify vehicle model before the team follows up.
- Organise service reason, preferred branch, visit window 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 appointments intent and explain the scope.
- 02
Relevant questions
Which vehicle model needs service?
- 03
Captured details
Vehicle model · Service reason · Preferred branch · Visit window
- 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.
- Vehicle model
- Service reason
- Preferred branch
- Visit window
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 vehicle model needs service?” and “Is this routine maintenance or a specific concern?”
- A named team responsible for vehicle service request enquiries
Give each source an owner and a review date. Remove outdated instructions before the workflow goes live.
Integrations and limits
Diagnosis, job allocation and final estimates require workshop review.
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
Driving safety concerns, breakdowns or warranty disputes.
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 appointments 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 driving safety concerns, breakdowns or warranty disputes.
- Review live enquiries. Use the team inbox to handle follow-ups and improve unclear answers.
Questions about vehicle service request
What does the team need from the first conversation?
Start with vehicle model and service reason. Collect the other suggested details only if they help the next action. Is this routine maintenance or a specific concern?
Can it complete this request automatically?
Diagnosis, job allocation and final estimates require workshop review. The catalogue is an example, not a claim that the integration is already enabled for your account.
Which situations need a colleague?
Driving safety concerns, breakdowns or warranty disputes. Agree on the responsible team and response expectations before launch.
Can we change the questions?
Yes. Review these prompts against your automotive process. Which vehicle model needs service? may need a shorter form or additional context for your customers. Test changes with staff before enabling them.