Multi-Department Contact Form Template
One front door, four departments — the form asks the right follow-up for whichever team is chosen and skips everything else.
One form, every team. Choose who you need and we'll ask just one or two things that help that department answer you faster.
The classic multi-department contact page offers four email addresses and hopes visitors choose correctly; the classic shared form asks everyone every question. Both fail the same way — the burden lands on the visitor. This template inverts it: one required choice, and the form itself adapts, asking sales prospects about product lines, support seekers for ticket numbers, billing questions for the invoice, and candidates for the role. Four department-specific forms, wearing one link.
Why these fields. The department selector is the axle, and each follow-up field is chosen as the one question that most accelerates that team's first reply. A ticket number lets support open with the history loaded. An invoice number lets billing answer instead of asking. A product line lets sales route to the right specialist. A role title lets HR skip the "which position?" email. Crucially, all four follow-ups are optional and short — the conditional reveal keeps the form at five visible questions for everyone, which is why it converts like a simple form while collecting like a routed one. Focus mode leans into this: one question at a time, and respondents never even sense the paths they didn't take.
What we left out. A separate form per department linked from a hub page — that pattern works, but it multiplies maintenance and splits your response history four ways. Also org-chart honesty like "Level 2 Technical Support": visitors think in needs, not in your reporting lines, and four plain labels cover most companies.
Who uses this. Companies of ten to a few hundred people where departments are real but a contact-center platform is overkill, e-commerce shops splitting orders from wholesale from careers, and agencies routing new business, current clients, and job seekers through one polished front door.
Make it yours. Rename departments and rewrite each follow-up in the Logic panel — the four show-rules are working examples of the pattern, one per lane. Route by webhook and branch on the department answer so each team's messages land in their own channel or tool; the follow-up context rides along in the payload. Filter the responses view by department for weekly reviews, and export CSV when you want to see volume per team — the case for hiring that second support person is usually sitting in that column.
One link to remember. Business cards, email signatures, the website footer — everything points at a single URL, and the form does the sorting. That's the whole trick, and it never stops being useful.
Frequently asked questions
How does each department get only its own messages?
Push submissions through a webhook and branch on the department answer in your receiving tool — each team's messages land in their own channel, with the follow-up context included.
Why do different people see different questions?
Four logic rules — one per department — reveal the single follow-up that helps that team most. Everyone else's path stays five questions short. The rules are editable in the Logic panel.
Can I add or rename departments?
Yes — edit the selector options, then update or add the matching show-rule so each new lane gets its own follow-up question. Changes go live on the shared link immediately.
How do I see which department gets the most volume?
Export the CSV and count by the department column, or just filter the responses view per team — it's the simplest staffing-signal report you'll ever run.