The call comes in at 7:40 in the morning. The van is already on the main road, nobody is in the office, and after the sixth ring the caller hangs up. For a business with a handful of people that is not an edge case: according to the German Federal Statistical Office, in 2025 3.5 % of all people in employment aged 15 to 64 were self-employed without any employees, and 30.8 % of the self-employed who do have staff regularly worked between 6 p.m. and 11 p.m. that year. Someone on a roof, kneeling in a customer's basement or writing quotes in the evening does not pick up the phone at that moment. The usual answer is a hold queue or voicemail. Both only move the problem: one costs the caller time, the other leaves a message nobody can act on. This article describes the third route — a callback request on your own website that takes twenty seconds to fill in, names a time window your calendar can actually keep, and lands in an inbox where it gets assigned to a person.
Why the call goes unanswered
The availability gap has a sober cause: a company's working hours do not line up with the hours in which someone can answer the phone. The German Federal Statistical Office measures that shift in its indicators on the quality of work.
The share of people in employment who had regularly worked in the evening within the previous four weeks stood at 14.4 % in 2025; among employees it was just under one in seven (13.4 %). Among the self-employed with staff it is 30.8 %, more than twice as many. At night, 4.3 % of people in employment worked regularly. That is not a statistic about diligence but about reachability: whoever sits at a desk in the evening spent the day on a building site — and that is where the phone was ringing.
These businesses are the normal case of the German economy, not the exception. According to the German Federal Statistical Office, in 2024 the vast majority of companies — 3.2 million, or 99.3 % — counted as small and medium-sized enterprises. The German Confederation of Skilled Crafts currently lists 1,038,126 businesses in the crafts registers and in the register of trades similar to crafts; that means 13.7 percent of all people in employment and 28.7 percent of all apprentices in Germany work in the skilled crafts. Almost none of those businesses has a switchboard. There is a line, there is a mobile phone, and there are hours in the day when nobody is holding either.
What the caller does instead is predictable. Around 95 % of the population in Germany aged 16 to 74 used the internet in the first quarter of 2025 (German Federal Statistical Office). Someone who cannot get through looks at the website — the same page where the number came from. If all it shows is that same number again, the road ends there. If it shows a short block that takes a name, a number, a one-line request and a time window, the contact is not lost, it changes channel. How often that switch happens can be measured; how to attribute phone calls to the website is covered in measuring phone calls from the website.
The Monday test
Hold queue, voicemail, callback: three routes, three effects
A hold queue is neither forbidden nor wrong in principle, but it is regulated and expensive in practice.
Section 115 (1) of the German Telecommunications Act permits hold queues only where one of five conditions is met; one of them applies when the call goes to a geographic number. For the landline number of a trades business a hold queue is therefore permitted. If the number does not fall under the first three cases, subsection 2 requires an announcement about the expected duration and the cost the first time the queue is used. The practical objection stands regardless: a hold queue needs someone to pick up at the end. In a business without a switchboard, that someone is missing on many days.
Voicemail is the common alternative and the weaker one. It records what is spoken, and that is rarely what the business needs: the name is mumbled, the number dictated too fast, the request told in three sentences without a place, a date or any sense of urgency. Whoever calls back is calling into the dark and often reaches nobody again. The callback request turns that around: it asks four things, it asks them in writing, and it settles when the call will come.
Scroll table sideways
| Aspect | Hold queue | Voicemail | Callback request on the website |
|---|---|---|---|
| What the caller does | Wait without knowing how long | Speak with no acknowledgement | Fill in four fields, read a confirmation |
| What reaches the business | Nothing until someone picks up | A recording without structure | Name, number, request and time window as text |
| Who handles it | Whoever is near the phone | Whoever listens to the mailbox | Whoever is assigned in the request inbox |
| Legal frame | Section 115 TKG, announcement duty depends on the number | No separate rule | Pre-contractual measure under Article 6(1)(b) GDPR |
| Cost when it goes wrong | The caller's waiting time | A call back into the dark | A call at the agreed time |
The difference is not technical, it is directional. A hold queue and voicemail ask the caller to carry the uncertainty. The callback request takes it off them by naming a point in time. That is the whole trick, and it only holds as long as the stated time is real. A window the business does not keep is worse than no window at all — then the caller has waited twice for nothing. How much that weighs on a bad day is visible in emergency work: roofer websites, storm damage and emergency duty describes the day when everyone calls at once.
What Section 115 TKG actually says
The callback block: four fields, not twelve
A callback block is not a second contact form. It has one purpose: to restore the connection that has just broken. For that it needs four pieces of information and no fifth.
Every extra field costs completion rate, especially on a phone where the keyboard covers half the screen. The general enquiry form with mandatory fields, attachments and a subject picker has its own place; how to build it is covered in contact forms that turn visitors into leads. The callback block sits next to it, not inside it.
- Name in one field, not split into first and last name — you will ask again on the phone anyway
- Phone number as a numeric field so the phone shows the digit keypad and not the letters
- The request in one sentence, single line, with a real example in the placeholder
- The time window as two to four options with real clock times, no free text
- One sentence about data protection with a link to your own policy, directly above the button
- A visible confirmation after sending that repeats the time window that was chosen
- No mandatory fields the caller does not have at hand — no customer number, no job number, no address
Request a callback
Name [ Meier ]
Phone [ 030 23125 471 ]
What is it about? [ Heating leaking, basement ]
When suits you?
( ) today 12:00 to 12:45
( ) today 16:30 to 18:00
(x) tomorrow 07:00 to 08:00
[ Request a callback ]
We will call inside the window you chose.
We use your details only for this callback.
Details are in the privacy policy.Choosing the time windows is the one place where the block needs care. Words like "morning" or "afternoon" help nobody, because both sides read them differently. Real clock times help, as long as they match the business: a roofer on scaffolding until 4 p.m. does not offer a window at 11 a.m. In XICflow the windows come from the same source as the opening hours, so one change carries into both displays; why that single source matters is covered in keeping opening hours and availability current.
The placeholder does the work
The time window: promise what the calendar allows
How fast a callback has to arrive is not only a question of manners.
The Court of Justice of the European Union touched on it in Case C-298/07, which concerned the mandatory details of a service provider: an electronic enquiry form can be regarded as a direct and effective means of communication where the provider answers consumer enquiries within 30 to 60 minutes. The ruling is about imprint obligations and not about a trades business calling back, but it gives a usable yardstick: an hour counts as immediate, a day does not.
For a business out on site, an hour is rarely realistic — which is exactly why the block offers a window and not a deadline. A window is an arrangement, not a promise: "today between 16:30 and 18:00" says when somebody has time, not that the phone will ring in ten minutes. Anyone phrasing it more tightly promises more than the day allows. What happens after the request arrives, and how a dependable response time is organised, is covered in responding to enquiries and response time.
Scroll table sideways
| Wording on the page | What the caller understands | What the business can keep |
|---|---|---|
| "We will get back to you promptly." | Within the next few minutes | Nothing in particular |
| "Callback within 24 hours." | Tomorrow around this time | Only with a cover rule for holidays and sickness |
| "Today between 16:30 and 18:00." | A span of 90 minutes | A window after the last appointment |
| "Tomorrow 07:00 to 08:00." | Before the working day starts | The hour before the first job |
| "We will call back as soon as we can." | At some point | Everything and nothing |
Three windows are enough in almost every business, and they come out of the working day rather than the calendar: the hour before the first job, the lunch break and the time after the last appointment. Offering more creates choice without gain. Offering only one loses everybody it does not suit. If it is clear on Friday that nobody is reachable on Monday, the Monday window is hidden rather than dressed up with an apology.
Monday to Thursday
07:00 - 08:00 before the first job
12:00 - 12:45 lunch break
16:30 - 18:00 after the last appointment
Friday
07:00 - 08:00 before the first job
12:00 - 13:30 break, then back on site
Company closures and public holidays
windows hidden
cover arrangement shown insteadA window without cover is a promise without funding
The message on the answering machine
The callback block only works if the caller hears about it. The most important place for that is the announcement they listen to anyway. The usual message names the business, asks for a message and ends.
It wastes the one moment when the caller's full attention is there. An announcement that points to the callback route turns a lost call into an enquiry — provided the address it names is short enough to keep in your head.
What the message names
The company name, one sentence about the situation ("we are out on site"), the pointer to the callback page with an address people can remember, and the request to leave a message anyway if it is urgent. Four sentences, not ten — anyone speaking longer loses half the callers before the end.
What the message leaves out
No clock times that change every week, no names of individual staff, no list of services. Everything that changes lives on the website and not on the tape; otherwise the announcement ages faster than anyone re-records it.
When it gets re-recorded
Before closures, when times change and when the callback address changes. One fixed date a year is not enough: every change to the time windows on the website is the trigger to put the script next to it and check it sentence by sentence.
The address in the announcement is the sticking point. A long address with slashes and hyphens cannot be carried over the phone. Short and speakable means the company's main address plus one word. Whoever reads it out reads it twice and slowly. Whoever sets it up also adds a redirect from the spelling listeners tend to type — with and without a hyphen, with and without an umlaut.
Hello, you have reached [company name].
We are out on site right now and cannot
take the call.
On our website, [address] dot de,
slash callback, you can leave your name,
your number and your request in twenty
seconds and pick a time window.
We will call back inside that window.
If it is urgent, please leave a message.information which allows rapid electronic contact and direct communication with them, including their electronic mail address,
On a phone: tap instead of copy out
A large share of calls starts on the website: somebody looks up the business, finds the number and taps it.
If the number sits there as an image or as plain text without a link, it has to be copied out by hand — and that is exactly where contacts break off. A tappable phone number is technically a link with the tel: scheme and costs nothing but care in how it is written. It belongs in the header, in the footer and on the contact page, not in one single place deep inside the site.
Right next to the number sits the second button: the callback request. That pair is the actual answer — call for everyone who wants somebody now, callback for everyone with no time to wait. On narrow screens both buttons sit under each other and are tall enough for a thumb to hit. What else goes wrong on small screens is collected in mobile usability for a business website.
- Store the number in international notation inside the link, display it in readable form
- Show the "call" button and the "request a callback" button together, never just one of them
- Keep both buttons in the header so they are reachable without scrolling
- On the contact page, also name the hours when a call actually makes sense
- After sending, lead to a confirmation page of its own that repeats the chosen window
The block belongs to the conversion group and is placed and labelled in XICflow like the other blocks in that group; the documentation for it sits under blocks: conversion and CTA. Anyone adding it puts it on the home page, on the contact page and on the service pages that usually get enquired about by phone — not on every page, or it loses its meaning. How a page comes together in this system is shown in how XICflow works.
Who works the inbox
A callback request is an enquiry with an expiry date. If the chosen window runs out without anyone calling, the damage is greater than before the block existed.
That makes assignment not a detail but the core of the matter: every incoming request needs a person, a deadline and a visible state. In XICflow callback requests run into the same request inbox as every other enquiry and are assigned there; how the inbox and team assignment work together is covered under requests and team.
- Make it visible: every callback request triggers a notification on a device somebody actually carries.
- Assign it: one person takes it, visibly for the others, so that two people do not call or nobody does.
- Check the window: if the chosen window does not fit, send a short message beforehand instead of letting it lapse.
- Call and record: note the outcome in two lines so the next person knows where things stand.
- Close it: completed requests leave the list, open ones stay visible until somebody touches them.
Who works the inbox depends on the size of the business. With three people it is whoever is in the van; with fifteen it is the office, with cover for the afternoon. Both work as long as it is settled and visible to everyone. Who gets which rights on the website and in the inbox is a decision of its own; maintaining a website as a team describes the roles behind it.
Why callback requests do not belong in a shared mailbox
Mandatory details and data protection
A callback block processes personal data: name, phone number, request.
The legal basis is usually Article 6(1)(b) of the General Data Protection Regulation — processing is lawful where it is necessary for the performance of a contract or in order to take steps at the request of the data subject prior to entering into a contract. A callback request is exactly that: a pre-contractual step at the request of the data subject. A consent tick box is usually not the right route for it; a clear sentence with a link to the privacy policy is.
Alongside that sits the duty under the German Digital Services Act. Section 5 (1) no. 2 requires information which allows rapid electronic contact and direct communication, including the electronic mail address. The callback block does not replace those details, it adds to them: the mail address stays in the imprint. Which texts a business website needs beyond that is collected in legal pages: imprint and privacy policy.
- One sentence above the button: what the details are used for and how long they are kept
- A link to the privacy policy right beside it, not only in the footer
- No fields that are not needed for the callback — every field has to justify itself
- Set a deletion period and keep to it: a completed callback request does not stay in the list forever
- Keep the mail address in the imprint, even when the callback route is the more convenient one
- Document your own assessment before passing anything to a messenger — see WhatsApp as a contact route
The retention period is where most businesses get vague. A callback request that turned into a job belongs in the job file and follows its retention rules. A callback request without a job has no business being there and is deleted after a defined time. Set that period once, name it in the privacy policy and store it in the inbox, and you will not have to explain it later.
The first week: what to do
- Day 1: call your own number at three times of day and write down what happens each time.
- Day 2: settle on three time windows the calendar really allows and agree them in the team.
- Day 3: place the callback block on the home page, the contact page and the two most visited service pages.
- Day 4: re-record the announcement, with the short address, spoken twice and slowly.
- Day 5: set up the inbox and assignment, and put the notification on a device somebody carries.
- Day 6: run a test from outside: request a callback, pick a window, set a timer, check the call arrives.
- Day 7: look at the numbers of the first week — how many requests, how many done inside the window, which windows were chosen.
After four weeks it becomes clear whether the block carries. Two numbers are enough: the share of callback requests completed inside the chosen window, and the spread across the windows offered. A window nobody ever picks gets removed. A window that is oversubscribed gets a second one beside it. If the site has plenty of visitors but neither calls nor callback requests arrive, the cause is usually somewhere else; visitors but no enquiries works through the usual reasons.
XICflow builds the callback block in, connects it to the request inbox and team assignment, and draws the time windows from the same source as the opening hours, so a change does not have to be maintained in three places. What that includes is listed under features; if you would rather talk through your own case first, use the contact page.
The sentence that makes the difference
Sources