Inquiry Intake Forms for Marketing Agencies
Design short Kiguri intake forms for marketing prospects and clients without collecting private briefs or promising campaign performance.
Choose one form purpose
Create separate forms for new-business inquiries, brand strategy, creative services, content production, media, public relations, account support, partner contact, careers, and general agency information. A title should explain the next step: "Request a strategy conversation" is clearer than "Tell us about your campaign." For each form, assign office or market, primary role, backup, hours, channel, and fallback queue. A multi-office agency can ask the visitor to select an office first. Keep forms short enough for a phone, and publish a review date for the introduction and service labels.
Use safe fields
Ask for agency or region, broad campaign type, visitor role, preferred channel, contact window, and concise context. A prospect may choose "Product launch" and name a target market without uploading a private brief. Let the visitor review and correct the summary before it is routed.
Do not ask for ad-account credentials, customer lists, payment-card details, passwords, unpublished creative, confidential budgets, private performance dashboards, identity documents, or contract terms in open reception. If staff need a brief or file, they can provide the agency's approved submission channel.
Use a clear notice: "This form supports routine agency coordination and routes requests to a human owner."
Make submission honest
After submission, show the selected office, broad service, and next operational owner when appropriate. Say whether a person reviews the queue during published hours. Do not promise a proposal, creative review, media plan, callback, or result. Let the visitor correct the summary before it is routed.
A concise note might read, "London agency, content inquiry, prefers browser phone." The shared queue can assign business development or an account lead without exposing private campaign material.
Route to people
Use human handoff for scope questions, account support, accessibility, media coordination, or a complaint to an account lead. Explain what will be shared and avoid forcing the visitor to repeat details. Browser phone can handle a longer administrative explanation; video and screen sharing can show a public capabilities page; a private room can focus a discovery call.
Hosts should close dashboards, ad accounts, customer data, budgets, private briefs, and unrelated tabs before sharing. A private room is a conversation setting, not a confidentiality, security, legal, or compliance guarantee. Keep client materials in the agency's approved systems.
Keep performance and legal boundaries visible
An intake form should not ask the AI to forecast conversions, evaluate media safety, interpret a contract, or provide data-protection advice. If a visitor asks about impressions, rankings, return on ad spend, consent, or a legal claim, route to qualified agency or client-service staff through the approved process. Do not imply that form submission means the agency accepted an engagement.
Maintain forms across offices
Keep a form register with title, office, audience, owner, backup, hours, channels, fallback, review date, and retirement date. Update holiday closures, service categories, team contacts, and campaign links. Retire forms for closed offices or old launches. Test each form from a phone before a pitch event, product launch, or seasonal campaign.
Ask a staff member who did not build the form to complete it as a first-time prospect. Check office labels, field descriptions, boundary notice, handoff message, urgent security contact, and after-hours wording. Archive changes in the agency runbook.
Review intake quality
Inspect abandoned forms, repeated answers, misroutes, and notes that contain more information than staff need. If visitors paste a private brief, strengthen the boundary and provide the approved channel. If account-support questions reach new business, adjust destinations. If a form receives no review after hours, publish the queue window.
Do not use completion counts to claim campaign performance, lower acquisition cost, client retention, or compliance. The useful measure is whether routine context reaches the right person with minimal unnecessary data.
Launch checklist
1. Define one routine purpose per form. 2. Use office, service, role, channel, and concise-context fields. 3. Exclude credentials, customer lists, budgets, and private briefs. 4. Publish performance, legal, and security boundaries. 5. Assign owners, backups, hours, and fallbacks. 6. Test mobile completion, handoff, and queue states. 7. Review abandoned forms and retire stale links.
Related guides: customer inquiry routing for marketing agencies, shared response queue for marketing agencies, and private consultation rooms for marketing agencies.
Keep a field dictionary
Define what "New business," "Account support," "Media," "Partner," and "General information" mean, and add a short exclusion for each. Review the dictionary with business development, account services, operations, and communications leads. If a form starts attracting a new kind of question, create a separate destination instead of adding many fields. Fewer clear choices help prospects finish quickly and give staff a useful, non-confidential summary.
Review campaign changes
Before a product launch, pitch event, or public campaign, test the form from a first-time visitor perspective. Confirm office, service, channel, handoff, queue fallback, and security-contact wording. Retire the form after the campaign or update its purpose and review date. Keep the decision note in the agency runbook so backups know who owns the next review.
Share the next review date with every backup role before promotion.
Frequently asked questions
Keep the first response practical
When no live host is available, state the review window that the agency actually follows. Do not display a generic "someone will be in touch" promise if the team has no defined owner.
Review the form with people who answer different kinds of inquiries. Ask a project manager, account lead, creative coordinator, and office administrator to complete the flow from a phone. Their questions often reveal labels that make sense internally but confuse a prospect. Keep a dated field dictionary so temporary staff know which values are public, which are internal, and which require an approved submission channel. Revisit the dictionary when services, offices, or campaign destinations change.
Can an intake form forecast campaign performance?
No. It collects routing context and sends questions to agency staff.
Should a prospect upload an unpublished brief?
No. Use the agency's approved submission channel.
Can one form serve several offices?
Yes, when office selection, owners, hours, and fallbacks are explicit.
Does submission guarantee a proposal or callback?
No. Publish actual review hours and next steps.
Is a private follow-up room automatically secure?
No. The agency defines confidentiality, security, retention, and compliance practices.
What if a visitor reports an account-security issue?
Direct them to the agency's established security contact.
Sources and further reading
• [Kiguri customer inquiry routing for marketing agencies](https://kiguri.com/blog/customer-inquiry-routing-for-marketing-agencies) • [Kiguri shared response queue for marketing agencies](https://kiguri.com/blog/shared-response-queue-for-marketing-agencies) • [American Association of Advertising Agencies](https://www.aaaa.org/) • [NIST Privacy Framework](https://www.nist.gov/privacy-framework)
**Image candidate:** Unsplash marketing coordinator photo: https://images.unsplash.com/photo-1556761175-b413da4baf72
**Suggested image alt text:** Marketing agency coordinator reviewing a concise inquiry form.

Sources and further reading
Kiguri product overview, Kiguri pricing, security information, and Kiguri guides.