Inquiry intake forms for partner offices

Start with the host’s first question

Before choosing fields, ask hosts what they need to know before replying. In a shared partner office, the answer is usually the visitor’s name, organization, relationship to the office, and reason for the visit. Those four facts let a host identify the likely owner without asking the visitor to understand the internal org chart.

Write the fields in visitor language. “Which organization are you visiting with?” is easier to answer than “Account segment.” “What would you like help with today?” is more inviting than “Request classification.” Add an “I am not sure” choice whenever a visitor could reasonably be between categories.

Keep the first form proportional to the request. A tenant looking for a greeter should not complete a partner qualification survey. A prospective channel partner may need one optional question about region or the type of collaboration they have in mind. If a field does not change the next step, remove it from the initial intake.

A practical core field set

Most partner offices can begin with five fields:

• **Name:** so the host can address the visitor naturally. • **Organization:** so the host can recognize the relationship or locate the correct account owner. • **Relationship:** current client, prospective client, referral or channel partner, tenant, event guest, vendor, or another visitor. • **Purpose:** a short choice such as meeting a host, asking a question, requesting an introduction, or finding an event destination. • **Additional context:** optional free text in the visitor’s own words.

Keep contact information limited to what your follow-up process actually uses, and explain why an offline contact detail is requested.

Avoid collecting passwords, confidential documents, or detailed account records in an open reception form. The initial inquiry should help a host decide where to continue the conversation. A private consultation after handoff is a better place for a narrower client discussion.

Use relationship choices to guide routing

Relationship is a useful first branch because it maps to a person, not just a topic. Create a routing policy your hosts can remember:

• A **current client** goes to the account owner, client-success lead, or project host. • A **prospective client** goes to partner development or the sales host. • A **referral or channel partner** goes to an alliance or regional partner manager. • A **tenant or resident** goes to the local operations host. • An **event guest** goes to the event owner or designated greeter. • A **vendor** goes to the office operations owner.

These categories are not an automatic Kiguri classification. Your team defines the policy; Kiguri captures what the visitor says and displays it with the inquiry in the response queue. A host can accept the conversation or reassign it when the initial choice is not quite right. Preserve the original answer when reassigning so the next host does not make the visitor start over.

Ask one useful purpose question

“How can we help?” is friendly but can produce vague replies. Pair it with a few concrete choices and an optional explanation. For a partner office, choices might be “meet my host,” “ask a general office question,” “request an introduction,” “find an event,” and “discuss an existing client project.” Keep “something else” available for requests your list does not anticipate.

If the visitor selects an existing client project, ask only the detail that determines the next host, such as the project name or partner team. Do not turn the form into a complete discovery call. The host can ask follow-up questions after accepting the handoff.

Let the AI receptionist handle the obvious questions

The AI receptionist can answer stable, approved questions about where visitors should start, which destinations are available, and how to request a host. Give it a small source of truth and an owner who reviews it when partner programs, events, or office destinations change.

Set clear boundaries. The AI should not invent a client commitment, interpret a partner agreement, provide a pricing exception, or make a relationship decision. If a question is account-specific or uncertain, it should ask for clarification or route the original inquiry to a person. Accurate limits build more trust than a confident answer that a host must correct.

The AI receptionist for partner offices guide explains how to write approved answers and define the human boundary. The customer inquiry routing guide has examples of preserving context when a request changes owners.

Connect the form to a visible response queue

An intake form is only useful if someone can see what happens next. Kiguri’s response queue presents the visitor’s context to employees who can accept or reassign the conversation. Define who watches the queue during normal office hours and what the offline path should say when nobody is watching live.

Use the same language in the queue and in the form. If the form says “referral partner,” do not show “alliance lead” without an explanation that helps the host. Include the visitor’s free-text message in the handoff so the first response can acknowledge the actual request.

Decide how a host signals availability. A person may be ready for chat but not for browser phone or video. Kiguri supports live formats including chat, browser phone, video, and screen sharing, plus private consultation rooms. Offer the mode the host can accept and tell the visitor what will happen after they select it. A status indicator is guidance, not a promise of an instant meeting.

Let the map answer simple destination questions

Some questions are easier to answer with a destination than a field. Name public areas such as “Client meetings,” “Tenant help,” and “Community events” in language outsiders understand, and keep a direct reception route visible for visitors who prefer to ask a host. The virtual front desk for partner offices guide covers this map approach; branded visitor links explains how to introduce the same journey from email and event materials.

Test the form with real partner scenarios

Run at least five walkthroughs before publishing broadly: a current client who knows their account owner, a tenant who only needs directions, a prospective channel partner seeking an introduction, an event guest arriving after hours, and a visitor who selects “I am not sure.” Ask each tester to complete the form without coaching.

Then read the handoff as the assigned host. Can you tell who the visitor is, which organization they represent, why they came, and what response they expect? If not, change the wording or add one optional detail. If the form feels long, remove fields before adding automation.

Test the offline state separately. The visitor should know whether their inquiry was received, what follow-up path exists, and whether they can add context without repeating everything. Review a sample of accepted and reassigned inquiries to make sure context survives a handoff.

Measure useful context, not form completion alone

Frequently asked questions

What should a partner-office inquiry form ask first?

Start with name, organization, relationship to the office, reason for visiting, and optional free-text context. Add a field only when it changes routing or the immediate next step.

Can one form route tenants and clients differently?

Yes. Offer relationship choices and map each choice to the host policy your team defines. Kiguri passes the visitor’s answers into the response queue, where a host can accept or reassign the conversation.

Should an inquiry form collect a phone number?

Only if your follow-up process genuinely uses it. Explain why the detail is needed; otherwise let the visitor continue in the Kiguri conversation or request a host directly.

Can the AI complete the form for the visitor?

The AI can ask questions and answer approved general questions in the reception flow. Keep account-specific or uncertain requests available for human review rather than asking the AI to guess a category.

What happens when no employee is available?

The visitor can receive an offline explanation and the inquiry can remain in the response queue for follow-up, according to your team’s operating policy. Do not promise an immediate response unless your team can provide it.

Sources and further reading

• [Kiguri virtual reception](https://kiguri.com/) • [Kiguri pricing](https://kiguri.com/#pricing) • [Kiguri AI receptionist for partner offices](https://kiguri.com/blog/ai-receptionist-for-partner-offices) • [Kiguri customer inquiry routing guide](https://kiguri.com/blog/customer-inquiry-routing-for-saas-support-teams) • [Kiguri human handoff workflow guide](https://kiguri.com/blog/human-handoff-workflow-for-saas-support-teams) • [Kiguri virtual front desk for partner offices](https://kiguri.com/blog/virtual-front-desk-for-partner-offices)

Sources and further reading

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