Buyer & Vendor Dashboards

As of v0.1.39, myProp provides dedicated self-service dashboard views for sales buyers and property vendors. Both dashboards connect directly to the AgentOS API via existing tRPC routers and follow the same interaction patterns as the tenant and landlord portals.

Buyer Dashboard

Route: /:company/accounts/buyer/:buyerId

The buyer dashboard gives purchasers real-time visibility into their viewings, offers, purchase profile, and available properties — all without needing to contact their agent.

Tabs

Overview

Displays a summary of the buyer's current activity as KPI cards:

Metric	Description
Total Viewings	All viewings, with upcoming and completed counts
Upcoming Viewings	Scheduled viewings not yet attended
Total Offers	All offers, with active and accepted breakdown
Active Offers	Offers awaiting an agent or vendor response
Accepted Offers	Offers that have been agreed
Property Alerts	Whether the buyer has active property alert notifications

Purchase Situation

Shows the buyer's full purchase profile:

Buyer Status — First-time buyer, cash buyer, mortgage Agreement in Principle (AIP) status, and chain position.
Solicitor Details — Assigned solicitor contact information.
Property Preferences — Target areas, property types, and bedroom requirements.

Viewings

Paginated list of all viewings with status filtering.
Each row shows: date/time, property address, agent information, viewing status badge, and a feedback indicator.

Offers

Paginated list of all submitted offers with status filtering.
Each row shows: offer amount, property, submission date, status badge, conditions, and any agent response notes.

Properties

Grid of currently advertised sales properties from the agency.
Each card shows: property image, address, asking price, bedrooms, bathrooms, receptions, property type, and a description snippet.

Vendor Dashboard

Route: /:company/accounts/vendor/:vendorId

The vendor dashboard gives property sellers visibility into their sales instructions, received offers, and viewing activity.

Tabs

Overview

Displays a portfolio-level summary as KPI cards:

Metric	Description
Total Instructions	All sales instructions (active + completed)
Active Instructions	Instructions currently on the market
Completed Instructions	Instructions that have exchanged or completed
Total Viewings	All viewings across all instructions
Total Offers	All offers received across all instructions
Highest Offer	The highest single offer amount received
Average Days on Market	Mean time instructions have been listed

Instructions

Paginated, filterable list of all sales instructions.
Click any instruction to expand an inline detail view showing:
- Property image and address
- Bedrooms, bathrooms, receptions, and property type
- Key dates (listed date, agreed date, completion date)
- Marketing status
- Full description
- Feedback summary

Offers

Select an instruction from a dropdown to view its associated offers.
Each offer shows: buyer name, offer amount, date submitted, status badge, and any conditions.

Viewings

Select an instruction from a dropdown to view its associated viewings.
Each viewing shows: buyer name, date/time, viewing status, interest level, star rating, and feedback comments.

Shared Behaviour

Both dashboards implement the following consistent patterns:

Responsive navigation — Sidebar on desktop, dropdown menu on mobile.
Service availability check — Verifies AgentOS API availability before attempting to load data.
Back navigation — A back-to-accounts link is always present.
Loading states — Animated skeleton placeholders are shown while data is fetching.
Error handling — Error banners with a Try Again retry button are shown on API failures.
Empty states — Illustrated empty state messages are shown when no data is available for a section.
Status badges — Colour-coded status indicators (amber for pending/upcoming, green for accepted/completed, red for rejected/cancelled).

Technical Details

Detail	Value
Buyer route	`/:company/accounts/buyer/:buyerId`
Vendor route	`/:company/accounts/vendor/:vendorId`
Data layer	Existing tRPC routers (`buyer.`, `vendor.`)
API	AgentOS (letmc.com)
Backend changes	None required
New files	6 (page route, loading skeleton, client component — per dashboard)