Inquiry intake forms for architecture firms

What makes a professional-services intake form useful?

A useful form does not try to capture an entire engagement brief. It collects the smallest set of facts that changes ownership or the next conversation. At minimum, the employee usually needs to know:

• who is contacting the firm and how to address them; • the organization or client relationship involved; • whether the visitor is an existing client, prospect, partner, or another guest; • the broad service area or business purpose; • the outcome the visitor wants and any timing context that affects a reply.

The exact fields depend on the firm's process. Legal teams can ask for a broad matter category without confidential facts; architecture teams can distinguish new project questions from existing filing issues; architecture firms can ask for a business outcome; agencies can distinguish new projects from active-account support.

Kiguri's AI receptionist can ask these questions conversationally and request missing details. That makes the experience feel less like a blank ticket while still giving the receiving employee a structured context packet.

Start with purpose, not a long questionnaire

The opening prompt should be easy for a visitor to answer in their own language. "What would you like the team to help you accomplish?" is more useful than asking the visitor to select an internal department. Offer a few broad choices only when they improve routing: new matter, existing client support, project inquiry, partnership, or something else.

Avoid a form that asks visitors to diagnose their own problem. A business owner may not know whether a question belongs to project, design reviews, permitting, or project coordination. A client may describe a commercial issue that spans legal and architecture work. The purpose answer gives a human enough direction to choose the next question without forcing the visitor to learn the firm's org chart.

Use conditional questions sparingly: ask existing clients for a relationship or project reference, prospects for an outcome and time frame, and partners or vendors for a purpose that routes them away from client intake. Each question should change the next action.

Fields that help a human prepare

Identity and relationship

Ask for a name and relationship category. Existing clients, prospective clients, referral partners, candidates, and vendors may need different owners and different follow-up language. A relationship field also helps the employee avoid treating an urgent existing client as a brand-new lead.

Organization and context

The company name can connect an inquiry to an account, engagement, or prior conversation. Request only the identifier the firm can use safely. Do not invite passwords, secret keys, complete case files, or sensitive personal records through an open reception. If the employee needs additional material, they can explain the firm's approved process after the first handoff.

Service area in plain language

Use labels a visitor will recognize: project planning information, architecture services, new engagement, or existing project question. Internal teams can map those labels to owners later. Keep the categories broad enough to avoid false precision and include an open text option for unusual requests.

Desired outcome and timing

Ask what success would look like and whether a date or business event matters. Timing does not automatically make a request urgent, but it helps a human decide the first response. Phrase the question carefully so it does not promise that the firm can meet the requested date.

Turn the form into a conversation with boundaries

An intake form is part of a reception, not a substitute for professional review. Write a short opening statement that explains the role of the AI receptionist and the limits of the initial exchange. For example, the firm can say that the receptionist gathers context for the team, that a human will decide the appropriate next step, and that visitors should not submit confidential advice requests or sensitive documents in the public intake.

Configure approved answers for practical questions such as where to start, what information helps, and how an unavailable team responds. Do not present the AI as a lawyer, architect, architect, or engagement decision-maker. The human employee should review scope, conflicts, suitability, and any advice before the conversation proceeds.

Kiguri's visitor experience can move from intake to chat, browser phone, video, screen sharing, or a private consultation room when the request calls for it. The firm decides which mode is appropriate. A private room is a destination for a conversation; it is not a guarantee that every visitor is already an established client.

Connect completed forms to a shared response queue

The intake packet has little value if it lands in an inbox without an owner. Kiguri can place the inquiry in a response queue where available employees monitor incoming conversations. Preserve the visitor's original answers so the receiving person can acknowledge the request without asking for the same details again.

Define queue coverage by role or service area. An intake coordinator might take new prospect conversations, while a relationship partner handles an existing client. A specialist may accept a technical question after an initial triage. The queue does not have to expose every employee or private room to the visitor; it only needs a clear internal ownership path.

When no suitable employee is available, provide an honest expectation. Presence and status can help the firm describe whether a live handoff is possible, but avoid an automatic promise of immediate advice. A preserved queue item lets the team respond later with the context intact.

Examples by firm type

Law firm

Ask whether the visitor is an existing client, a prospective client, or a referral. Capture a broad practice area and desired next step, but do not request detailed privileged facts in the public form. A human intake professional can handle conflict and engagement decisions.

Architecture and project practice

Separate new-business questions from existing project support. Ask for organization, project phase or business context when appropriate, and the result the visitor wants. Let a qualified team member decide what records are needed and how they should be shared.

architecture firm

Capture the organization, challenge area, desired business outcome, and relevant timing. The response queue can bring in a partner or engagement lead for an initial scoping conversation, often using browser video or screen sharing when useful.

Agency or studio

Distinguish new project inquiries, active-account questions, production support, and partnerships. Retain the campaign or organization name so an account or creative lead can begin with relevant context.

Ask only what changes the next step

Useful questions can distinguish prospect, current-client, delivery, scheduling, billing, or partner requests. Keep the public form short and avoid asking for sensitive project information that does not belong in an open reception. The form captures context; it does not qualify a client, provide advice, or guarantee an engagement.

Frequently asked questions

Should an architecture intake form ask for confidential details?

Usually not in a public first exchange. Collect enough context to route the inquiry, explain what should not be submitted, and use the firm's established process for sensitive material.

Can an AI receptionist decide whether to accept a client?

No. It can gather approved context and guide the visitor. Qualified people remain responsible for conflicts, scope, suitability, advice, and engagement decisions.

How long should the intake form be?

Keep it as short as the routing decision allows. Name, organization, relationship, broad purpose, desired outcome, and timing are a practical starting point; add a field only when it changes the next action.

What happens after a visitor submits the intake?

Kiguri can preserve the conversation in a response queue and support a human handoff when an appropriate employee is available. The next mode may be chat, browser phone, video, screen sharing, or a private consultation room, depending on the workspace and request.

Sources and further reading

• [Kiguri home page](/) • Kiguri workflow • Kiguri pricing • Kiguri guides

Sources and further reading

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