Shopper’s assistant
Questions, approved offers and explanations the shopper can receive.
The conversation is open. Private desk figures stay behind the boundary.
See how the contract check distinguishes shopper-facing terms from the store’s private economics, and where deployment review still matters.
A boundary, not a prompt instruction.
Contract boundary check
Check the selected terms before allowing them into the conversation.
Private desk figures
Dealer invoice cost, manufacturer holdback and minimum approved price belong on the dealership side.
- Approved shopper-facing terms
- Signed deal record
- Checked morning handoff
Architecture overview. Each dealership’s server-side controls and connections require deployment review.
Test what can cross.
Select a private desk figure to see the entire selection rejected by the contract validator.
Contract check passed
Allowed by the contract check
The selected shopper-facing terms pass this check.
Approved response preview
- Selling price$41,200.00
- Documentation fee$199.00
- Total price with taxes and fees$44,390.00
This interactive example runs the contract validator in your browser with synthetic values. It does not test a dealership’s production deployment.
These synthetic values are public examples. This browser demonstration runs the real contract validator; it does not test a live dealership, a model connection or a payment processor.
Four controls behind the conversation.
Intended platform controls that separate open conversation from private dealership pricing authority.
Protected dealer figures
Keep private dealership economics separate from shopper-facing terms. Reject a selection containing a protected field rather than partially forwarding it.
Prices calculated to the cent
Calculate the money separately from the conversation. The assistant explains approved figures; your store owns its prices and exception decisions.
Signed deal records
Check that the agreed record is unchanged before the handoff. A mismatch needs review before the deal moves to its next step.
Credit consent and manager review
Bring the shopper’s consent with a payment check. Keep requests outside approved pricing rules with the desk manager for review.
What this demonstrates. What production still needs.
Clear separation between what you can verify in this browser today and what each dealership deployment requires before launch.
| Control | Evidence on this site | Deployment requirement |
|---|---|---|
| Protected dealer figures | The contract check rejects a selected private field and the whole selection fails. | Verify the check at every server-side prompt, tool-result and shopper-response boundary. |
| Pricing authority | Illustrative prices and contribution use separate arithmetic rather than model-written totals. | Review dealer rules, taxes, disclosures and exception permissions in the configured system. |
| Signed deal records | The walkthrough explains a checked handoff. | Review signing keys, trusted verification, expiry, replay handling and access controls. |
| Credit consent | The buyer journey explains consented soft-pull pre-qualification. | Connect an authorized provider and confirm consent, identity and lender requirements. |
| Payments and holds | The site explains an illustrative refundable hold and does not collect payment. | Confirm processor setup, authorization, refund handling and dealership terms. |
| Dealer-system connections | The walkthrough describes the intended handoff. | Verify each dealership’s connection, permissions and operational workflow. |
| External assurance | No independent audit report is supplied by this marketing demonstration. | Complete the relevant security, legal and operational reviews before launch. |
Bring your toughest boundary questions.
Review pricing authority, consent, record verification and the requirements of your dealership’s deployment.