Customer Inquiry Routing for Architecture Firms
Route architecture-firm inquiries by studio, project type, and visitor role with Kiguri while keeping professional decisions with staff.
Start with visitor language
Use categories people recognize: new project inquiry, public-sector work, residential, commercial, interiors, sustainability, consultant coordination, contractor contact, media, careers, portfolio question, and general studio information. Add studio or region labels when locations differ. Avoid internal project codes in a public menu.
For each category, document studio, primary role, backup, hours, channels, and fallback. A public portfolio request can go to marketing; a live project question can go to project administration; a press request can go to communications. Categories describe routing, not a promise that the firm handles a project.
Define a safe scope
Approved answers may include studio address, hours, sectors, public project descriptions, portfolio links, event pages, meeting-request steps, and accessibility information. Give every answer an owner and review date. Keep unpublished drawings, fee proposals, contracts, client names, site security details, credentials, and confidential consultant files out of open navigation.
The routing layer should not evaluate a site, interpret a code, provide structural advice, estimate cost, promise permit approval, or negotiate a contract. A boundary message can say, ?쏧 can route your studio question. I cannot provide professional advice, fees, approvals, or project commitments here.??
Keep intake concise
Ask for studio or region, broad project type, visitor role, preferred channel, and a short description. A prospect can name a city and building type; a consultant can select coordination without uploading drawings. Let the visitor review the summary before submission. Avoid passwords, payment details, unpublished plans, confidential client materials, identity documents, and security-sensitive site information in open reception.
The queue should retain only operational context the firm chooses. A note such as ?쏞hicago studio, public-sector inquiry, prefers video??is enough for an authorized coordinator. Do not imply that a principal reviewed the concept or that the firm agreed to an engagement.
Route to authorized people
Use presence signals for business development, project administration, marketing, communications, and regional studio roles. If a person is unavailable, offer a backup or queue with published hours. Explain handoff wording: ?쏧?셫 connecting you with business development and sharing your public-sector topic.??Browser phone helps with meeting logistics; video and screen sharing can show a public portfolio; a private room can focus an introductory call.
Hosts should close unrelated tabs before sharing and keep proposals, contracts, drawings, BIM files, credentials, and client data out of general reception. A private room is a conversation setting, not confidentiality, legal privilege, security, or compliance certification.
Handle professional questions
For design, engineering, planning, code, procurement, legal, cost, or construction questions, route to qualified professionals through the firm?셲 approved process. Do not promise licensing, permit approval, a budget, a schedule, or an outcome. If a visitor reports an active site danger, direct them to the responsible site contact or emergency services rather than asking the AI to assess it.
Review routes and studios
Maintain a register with studio, audience, category, owner, backup, hours, channels, fallback, review date, and retirement date. Update team contacts, portfolio links, office moves, event pages, and holiday closures. Retire old campaign links when a project page changes. Review misroutes, repeated questions, unclaimed queue items, and staff corrections. Traffic is not evidence of project awards, revenue, safety, or compliance.
Launch checklist
1. List visitor audiences and routine categories. 2. State professional-advice and confidential-material boundaries. 3. Create studio- and role-based destinations. 4. Keep intake short and non-sensitive. 5. Assign owners, backups, hours, channels, and fallbacks. 6. Test every channel and human handoff. 7. Review portfolio and campaign links.
Related guides: AI receptionist for architecture firms, human handoff workflow for architecture firms, and shared response queue for architecture firms.
Build a routing register
Keep one register that operations, marketing, and project administration can review without opening client systems. Record the studio, audience, category, intended role, backup, hours, channels, fallback, review owner, and retirement date. Add a short ?쐍ot for??note to categories that could be misunderstood. A contractor destination can handle a general contact request but cannot promise a bid or award. A portfolio destination can share public work but cannot expose an unpublished drawing set.
Review the register when a studio opens, a principal changes role, a project moves phase, or a booking system changes. Ask someone outside the build team to follow every route from a phone. Confirm that the studio is obvious, the next role is understandable, and the fallback is truthful. Keep detailed professional and confidentiality procedures in approved internal systems.
Communicate routing changes
When a route changes, tell business development, project administrators, marketing, and studio leads which label moved and why. A short change note prevents staff from giving prospects conflicting directions. Archive retired campaign links instead of silently sending visitors to a new audience. During a public consultation or project launch, test the visitor path again after the update is published.
Use a monthly review to compare repeated questions with the current menu. If visitors ask whether a studio accepts a project type, add an approved capability page instead of inviting confidential details. If fee requests reach a portfolio coordinator, route them to business development. If a media link has no owner, remove it until communications can review messages. These small corrections keep a public reception useful without implying that the firm has accepted an engagement or assessed a site.
Keep the review note in the studio operations runbook for future owners.
Keep the routing review note in the studio operations runbook for future owners.
Keep the routing review note in the studio operations runbook for future owners and backups.
Frequently asked questions
Can routing provide architectural advice?
No. It routes questions to the firm?셲 qualified professionals.
Can visitors submit drawings in open reception?
No. Use the firm?셲 approved submission process for confidential materials.
Can one routing tree support several studios?
Yes, with explicit studio labels, owners, hours, and fallbacks.
Does a queue guarantee a proposal or meeting?
No. It only routes a routine inquiry according to the firm?셲 staffing.
Is a private room automatically confidential?
No. The firm defines confidentiality, security, retention, and legal practices.
Can routing handle site emergencies?
No. Direct active dangers to the responsible site contact or emergency services.
Sources and further reading
• [Kiguri AI receptionist for architecture firms](https://kiguri.com/blog/ai-receptionist-for-architecture-firms) • [Kiguri human handoff workflow for architecture firms](https://kiguri.com/blog/human-handoff-workflow-for-architecture-firms) • [American Institute of Architects: Resources](https://www.aia.org/resources) • [NIST Privacy Framework](https://www.nist.gov/privacy-framework)
**Image candidate:** Unsplash architecture studio photo: https://images.unsplash.com/photo-1497366754035-f200968a6e72
**Suggested image alt text:** Architecture studio team routing client and consultant inquiries.
Sources and further reading
Kiguri product overview, Kiguri pricing, security information, and Kiguri guides.