Knowledge > Products > WiseAI Realtor > Information Architecture
WiseAI Realtor — Information Architecture (v0)
Method: IA before layout. This organizes everything the system holds, how it groups, and what already exists — so the layout decision (bento / workflow rail / big-box) is made per screen archetype on top of a settled structure, not guessed. Sources: founder's inventory, the Codex design docs, and do-not-reinvent.md.
1. Product surfaces (top of the tree)
| Surface | Who | What |
|---|
| Public Website | Buyers/sellers | Per agent/team/brokerage marketing site + listings + guides + AI chat/voice CTAs. (Or skipped — see Decision #1.) |
| Agent Backend ("command center") | Solo REALTOR | The focus of this revamp. Daily work + marketing + AI + settings. |
| Team/Brokerage Backend | Team lead / broker | Superset of the agent backend + people, lead routing, multi-agent reporting. |
| Lead micro-surfaces | Leads | QR scan landing, public intake form, listing detail page, private review-feedback page. |
| AI layer (chat + voice) | Cross-cutting | Not a screen — runs across website, QR, phone; configured in the backend. |
Eight logical groups. Each row = a nav destination + its key sub-screens. (Solo agents see a trimmed set; team/brokerage unlocks more — Decision #2.)
A. Daily Work — the command-center core
| Destination | Sub-screens / contents |
|---|
| Dashboard | Overview: new/warm leads, calls, chats, QR scans, follow-ups due, AI-recommended next actions, top listings/content, language breakdown |
| Leads | Pipeline (kanban) + table; lead drawer (AI summary, intent, urgency, timeline, next action, consent); filters by source/status/language/listing/campaign/agent/date; assign/reassign |
| Conversations / Inbox | Unified chat + voice; transcript, AI summary, intent + language label, handoff action, follow-up draft, convert-to-lead/task |
| Tasks & Follow-ups | Reminder tasks (overdue leads), follow-up drafts, calendar of showings/callbacks |
B. Listings & Properties
| Destination | Sub-screens |
|---|
| Listings | Manual listings CRUD + DDF/MLS feed; map/filter; featured; status (active/pending/sold) |
| Listing detail/editor | Facts, gallery, description, map/community, compliance fields |
| Listing Studio | AI listing kit: MLS copy ×3 + social + email + open-house, fair-housing linter, "facts used" receipt |
C. Marketing & Content
| Destination | Sub-screens |
|---|
| Content Studio | WYSIWYG editor (left blocks / center canvas / right AI panel). Types: blog, newsletter, social post, buyer/seller guide, neighbourhood page, market update, open-house follow-up. AI: generate/rewrite/translate-adapt/SEO-GEO/compliance/CTA. Publish/schedule/export/send-newsletter/social-pack |
| Newsletters / Broadcasts | Compose + audience + consent + send (email via Resend / SMS via Telnyx) |
| Reviews & Testimonials | Reviews Engine (owner-pressed requests, CSV import, suppression, CASL footer, funnel); testimonials manager (rating + photo) feeding the website |
| QR Campaigns | Create QR (listing/open-house/feature-sheet/mailer/guide) → landing template → capture fields → download print assets; scan analytics |
D. Website
| Destination | Sub-screens |
|---|
| Website builder | Template family + brand kit (logo/colours/fonts/button/card/header/hero/listing-card/chat-CTA), page library, section library, draft→publish, desktop/mobile preview |
| Website mode | Hosted-by-us or bring-your-own (embed AI + feed leads only) — Decision #1 |
E. AI Agents
| Destination | Sub-screens |
|---|
| Chat Agent | Knowledge sources (profile, listings, neighbourhoods, guides, FAQs, policies, multilingual), conversation rules + guardrails, website placement, listing context, testing, analytics |
| Voice Agent | Lines (Premium main: EN/ES/FR + Community lines: PA/UR/MandarIn/HI), voices, scripts, routing, business hours, escalation, capture fields, call-summary format, transcripts, analytics |
| Multilingual config | Top languages per farm area; premium vs community-line framing; language routing |
F. Insights
| Destination | Sub-screens |
|---|
| Analytics & Attribution | Website traffic, listing views, lead conversion, QR scans, calls, chats, content + language performance, agent/team performance. Key reports: which listings/signs/languages/content create leads; which conversations need human follow-up |
G. Connect — Integrations / APIs / Connectors
| Destination | Sub-screens |
|---|
| Integrations | CRM (IXACT, Follow Up Boss, kvCORE/BoldTrail…), DDF/MLS (CREA), calendar (Cal.com/Google), email/SMS (Resend/Telnyx), Zapier/webhooks, API keys |
H. Manage — Admin / Settings / Team
| Destination | Sub-screens |
|---|
| Team & Brokerage (team/brokerage tiers) | Agents, agent profiles, lead routing, language routing, teams, offices, recruiting pages, reporting |
| Settings | Business profile, hours, branding, compliance/consent (CASL/PIPEDA/REALTOR trademark/AI disclaimers), notifications |
| Billing & Plan | Subscription, package add-ons, invoices |
| Account | Profile, security, API keys |
3. Core data entities & relationships
User ──< belongs to >── Team ──< belongs to >── Brokerage
│
├─ owns ─ Website ──< has >── Pages ──< has >── Sections ── Brand Kit
├─ owns ─ Listing ──< generates >── Lead
│ └─< target of >── QR Campaign ── Landing Page
├─ owns ─ Content item ──< rendered in >── language versions / channels
├─ owns ─ Voice line ── language / routing
└─ configures ─ Chat agent / Integrations
Lead ──< has >── Conversation(s) [chat | voice] ──< has >── Transcript + AI summary
Lead ── Contact ── consent status ── language preference ── source attribution
Contact ──< target of >── Review request ── feedback / suppression
Key shared tables already in place (do-not-reinvent.md): local_businesses (+ metadata.website draft/published), local_business_listings, local_business_leads, voice_* (prayer/callback/visitor — used by chat+voice), lead_events, campaign_members, articles (brand-partitioned), reviews tables, local_business_voice_lines.
4. Existing vs new (build map)
| Area | Status | Where |
|---|
| Public website + templates, listing detail, QR scan, guides | Exists | RealEstateSiteTemplate, src/app/s/[slug]/*, src/lib/real-estate/* |
| Leads inbox (chat+voice unified) | Exists | src/app/admin/[token]/components/InboxTab.tsx |
| Chat agent + Voice agent (multilingual) | Exists | api/chatbot/stream, voice-agent-livekit/verticals/real_estate/ |
| Content/website editor (draft/publish) + Listings manager | Exists | WebsiteEditor/, api/real-estate/site-content, /listings |
| Listing Studio, Reviews Engine, fair-housing linter | Exists | ListingStudio.tsx, reviews tables, fair-housing.ts |
| Analytics/attribution dashboard (realtor-framed) | Partial | demo-event analytics exist; realtor reporting view is new |
| DDF/MLS live feed | Built, inert | src/lib/real-estate/ddf/* (gated) |
| Content Studio (full WYSIWYG, multi-type, multilingual gen) | Partial→new | editor exists; blog/newsletter/social/guide generation per-language is greenfield |
| Integrations hub (CRM/Zapier/API keys) | Greenfield | — |
| Team/brokerage roles, routing, recruiting | Greenfield | RBAC exists (token+role); brokerage hierarchy + routing new |
| Unified realtor app shell (the revamp) | New | this project |
5. Decisions to LOCK before layout
- Website hosting model — DECIDED 2026-06-27 → (c) BOTH, as tiers. Offer hosted-by-us premium websites AND a bring-your-own-website mode (agent keeps their existing site — SellingToolz/RealtyNinja/etc. — and we provide backend + AI chat embed + voice line + content + leads only). Widens the market (many agents won't switch sites but will buy the AI front office; Team Beckett themselves run teambeckett.ca on SellingToolz). Implication for UX: "Website" is a pillar for hosted accounts but collapses to an "AI embed + connected site" module for BYO accounts — the backend (leads/AI/content/CRM) is identical for both.
- Account scope / progressive disclosure: one app shell where solo → team → brokerage unlocks extra groups (recommended), vs separate apps.
- Backend convergence: build a dedicated WiseAI Realtor app shell that REUSES existing data/APIs (recommended) vs extending the current
/business/[token] + /admin/[token] dashboards in place.
- Content MVP scope: founder named blogs + newsletters + testimonials; defer social packs / market updates / per-language generation to V1?
- Multilingual surfacing: language as a cross-cutting attribute (chips on leads/content/voice everywhere) + a small config screen — vs a dedicated top-level section.
- Analytics depth in MVP: the 5 "which X creates leads" reports vs a fuller BI view.
5b. Post-research feature additions (2026-06-27)
6-agent competitor research (competitive-analysis.md) confirmed the IA above and added a CRM spine we were light on. Folded into the nav (mostly group A "Daily Work" + a new Contacts area):
- Contacts with relationship memory (birthdays, anniversaries, family, mortgage, referral history) + Smart Lists (dynamic saved segments as nav) + unified timeline.
- AI Follow-Up Coach ("call these 5 today + why") — keep-in-touch engine.
- Pipeline (Kanban) + lead scoring + speed-to-lead / "unactioned leads" KPI.
- Action Plans + drip campaign library (buyer/seller/FSBO/expired/past-client/investor/newcomer).
- Active Business Hub (deals: key dates, offers, docs, commissions, activity plans).
- AI text/SMS ISA lane (alongside chat + voice) + autopilot/co-pilot mode switch.
- Direct Canadian board feeds + VOW/sold data (not DDF-only) under Listings — table stakes.
- Integrations hub incl. 2-way Follow Up Boss + concierge onboarding (productized).
Design direction for all of the above is locked in design-direction.md (Workflow-Rail shell + per-archetype layouts + navy/teal/gold system).
5c. Decision — Website lives IN the unified dashboard (2026-06-27)
DECIDED: Pro Website management is a nav pillar inside the one backend, not a separate app. The website is a lead/content surface, so it must live where Leads/Inbox/Content/CRM live (separating it recreates tool-sprawl). Per the "both tiers" decision: for hosted accounts "Website" is a full pillar (pages, sections, brand kit, templates, SEO, domain, area guides); for bring-your-own accounts the same slot collapses to a lighter "Connected Site / AI Embed" module (widget embed + QR/landing routing + lead sync). The visual editor is a launched full-screen focus mode (exits back to the dashboard) — reusing the existing WebsiteEditor. Nav gains a "Website" item between Listings and Content Studio.
6. Next step (after IA sign-off)
Lock Decisions #1–#6, then map each screen archetype to a layout pattern — they differ by screen:
- Dashboard → bento command center
- Leads / Listings → table + drawer (workflow rail on the drawer)
- Content Studio → 3-pane editor
- Settings / Integrations → big-box module grid
- Conversation Center → inbox split-view
Then build standalone HTML mockups, backend command center first (per founder), in C:\dev\realtor-mockups\.