Auto Club Group: driver and vehicle voice demo

Status: Current | Last reviewed: 2026-09-29

This example connects a voice assistant with a form you can use on your phone or computer. Use sample information: submitting a form does not change an insurance policy or issue coverage.

The linked app uses the separate Auto Club Group · Auto insurance catalog: ACG insurance blue, the supplied AAA logo, matching driver/vehicle form layouts, and a summary after submission. See ACG auto forms for the component and font details.

Original text-link demo

  1. Open TrueServe Auto Voice Demo, select version 5 in Salesforce Agentforce Builder, and use live action testing. You can also use the Agent Studio Voice integration.
  2. Tell the assistant you want to add a driver or a vehicle and agree to receive the form link. The assistant uses the supplied caller number (ANI); if it is missing, it asks for your mobile number including country code.
  3. Open the texted link. The page shows Form session connected when ready.
  4. Fill out the form. For a driver, enter a sample name, date of birth, relationship, and two-letter license state. For a vehicle, enter a sample 17-character VIN, year, make, model, and use.
  5. Review the demo disclosure and select its checkbox.
  6. Select Submit details. The page shows Details received. You do not need to say “done” for the waiting action to receive your submission.

Version 5 opens the form immediately and checks for submission in short steps for roughly a minute after opening or another conversation turn. You can ask questions about the fields while you fill it out. Submit during that checking window to test acknowledgement without saying “done”. A later submission is still saved, but the assistant may need another turn to check it.

Use TrueServe Auto Voice Demo. The earlier Loop Probe, Hooks Probe, and After Wait Probe test agents have been removed. Set ANI to the receiving mobile number or leave it blank and give the number when asked. Do not enter experienceSessionId—the agent creates it internally.

This version is available for Builder acceptance testing. The short-check pattern was tested in Agentforce Voice API sessions, and the connection/form workflow was tested with live authoring actions. Complete authenticated Builder and PSTN/SIP acceptance is still outstanding.

Cancel closes the request. If you lose connectivity, the page reconnects without clearing your entries. If a submission fails, keep the page open and retry. Reopening the private link reconnects to that session.

Sessions expire after an hour by default. If the page says Session ended, start a new conversation to obtain a new link. The AWS example also resets sessions when its demo service is replaced.

The private link belongs to your session; do not share it. The operator should verify waiting behavior when changing the voice runtime or action configuration.

In Builder, the operator can set the ANI preview variable before starting the test. A live test sends a real text message to that number. The connection action creates the session automatically; no launcher script is required. If you prefer speaking, tell the assistant and it will collect the demo details without sending a text. If a text cannot be confirmed, the assistant offers that spoken path.

Spoken field-by-field edits do not currently fill or change the visible form. The spoken path collects a complete, confirmed submission.

Salesforce-native prototype

Select TrueServe Auto Voice Salesforce Native, version 4, for the separate Experience Cloud prototype. Start a fresh Builder preview after selecting the version. It uses the same ACG driver and vehicle styling and requires sign-in before displaying your form. The original agent above is still available.

  1. Set ANI to your WhatsApp number and Email to the email you want to use for sign-in before starting Builder's voice preview. The demo creates a dedicated test account automatically for a new email; no tester Name is needed. Reusing Email reuses that account, even if ANI changes. If ANI is set, the assistant uses it without asking again. You do not need an experience ID. Leave Email blank only when your number already identifies a portal account.
  2. Ask to add a driver or vehicle. Agree to a WhatsApp link if delivery is enabled. WhatsApp delivery is enabled in the demo org and receipt was confirmed on September 28. If delivery is unavailable, the assistant can continue by voice; it does not request another number or ask you to sign in to an unsent link.
  3. Open the newest private link. New notifications go directly to the ACG sign-in page. A new test account may take a moment to prepare before the page requests an email verification code. Enter that code on the page and select Verify and continue, never give it to the voice agent. Opening the WhatsApp link alone does not complete sign-in.
  4. If this is your first passwordless sign-in, select Verify my email address and follow Salesforce's email link. Return to the page and select Send email code. You can also select Use username and password.
  5. Keep the call open. Ask about any field or give a field value by voice; the assistant can update the displayed form. The page refreshes automatically.
  6. If your typing conflicts with a newer agent update, choose Use agent’s values or Keep my changes. Review the values and demo disclosure.
  7. Select the acknowledgement checkbox and Submit request. A receipt appears. No spoken completion is required when the agent's status checks observe the submission. Ask for the other workflow to reuse the same page and link.

The link identifies your form but does not sign you in by itself. Only the portal account selected for this session can open it. Email selects that account; it does not change where another account's code is sent. The driver's name is still required in the Add a Driver form and is separate from the generated tester name. Sign-in may take a moment, and links expire after an hour. Request a new link if it expires.

If the browser reports Too many redirects before the ACG page appears, tell the demo operator the device/browser and whether the error occurs before or after code verification. An IPv4-only login restriction was removed from the two demo profiles on September 28, after which the customer confirmed that the ACG code-entry page opened on mobile. Retry the same unexpired link after an operator corrects access settings.

The native prototype runs a bounded series of fast status checks after a turn. If those checks have ended, your submission is still saved, but another voice turn may be needed before the assistant acknowledges it. Successful customer code verification and microphone-based Builder/PSTN acceptance are still being validated; the completed form integration test used text authoring turns and a portal session entered by an administrator.

See also