Contact Sales and Demo Request Form UX
A demo request is the highest-intent action on a B2B site, and many forms treat it like a support ticket. Ask a few useful questions, let people book a time immediately, and tell them exactly what happens next.
What makes a good demo request form?
A good demo request form asks for name, work email, company and one qualifying question, then lets the person book a time straight away instead of waiting for an email. The confirmation screen says who they’ll meet, how long it takes and what to prepare. Every extra step between the form and the calendar loses meetings.
What does the flow look like?
The mock-up shows the three screens of a fictional demo flow: a short form with one qualifying question, a booking step for qualified leads, and a confirmation that sets expectations.
See Ledgerly with your own approval workflow.
Times shown in your time zone (EDT).
For visitors who don’t qualify for a sales call, route them to a trial, a recorded demo or a pricing page, rather than a dead end. Nobody who asked for help should leave with nothing.
Which fields should you ask for?
Ask for what sales needs to prepare the call and route the lead, and enrich the rest. Phone number, job title and company size can often be found or asked during the call. Each required field should have a reason you could explain to the person filling it in.
| Field | Keep? | Why |
|---|---|---|
| Name and work email | Yes | Needed to book and follow up |
| Company | Yes | Needed to prepare and route |
| One qualifying question | Yes | Routes to sales or self-serve |
| Phone | Optional | Many buyers won’t give it; ask later |
| Job title, company size | Usually not | Enrich from public data or ask on the call |
| ‘How did you hear about us?’ | Optional | Useful for attribution, never required |
What should the confirmation screen say?
The confirmation should say the meeting is booked, when and with whom, what will happen in the call, and how to reschedule. Send the same details by email with a calendar invite. Errors on the form must be clear and specific, which is also an accessibility requirement: WCAG 3.3.1 says detected input errors must be identified and described in text (W3C on error identification). Wording examples are on error messages and microcopy.
A 20-minute call with Maya from our team. A calendar invite is on its way to sam@acme.example.
Measure the share of form starts that become booked meetings, and the share of booked meetings that happen. A high no-show rate usually means the confirmation and reminders are too thin.
Let buyers book, not wait.
A booked meeting on the confirmation screen beats a ‘we’ll be in touch’ email every time.
Where should the demo form appear?
Put the demo action in the main navigation and at the end of key pages, and use the same short form everywhere. On the homepage, it is usually the primary or secondary action; see homepage UX. For self-serve products, the trial signup may be the better primary action, covered on signup form design. Landing page forms for paid campaigns are covered in traffic but no signups. Full checks are in the UX audit checklist.
Frequently asked questions
How many fields should a demo request form have?
Usually four: name, work email, company and one qualifying question.
Should demo forms include a calendar?
Yes, for qualified leads. Booking in the same session catches buyers while intent is highest.
Should I require a phone number on a demo form?
Usually not. Many buyers won’t give one; make it optional or ask during the call.
What should a demo confirmation page say?
When the meeting is, who it’s with, what will happen, what to prepare and how to reschedule.
What should happen to leads who don’t qualify for a demo?
Route them to a trial, recorded demo or pricing page instead of a dead end.
How do I reduce demo no-shows?
Clear confirmation, a calendar invite, a reminder email and something useful to prepare.
Sources & further reading
Standards and platform rules change. These sources let you verify the current requirements directly. All screens shown are mock-ups of fictional products.