Business Contact Form Template
A professional front door for your company — routes each enquiry to the right department and captures the context sales and support actually need.
Tell us a little about what you need and we'll route your message to the right team.
A business contact form has a harder job than a personal one: it is often the very first structured interaction a prospect, customer, or journalist has with your company, and the message it collects usually needs to travel to a specific team before anyone can act on it. This template is built around that routing reality.
Why these fields. The department dropdown is the backbone. Without it, someone in a shared inbox plays traffic controller for every message — with it, you can filter the responses view by team, forward in batches, or wire a webhook so each department's messages land directly in their own tools. Work email and company name are required because business follow-ups need both: replies go to a real mailbox on the buyer's domain, and knowing the company lets sales check fit before writing back. Company size is the one qualifying question worth its friction — it changes who should answer and how. A 200-person prospect asking about pricing warrants a different reply than a solo founder, and this single select tells you which is which without an interrogation.
What we left out. Phone number (async-first companies rarely cold-call back, and requiring it depresses completion), budget fields (premature at first contact and faintly hostile), and CAPTCHA walls (Formlark's invisible layered protection handles bots without taxing humans).
Who uses this. SaaS companies link it from the "Contact sales" button, agencies use the Partnerships lane to catch collaboration offers, and any team drowning in a shared info@ inbox uses the department split to end internal forwarding chains.
Make it yours. Rename departments to match your org — many teams add "Careers" or "Security" lanes. If one lane dominates, give it a dedicated form and link it from the ending screen. Add conditional logic so choosing "Press & media" reveals an outlet-name question, or "Billing" reveals an account-email field — the editor's Logic panel does this in a few clicks. Finally, connect a webhook per your ops stack: each completed enquiry can POST to Slack, a CRM, or a ticketing tool the moment it arrives, signed so you can verify it came from your form.
Measuring the front door. After a month of traffic, the department column becomes a diagnosis of your website rather than of your visitors. Billing enquiries dominating means account holders cannot find self-serve answers; a silent Press lane means either the newsroom page works or nobody is looking, and the message texts tell you which. Compare the company-size mix against your target segment each quarter — a front door that mostly admits the wrong-sized companies is a positioning problem no reply can fix.
A note on tone. The intro line promises routing, and the ending confirms it happened. That small loop — "tell us who this is for" → "the right team has it" — is what makes a company feel organized from the first click.
Frequently asked questions
Can each department get its own notifications?
Route with a webhook: filter on the department answer in your receiving tool, or create one form per team and link them from a hub page. Email notifications go to the form owner.
Can I show extra questions only for some departments?
Yes — open the Logic panel and add a rule like "When team is Press & media, show Outlet name". Conditional questions keep the form short for everyone else.
Does this work embedded on our website?
Yes. Use the inline embed for a seamless section, the iframe for maximum compatibility, or the popup for a "Contact us" button — all three snippets are on the Share page.
Is respondent data exportable for our CRM?
Every response is exportable as CSV with one click, and webhooks can push each submission to your CRM in real time.