See the dealership operating platform work.

One record. Every source attached.

The Dealership Operating Platform connects source health, identity resolution, dealership definitions, store access and every product using the governed record.

Built features
DMS APIs29 CRM datasetsLive appointmentsCustomer identityFreshness + lineageStore permissions
Step 1 of 4

Connect the systems already in use.

DMS, CRM, service and website records enter with their source identity and freshness intact.

Ready · 15 seconds
Dealership Operating Platform / Record explorer
All systems current DO
Illustrative dealer group · masked sample

Canonical record DEMO-CUST-0142

Seven source records resolved into one governed customer, vehicle and deal relationship.

Access: Central + group aggregate⌄
Resolved entities
2
customer + vehicle
Active definitions
4
shared across products
Freshest update
5:34
website · today
Attached sources
Refresh and identity status
6 domains
Resolved relationship
Fields masked in demo and constrained by access
Identity resolved
Maya C.
DEMO-CUST-0142 · m•••@example.invalid
SMS + email eligible
Vehicle2021 midsize SUV
Mileage48,320
Payments27 / 72
Position+$3,330 equity
Last service74 days
Last outbound41 days
Eligible contact = permitted channel + no DNC + outside cadence window. Definition version 3.4 is shared by Audience, Loyalty and Direct Mail.
Ask

Answers against approved views with the definition beside the result.

Audience

Builds a masked, permission-aware segment before any activation.

Loyalty

Recognizes VIP benefits and the next service opportunity.

Brief

Delivers exceptions and pace changes to authorized managers.

DMS-0142 + CRM-8841 + RO-30442 + WEB-7710 + APPT-0552 + INV-0142 + RC-26-417 → identity rules v2.7 → DEMO-CUST-0142 → eligible_contact v3.4 → Ask / Audience / Loyalty / Brief
Motion use: the original source cards stitch into this record; the definition and access boundary lock into place; the four product consumers illuminate only after the canonical record resolves.

Ask a dealership question. Inspect the answer.

Ask keeps the conversation, a concise answer, optional visuals, and a persistent evidence panel for scope, permitted fields and sources.

Built features
Threaded follow-upsSaved folders18 metric definitionsInline visualsSource citationsPII guardrails
Step 1 of 5

Ask in dealership language.

Start with the question a manager would ask in a meeting. No report builder or field names required.

Ready · 14 seconds

Ask

Finance review / July 80+ month contracts

How many retail contracts ran 80+ months in July?
BC

284 retail contracts ran 80 months or longer.

216 carried GAP. The remaining 68, or 23.9% of the cohort, did not. West had the lowest attachment rate at 72.4%.

80+ month contracts284
With GAP216
Without GAP68
GAP coverage by rooftop
Retail finance · delivered July 1 to 31 · term ≥80 months
68 to review
North Store64 / 82
Central Store59 / 76
South Store51 / 68
West Store42 / 58
BC

North has the most contracts to review.

North has 18 without GAP, Central 17, South 17 and West 16. West still has the lowest attachment rate because it delivered fewer long-term contracts.

Motion use: the question breaks into visible scope and definition rules; the result counts up; selecting Data or Sources moves the evidence into the foreground without leaving the answer.

Build the audience. See every exclusion.

The product turns a plain-language request into applied filters, safeguards, live counts, masked samples, an approval and a receipt.

Built features
Nested AND / ORSaved segmentsMasked previewsConsent + DNDCadence capsAutomation recipesRe-entry + exitsSend TextConversationsCommunications CenterCampaignsActivation receipts
Step 1 of 5

Describe the owners you want to reach.

Use the opportunity in plain language. The builder turns it into inspectable dealership rules.

Ready · 16 seconds
Audience / Builder
Activation role verified DO
Show
Illustrative dealer group · masked sample

Service-to-trade opportunity

Build, inspect and activate an eligible owner audience.

All permitted rooftops⌄
1 Build2 Preview3 Approve4 Activate
Starting owners3,160
Qualified214
Suppressed27
Ready187
Masked audience preview
Representative matches only · no raw contact detail exposed
CustomerStoreVehiclePaymentsEquityLast serviceLast contactChannels
M••• C.Central2021 midsize SUV27+$3,33074d41dSMS + email
J••• R.North2020 compact SUV38+$4,180103d57demail
A••• T.South2022 full-size SUV25+$2,71046d35dSMS
Approved outreach workflow

187 eligible owners · Demo Operator approval required · cadence reserved at send time

ACTIVATION RECEIPT · DEMO-ACT-2026-07-31-001
187 eligible · approved by Demo Operator · destination: approved outreach workflow · 2026-07-31 10:42:18 CDT
Motion use: each filter physically narrows the population; 27 suppressed records exit the flow; activation remains inert until approval; the receipt stitches back to the audience definition.

See the operating issue before it becomes a month-end surprise.

Ledger maps the accounts each dealership already uses into one operating definition and keeps every result tied to its source lines.

Built features
Step 1 of 4

Choose the operating question.

Start with a dealership decision, then constrain the stores, dates and approved records behind it.

Ready · 10 seconds
Ledger / Operating statement/performance
Governed data current DO
Illustrative dealer group · masked sample

Service absorption by rooftop

Trace the result from operating definition to source accounts.

All permitted rooftops · July
Operating question
Scope and definitions remain inspectable
Approved view
Rooftop comparison
Current period · source-linked
1 exception
Open the source lines behind the gap

No change is made until an authorized operator confirms it.