Configure your AI chat
Prepare website knowledge, greeting, lead capture, handoff and after-hours behaviour. Test the enabled configuration against real dealership questions before launch.
Before you start
For a dealer administrator working with the chat owner. Have the approved website, allowed hostnames, handoff mailbox, timezone and test scenarios ready. The steps below name controls found in the shared platform. Advanced blueprint capabilities remain subject to configuration and verification.
Editorial review: 23 September 2026. Controls depend on your enabled dealer configuration; confirm access with the DriveAgent team.
Yournextsteps
Work through the checks below with the person responsible for your dealership configuration.
1. Configure knowledge sources
In Chat configuration, review Website URL and Allowed domains. Use the approved public HTTPS website and exact allowed hostnames. Review crawl depth, maximum pages and crawl frequency. Check inventory retrieval with known vehicles; the presence of a feed does not prove that every answer is current.
2. Set the greeting and appearance
Review Greeting message, Suggested questions, Position and Primary colour. Make the greeting clear about the assistant and route customers toward supported tasks. Personality templates and custom system-prompt control remain requirements to confirm in the enabled product.
3. Configure human handoff
Set Handoff email and Enable human handoff. Test an explicit request for a person and verify that the correct team receives it. Priority routing, frustration signals and keyword rules remain configuration requirements; check the actual available controls before relying on them.
4. Review lead capture
Check Enable lead capture and Require email before chat. Use approved test details and verify what is saved and where the team sees it. Lead scoring, CRM stage mapping and automated follow-up remain requirements to validate in the connected workflow.
5. Check after-hours behaviour
Set Timezone and Offline message. Agree who handles enquiries outside staffed hours and test the resulting message and handoff. Daily hours, holiday schedules and appointment actions need confirmation in the enabled configuration.
6. Test and enable
Run known-stock, unavailable-stock, incorrect-price, missing-policy and human-handoff scenarios. Record expected and actual responses. Verify lead capture and staff receipt before enabling the widget for the dealer. If results are wrong, keep the affected workflow disabled and ask the team to review retrieval and routing.
Review before you launch
Confirm configuration, approvals and support arrangements with your team. Test the customer journey using approved test details before switching on customer-facing activity.
Talk to our teamScope and troubleshooting
Questions andchecks
Grounding uses configured sources, but it is not a guarantee against incorrect or unsupported responses. Verify representative answers, stale stock, conflicting prices and unknown policies. Make a human route available when an answer cannot be supported.
Crawl and index timing depend on the source pipeline and configured frequency. Confirm a changed page or vehicle can be retrieved before treating the update as available. This guide does not claim universal five-minute updates or a measured sub-two-second response time.
Multilingual conversations and custom intents remain product requirements. Confirm the enabled languages and test dealership-specific terminology and handoff with appropriate reviewers. Language-specific knowledge bases and guaranteed terminology accuracy are not verified by this guide.
Test the handoff path to confirm the conversation and permitted lead details received by the assigned team. Sentiment thresholds, failed-attempt limits, topic-specific routing, transcript completeness and lead scores remain requirements to verify for the configured workflow.
Conversation continuity depends on identity, session handling and retention policy. Cross-device memory and configurable 7-day, 30-day or permanent retention remain specified requirements, not a promise that visitors can be recognised without appropriate identity and privacy controls.
The shared platform contains experiment assignment, result calculations and winner recommendations. Confirm the experiment setup available to your account. Four simultaneous variants, automatic winner promotion and the full set of personality, greeting, qualification and CTA experiments remain requirements to verify; a recommendation is not automatic activation.