Back to Catalog

workflow

Dealership OS

Dealership OS is the public product wrapper for the existing tenant-scoped Dealership Vertical Pack on the StackFast Conversation Continuity MCP. It reuses one relationship root, one opportunity authority, one consent authority, and one governance store.

Host and data posture

Where this product is meant to live.

Sell the canonical evaluator as a governed dealership operating capability; never duplicate the MCP server, relationship root, opportunity authority, or governance store.

Commercial shape

Operator-console system

Data posture

Tenant brain required

Approval posture

Operator action

Best demo

ChatGPT / OpenClaw hosted

Best daily use

OpenClaw hostedStackFast UIDirect MCP/API

Who it is for

Dealership owners, general managers, sales managers, BDC leaders, salespeople, dealer groups, approved implementation partners, and entitled agents that need governed opportunity discipline without installing a second CRM, lead engine, or autonomous outbound worker.

Problem it solves

Opportunities fall through cracks when ownership is vague, the customer's unresolved need is not visible, handoffs break, manager reconciliation ends with activity counts instead of decisions, or contact authority is uncertain. Dealership OS makes leak points, holds, owners, next actions, coaching steps, and lawful disposition recommendations explicit.

Activation model

Inquiry and assisted tenant setup. Discovery is public; execution requires an authenticated Dealership OS entitlement and tenant binding. No checkout price is published because pricing has not been ratified.

Composition decisions

What is packaged here, and what is not.

These notes prevent agents from splitting proof lanes into duplicate Store products before the repo has a first-class product record, entitlement, and receipt-backed runtime.

Dealership lead follow-up evaluation

first class product

The capability has a distinct buyer job, entitlement, manual, and customer connector while reusing the canonical Conversation Continuity server.

Agent guidance
Discover and sell Dealership OS; call the one canonical evaluator. Do not expose internal worker, governance-store, framework, or test names as separate products.

Governance registration and STOP recording

composed capability

These are first-party governance operations, not customer Store tools.

Agent guidance
Never advertise or grant these modes through ordinary Dealership OS entitlement.

Proof and source paths

  • The canonical lead evaluator and read-only sales-floor advisor are registered in the production Conversation Continuity Dealership Vertical Pack
  • Synthetic acceptance is fixture-only and performs no outbound action
  • Live evaluation is fail-closed on tenant, consent, STOP, sender, identity, quiet-hours, pacing, assignment, and schema boundaries
  • MCP calls use the shared auth, entitlement, audit, MASK-safe output, metering, and idempotency rails
  • Operator-only governance writes remain outside customer entitlement

Repo evidence

  • docs/wiki-manuals/dealership-os-mcp-manual.md
  • lib/conversation-continuity/vertical-packs.ts
  • lib/conversation-continuity/dealership-lead-worker-mcp.ts
  • lib/conversation-continuity/dealership-sales-advisor.ts
  • app/api/mcp/route.ts
  • lib/tool-registry/callable-mcp-tools.ts

Capabilities

check lead follow up

mcp

Check whether a lead follow-up may be sent, held, or escalated before customer contact.

Agent use
Call stackfast.conversation_continuity.dealership_lead_worker.evaluate with mode=evaluate for a tenant-bound lead or mode=synthetic_acceptance with fixture_id=synthetic_internet_lead_v1 for the no-customer-data walkthrough. Honor outbound_performed:false, send_allowed, hold reasons, manager exceptions, action cards, and receipt ids. Never claim a send occurred.

sales floor brief

mcp

Get a public-safe dealership sales-floor coaching brief for opportunity leaks, ownership, manager reconciliation, customer connection, presentations, or disposition.

Agent use
Call stackfast.conversation_continuity.dealership_sales_advisor.brief with one bounded workflow and a transient operator situation. Return findings, an ordered structured_plan, next_actions, a human_action_card, public citations, advisory_receipt_id, and every no-outbound/no-CRM/no-inventory/no-deal-desk/no-opportunity-authority-write invariant. Use Human Connection and Backward Selling only as customer-safe outcome structure; never expose protected method bodies, assess a person, grant a credential, or write a disposition.

