Skip to main content
The Forgeby HustleForge
Real Estate & Brokerage

AI Receptionist

Give callers a useful next step when agents are busy.

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.

Brokerage tools are Limited release on Pro and require technical setup. A finished brokerage screen and this full workflow have not been demonstrated. Confirm access and the work your team must do before buying.

Where this breaks down today

A potential buyer calls after hours or while the agent is in a showing. Voicemail captures the interruption, but the office still needs the caller’s request and a responsible person for the next step. Supported receptionist handling brings that information into the follow-up process.

  • 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. 1

    Every call lands in one queue

    Proposed, not yet verified: 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. 2

    Caller matched to the same record

    Proposed, not yet verified: 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. 3

    Qualification captured in a transcript

    Proposed, not yet verified: 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. 4

    Routed by the same rule as any lead

    Proposed, not yet verified: 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. 5

    Appointment booked or handed off

    Proposed, not yet verified: 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. 6

    Escalated when a person is needed

    Proposed, not yet verified: 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.

Social publishing

Listing to lead, on social

Social content intake, templates & compliance reviewContent calendar, broker approval & scheduled publishingSocial inquiry intake & lead convergenceCampaign Wallet budget approval & spend controls

Proposed, not yet verified: 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. 1

    Listing content moves into the workspace

    Proposed, not yet verified: Photos, copy, and listing details start in the same workspace as the listing record itself, not a folder no one can find.

  2. 2

    Brand and fair-housing templates apply

    Proposed, not yet verified: Content runs through the brokerage's brand templates and fair-housing disclosure gate before it goes anywhere near a review queue.

  3. 3

    Broker approval before anything schedules

    Proposed, not yet verified: A broker or authorized reviewer approves the post before it can be scheduled — no listing content publishes without that step.

  4. 4

    Calendar and scheduled publishing

    Proposed, not yet verified: 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. 5

    Inquiries land on the same lead record

    Proposed, not yet verified: 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. 6

    Organic and paid stay separated

    Proposed, not yet verified: 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

Facebook publishing connectorInstagram publishing connectorLinkedIn publishing connectorTikTok publishing connectorX (Twitter) publishing connectorGoogle Business Profile publishing connector
Direct posting to Facebook, Instagram, LinkedIn, TikTok, X, and Google Business Profile is being switched on one network at a time. Until a given network is live, a post that cannot go out tells you exactly why — it is never reported as sent.

See current availability by plan, provider, and rollout stage

What employees see

  • Proposed view, not yet verified: The caller matched to the same contact and lead record a web inquiry or referral would create — or a new one opens automatically.
  • Proposed view, not yet verified: Qualification notes and a transcript attached to that record, not left in someone's memory.

What managers control

  • Proposed view, not yet verified: Recordings are kept only where consent is captured and configured — that setting belongs to the brokerage, not a default The Forge sets.
  • Proposed view, not yet verified: 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 supported telephony provider, configured and tested for this brokerage; provider availability alone does not verify the complete handoff
  • Facebook, Instagram, LinkedIn, TikTok, X, and Google Business Profile, for the social-publishing loop below

Security & data

Agent, team and office record separation has not been verified. Tenant isolation is not proof of private agent or commission access. Review and test exact permissions before entering confidential records. Immediate escalation to a person for emergencies, complaints or existing clients must be verified before relying on the receptionist.

AI Receptionist — questions

Related

The Forge — AI Receptionist
  • Proposed view, not yet verified: Recordings are kept only where consent is captured and configured — that setting belongs to the brokerage, not a default The Forge sets.
  • Proposed view, not yet verified: 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.
  • Proposed view, not yet verified: The caller matched to the same contact and lead record a web inquiry or referral would create — or a new one opens automatically.
  • Proposed view, not yet verified: Qualification notes and a transcript attached to that record, not left in someone's memory.