Try the workflow.
Know its limits.

What works & limitations

• The request flow validates fictional details, matches configured demo buyers, calculates sample bids, and lets you simulate credits or reset the ledger.
• Buyer names, balances, vehicles, arrival examples and financial figures are fictional. City scenarios do not establish coverage or search demand. Prices and calculator assumptions are not quotes, forecasts or measured business results.
• No actual buyers, telephone network, payment provider, CRM, repair technician or human handoff destination is connected. Nothing here books an appointment, charges a card or reserves a territory.
• Sarah uses local scripted rules and mock provider adapters. You can test context, corrections, interruptions, silence and failures. This is not a connected language model or a live phone conversation.
• For immediate danger, contact emergency services directly. Do not rely on this demo for emergency assistance.

Demo data & privacy

Use fictional information only. The lead form requires a name beginning with “Demo” and a reserved test phone number, such as 202-555-0142. Do not enter real contact details, exact addresses or sensitive information into any demo field.

The lead simulator keeps its state in page memory; refreshing starts a fresh session. It does not save form entries to browser storage or submit them to the live site. Exporting CSV explicitly downloads a file to your device, which remains until you remove it.

The Voice Lab keeps its current conversation in page memory until you restart or leave. Audio recording is off. Optional microphone checks and speech input require explicit controls. Speech input is available only when the browser confirms an existing on-device English recognition capability; there is no remote fallback or automatic language-pack download. Optional spoken replies use only voices marked local by the browser. Typed messages remain available.

Loading the website still requests files from its hosting service, which may process normal connection metadata such as your IP address. This page describes the current prototype behavior; it is not a claim of regulatory certification or a complete production privacy policy.

Before a live service

A live launch needs verified buyers and service coverage, a pricing model, a selected provider and budget, authenticated backend integrations, a real human escalation destination, and approved privacy and consent flows. Those decisions have not been completed. The demo does not authorize or initiate outbound calls.