Connect through the safest approved path
and label the capability accurately.
Quantum communicates with dealership inventory, CRM, communication, calendar, and operating systems through certified APIs, dealer-authorized APIs, webhooks, ADF/XML, managed feeds, and scheduled exports. Every connection has a documented method, data scope, authorization, capability, and current status.
Integration matrix: capability and current status
| System | Category | Connection Method | Read Capability | Write Capability | Events/Webhooks | Dealer Authorization | Current Status | Last Verified | Notes |
|---|---|---|---|---|---|---|---|---|---|
| Example CRM | CRM | Dealer-Authorized API | Contacts, owners, opportunities | Notes, appointments | Lead and appointment updates | Authorized dealership signer required | Pilot | July 2026 | Availability varies by rooftop configuration |
| Lead delivery (ADF/XML) | Lead Source | ADF/XML | Not applicable | Create lead or opportunity | Inbound lead only | Required | Live | July 2026 | Lead creation only; not a bidirectional CRM connection |
| Inventory feed | IMS | Managed Feed | VIN, pricing, photos, availability | None | Scheduled refresh | Required | Live | July 2026 | Canonical vehicle record source |
| Marketplace inquiries | Lead Source | Managed Feed | Inquiry, listing, buyer contact | None | Inquiry received | Required | Pilot | July 2026 | Channel availability varies by dealership account |
| Voice and SMS provider | Communications | Communication Provider | Call and message events, recordings, transcripts | Outbound message and call | Delivery, opt-out, transfer | Required | Live | July 2026 | Consent and suppression enforced before any send |
| Email delivery | Communications | Communication Provider | Delivery and bounce events | Outbound email | Delivery status | Required | Live | July 2026 | Dealer-approved sending domain required |
| CRM event webhooks | CRM | Webhook | Event payload | None | Lead, ownership, appointment, stage | Required | Dealer-Authorized Bridge | July 2026 | Availability depends on the connected system |
| CRM scheduled export | CRM | Scheduled Export | Opportunities, activities, outcomes | None | None | Required | Live | July 2026 | Read-only reconciliation and outcome matching |
| Dealership calendar | Calendar | Dealer-Authorized API | Availability and appointments | Create or update appointment | Appointment changed | Required | Pilot | July 2026 | Scope depends on the dealership calendar provider |
| DMS operational records | DMS | Scheduled Export | Deal, delivery, and sold status | None | None | Required | Planned | Not applicable | Scoped for outcome verification; not deployed |
| Certified vendor CRM API | CRM | Certified API | Planned | Planned | Planned | Required | Planned | Not applicable | Requires vendor certification program |
| Browser workflow adapter | Infrastructure | Demo Adapter | Demonstration only | None | None | Not used in production | Unavailable | Not applicable | Labeled prototype; never represented as a production integration |
Showing 12 of 12 connections. Status applies to the listed capability, not to an entire company.
No vague logo wall. No implied partnership. Exact capability and current status.
Using a technology is not the same as integrating with it.
Quantum distinguishes the commercial and technical relationship behind every name or logo displayed on this site.
- 01
Technology We Use
A vendor that supports Quantum’s own infrastructure.
- 02
Available Connector
A documented connection method exists, but customer activation may still be required.
- 03
Live Dealer Connection
A dealership has authorized and is using the connection in production.
- 04
Certified Integration
The system vendor has formally approved the integration under its program.
- 05
Strategic Partner
A separate commercial or product relationship exists and may be named publicly.
A vendor conversation, API listing, software subscription, customer request, or displayed logo does not automatically create a partnership.
One opportunity may move through several systems before the result is complete.
CRM
Contacts, opportunities, stages, owners, activities, appointments, and outcomes.
DMS
Vehicle, customer, deal, finance, service, accounting, and finalized operational records.
IMS
Inventory, pricing, photos, vehicle availability, merchandising, and syndication.
Lead Sources
Marketplace, websites, third-party marketplaces, campaigns, calls, forms, and referrals.
Communications
Voice, SMS, email, web chat, approved messaging channels, recordings, and delivery events.
Calendars
Dealership availability, salesperson schedules, appointments, reminders, and attendance.
Identity and Access
Users, roles, locations, authorization, activation, and revocation.
Knowledge
Dealer-approved playbooks, policies, scripts, SOPs, and customer-facing information.
Quantum uses the connection method the system and dealership permit.
Certified API
Vendor-approved production integration with documented authentication and data capability.
Dealer-Authorized API
Access activated and scoped by an authorized dealership user through the vendor’s approved process.
Webhook
Approved real-time events delivered from the connected system to Quantum.
ADF/XML
Automotive lead delivery primarily used to create a new CRM lead or opportunity.
Managed Feed
Approved inventory or operational data delivered through a supported file or service connection.
Scheduled Export
Dealer-controlled report used for read-only context, reconciliation, or outcome matching.
Communication Provider
Voice, SMS, email, and delivery events received through the approved channel provider.
Demo Adapter
A clearly labeled prototype used to demonstrate workflow behavior. Not represented as a permanent production integration.
Every capability should tell the buyer how real it is today.
- Certified
Formally approved by the system vendor for the documented capability.
- Live
Operating in a production dealership workflow.
- Pilot
Running in a controlled production or pre-production deployment with limited scope.
- Dealer-Authorized Bridge
Enabled through an approved dealership-controlled method while a deeper connector is unavailable or in progress.
- Planned
Defined on the roadmap but not currently available for customer deployment.
- Unavailable
Not supported through an approved method.
Status applies to a specific capability, not to an entire company logo. A connector may support lead creation while appointment writeback remains planned.
The dealership decides where Quantum connects and what it may do.
Dealer approval is often required, but it does not replace the system vendor’s API, certification, contractual, or security requirements.
Dealer authorization record
- 01Dealer group and rooftop
- 02Authorizing signer
- 03System and account
- 04Approved data categories
- 05Permitted users and departments
- 06Read scope
- 07Write scope
- 08Allowed workflows
- 09Activation date
- 10Expiration
- 11Revocation method
- 12Vendor requirement
Quantum uses least privilege and maintains a visible record of the dealership’s current authorization.
Show the exact read, write, and event capability for each CRM.
Possible read capabilities
- Contacts
- Opportunities
- Stages
- Owners
- Activities
- Appointments
- Consent
- Outcomes
Possible write capabilities
- Create or update contact
- Create lead or opportunity
- Add activity or note
- Create or update appointment
- Record consent or opt-out
- Update authorized fields
- Record outcome
Possible events
- Lead created
- Ownership changed
- Activity added
- Appointment changed
- Stage changed
- Sold or lost outcome
Quantum publishes capability at the endpoint and workflow level, so you always see what a connector can do today rather than a blanket “full integration” label.
Inventory and communication events enter the same opportunity history.
Inventory may provide
- VIN and stock number
- Year, make, model, and trim
- Mileage
- Price
- Photos
- Availability
- Sold status
- Feed timestamp
Communications may provide
- Inbound and outbound message
- Call event
- Delivery status
- Recording
- Transcript
- Opt-out
- Transfer
- Human response
Quantum connects those events to the dealership, buyer, vehicle, source, owner, conversation, and CRM opportunity before Hannah or Coach is allowed to use them.
A buyer should know what the connection can do before the demo.
Filter by system category and by current status. Every row carries its own method, scope, authorization requirement, verification date, and notes.
Integration matrix: capability and current status
| System | Category | Connection Method | Read Capability | Write Capability | Events/Webhooks | Dealer Authorization | Current Status | Last Verified | Notes |
|---|---|---|---|---|---|---|---|---|---|
| Example CRM | CRM | Dealer-Authorized API | Contacts, owners, opportunities | Notes, appointments | Lead and appointment updates | Authorized dealership signer required | Pilot | July 2026 | Availability varies by rooftop configuration |
| Lead delivery (ADF/XML) | Lead Source | ADF/XML | Not applicable | Create lead or opportunity | Inbound lead only | Required | Live | July 2026 | Lead creation only; not a bidirectional CRM connection |
| Inventory feed | IMS | Managed Feed | VIN, pricing, photos, availability | None | Scheduled refresh | Required | Live | July 2026 | Canonical vehicle record source |
| Marketplace inquiries | Lead Source | Managed Feed | Inquiry, listing, buyer contact | None | Inquiry received | Required | Pilot | July 2026 | Channel availability varies by dealership account |
| Voice and SMS provider | Communications | Communication Provider | Call and message events, recordings, transcripts | Outbound message and call | Delivery, opt-out, transfer | Required | Live | July 2026 | Consent and suppression enforced before any send |
| Email delivery | Communications | Communication Provider | Delivery and bounce events | Outbound email | Delivery status | Required | Live | July 2026 | Dealer-approved sending domain required |
| CRM event webhooks | CRM | Webhook | Event payload | None | Lead, ownership, appointment, stage | Required | Dealer-Authorized Bridge | July 2026 | Availability depends on the connected system |
| CRM scheduled export | CRM | Scheduled Export | Opportunities, activities, outcomes | None | None | Required | Live | July 2026 | Read-only reconciliation and outcome matching |
| Dealership calendar | Calendar | Dealer-Authorized API | Availability and appointments | Create or update appointment | Appointment changed | Required | Pilot | July 2026 | Scope depends on the dealership calendar provider |
| DMS operational records | DMS | Scheduled Export | Deal, delivery, and sold status | None | None | Required | Planned | Not applicable | Scoped for outcome verification; not deployed |
| Certified vendor CRM API | CRM | Certified API | Planned | Planned | Planned | Required | Planned | Not applicable | Requires vendor certification program |
| Browser workflow adapter | Infrastructure | Demo Adapter | Demonstration only | None | None | Not used in production | Unavailable | Not applicable | Labeled prototype; never represented as a production integration |
Showing 12 of 12 connections. Status applies to the listed capability, not to an entire company.
Every logo must represent a real, explainable relationship.
Before publishing a logo, confirm
- Permission to display it
- Correct current brand asset
- Relationship category
- Technical capability
- Customer activation requirement
- Current deployment status
- Public description approval
- Last verification date
Display groups: kept separate
- Certified Integrations
- Live Dealer Connections
- Available Connectors
- Technology We Use
- Strategic Partners
These groups stay separate, so a displayed name is never mistaken for a partnership.
If the relationship cannot be explained in one accurate sentence, do not display the logo yet.
Different systems connect through one consistent operating model.
Quantum normalizes each approved connection into the same person, vehicle, opportunity, conversation, appointment, ownership, consent, event, recommendation, and outcome structure.
- 01Authentication
- 02Tenant and rooftop scope
- 03Read capability
- 04Write capability
- 05Event subscription
- 06Field mapping
- 07Pagination and backfill
- 08Idempotency
- 09Rate limits
- 10Retry
- 11Dead-letter handling
- 12Schema versioning
- 13Reconciliation
- 14Audit
- 15Revocation
Hannah and Coach use the normalized Quantum contract, not vendor-specific assumptions embedded inside the agent prompt.
A connector is not live when credentials are entered. It is live when the workflow is proven.
- 01DiscoverConfirm the system, version, rooftop, users, desired workflow, and vendor requirements.
- 02AuthorizeRecord the dealership signer, data scope, permissions, expiration, and revocation path.
- 03ConnectConfigure authentication, endpoints, fields, events, limits, and secrets.
- 04ValidateTest identity, reads, writes, events, failure behavior, and tenant isolation.
- 05ReconcileCompare Quantum records with the destination and correct mapping or timing gaps.
- 06ActivateEnable Hannah, Coach, Marketplace, or workflow actions only after the required capabilities are verified.
Give every connector only the access its workflow requires.
Quantum does not ask dealerships to share personal employee credentials or bypass multi-factor authentication. Production connections must use a vendor-permitted and dealership-authorized method.
- Tenant-scoped credentials
- Short-lived tokens where supported
- Encrypted secrets
- Role-based access
- Read/write separation
- Environment separation
- Audit logging
- Credential rotation
- Revocation
- Data minimization
- Sensitive-field redaction
- Incident response
Know when data is late, incomplete, rejected, or unavailable.
Health indicators
- Authentication status
- Last successful read
- Last successful write
- Last event received
- Data freshness
- Queue depth
- Retry count
- Rate-limit status
- Schema error
- Reconciliation status
- Required action
Connection states
- Healthy
- Degraded
- Retrying
- Attention Required
- Paused
- Revoked
When required context is stale or unavailable, Quantum limits agent authority rather than allowing an unsupported action.
Common questions.
Does dealer approval give Quantum access to every CRM?+
No. Dealer approval is often necessary, but access also depends on the vendor’s technical, contractual, security, and partner requirements.
What is ADF/XML used for?+
ADF/XML is commonly used to deliver a new automotive lead into a CRM. It is not a complete replacement for bidirectional CRM read, activity, appointment, ownership, or outcome APIs.
Does Quantum use browser extensions?+
A browser adapter may support a clearly labeled demonstration or workflow prototype. Production connections should use vendor-permitted, dealer-authorized methods.
Can one connector be live for some functions and planned for others?+
Yes. For example, lead creation may be live while activity read or appointment writeback remains in pilot. The matrix labels each capability separately.
How does Quantum handle a failed write?+
The write remains pending or retrying until confirmed, rejected, reconciled, or escalated. Quantum does not report success without destination confirmation.
Can a dealership revoke access?+
Yes. Every production connection must have a documented suspension and revocation process.
Related solutions across the platform.
Verified writeback.
Every call, text, and outcome signed and posted back to your CRM.
The operating layer.
One thin layer above your CRM, feed, and phone system, governed by design.
Governance you can hand to legal.
Roles, audit trail, retention, and consent, published in full.
Know the approved path before building the workflow.
Bring your CRM, DMS, IMS, communication providers, calendars, and lead sources. Quantum will map the available methods, permissions, capabilities, gaps, and first controlled connection.
Talk to salesExact connection. Exact authority. Exact current status.