Inquiry intake forms for real estate teams

Start with the minimum useful context

Use a short sequence: name, organization, relationship, purpose, and a concise description. Relationship choices may include prospective tenant, buyer, current client, property owner, broker partner, vendor, event guest, or general visitor. Keep an “other” option and a free-text field for visitors who do not fit a label.

Ask one question only when it changes the next step. A tour request may need property or region. A partner conversation may need the relevant market. A current client may need an account reference, but never ask for passwords or sensitive financial material in a public reception. Explain why an optional question helps, and let a human clarify anything ambiguous.

Use progressive disclosure

Do not ask every visitor to complete a full property brief. Begin with a short arrival form. After the visitor identifies a purpose, show one or two relevant follow-up questions. For example, a tour request can ask whether the visitor is looking for office, retail, or residential space. A vendor question can ask which operating area is involved. A broker partnership request can ask for region and preferred contact mode.

Progressive disclosure also helps a human handoff. The receiving host sees the visitor's original purpose and the answers that led to routing, rather than a pile of fields with no explanation. If the visitor cannot answer a follow-up, preserve the request and let the host ask it conversationally.

Keep the AI boundary clear

Kiguri can provide approved answers for public information such as how to request a host, which visitor destinations exist, or where current general information is published. Assign an owner to maintain those answers. Property availability, pricing exceptions, contract terms, legal questions, and account-specific advice should go to the responsible human team.

When the AI is uncertain, it should acknowledge the boundary and keep the visitor's purpose intact. An honest “A property host can clarify that” is more useful than an invented estimate. The intake is for context and orientation, not an autonomous real estate decision.

Route by relationship and purpose

Create a routing matrix staff can understand:

• Prospective tenant or buyer: leasing or sales host. • Current client: account or property-services host. • Property owner: portfolio or operations host. • Broker partner: partnerships host. • Vendor: operations owner. • Event guest: event host.

These are operator-defined policies, not automatic Kiguri classifications. Give each category a first owner and backup. The queue should show the visitor's organization, relationship, purpose, and original wording so the first host can accept or reassign without restarting intake.

Offer a channel that fits the inquiry

Chat works for a quick introduction or a location question. Browser phone is useful for a voice conversation without another application. Video can support a property discussion or guided welcome. Screen sharing can help explain a map or workflow. A private consultation room is appropriate for account-specific detail after the host accepts the request.

Tell visitors which mode comes next. “Request a browser-phone conversation with a leasing host” sets a better expectation than “escalate.” If no host is available for video, preserve the request and offer chat or a clear follow-up path. Do not make every visitor choose a channel before ownership is established.

Make the map support intake

Kiguri's virtual office map can show reception, property services, leasing, partnerships, and private consultation destinations. Use visitor language rather than internal department codes. A visitor looking for a tour should not have to understand the team's org chart.

Expose only the destinations needed for the journey. Keep internal workrooms private and provide a direct reception link for visitors who prefer a simple path. If multiple properties or offices share one branded experience, use location labels that make the intended host clear without exposing unnecessary employee information.

Test with real scenarios

Pilot five inquiries: a prospective tenant requesting a tour, a current client asking for an account host, a property owner seeking an update, a broker partner proposing a collaboration, and a vendor with an operational question. Check whether each person can complete the intake quickly and whether the receiving host can act without repeating the first questions.

Read the offline message as a visitor. Does it explain what happens when no host is available? Does it avoid promising an appointment or response time the team cannot guarantee? Review the approved answers whenever public information changes. Remove fields that do not affect routing, and add only questions that resolve a real ambiguity.

Keep the form useful after the first handoff

An intake is successful when the next employee can start a relevant conversation, not merely when a visitor completes every field. Show the summary to the host in the same order the visitor answered: who they are, what relationship they have, what they want, and which property or region matters. If a field is optional, do not make the host assume that an empty answer is a missing error.

Review the form with leasing, client-services, operations, and partnership owners separately. Each team can identify one question that changes ownership and one question that creates unnecessary friction. Keep the shared intake stable, then add a clearly labeled follow-up question only for the relevant purpose. This preserves a consistent branded arrival while allowing real estate specialists to ask better questions after a human accepts the handoff.

Frequently asked questions

Is this an automated property lead-scoring form?

No. This guide describes concise context collection and human routing through Kiguri. It does not claim automated lead scoring, valuation, or qualification.

Should we ask for budget in the first interaction?

Only if your own policy truly needs it and the question is appropriate for the visitor's purpose. Avoid collecting sensitive details in a public reception and prefer a human conversation for context-specific questions.

Can an intake request a video tour?

It can explain an available conversation mode when configured in the Kiguri workspace. Confirm current channel behavior and host availability before promising a live tour.

What if the visitor chooses the wrong category?

Keep an “other” path and let the host reassign the inquiry while preserving the original description.

Sources and further reading

• [Kiguri home](https://kiguri.com/) • [Kiguri pricing](https://kiguri.com/#pricing) • [Kiguri security information](https://kiguri.com/security) • [Kiguri blog](https://kiguri.com/blog)

Verify current Kiguri features, plan limits, and pricing before publishing visitor-facing claims.

Sources and further reading

Kiguri product overview, Kiguri pricing, security information, and Kiguri guides.