MotorOS CRM
MotorOS CRM is built for automotive retail — not retrofitted from generic sales software. Track buyers against inventory, ingest site leads automatically, and give your agency a separate Platform CRM for onboarding dealers without mixing pipelines.
New lead
Jamie Rivera
2024 F-150 XLT
Alex Kim
Booki · site form
Qualified
Morgan Lee
2023 RAV4 LE
Appointment
Test-drive Sat
10:30 AM · lot
Drag cards between stages · tap to open contact
Agencies sell and onboard dealers in Platform CRM. Each rooftop runs retail leads in Dealer CRM. APIs enforce org boundaries so client contacts never leak across tenants.
Rooftops & dealer groups
Retail pipeline for test-drives, trade-ins, and buyers — every lead can link to a unit in your native inventory.
Agencies & multi-dealer operators
Agency sales pipeline for winning and onboarding dealership clients — completely separate from each dealer’s inventory CRM.
MotorOS CRM mirrors how dealers actually work: capture, qualify against inventory, book the appointment, and close — without exporting to spreadsheets.
A buyer submits your site form, Booki flow, or a BDC rep enters a walk-in — the lead lands in Dealer CRM with source metadata.
Attach the F-150 they asked about, move the card to Qualified, and add notes from the first phone call.
Book a test-drive in CRM or pull in a booking-engine confirmation — both show under the pipeline.
Mark Sold, update inventory status, and the same unit drops off feeds automatically while the buyer record stays for future service.
Capture inquiries where they happen — your website, booking flows, or the desk — and work them in a pipeline designed for automotive follow-up.
Drag contacts across stages on desktop or touch devices. Dealer and Platform CRM each get purpose-built stage names — not one-size-fits-all columns.
Name, email, phone, company, type, stage, and sales notes in one modal. Edit inline or open the full form without leaving the board.
Every ingested lead stores its source — Booki, dealer site API, or manual entry — so you know which channel drove the conversation.
Bearer-authenticated `/api/crm/ingest` creates dealer CRM contacts from your public site or Booki tenant, optionally linked to a vehicle ID.
MotorOS inventory is the source of truth. CRM leads reference the same vehicles that power your website, feeds, and syndication.
Attach a stock unit when creating or editing a lead. Pipeline cards show year/make/model and stock number at a glance.
Ingest API verifies the vehicle belongs to the dealer org before linking — no cross-dealer or stale ID mistakes.
From Dealer CRM, jump straight to Inventory to confirm pricing, photos, and availability while on a call.
The same unit on a lead is the one syndicated to Google Vehicle Ads, Facebook Marketplace, and custom CSV/XML feeds.
Keep test-drives and onboarding calls visible next to the pipeline — not buried in a separate calendar tab.
Schedule title, location, and time on Platform CRM prospects. Dealer CRM shows upcoming test-drives and meetings in a dedicated panel.
When the AUTO booking API is connected, confirmed appointments surface alongside CRM-native entries on the dealer pipeline page.
Agency staff create onboarding appointments tied to Platform CRM prospects — context stays with the deal.
See booking-engine and manually entered appointments in one chronological list under the pipeline board.
CRM sits beside Marketing, Content Studio, and Meta tools so follow-up and campaigns share the same dealer context.
Plan campaigns, attach media, track todos, and schedule organic social posts — adjacent to CRM in the Growth section of the portal.
Connect Meta once, compose posts, and publish to Facebook and Instagram without exporting lead lists to third-party schedulers.
Visual calendar for scheduled social posts tied to campaigns and projects — keep retail events aligned with lead-gen pushes.
Database schema supports per-contact email, SMS, and call history — UI surfacing is on the roadmap.
Pull leads in and push context out — Google, feeds, booking, and your owned website all connect to the same CRM records.
Booki tenants forward form submissions to MotorOS ingest — name, email, phone, and message land as a sourced dealer lead.
OAuth connections for Analytics, Search Console, Google Ads, and Business Profile — traffic and conversion context beside CRM workflows.
Import and export CSV/XML via HTTPS, FTP, or SFTP. Leads reference the same stock records feeds keep in sync.
Dealer sites built in MotorOS can post leads through the ingest API with optional vehicle context from the VDP.
Lot staff and BDC reps stay in MotorOS from the lane to the desk — especially with the Hardware tablet bundle.
Drag-and-drop pipeline uses touch sensors — reps can move leads on a tablet during a walk-around without a mouse.
Pre-provisioned Apple or Android tablets capture vehicle photos on-site and upload to inventory records your CRM references.
Central asset folders, tags, and storage quotas — attach campaign or lot photos that support both marketing and sales follow-up.
Generate and edit listing media in-portal so the unit on a lead always has fresh gallery content.
When a lead becomes a service issue — or inventory needs agency help — tickets carry vehicle and asset context into support.
Open a support request from inventory detail with stock, VIN, and page context pre-filled.
Attach photos and files from the asset library when filing tickets — BDC and service share the same media.
Ticket list shows SLA status, priority, and type (support, bug, feature, question) for dealer and agency queues.
Agency admins filter support requests across client orgs while dealers see only their own tickets.
Pipeline counts are just the start — dashboard growth scores and recommendations connect CRM activity to broader dealer performance.
Live lead and prospect counts on CRM pages — know pipeline volume before opening a single card.
Recent portal actions across inventory, projects, and tickets give managers situational awareness alongside CRM work.
Website health, SEO, accessibility, and overall growth scores calculated from portal activity and site audits.
Actionable recommendations generated from your connected analytics and site data — prioritize fixes that affect lead flow.
Multi-dealer operators get org switching, isolated client CRM, billing, and internal automation without exposing dealer retail data.
Agency staff view-as a dealer to open that rooftop’s inventory CRM — Platform CRM stays in agency admin mode.
Manage dealer client orgs, profiles, and onboarding from the agency Clients hub linked to Platform CRM stages.
API layer rejects cross-org CRM access — client contacts always stay in the client’s own org.
Agency-internal workflow builder with templates for operational tasks — separate from dealer retail CRM automation.
Track agency hours, send invoices, and route approvals from the same portal that hosts Platform CRM.
Upload transcripts for summaries, action items, and follow-up ticket creation — useful for onboarding calls logged in Platform CRM.
Horizontal CRMs can track contacts — but they were not built around stock numbers, VDP leads, and agency-managed dealer groups.
| Capability | Generic CRM | MotorOS CRM |
|---|---|---|
| Vehicle context | Custom fields or manual notes for “interested unit.” | Native inventory picker — year, make, model, stock # on every card. |
| Lead ingestion | Zapier glue or inbox forwarding. | First-party ingest API with org scoping and optional vehicle ID validation. |
| Agency + dealer | Separate products or messy multi-tenant hacks. | Platform CRM for agency sales; Dealer CRM per rooftop — hard-separated. |
| Adjacent stack | CRM bolted onto unrelated DMS or website vendor. | Website, inventory, feeds, Google, Meta, and CRM in one portal. |
Placeholder testimonials — replace with approved customer quotes when available.
“We stopped losing site leads in marketplace inboxes. Everything from the VDP form hits Dealer CRM with the unit attached.”
“Platform CRM finally separates our agency pipeline from each client’s retail leads. Onboarding calls stay tied to the prospect.”
Book a walkthrough of Dealer CRM and Platform CRM, or sign in if your portal is already live.