Multi-Department Contact Form Template

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. It is four department-specific forms wearing one link.

Each follow-up earns its place. The department selector is the axle, and each follow-up field is 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. All four follow-ups are optional and short, so 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 did not take.

What we didn't build. A separate form per department linked from a hub page. That pattern works, but it multiplies maintenance and splits your response history four ways. Org-chart labels like "Level 2 Technical Support" stay out too: visitors think in needs rather than in your reporting lines, and four plain labels cover most companies.

Who runs one door for four teams. 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.

Rename, route, and point one link at it. Rename departments and rewrite each follow-up in the Logic panel, where 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, and 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. Business cards, email signatures, the website footer: everything points at a single URL, and the form does the sorting. That is the whole trick, and it never stops being useful.