Your inquiry form should know when to stop asking.

One form can serve several services without making every customer answer every question.

Stephen Stilwell · September 13, 2026 · 3 min read

A customer asking for a website redesign should not have to answer questions about your social media management package. Yet that is an easy situation to create when one inquiry form serves an entire business.

Start with the service

Tally’s documented conditional logic lets a form show or hide questions based on previous answers. The feature is available on its free plan. That creates a simple option for a small agency: ask what the person needs help with before asking for details.

Relevant doesn’t always mean necessary

A form can ask twelve relevant questions and still demand too much too soon. Separate what you need to decide the next step from what you can ask once a conversation begins.

For example, a deadline may help establish whether a project is possible. A complete inventory of existing content may be better collected after the initial discussion.

Check both paths before sharing

Try each service option. Change an answer halfway through. Check whether hidden required fields prevent submission. Read the confirmation message as a customer would.

These checks can reveal friction, but they do not establish that a shorter form improves conversion. That requires actual usage data.

The useful decision

The form is part of the customer experience. Give it the same attention as the page that brought someone there.

Source: Tally’s conditional logic documentation ↗