“Can someone give me a call?” A promising little sentence. Until it lands in a shared inbox, everyone assumes someone else has it, and the phone stays beautifully silent.
A callback request form collects a visitor’s name, phone number, reason for calling and preferred time, so a business can arrange a conversation. A time preference is a request, not a confirmed appointment.
Below is wording you can copy into your form builder, with a thank-you message that sets honest expectations. Then we’ll handle the part a form cannot do on its own: making sure someone actually follows up.
No email address held hostage for the template. We’re trying to start a conversation, darling, not a paperwork relationship.
Your callback request form template. Small, but charming.
Let’s find a time to talk.
Leave your number and tell us what you’d like to discuss.
- What should we call you?AlexYour name · required
- What number can we call?[Your phone number]Phone number · required. Include your country code.
- What would you like to discuss?A new website for our studio.Optional · a sentence is plenty.
- When would a call suit you?Tuesday afternoon · [time zone]Optional · preferred day and window, or “No preference”.
Our callback hours are [days, hours and time zone]. Your preferred time is a request, not a confirmed appointment.
Illustrative form · fictional answers · nothing is submitted
Open the editable wording
CALLBACK REQUEST FORM Heading: Let’s find a time to talk. Introduction: Leave your number and tell us what you’d like to discuss. [Business] will use these details to respond to this callback request. What should we call you? Your name · required What number can we call? Phone number · required. Include your country code. What would you like to discuss? Optional · a sentence is plenty. When would a call suit you? Optional · preferred day and window, or “No preference”. Timing note: Our callback hours are [days, hours and time zone]. Your preferred time is a request, not a confirmed appointment. [Explain your real response process.] Privacy: [Link your business privacy notice and review your builder’s required submission notices and agreement controls.] Button: Request a callback Confirmation after successful submission: Thanks, [name]. We’ve received your callback request about [topic]. Your preferred time is [day/window/time zone]. This is not a confirmed appointment. [Explain how and when your team will confirm or contact them.] Before publishing: Replace every bracketed instruction. Set required fields in your builder. Check phone formatting, privacy controls, opening hours, saved entries and the actual follow-up process. This is editable wording, not a working form or a Kibi import file.
Copy and download happen in your browser. This is wording to adapt, not a prebuilt form or an import file.
This is editable question wording, not a working form or an import file. Copy it into your chosen builder, replace every bracketed instruction and set which fields are required before publishing.
The preview uses fictional answers. The copy button leaves those answers out and gives you the questions, button label and confirmation text.
What should a callback request form include?
A callback form needs enough information to place a useful call. It does not need everything your sales team might eventually learn about the person.
Keep the fields that change the next conversation. If you will ask the same question again on the call anyway, check whether it belongs on the form at all.
| Field | What it helps you do |
|---|---|
| Name · required | Know how to address the person. A full legal name can usually wait. |
| Phone number · required | Place the requested call. Ask for a country code when your audience spans countries. |
| Reason for the call · optional unless needed to route it | Prepare or choose the right colleague. A short answer or a few useful options is enough. |
| Preferred day and time window · optional | Review when the person is likely to be available. Include “No preference” and explain whose time zone applies. |
| Email · optional, only if useful | Offer another way to discuss the callback time. Explain why you want it; a phone enquiry need not require two contact methods. |
| Location or service area · only when relevant | Check whether your team can help, for example when a home-service company serves particular postcodes. |
“Tuesday afternoon” is a preference. Not a booking.
Someone selects Tuesday afternoon. Your form says “Appointment confirmed!” Meanwhile, your only available colleague is on a ladder. We have accidentally arranged a small disappointment.
A callback request is an invitation to arrange a call. A booking system reserves an available slot. A quote-request form gathers the scope needed to discuss a price. Those are three different jobs.
Use “Request a callback” on the button. On the confirmation screen, say the request was received and explain how your team will handle the preferred time.
Only show that confirmation after the form has accepted the submission. If saving fails, show a useful error and an available alternative contact route. A cheerful thank-you cannot rescue an enquiry that never arrived.
Make the form friendly to thumbs, too.
The visitor may be between meetings, on a train or standing beside the thing they need help with. A callback form should not demand a quiet room and a laptop.
Use visible labels above the fields. Mark required and optional questions clearly, and place format help beside the relevant field. W3C’s form guidance explains why disappearing placeholder text should not carry the instructions.
Choose a telephone field where your builder supports it. Keep phone numbers as phone numbers, including a leading plus sign; do not treat them as quantities or insist everyone follows one country’s format.
Let people pick a broad window, or say “No preference.” If a precise time matters, ask for the day and time zone too. “After lunch” has a lovely personality and terrible international coordination.
Test the real published form on your phone: labels, keyboard, validation, error recovery and the confirmation message. Make sure the page stays usable when text is enlarged.
Permission for a callback. Not a surprise fan club.
Explain that the business will use the details to respond to this request, and link its privacy notice. Do not hide that explanation in a mystery checkbox labelled “I agree.”
A requested phone call is not blanket permission for promotional emails, texts or WhatsApp campaigns. Keep optional marketing choices separate, unticked and specific to what you intend to send.
If your builder or connected service requires a submission notice and agreement, keep those visible. The example wording here does not replace that service’s consent controls or your business’s privacy obligations.
Avoid asking for passwords, payment-card details or sensitive documents in a callback form. If someone needs to share more later, explain the appropriate route during the conversation.
Same little form. A different first conversation.
An agency prospect and a homeowner both want a call. The person making that call needs different context. Change the useful question, rather than growing the form into a questionnaire with commitment issues.
For a reception team, a question about appointment availability may be enough to prepare the callback. Leave sensitive details off the form.
| Business | Useful extra question | What it prepares |
|---|---|---|
| Design or marketing agency | What would you like to discuss? New website / campaign / ongoing support / not sure yet. | The right colleague can review the enquiry before calling. Leave the full brief for the conversation. |
| Home-service business | What service do you need, and which area is it in? | Check service fit before discussing a visit. A callback request does not book an inspection. |
| Small sales team | Are you asking about a new purchase or something you already use? | Separate a new sales enquiry from an existing customer question without making the visitor navigate your organisation chart. |
The form did its bit. Give the callback a person.
One request. What happens next?
A good time to say hello.
“Could you call on Tuesday afternoon?”
Review the reason and preferred window.
Give the request a named owner.
Agree a time and plan the callback.
The requested window is not a reserved slot.
The shop is shut. The request can wait safely.
“I’ve sent this after your team has finished.”
Confirm receipt only after the entry is saved.
Explain your actual opening hours.
Review and assign it when the team is back.
Do not promise an immediate call when nobody can make it.
A small change. Keep the context.
“Could we do Thursday instead?”
Read the latest message before calling.
Check the new window with the person handling it.
Update the planned follow-up and leave a note.
A human reviews the change; this illustration is not automatic scheduling.
Fictional examples of a team’s working routine, not product screenshots or a booking system.
The real test is not whether a notification arrived. It is whether someone can see the request, understand the preferred time and take responsibility for the call.
Use the three situations above as a team exercise. They are illustrative working habits, not a claim that Kibi automatically books calls, interprets time preferences or reschedules tasks.
In Kibi, bring the enquiry into the CRM through a supported form connection, review its details and plan the next follow-up in Today. Keep the requested window in context rather than silently treating it as a confirmed calendar slot.
Called at the agreed time and got no answer? A missed call is not a cue for a grand pursuit. Send a short note through the contact route they agreed to use, and offer an easy next step.
Team routing is available on Team and Growth. Decide who receives these enquiries and who checks requests that still need attention. A shared destination is useful; a named person is what makes the promise less slippery.
Two messages. Neither says “your call is booked.”
Use an on-page confirmation for every successful request. An email acknowledgement is an extra only when the visitor has supplied an email address for that purpose and your setup sends it.
These are manual, editable email examples, not a promise of an automatic Kibi sequence. Replace the brackets and use response expectations your team can keep.
Callback request received
Hi [name],
Thanks for asking us to call about [topic]. We have your preferred time as [day, time window and time zone].
[Explain your actual next step and response window.] The requested time is not confirmed yet.
If your availability changes, reply here with a better window.
[Your name] [Business]
Use only if this inbox is monitored and the visitor gave an email address for this conversation.
Offer another time
Hi [name],
Thanks for your callback request. We can’t cover [requested window], but I can call [alternative day, time and time zone].
Would that work for you? If not, send a window that suits you and we’ll work from there.
[Your name] [Business]
Offer a time someone can actually cover. Send it through an appropriate contact route the person has provided.
Put it on your website. Then try being the visitor.
On WordPress, build the questions in Kibi Forms and add the form to the relevant page. On Framer, build and connect the form using Kibi Forms for Framer, keeping the current Kibi Send notice and agreement controls.
Whichever builder you use, review the connection and field transfer rather than assuming a preferred time creates a CRM task. Send a clearly labelled test request on your own site and inspect what actually arrives.
Check the saved entry first, then any notification and the CRM record. Email delivery is a separate step. A form that looks fine from the front can still leave the person responsible without the information they need.
- Complete the form on a small phone. Can you understand every field without reading the placeholder?
- Try an invalid phone number and a missing required field. Does the error explain what to change?
- Check an after-hours request and a request from another time zone. Does the message set the right expectation?
- Inspect the saved details and connected CRM record. Are the phone number, reason and preferred window readable?
- Give the test enquiry to a colleague. Can they find it, identify the owner and plan the callback without asking you?
A few things worth clearing up before you call.
What is a callback request form?
A callback request form lets a website visitor ask a business to phone them. It usually collects a name, phone number, reason for the call and preferred time. Unless your system explicitly reserves an available slot, submitting it requests a call rather than confirms an appointment.
Which fields are required for a callback form?
A name and callable phone number are a useful starting point. Require a reason, location or time preference only when your team needs that detail to handle the request. Mark other fields optional and avoid making email compulsory when a phone call is the only reply route you need.
Should I ask for a preferred callback time?
Ask when your team can use the answer. Offer realistic windows, state the relevant time zone and allow no preference. Explain that your team will review the request. Do not describe the selected window as booked unless your setup actually reserves availability.
Can I use this callback request template in WordPress or Framer?
Yes. Copy the question wording into your builder and adapt it to your business. It is not a plugin import file or a ready-connected form. Configure required fields, submission notices, confirmation text and the connection, then test the published form on your own site.
Is a callback request permission to send marketing messages?
Do not treat it as blanket marketing permission. Explain how you will respond to this request and keep any optional marketing choices separate and specific. The template does not replace your business’s privacy notice, submission controls or applicable obligations.
Does Kibi automatically book the callback?
This guide does not describe an automatic booking system. Review the request, agree a workable time and plan the follow-up in Kibi’s Today view. A preferred time submitted through a form should not be presented as a reserved appointment.
Is the template free, and is Kibi CRM free?
The question wording in this article is free to copy and adapt. Kibi CRM has a 14-day trial, then a paid plan. The template is not a free CRM subscription. Check the pricing page for current plans and included features.
Nice form. Now keep the promise behind it.
Before you polish the button for another afternoon, follow one test request all the way through. Can someone find it, understand it and make the next call?
That is where Kibi CRM earns its place: the enquiry, the responsible person and the next action in one working routine. Less “did anyone call?” More “I’ve got this.” Attractive behaviour, honestly.
Start a 14-day trial, connect a supported source and run that small test with your team. You do not need a hundred enquiries to find out whether tomorrow’s callback will be easier.
Try one thing on the next enquiry.
Pick a change your team can use tomorrow.