Here’s a reply you can copy–paste straight back to the Replit agent:

⸻

Thanks – this is a substantial UI rebuild, so let’s do it with a clear phased plan.

Overall priority order:
	1.	D: Navigation shell + T-Card component (foundation)
	2.	A: Conversations Inbox + Conversation Detail
	3.	B: Appointments Diary (Today + Calendar views with capacity tracking)
	4.	C: Data & Campaigns (upload flows + campaign creation wizard)

Phase 1 – Foundations (D)

Goal: Get the core layout and shared components in place.
	•	Build the navigation shell with the 6 items:
	•	Dashboard
	•	Conversations
	•	Campaign customers
	•	Appointments
	•	Data & campaigns
	•	(Conversation detail as its own route, reached from Conversations)
	•	Implement the T-Card component as a reusable element that will appear:
	•	In Conversation Detail (left panel / top on mobile)
	•	Inline in Campaign customers when a row is expanded
	•	T-Card should include the structure for:
	•	Customer + vehicle + reg
	•	Equity, equity trend, payments, HOT flag
	•	Appointments (past + upcoming)
	•	Tabs: Overview / Notes / Full chat history
(Data can be mocked/partial at first – focus on layout and wiring.)

Phase 2 – Core manager workflow (A)

Goal: Make the escalation + reply workflow fully usable.
	•	Conversations Inbox
	•	Paginated (25 per page), default “Active & recent” filter
	•	Columns as per spec: customer, vehicle/reg, stage, campaign, conversation status, appointment status, HOT flag, last message snippet, last message time
	•	Conversation Detail
	•	Top status banner (Booked / Needs manager review / Awaiting customer / Paused / Do not contact)
	•	Header strip with key info + HOT flag
	•	Message timeline (LIA / Customer / Manager messages + system markers)
	•	Manager reply box:
	•	Send as manager
	•	Send & let LIA continue / Send & pause LIA
	•	Mark escalation as resolved when applicable
	•	T-Card visible by default on this screen

Once Phases 1 & 2 are done, we’ll have the core daily workflow working (manager can see conversations, handle escalations, and reply with context). After that, move on to:
	•	Phase 3 – Appointments Diary (B) – Today + Calendar views with capacity rules
	•	Phase 4 – Data & Campaigns (C) – full-book upload + campaign creation wizard, using existing Supabase schema and keeping all behaviour logic in the state machine.

Please start with Phase 1 (D) and Phase 2 (A) as the first milestone.