Where did this come from?
The inquiry keeps the project, page, source, and visitor journey attached instead of arriving as another context-free email.
Behind the scenes
What happens after someone requests information?
The form is only the beginning. The important part is what happens next: the inquiry is captured, the right person owns it, follow-up is visible, and leadership can see whether the launch is staying on track.
Who should respond?
Journey context can become a short insight and a response draft, so the agent starts from the buyer's actual behavior.
Is follow-up happening?
Project, listing, community, and lead-type rules point each inquiry to the right agent or team, with broker override when needed.
Inquiry flow
One request becomes an organized follow-up path.
Chapters 7-9
The public inquiry becomes a private team workflow.
This part of the walkthrough shows what happens after the buyer raises a hand: ownership, context, follow-up, and the broker view.
See what the team needs after an inquiry comes in.
Review leads, routing, ownership, reporting, and agent context.
Make follow-up visible before it slips.
The next five minutes
Follow one inquiry the way your team would talk about it.
Someone registered. What did they see first? Who owns the call? Is the lead stale? Does the agent need a draft? The Hub exists to make those questions visible before they become follow-up gaps.
Start where the buyer came from
Review the public community path first so the inquiry has context before anyone opens the private team view.
Make the owner obvious
The team should see who owns the next step, why that owner makes sense, and whether a broker needs to override the route.
Give the agent enough to respond
The agent should know what the buyer viewed, what they requested, and what message would feel relevant instead of generic.
Keep leadership out of the dark
The broker should be able to see status, stale follow-up, assignment history, and CRM/export readiness without chasing updates.
What usually gets unclear
The questions your team should not have to chase.
- Where the buyer came from
- What the buyer looked at before asking for help
- Who owns the next step
- Which leads are new, stale, assigned, or high priority
- Where manual override is needed
- What the assigned agent sees
- What the broker can report
- What should move to CRM or export next
Who it helps
Different people ask different questions after the same inquiry.
The buyer wants help. The agent wants context. The broker wants accountability. The builder wants visibility. The Hub keeps those questions connected.
Broker / admin
You stop asking, "Did anyone follow up?"
- See every new inquiry, assigned owner, lead status, priority, and follow-up gap.
- Review project routing, Smart Lists, export readiness, and reporting without asking agents for updates.
- Track launch health for one community first, then expand the same pattern across more campaigns.
Agent
Agents stop guessing why someone reached out.
- Open a role-based portal with assigned leads, visitor journey context, notes, and next actions.
- Use AI-drafted response language as a starting point while keeping the agent in control of the message.
- Work buyer, seller, listing, event, and registration leads without seeing brokerage-wide settings.
Client / consumer
Buyers feel like someone understood the request.
- Browse a polished community, listing, event, or agent page that feels specific instead of generic.
- Submit a simple form while AIRES preserves the context of what they viewed before reaching out.
- Get routed to the right person faster because the Hub knows the project, source, and likely intent.
Private data stays private
Send the public story first. Show the team workspace intentionally.
- Public pages are safe to send as a first link.
- Protected Hub screens are best screen-shared live first so lead data, roles, and routing make sense.
- Direct Hub access should be created intentionally with role-specific broker, admin, or agent accounts.
- The first launch can start with CSV/export proof, then move toward CRM/webhook/API sync as requirements are confirmed.
When someone asks to see the proof
The private team view shows what happened after the form.
The public website stays polished and buyer-focused. The private team view gives the brokerage the routing, assignment, and follow-up controls that make the site useful after the form is submitted.
Zero-dropped-lead context
AI Insight: Buyer reviewed Oak Hill listing content before submitting. Prioritize a specific, property-aware follow-up.
Traditional forms say someone wants information. Lead Hub shows what they cared about before they asked.
Inbox
See every lead with source context and next action controls.
Filter by status, priority, assigned agent, project, or search term, then assign, update status, export, or draft a response.
Project routing
Route listings and communities to the right owner.
Use project rules for featured listings, neighborhoods, buyer inquiries, seller requests, and manual overrides when a lead needs a different owner.
Agent portal
Give agents the leads they need to work.
Each agent can sign in with named role-based access to a focused lead view, review visitor context, and respond without exposing brokerage-wide settings.
