A Callback Request Instead of a Form

Two kinds of enquirer

Some people prefer to write, on their own time, with the details laid out.

Others will not, either because the problem is hard to describe in writing, or because they would rather talk, or because they are on a phone and typing a paragraph is genuinely awkward.

The second group will call you if they are ready to, and will leave if they are not, since a form is the only alternative offered.

A callback request captures them at a lower commitment than a call and a lower effort than a form.

Why it converts

• Two fields rather than six.
• No need to describe the problem in writing.
• Lower commitment than telephoning now.
• Works on a phone without a keyboard.
• Suits people who are not ready to explain.

The third is underrated. Somebody uncertain about whether their problem is worth your time will hesitate over a call and will happily ask you to ring them, which puts the awkwardness on you rather than on them.

Keep it to two fields

Since the whole advantage is that it is not the form.

A number, and a good time to call, and nothing else.

Adding a name is defensible. Adding what the enquiry is about defeats the purpose entirely, since that is the thing they did not want to write.

A callback form that grows to five fields has become the contact form with a different heading, and it will convert like one.

Resist the pull to qualify at this stage, because the qualifying happens on the call, which is the point.

Ask when, not just whether

The field that makes the difference operationally.

A good time to call, offered as a few choices rather than a free text box: this morning, this afternoon, this evening, tomorrow.

That doubles the chance of reaching them, since a callback to somebody at work is a missed call and a wasted attempt.

It also tells you something about urgency, since somebody choosing as soon as possible is in a different situation from somebody choosing next week.

Keep the options few and specific to how you actually work, and include an out-of-hours option only if you will honour it.

State the response time and mean it

Since the whole thing turns on the callback happening.

Say when you will call: within the hour during working hours, or by the end of the next working day.

Choose a promise you can keep on a busy day rather than a good one, because a missed callback is worse than no callback option.

Send an immediate confirmation by message where you can, so the person knows the request registered.

And where you cannot reach them, leave a message saying you tried and giving a number, since a missed call from an unknown number is ignored.

Two attempts at different times of day is the reasonable effort, after which a message and a note is enough.

A worked example

A business had a six-field enquiry form and steady but modest submissions.

They added a small block above it: a number, a time preference with four options, and a line saying we will call you back within two working hours.

The form stayed exactly as it was.

Callback requests came in at roughly the same volume as form submissions within two months, and total enquiries rose by close to that amount.

The callbacks converted at a higher rate, which the owner attributed to being a conversation rather than an exchange of messages.

The people using it were plainly not the people who had been using the form.

Where to put it

Beside the form rather than instead of it, and on the same pages.

Two routes offered as alternatives, clearly labelled, rather than one route with a secondary option buried beneath it.

Say what each is for in a few words: send details and we will price it, or leave a number and we will call.

That framing helps somebody choose rather than making them decide between two similar-looking things.

On a phone, the callback should come first, since that is the context where typing is hardest.

Watch for the abuse case

Briefly, since it is the practical objection.

A two-field form is easy for automated submissions, so it will collect some rubbish.

Use whatever spam protection you already have on the main form, which usually covers it.

Expect a proportion of numbers to be wrong or mistyped, which is ordinary rather than malicious, and do not let it discourage the channel.

And where somebody requests a callback and then does not answer twice, that is a lead like any other rather than a problem with the mechanism.

Record them like any other enquiry

Since a callback that lives only as a notification is easily lost.

Put each request into whatever list your other enquiries go into, with the date, the number, and the requested time.

Otherwise a busy afternoon means a request seen on a phone, intended to be dealt with later, and forgotten entirely.

Recording them also lets you see how many arrive and what proportion convert, which is what tells you whether the channel is worth keeping.

And note the outcome, including the ones you could not reach, since a pattern of unanswered callbacks at a particular time of day is useful information about when to try.

The counter-case

Callbacks are not right for every business.

Where you need detail before a conversation is useful, a call without it wastes both parties' time and a form is genuinely the better route.

A business that cannot reliably return calls within a stated time should not offer this, since the failure is more visible than a slow email reply.

And in some markets people actively dislike being telephoned, which is worth knowing about your own customers before assuming.

Add two fields beside the form, promise a time you can keep, and watch whether the people using it are new.

What to add

1. A number field and a time preference.
2. Nothing else, including the reason.
3. Four time options, not free text.
4. A response time you can keep on a busy day.
5. An immediate confirmation message.
6. Two attempts at different times.
7. Place it first on mobile.

Step two is the one that gets eroded, since every field added to a callback request moves it back toward the form it was meant to be an alternative to.

The scheduled version of this is covered in booking a time instead of sending a message.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.