Build in public
Reworking the demo call form: a single step, clearer consent, and campaign source capture
Today was a small, focused day. I didn't touch the voice agent at all. All the work went into the demo call form on the website, the place where someone asks Dialessa to ring them so they can hear the agent for themselves.
What I built
The form used to walk visitors through several steps. Now they fill in all their details in a single step. I made a few changes along the way:
- One screen instead of several. Every field now sits in one place, so people can see straight away how much they're being asked for.
- Consent line moved. It now sits directly under the submit button, so the agreement is right next to the button people actually press.
- Wider consent wording. It now covers follow-up texts as well as emails.
- Campaign source capture. The form now records campaign source details, which makes it easier to see where visitors come from.
The changes went live on the website the same day.
What was hard
Nothing technically difficult happened today. The hard part was judgement, not code.
With a multi-step form, it's tempting to think you're making things easier by showing less at a time. But every extra step is another moment where someone can wonder how much longer this will take. I went back and forth on whether one longer screen would feel heavier than several short ones. In the end I decided it's more honest to show the whole form up front. People can see the full ask before they start.
The consent line was the other thing I thought hard about. It used to sit somewhere you could easily skim past. If someone is agreeing to be contacted, that sentence should be right next to the button that does the agreeing. Moving it there was a small change. Getting the wording right took more care, because I was widening it to include texts. I wanted the line to say plainly what people can expect from us, without burying it in legal-sounding language.
The numbers
- Working sessions with coding agents: 1
- Prompts typed: 3
- Commits: 2
- Deploys: 2
- Hours of active work: about 1
What I learned
Clear consent and a good conversion flow aren't in tension. Putting the consent line where people will actually read it also makes the form easier to understand. It just feels more straightforward.
Measure before you guess. Until today I had no good record of where demo requests came from. Capturing campaign source details doesn't change anything for visitors, but it means any future decisions about where to spend effort can rest on something better than a hunch.
Small days count. It was 1 session with 3 prompts and about an hour of work. On days like this it's easy to feel you haven't done much. But the demo form is where interest turns into an actual conversation with the voice agent. Tidying the path into that conversation is worth an hour.
Written from that day's build log: the work sessions, commits and deploys recorded for it.