All work

Cox Automotive · Staff UX Designer · FY26 · In Progress

Dealer Chat: Communication Design for a Dealer-First Ecosystem

Dealership staff were managing deals over personal text messages. Cox Automotive's Command Center had no native communication layer — no teams, no channels, no shared context for the workflows that matter most. I helped define how dealership employees communicate internally in an ecosystem without any of the structures enterprise collaboration tools assume.

My role
Staff UX Designer: product strategy, membership model, messaging UX
Scope
45,000+ dealerships · membership model · permissions & visibility · MVP feature set
Cox Automotive Dealer Chat, internal messaging and group communication for dealership staff
6.25 / 7
Communication effectiveness score
4.3 → 5.8
Satisfaction improvement (7-pt scale)
8 features
Core requirements defined in 4 weeks

The problem

Dealer Chat wasn't a feature request — it was a structural gap. Cox Automotive's Command Center was a platform without a communication layer, and dealership staff had filled that void with personal phones, group texts, and whatever workaround fit the moment. Deals were being managed through text threads with no shared context, no deal-level history, and no visibility for the people who needed it.

The problem wasn't a messaging app — it was that the ecosystem had no model for how internal communication should work. Dealers don't have teams. They don't have channels. The mental models that enterprise collaboration tools are built on don't apply. Building this required working backwards from how dealerships actually function, not forward from Slack.

"The question wasn't what to build. It was how communication should work in an environment that doesn't have the structures we usually design around."


Research & discovery

The research question: how do dealership employees actually communicate to get deals done, and what does that reveal about how a purpose-built tool should work?

Key findings

  1. Communication was deal-centric, not person-centric. Dealership staff didn't think about messaging as a conversation between people — they thought about it as coordination around a deal, a customer, or a task. The mental model for a Dealer Chat inbox was fundamentally different from any consumer or enterprise messaging product.
  2. The membership model was the hardest design problem. Traditional messaging apps assume persistent membership — teams and channels that exist outside of any specific workflow. Dealerships don't work that way. Who is in a conversation, and who has visibility into it, depends on role, location, deal stage, and time of day. Defining the membership model was more consequential than designing any screen.
  3. Subscription reduction was a real constraint. Cox Automotive's ecosystem already included third-party messaging solutions some dealers were paying for. Any new communication feature had to justify the switch — not just be good, but be worth the cost and behavior change.
  4. Permissions and visibility were safety-critical. In a regulated industry, who sees what in a communication tool isn't a UX preference — it's a compliance question. The permission model had to hold up under audit, not just under normal use.

Design process

Eight core feature requirements defined in four weeks, from a greenfield brief with no direct precedent. The design process was more product strategy than UI — the decisions that mattered were structural, not visual.

Key design decisions


Outcomes & impact

This work is in progress. The core feature set is defined; the product is in active development across the 45,000+ dealership platform.

This work is in-flight

Dealer Chat is an active product. This case study reflects the research, product strategy, and design framework work completed through the MVP definition phase.