Inquiry intake forms for digital agencies

Why a standard agency contact form often breaks down

Digital agencies receive several kinds of visitor in the same week: a new brand prospect, an existing client asking about a campaign, a partner proposing a referral, and a contractor responding to a production need. A single email address may be easy to publish, but it hides the distinction between those conversations. The first employee to open the message may not be the person who knows the account, service, or deadline.

Long forms create a different problem. A prospect may know the business outcome but not the agency's preferred service vocabulary. They may not have a final budget, a complete brief, or a confirmed launch date. Requiring every field before anyone can respond turns uncertainty into abandonment. A good intake collects enough context for a human to help, then lets discovery continue in a conversation.

The minimum context an agency should collect

Start with questions that change ownership or the next step. Kiguri's AI receptionist can ask for the visitor's identity, company, and purpose; an agency can phrase those prompts in language its clients use.

Name and relationship

Ask how the visitor would like to be addressed and whether they are a prospective client, an existing client, a referral partner, or another guest. This single distinction prevents a current account question from being treated like a cold lead. It also gives the receiving employee a natural opening: “I see this is about your current project; I will connect you with the account team.”

Organization and project reference

The company name is often the key to ownership. For existing clients, request a project, campaign, or product reference if the visitor has one. Do not make the field mandatory when a prospect is still exploring. A short description such as “the new ecommerce site” can be more useful than an internal project code that a visitor does not know.

Desired outcome

Ask what the visitor wants to accomplish. Offer broad examples such as a new website, brand system, content program, product experience, campaign, or support on an active engagement. Keep an open text option for work that does not fit a menu. The goal is direction, not a premature estimate or qualification decision.

Timing and event context

A launch, board meeting, funding announcement, or seasonal campaign may affect the first response. Ask whether a date or event matters, but do not promise that the agency can meet it. “Is there a date we should understand?” is safer than “When do you need the project completed?” because it invites context without creating an automatic commitment.

Helpful materials, not sensitive files

Visitors may want to describe a website, product, or campaign. The public intake should not ask for passwords, private customer records, secret keys, or confidential files. Tell visitors what is useful to discuss at the first step and explain how the agency will request additional material through its own approved process.

Turn fields into an approachable conversation

A form can be conversational without being vague. Open with the agency's service promise and the AI's role: it gathers context and answers approved questions so a person can continue the conversation. Tell visitors that an employee decides the next step. This wording sets a boundary without making the arrival feel like a legal notice.

Use conditional prompts only when they reduce work. An existing client might be asked for a project name; a new prospect might be asked for an outcome; a partner might be asked what relationship they want to discuss. If an answer does not change routing, remove the question. Review the actual conversations after launch and rewrite prompts that produce one-word answers or repeated clarification.

The reception should also explain what happens when no one is immediately available. A visitor can enter the response queue with the context they supplied. Do not imply that an AI reply is a project commitment or that a visible team member is ready to give an instant estimate.

A practical agency intake map

Use the following as an internal design exercise before publishing a link:

| Visitor signal | Likely reviewer | First human action | | --- | --- | --- | | New project and business outcome | New-business lead or account director | Confirm goals and decide whether to schedule discovery | | Existing client and project reference | Account owner or producer | Acknowledge the project and clarify the requested outcome | | Creative or strategy question | Practice lead | Invite the relevant specialist when needed | | Delivery or website issue | Delivery lead or technical specialist | Ask a focused question or use screen sharing | | Referral, partner, or supplier request | Operations or partnerships owner | Review the relationship and next step |

This is an agency policy, not a claim that Kiguri automatically makes every assignment. The AI receptionist collects signals; the team applies account ownership, workload, and service rules.

Preserve the brief through human handoff

The value of an intake disappears when the receiving employee asks the visitor to start over. When an available employee accepts the inquiry, confirm the summary and correct anything inaccurate. A producer can say, “You are exploring a redesign for the customer portal, and the launch event is in October. Is that right?” The visitor can then add nuance instead of repeating a form.

Kiguri supports continuing a conversation by chat, browser phone, video, screen sharing, or a private consultation room. Match the channel to the work. Chat may be enough for a first clarification. Screen sharing can help explain a live site after the visitor agrees. A private room is more appropriate for client-specific discussion than a public reception. The employee should decide the destination and who needs to join.

Protect the agency's internal workspace

An interactive map can make a virtual office feel more human, but public access should not expose private employee rooms or client conversations. Keep the public arrival focused on reception and intended visitor destinations. Move client-specific work to a controlled private consultation room according to the agency's own access and records policies.

How to test an agency intake before launch

Run at least five realistic paths: a first-time prospect with no budget, an existing client who names a campaign, a partner request, a technical issue that benefits from screen sharing, and an after-hours visitor. Check that the AI asks only approved questions, that the response queue preserves context, that an available employee can accept the right request, and that every unavailable path explains the next step honestly.

Review completion, abandoned starts, repeated questions after handoff, time to a human response, and transfers to another role. If a field is never used, remove it. If employees repeatedly ask for the same missing detail, rewrite the prompt. A short, clear intake that leads to a confident handoff is more valuable than a form that looks comprehensive on paper.

Frequently asked questions

Should an agency ask for a full creative brief in the first intake?

Usually not. Capture identity, organization, relationship, broad purpose, desired outcome, and relevant timing. The agency can gather a full brief after a human understands the request.

Can the AI receptionist qualify a prospect or promise a project date?

It can collect approved context and answer approved questions. Agency employees remain responsible for estimates, scope, fit, advice, and commitments.

Can one Kiguri link serve prospects and current clients?

Yes. One branded reception can present clear purposes and route different contexts to the team. Separate links may still help a campaign, event, or client-specific arrival.

What happens when the right agency employee is busy?

The inquiry can remain in a response queue with its context preserved. The agency should set its own coverage and follow-up expectation rather than promise an immediate live answer.

Where can I review Kiguri's current product information?

Start with the [Kiguri virtual reception](/), pricing and plans, security information, and Kiguri guides.

Sources and further reading

• [Kiguri virtual reception](/) • Kiguri pricing and plans • Kiguri security information • Kiguri guides

Sources and further reading

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