A storm front passes through overnight, by morning a dozen roofs in the area are missing tiles - and within the same hour the enquiries arrive: by phone, on the answering machine and through the website. Insured storm and hail claims in German property insurance added up to around one billion euros in 2025, spread across roughly 479,000 reported claims at an average of about 2,100 euros (GDV). For a roofing business, days like these do not decide whether there is work, but which part of it lands in your own order book. This article describes how a roofer website cleanly separates the three concerns of storm damage, roof check and renovation, which fields the emergency form needs, what you may write about insurance - and how availability outside office hours is organised without anyone sitting at a computer at night.
Why the wave of orders starts in September
Insurers' claims statistics describe the annual rhythm of the roofing trade more precisely than any market study.
In German property insurance, natural hazards caused around 1.4 billion euros of damage in 2025, of which around one billion euros came from storm and hail (GDV). The number of claims was roughly 479,000, with an average claim of about 2,100 euros (GDV). The association explicitly classes these events as ones that hit many buildings at the same time while often leaving rather small and medium-sized damage to roofs, facades or windows. That is exactly the operational pattern: not one large project, but two hundred small jobs in a fortnight. Taking them on does not require an extra sales channel, but a website that shows the right thing at the right moment. The foundations are the same as for any trades business generating enquiries through its website - the weighting is different.
What counts as a storm day has been defined soberly by the German meteorological service: a day on which the maximum wind speed reaches or exceeds 8 Beaufort, measured as the highest ten-minute mean of the day (Deutscher Wetterdienst). Above that threshold the work begins for the roofing trade, and from September such days become frequent. How large the wave turns out to be varies considerably, though: in 2024, insured storm and hail claims in property insurance still stood at 1.9 billion euros (GDV), almost double the following year. For planning purposes that means two things. First, the scale of the season cannot be predicted, but its start can. Second, it pays to set up the website before the season rather than during the first storm week, when no one has a spare hand anyway.
Business sizes tell the same story. 1,038,126 businesses are entered in the German trade registers and in the register of trade-like occupations, employing around 6 million people (ZDH). 99.3 percent of all companies in Germany count as small and medium-sized enterprises (Statistisches Bundesamt). The roofing trade is one of the regulated crafts and appears under number 4 of Annex A to the German Trade and Crafts Code (Handwerksordnung). A business with eight people has nobody free during the storm week to sort the inbox - the pre-sorting has to be done by the website. Anyone who also wants to be found in the neighbourhood should have settled local visibility for local businesses beforehand.
Three concerns that land on the same website
On a roofer website, three people with very different senses of time meet. One has had a bucket standing in the loft for an hour and needs a phone number.
The second has been wondering since the last storm whether the roof should be looked at before winter, and is calmly comparing three firms. The third is planning a re-roof with insulation, is collecting quotes and expects a lead time. These three concerns need different pages, different forms and different commitments. A single contact form serving all three serves none of them properly in practice. How two customer groups can be separated on one website without duplicate upkeep is shown in the article on private and business customers on one website - the same mechanics apply to callout, roof check and renovation.
Storm damage today
Time frame in hours. The visitor is looking for a phone number, not a service overview. Callout page with the number, availability times, a short form and one sentence about the first-aid cover.
Roof check before winter
Time frame in weeks. Here the date, the price range and the scope of the visual inspection are what count. A dedicated page with a booking request and a sample report makes the offer tangible.
Renovation and re-roofing
Time frame in months. References, build-up, materials and the process from site visit to handover. The form may well be longer here, because the lead time allows for it.
The separation does not begin on a subpage but on the home page. Someone arriving at night with a wet loft does not scroll through a service overview but looks for a number within the first two screen heights. Three clearly labelled entry points side by side - report storm damage, book a roof check, request a renovation quote - handle that sorting without a word of explanation. The same pattern works in other trades; the plumbing and heating website with heat pump enquiries separates breakdown, servicing and new installation along the same logic. What matters is that the three entry points look equally important: as soon as one of them is styled as the main button, the wrong enquiries end up there too.
The callout page and its first three lines
A different standard applies to the callout page than to the rest of the website.
It is read on a phone, often in the dark, frequently by someone holding a bucket at the same time. 86 percent of people over 16 in Germany use a smartphone (Bitkom); at night it is in practice the only device within reach. How much depends on response time is shown by a study of 2,241 companies: the average response time to online enquiries was 42 hours, and 23 percent of the companies did not respond at all (Harvard Business Review 2011). In a separate analysis of 1.25 million contacts, firms that made contact within an hour were nearly seven times as likely to reach a qualified conversation as those that responded an hour later (Harvard Business Review 2011). The process behind the send button therefore matters more than the form in front of it - described in detail in the article on response time and the enquiry process.
- The number as a dial field, not as an image. It sits within the first screen height, as a tappable phone link, at a size you can hit without zooming. A number inside a graphic is worthless on a phone.
- The time window in plain words. "On call Mon to Sun, 6am to 10pm" says more than "here for you around the clock". Anyone calling outside those hours should know where they stand rather than speaking into a silent mailbox.
- The service area with a radius. "Storm callouts within 30 km of Hildesheim" saves you and the caller the conversation that would end in a refusal anyway.
- One sentence about first-aid cover. What the business does first in an emergency - temporary covering, tarpaulin, securing loose parts - and what about it is provisional. That sets the expectation before it forms.
- The route for everything else. A pointer to the roof check and renovation catches the enquiries that are not emergencies but have landed on the callout page.
The number belongs behind the button, not inside an image
For that to hold up, the page has to be fully operable on a phone: tap targets large enough, text legible without zooming, no element covering the phone number. The article on mobile usability lists the points that come up most often. And the underlying attitude matches what other sectors have to solve in exceptional situations: how a website leads people in a stressful moment straight to the right person is described in the article on immediate availability in a bereavement. The tone differs, the requirement does not: short routes, clear hours, no form journey in front of the phone number.
The storm damage form: short, but robust
Every field that has to be filled in at night is a field where someone abandons the process.
How strongly field count and abandonment are linked has been measured by the Baymard Institute for checkout flows: most sites there would manage with eight fields, yet the flows examined in 2024 contained 11.3 fields on average (Baymard Institute). Those figures come from an e-commerce setting and cannot be transferred one to one to a trades form - the direction still holds: every additional mandatory field costs completions. For the storm damage form that means distinguishing between two kinds of information. There are details without which you cannot set off, and details the conversation will clarify later anyway. Only the first kind belongs in the form. Which fields usually carry their weight is set out in the article on contact forms and their evaluation.
- Address of the property - not the billing address. Without it no job scheduling is possible.
- Phone number as the only mandatory contact field. An email address alone does not help at night.
- Type of damage as a choice of four to six entries: tiles loose, roof leaking, flashing or gutter damaged, storm damage to dormers, tree on the roof, other.
- Urgency in three levels: water is currently entering the building, danger to passers-by, can wait until tomorrow.
- Photo upload with multiple selection. Two phone pictures often save the first site visit and shorten the quote.
- A free-text field, not mandatory. Those who want to write, write; those who do not are not held up.
Scroll table sideways
| Feature | General contact form | Storm damage form |
|---|---|---|
| Mandatory fields | Name, email, subject, message | Property address, phone, type of damage, urgency |
| Salutation and subject | mandatory | dropped - the type of damage replaces the subject |
| Photos | not provided for | multiple upload straight from the camera |
| Confirmation | "Your message has been sent" | time window for the callback plus the callout number in the text |
| Recipient | one shared mailbox | shared mailbox plus the mobile number of the on-call staff |
| Availability | office hours | the time window sits above the form, not in the legal notice |
The confirmation page is the most underestimated text in the whole journey. It should repeat what the business is doing now, by when it will be in touch and which number to call yourself if in doubt. Anyone wanting to know how many people skip the form route entirely and reach for the phone instead will find the measurement method in the article on calls from the website. During the storm week that ratio shifts noticeably towards the telephone in practice - one more reason for not hiding the number behind the form.
Roof check: the plannable counterpart to the callout
The callout service fills the week after the storm. The roof check fills the weeks before and after - and it is the one offering in the roofing trade that can be scheduled completely.
As a product in its own right it needs three details that have to appear on the website: what is checked, how long it takes and what it costs. A roof check without a price range gets enquiries but is rarely booked, because the enquirer cannot judge the order of magnitude. If the range is stated as a span with conditions, half the follow-up questions are settled in advance. If the roof check follows a fixed process, online booking directly on the website is worth adding as well, because the callback coordination then disappears entirely.
- Put the scope of the visual inspection in writing: covering, gutters and downpipes, abutments, penetrations, roof windows, verge and ridge.
- State the duration and the price range, together with the conditions under which both change (roof area, pitch, access, cherry picker).
- Show an example of the written report - anonymised, two pages, with photos and a traffic-light rating.
- Name the period in which appointments are available, and keep it up to date once slots are taken.
- State what happens after the report: a quote on request, no automatic order.
- Offer the follow-up check after two years right away, instead of selling it separately later.
The roof check is the diary from which winter gets filled
Insurance, costs and what does not appear on the website
After storm damage, the second question after the phone number is the question of who pays.
Restraint is the right stance here: damage from storm and hail is as a rule automatically covered in German residential building insurance, whereas flooding, heavy rain and further natural hazards require an additional module that only around 59 percent of residential buildings in Germany had included in 2025 (GDV). Your website may explain that difference, but it must not state whether a specific claim will be settled - that is a matter for the insurer, not for the firm carrying out the work. A factual paragraph on documentation, claim notification and cost estimates is valuable; wording that holds out the prospect of coverage is risky. How prices can be presented without committing yourself is shown in the article on showing prices on your website.
Your own qualifications belong in equally restrained wording. The roofing trade appears under number 4 of Annex A to the German Trade and Crafts Code and is therefore a regulated craft (Handwerksordnung); the entry in the trade register and the master craftsman title are verifiable facts and may be named. What cannot be verified, and is therefore open to challenge, are commitments about outcomes, deadlines or durability that depend on weather and building fabric. Phrase things in time frames and conditions rather than assurances: "as a rule on site within 24 hours, provided wind speeds permit the job" holds up, a blanket promise does not. How references and credentials can be shown in a legally sound way is set out in the article on showing client references and logos.
A callout page promises no rescue; it states a number, a time window and a radius. Everything beyond that is decided by the weather.
Organising availability outside office hours
The most common mistake on callout pages is not a missing number but a commitment the business cannot keep.
"Available 24 hours" goes onto the page quickly and holds precisely until the first call at three in the morning that nobody answers. A stated time window with an honest rule for everything outside it is more robust. Part of that is making sure the hours on the website match those in the telephone announcement and in the business profile; the article on opening hours and availability kept current describes how these details are maintained in one place and shown everywhere.
- An on-call rota with names and a plan. Who is on duty when, and who takes over when that person is up on a roof? The rota belongs in the business, the time window on the website.
- A second recipient for every emergency form. A copy to a mobile number or a second mailbox prevents an enquiry from sitting untouched on a sick day.
- An honest message for the fringe hours. "Between 10pm and 6am we do not check the mailbox. In case of imminent danger, contact the fire service." That is not a weakness, it is information.
- A weekly look at deliverability. Form emails tend to land in the spam folder exactly when the volume jumps - which is to say, during the storm week.
- An end date for seasonal notices. A banner reading "Storm damage: on-call service active" does more harm in March than it did good in October.
And then comes the part few people talk about: the weeks after the wave. Once the emergencies have been worked through, the volume of enquiries drops visibly - not because the need disappears, but because the urgency has gone. That is exactly when the website becomes the tool that adds capacity utilisation: with the roof check, with references from the fresh jobs and with a visible booking option. How such a phase can be used is described in the article on the website during a quiet period. Conversely, when the order book is overflowing the website needs different signals so that the right enquiries remain - which is the subject of the article on the fully booked order book.
How XICflow maps the storm season onto the website
The obstacle in a roofing business is rarely the insight but the timing: the website would need to be finished in August, and in August the crew is on the roof.
XICflow therefore builds the structure once, in full, and hands it over so that upkeep afterwards comes down to a few steps. That includes the three separate entry points on the home page, a callout page with a phone link and a stated time window, the storm damage form with photo upload and urgency levels, plus a dedicated roof check page with a booking request and a price range. Which of those fits your business is settled fastest against a concrete example - the services overview shows the scope.
Technically, underneath sits a statically delivered site that still loads quickly when a storm front suddenly brings ten times the traffic. Form emails go to several recipients, the confirmation message is individually worded and states a time window, and deliverability is set up rather than hoped for. How such a project runs is described under how it works; finished examples from various trades can be found in the demos. What the website does not replace is the internal agreement about who has the phone at night - that decision stays in the business, the website only makes it visible on the outside.
Sources and Studies