A message that says "demo please" tells you almost nothing. You write back, wait, and write again. I would rather ask the useful things once, on one page, before anyone books time with me.
How it works
- Who they are: name, work email, company, role and team size.
- What they need: what they want to see, what they use now, and the problem in their own words.
- When: how soon they want to start, which weekdays suit them and their time zone.
The form does not hold a calendar slot. You read the request, then reply with your own link.
What a visitor's AI would ask
"What problem are you trying to solve?" Then "What do you use today?" Then "Which weekdays suit you?" It shows every answer and sends only after a yes. Read more about agent-fillable forms.
Good to know
Sort the CSV by start timeline first. People who say this month get a reply before people who are looking around. Visitors who are not ready for a call can join a webinar registration instead, or a waitlist for something you have not launched. A website feedback form shows why others leave. More ideas are in forms for SaaS and startups.
Questions
How do I tell a serious request from a casual one?
Sort the CSV by the start timeline and read the problem answer. A clear problem and a near start date deserve a reply first.
Can visitors pick a time on a calendar?
No. The form collects weekdays and a time zone as plain answers. You read them, then send your own scheduling link in your reply.
Can my team get a message for each new request?
Yes. Turn on notify_email to get a notice for each response, or add a signed webhook that passes each request to your own tool.