‘Request more information’ usually means a specific artefact: a datasheet, an accessibility statement, a capabilities pack. The form should ask for that topic up front so US and UK teams are not mailing the entire Dropbox.
Marketing ops or sales enablement.
Do not let it be optional.
Self-serve what you can.
So the next person does not resend the wrong version.
An information request is narrower than a sales inquiry: they believe the answer is a file or a fact pack. US buyers want spec PDFs; UK buyers may want the same plus a sustainability or accessibility statement. Naming the topic is how you stop sending the brand book to someone who needed torque values.
Gated content tools exist. This form is for sites that still email a human the right PDF.
Vague ‘info’ requests generate the wrong attachment and a second email.
Once you know the top five topics, replace the text field with a select on the form.
A public downloads page is kinder. A form is for things you will not post.
Human sends the right file the same day.
Use it for anything that is not sensitive.
Fine at scale. This form is the lightweight version.
Route those to the sales contact form instead.
Resources pages are static lists of PDFs plus this form for the rest. Publish the form at the bottom.
Regional specs: ask whether they need US or UK versions in the topic field rather than shipping both.
Possible later with automation. v1 can be a human.
Do not attach them to an auto-reply. Verify first.
Policy in copy. Trade-only packs should say so.
Ask which year or SKU in the message.