Connector proof

Catalog is not the same as customer-ready.

This product only becomes market-ready after a real host mounts the entitled tools, a safe call succeeds, metering records the event, and a customer-safe receipt exists. Until then, the page shows the strongest proven status without rounding up.

Catalog

Runtime registry and product manifest are present.

Entitlement

Execution requires OAuth or storefront entitlement scope.

Callable

2 tool(s) declared with no missing V1 tools.

Metering

MCP calls are routed through the metering receipt path.

Customer validated

Pending fresh host-surface call receipt.

Runtime registry status

Primary registry

stackfast.ai/api/mcp

Status

live reader mcp

Install gate

Public discovery is live. Customer execution requires a Dealership OS storefront entitlement, tenant binding, connector authorization, and policy setup; pricing and checkout remain inquiry-only.

Callable tools

  • stackfast.conversation_continuity.dealership_lead_worker.evaluate
  • stackfast.conversation_continuity.dealership_sales_advisor.brief

Missing or gated tools

No missing tools declared for the current V1 boundary.

  • This is a product facade over the existing Conversation Continuity MCP and Dealership Vertical Pack, not a second MCP server.
  • ChatGPT uses the safe connector name dealership_check_lead_follow_up, which resolves to the one canonical tool id.
  • ChatGPT uses dealership_sales_floor_brief for the one canonical read-only advisor tool; its six workflows share one schema and one metering contract.
  • The advisor uses public-safe Dealership OS guidance, returns no raw Brain excerpts or protected method bodies, and performs no outbound or authority write.
  • Customer modes are evaluate and synthetic_acceptance. register_governance and record_stop remain operator-only.
  • Every authenticated call and denial enters the shared metering rail; results expose opaque references only and outbound_performed is always false.
  • Dealership Sales Leadership Training is not part of this MCP product and remains behind the WO-11 qualified-human gate.

Install and activate

Connect this product through the StackFast MCP endpoint. Discovery metadata is public; execution uses OAuth and storefront entitlement checks.

MCP URL

https://stackfast.ai/api/mcp

Agent subscription

This product remains request-scope until its checkout, fulfillment, and public-name gates are complete.

Client snippets

ChatGPT

Add StackFast as a custom MCP connector, then approve OAuth when prompted.

Claude

Connect a remote MCP server using the StackFast MCP URL and a tenant-scoped token or OAuth flow.

Cursor

Register StackFast as a remote MCP server for project-scoped tool use.

Grok

Add StackFast as a custom MCP connector using the StackFast MCP URL and customer entitlement auth.

Product: Dealership OS
Product API: https://stackfast.ai/api/store/products/dealership-os
Pricing API: https://stackfast.ai/api/store/pricing/dealership-os
Manifest API: https://stackfast.ai/api/store/manifests/dealership-os
MCP URL: https://stackfast.ai/api/mcp
Auth: oauth_reader_or_storefront_entitlement
Checkout session API: https://stackfast.ai/api/store/checkout/session
Plans:
- Dealership OS assisted install: Request scope; checkout_ready=false; checkout_url=request_scope
Agent activation:
- Read this product manifest and pricing API.
- If a plan has checkout_ready=true, open its checkout_url or POST product_slug, plan_slug, and customer_email to the checkout session API.
- After Stripe payment, the signed webhook grants storefront_entitlements for the buyer email/account.
- Connect the LLM client to the MCP URL and approve OAuth so tools/list reflects the licensed reader surface.
- Call only tools exposed for that entitlement; unentitled execution must fail closed.

Agent-readable queries

Dealership OS MCPcheck whether a dealership lead follow-up may be sentdealership consent STOP quiet hours pacing checkdealer lead follow-up hold and next actionsample dealership lead walkthroughdealership opportunities falling through cracksdealership opportunity ownership and next actionsdaily dealership manager sales-floor reconciliationHuman Connection dealership customer situationBackward Selling dealership presentation structuredealership opportunity disposition recommendation
What's on your mind?

Ask anything. Your thought enters the reasoning engine.

Enter to send · Shift+Enter for newline · Mic to speak