AI-CHAT INFRASTRUCTURE FOR AUTO REPAIR
Turn repair intent into a request your shop can act on.
JackRelay is built to connect eligible ChatGPT discovery to a consented Get Quote flow, then route each request into the repair shop's configured workflow.
- Explicit customer consent
- Idempotent request creation
- No invented confirmation
Conversion path implemented and tested. Hosted ChatGPT launch and platform review are pending.
- 1Intent captured
- 2Eligible shop found
- 3Review and consent
- 4Request sent
- 5Shop inbox
ONE WORKFLOW. CLEAR STATES.
From the first question to shop follow-up.
Each capability has a narrow job. Select a view to see what the customer or repair shop receives at that point in the workflow.
A careful handoff from intent to request.
The customer sees the selected shop, reviews the repair details, and explicitly agrees before contact information is shared.
- Eligible service and shop context
- Structured vehicle and problem details
- A truthful request-sent outcome
BEFORE YOU SEND
Review your repair request
One queue for requests that need a human response.
Structured context arrives together, so the shop can review the vehicle, requested service, customer note, and current status without reconstructing the conversation.
- Request identity and source
- Customer-approved contact details
- Clear pending and resolved states
2019 Honda Civic · Jordan Lee
2021 Toyota RAV4 · Alex Morgan
2018 Subaru Outback · Sam Kim
Booking only when the shop's rules allow it.
Availability and booking are separate from quote-required work. A time can be offered only when the service mode, source quality, and shop configuration permit it.
- Canonical availability source
- Offering-specific booking mode
- No confirmation before a successful write
The appointment is confirmed only after the booking action succeeds.
Give every request an operational destination.
Create the shop record, add locations and services, then define how quotes, schedules, and confirmations should be handled.
- Business and location profile
- Service catalog and operating hours
- Quote and scheduling policies
- ✓Business profileName, contact, and ownership
- ✓LocationsAddress, territory, and hours
- ✓ServicesCatalog, duration, and mode
- 4Launch readinessReview and platform connection
AI-CHAT SURFACES
One repair workflow, adapted to the conversation.
JackRelay is designed around a canonical request lifecycle. Each AI surface still needs its own reviewed integration and launch path.
Designed first for eligible ChatGPT local-services discovery.
The conversion and MCP path are implemented and tested. Hosted launch remains subject to deployment, platform review, and production configuration.
A future adapter for the same canonical request states.
No Claude integration is represented as live. The planned model preserves the same consent, idempotency, and truthful-outcome rules.
Platform-specific presentation, consistent transaction semantics.
A Gemini surface would use the same repair intent, shop eligibility, and customer-consent boundaries after a supported integration exists.
Built to add surfaces without duplicating shop operations.
Future AI-chat support depends on official platform capabilities, reviewed distribution, and a verified production connection.
FOR REPAIR SHOPS
Set up once. Keep control at every step.
JackRelay gives the shop a direct operating surface first. External connections are added only when a supported, verified integration is available.
- 01Available now
Create your account
Use the shop signup path to create a secure JackRelay workspace.
- 02Available now
Build the shop record
Add business details, locations, services, hours, and intake policies.
- 03Product build
Work from the inbox
Review structured quote requests and keep the customer outcome explicit.
- 04Launch pending
Connect discovery
Publish only after production deployment and the relevant platform review.
FULFILLMENT PATHS
Start with JackRelay. Add verified connections when available.
The operating model does not depend on an unverified vendor integration. Shops can configure the native workflow, while future connectors remain explicit and capability-gated.
JackRelay inbox and configuration
Manage services, policies, requests, and outcomes in one canonical shop workspace.
- Structured request intake
- Quote-required service handling
- Clear operational status
Supported shop software
Connect only through an official adapter with known capabilities, permissions, and failure behavior.
- No fictional integrations
- Capability-aware routing
- Safe fallback to native handling
TRUST BY CONSTRUCTION
Consent before conversion. Clear outcomes after it.
The interface should make the real transaction state easier to understand, not make the product look further along than it is.
Explicit consent
Contact details are shared only after the customer reviews the request and agrees to the disclosure.
Idempotent writes
Stable request keys protect a retry from silently creating duplicate customer actions.
Truthful outcomes
A sent request is not presented as a confirmed price or appointment.
Protected identifiers
Public AI surfaces receive scoped references rather than private shop or vendor credentials.
FORWARD, WITH THE FACTS INTACT
Prepare your shop for AI-chat discovery.
Set up the operating layer now. Connect eligible discovery surfaces as each reviewed launch becomes available.