Preparing Dealer Brand App content
Preparing Dealer Brand App content
Preparing Dealer Brand App content
On this pack an opportunity is a lead to a rooftop or to the dealer group. The shopper and that team's members share one messenger thread. The public browse feed is not how a store works a test drive.
This page is the dealer-pack overlay of the opportunities article. Matcher, auto-fill, and the generic offer/request types still exist on Layer 1. The types below are the ones this pack adds and the clone enables.
Creating a lead stores metadata.conversationId and the shopper is sent to /messages?c=. Chat about the same vehicle reuses the open inquiry. The product agent is not that thread.
| Kind | Who starts it | Desk meaning |
|---|---|---|
vehicle_inquiry | Chat with seller, or check availability | One open thread per shopper and vehicle |
test_drive | Card dialog or vehicle page | Date and time of day |
trade_in | Vehicle page or sell/trade | VIN and miles, optional asking price |
finance_inquiry | Ask about financing | A question. No SSN, no credit pull |
service_appointment | /service | Rooftop, date, and a note |
product_offer | Seller offer, other products | Title, category, optional SKU and price |
partner_application | How I shop, dealer or supplier | One open application per person. Not a staff role |
Enabled on the DealerDirect clone in ring-config.json → opportunities.enabledTypes, together with offer, request, and job.
Stages on the desk: new, contacted, appointment_set, showed, sold, lost.
A shopper taps Chat, Test drive, Value my trade, Ask about financing, Book service, or sends an offer. They must be signed in. They land in Messages with your team already on the thread. You work the row at /dealer/leads.
Sold and lost inquiries do not reopen. A new chat after that starts a new lead. A second chat while the inquiry is still open returns the same thread.
The buttons live on the inventory card and the vehicle page.
Members of that rooftop, and members of the parent group, can see the lead.
Do not treat Ask about financing as a pre-approval. The copy tells the shopper there is no credit pull and no SSN. Do not add those fields.
No. The agent uses agentChat=1 and conversation type product. Dealer leads use type opportunity and the rooftop team.
No. The API returns 401. The button sends them to login and back to the vehicle, service page, or sell page.
It still runs inside Layer 1 createOpportunity for types that go through that service. This page documents the dealer kinds and the thread handoff. Do not quote matcher accuracy percentages.
The rooftop entity had no members in memberRoles. Add staff on the entity. The lead row still exists.
On this pack an opportunity is a lead to a rooftop or to the dealer group. The shopper and that team's members share one messenger thread. The public browse feed is not how a store works a test drive.
This page is the dealer-pack overlay of the opportunities article. Matcher, auto-fill, and the generic offer/request types still exist on Layer 1. The types below are the ones this pack adds and the clone enables.
Creating a lead stores metadata.conversationId and the shopper is sent to /messages?c=. Chat about the same vehicle reuses the open inquiry. The product agent is not that thread.
| Kind | Who starts it | Desk meaning |
|---|---|---|
vehicle_inquiry | Chat with seller, or check availability | One open thread per shopper and vehicle |
test_drive | Card dialog or vehicle page | Date and time of day |
trade_in | Vehicle page or sell/trade | VIN and miles, optional asking price |
finance_inquiry | Ask about financing | A question. No SSN, no credit pull |
service_appointment | /service | Rooftop, date, and a note |
product_offer | Seller offer, other products | Title, category, optional SKU and price |
partner_application | How I shop, dealer or supplier | One open application per person. Not a staff role |
Enabled on the DealerDirect clone in ring-config.json → opportunities.enabledTypes, together with offer, request, and job.
Stages on the desk: new, contacted, appointment_set, showed, sold, lost.
A shopper taps Chat, Test drive, Value my trade, Ask about financing, Book service, or sends an offer. They must be signed in. They land in Messages with your team already on the thread. You work the row at /dealer/leads.
Sold and lost inquiries do not reopen. A new chat after that starts a new lead. A second chat while the inquiry is still open returns the same thread.
The buttons live on the inventory card and the vehicle page.
Members of that rooftop, and members of the parent group, can see the lead.
Do not treat Ask about financing as a pre-approval. The copy tells the shopper there is no credit pull and no SSN. Do not add those fields.
No. The agent uses agentChat=1 and conversation type product. Dealer leads use type opportunity and the rooftop team.
No. The API returns 401. The button sends them to login and back to the vehicle, service page, or sell page.
It still runs inside Layer 1 createOpportunity for types that go through that service. This page documents the dealer kinds and the thread handoff. Do not quote matcher accuracy percentages.
The rooftop entity had no members in memberRoles. Add staff on the entity. The lead row still exists.
On this pack an opportunity is a lead to a rooftop or to the dealer group. The shopper and that team's members share one messenger thread. The public browse feed is not how a store works a test drive.
This page is the dealer-pack overlay of the opportunities article. Matcher, auto-fill, and the generic offer/request types still exist on Layer 1. The types below are the ones this pack adds and the clone enables.
Creating a lead stores metadata.conversationId and the shopper is sent to /messages?c=. Chat about the same vehicle reuses the open inquiry. The product agent is not that thread.
| Kind | Who starts it | Desk meaning |
|---|---|---|
vehicle_inquiry | Chat with seller, or check availability | One open thread per shopper and vehicle |
test_drive | Card dialog or vehicle page | Date and time of day |
trade_in | Vehicle page or sell/trade | VIN and miles, optional asking price |
finance_inquiry | Ask about financing | A question. No SSN, no credit pull |
service_appointment | /service | Rooftop, date, and a note |
product_offer | Seller offer, other products | Title, category, optional SKU and price |
partner_application | How I shop, dealer or supplier | One open application per person. Not a staff role |
Enabled on the DealerDirect clone in ring-config.json → opportunities.enabledTypes, together with offer, request, and job.
Stages on the desk: new, contacted, appointment_set, showed, sold, lost.
A shopper taps Chat, Test drive, Value my trade, Ask about financing, Book service, or sends an offer. They must be signed in. They land in Messages with your team already on the thread. You work the row at /dealer/leads.
Sold and lost inquiries do not reopen. A new chat after that starts a new lead. A second chat while the inquiry is still open returns the same thread.
The buttons live on the inventory card and the vehicle page.
Members of that rooftop, and members of the parent group, can see the lead.
Do not treat Ask about financing as a pre-approval. The copy tells the shopper there is no credit pull and no SSN. Do not add those fields.
No. The agent uses agentChat=1 and conversation type product. Dealer leads use type opportunity and the rooftop team.
No. The API returns 401. The button sends them to login and back to the vehicle, service page, or sell page.
It still runs inside Layer 1 createOpportunity for types that go through that service. This page documents the dealer kinds and the thread handoff. Do not quote matcher accuracy percentages.
The rooftop entity had no members in memberRoles. Add staff on the entity. The lead row still exists.
