AI Receptionist
Every call — live, missed, or voicemail — lands on the same lead record and routes by the brokerage's own rule, so a 6:40pm call never depends on who's near a phone.
Built for: Brokerages that lose after-hours or overflow calls to voicemail today, and want those calls routed the same way a web lead already is.
Where this breaks down today
A missed call from a lead goes unanswered because no one was watching the queue, and a comment or DM on a listing post never makes it onto anyone's follow-up list.
- A 6:40pm buyer inquiry goes to voicemail instead of a live answer.
- Live, missed, and voicemail calls end up in separate places, so nothing forces a callback.
- A social comment or DM asking about a listing sits outside the lead pipeline entirely.
How The Forge addresses it
- 1
Every call lands in one queue
Live, missed, and voicemail calls the receptionist handles all land in the same queue — nothing sits in a separate voicemail box no one checks.
- 2
Caller matched to the same record
The caller is matched to the same contact and lead record a web inquiry or referral would create, or a new one opens automatically.
- 3
Qualification captured in a transcript
What the caller wants and why is captured in a transcript and qualification notes attached to that record, not left in someone's memory.
- 4
Routed by the same rule as any lead
The call routes to an agent by the brokerage's existing rule — round-robin, territory, or team — the same rule a web lead follows.
- 5
Appointment booked or handed off
A showing gets booked directly, or a follow-up task lands with a named owner and a response window, same as any other lead.
- 6
Escalated when a person is needed
A call that needs a person right away — an emergency, an existing client, a complaint — escalates to a person instead of staying with the receptionist.
Listing to lead, on social
A listing photo posted to Instagram and a phone call from a sign rider should not live in two different worlds. The social publishing layer moves a listing from content to a scheduled post. Any inquiry it generates lands on the same lead record a call or web form would create.
- 1
Listing content moves into the workspace
Photos, copy, and listing details start in the same workspace as the listing record itself, not a folder no one can find.
- 2
Brand and fair-housing templates apply
Content runs through the brokerage's brand templates and fair-housing disclosure gate before it goes anywhere near a review queue.
- 3
Broker approval before anything schedules
A broker or authorized reviewer approves the post before it can be scheduled — no listing content publishes without that step.
- 4
Calendar and scheduled publishing
Approved posts sit on a shared content calendar, and every publish attempt reports an honest status — published, or the specific reason it could not be.
- 5
Inquiries land on the same lead record
A comment, DM, or form reply from that post is matched to the same contact and lead record a call would produce, or opens a new one.
- 6
Organic and paid stay separated
Organic reach and paid campaign performance are tracked separately, so a listing's traction is never blended with what was paid to promote it.
- A paid campaign's budget only goes live after a different approver than the requester signs off on it.
- Spend can never exceed what was approved, and provider cost, media spend, and Forge's own management fee are always itemized separately.
- Nothing paid activates automatically — every campaign starts stopped until someone with approval authority turns it on.
Provider connectors
See current availability by plan, provider, and rollout stage
What employees see
- The caller matched to the same contact and lead record a web inquiry or referral would create — or a new one opens automatically.
- Qualification notes and a transcript attached to that record, not left in someone's memory.
What managers control
- Recordings are kept only where consent is captured and configured — that setting belongs to the brokerage, not a default The Forge sets.
- Each call's cost shows on the call record itself, and call volume, response time, and per-call cost roll into the same reporting lead routing already uses.
Integrations required
- A telephony provider (required — the code path is live today, but calls only reach the queue once this is connected)
- Facebook, Instagram, LinkedIn, TikTok, X, and Google Business Profile, for the social-publishing loop below
Security & data
A call that needs a person right away — an emergency, an existing client, a complaint — escalates to a person instead of staying with the receptionist.
AI Receptionist — questions
Related
Lead Routing
Every inbound lead is routed to an agent within minutes, by a rule the whole team can see — not a habit a few people benefit from.
ExploreTransaction Management
Every transaction's milestones and deadlines are tracked from contract to closing, so a financing contingency doesn't surface as a surprise the week of closing.
ExploreCommission Visibility
See a forecasted commission — split, referral fee, and all — the day a deal goes under contract, checked against the actual closing statement instead of trusted blind.
ExploreReal Estate & Brokerage overview
Back to the full brokerage industry page — pain points, the guided demo, and the plan recommendation.
ExploreReal estate operating guide
The full vocabulary, data records, roles, compliance detail, and launch timeline in one reference doc.
Read the guide- Recordings are kept only where consent is captured and configured — that setting belongs to the brokerage, not a default The Forge sets.
- Each call's cost shows on the call record itself, and call volume, response time, and per-call cost roll into the same reporting lead routing already uses.
- The caller matched to the same contact and lead record a web inquiry or referral would create — or a new one opens automatically.
- Qualification notes and a transcript attached to that record, not left in someone's memory.