Customer Support
Reception and Call Answering for roofing companies
Nearly everything that goes wrong in a roofing business leaves a trace somewhere. A call nobody answered leaves none at all.
The record a ringing phone should leave
Three things, and the third is the one that changes how a week runs. Every inbound call answered against a standard you wrote down rather than against whoever happened to be free — the same greeting, the same questions, the same thresholds for what gets escalated immediately.
The caller identified and their reason captured in their own words, not summarised into a category. “Water in the upstairs bedroom since Tuesday” and “roof enquiry” are the same row in a system and completely different things to the person who has to act on them.
And a handoff to a named person, with the next step written next to it. Not into a shared inbox, not into a general queue — to somebody. That last detail is what separates a log from a record that produces work.
A missed call writes nothing down
Consider what happens when other things go wrong. An invoice that never went out is sitting in the system unsent. A permit nobody applied for leaves a job that cannot start. A crew that did not arrive generates a phone call within the hour. Each failure produces its own evidence, which is why each one eventually gets managed.
A call that rang out produces nothing. There is no row in the CRM, no entry in the pipeline, no note anywhere, and the caller does not tell you they tried. From inside the business the week looks exactly the same as a week in which every call was answered. The quantity is not merely unmeasured — without something that counts arrivals rather than outcomes, it is unmeasurable.
The asymmetry explains why this is usually the last function an owner fixes, long after bookkeeping and dispatch. Every other problem argues its own case. This one has to be believed on principle first and counted second, and most people quite reasonably want it the other way round.
So the deliverable that matters most is not a friendlier greeting. It is the existence of a denominator: arrivals, not just conversions, so that for the first time the thing that was invisible has a number attached to it and can be argued about with evidence.
Whose consent a recording needs
Owners who start counting calls almost immediately ask about recording them, and the answer is a jurisdiction question rather than a preference. The federal floor sits at 18 U.S.C. 2511, which provides that it “shall not be unlawful under this chapter for a person not acting under color of law to intercept a wire, oral, or electronic communication where such person is a party to the communication or where one of the parties to the communication has given prior consent to such interception unless such communication is intercepted for the purpose of committing any criminal or tortious act in violation of the Constitution or laws of the United States or of any State.” The closing qualifier is part of the provision and is quoted with it.
A state may require more, and one worked example of that class is Florida Statutes section 934.03, which permits interception “when all of the parties to the communication have given prior consent to such interception.” One party against all parties is a genuine difference, and it turns on where the people on the call are rather than on where the business is.
Which is why recording is an instruction we hold rather than a determination we make. You settle the rule with your own adviser; the desk applies it consistently, notes it in the answering standard, and does not quietly change it because a different state came up. The counting works without recording anything at all, so nothing about the number depends on resolving this first.
This describes two statutes to show that the requirement differs. It is not legal advice, it makes no determination about your calls or your obligations, and the rules vary by state and by the location of each party to a conversation. Those questions belong with your own counsel.
Upstream of everything else in the department
This is the first desk in Customer Support, and the boundary for the department as a whole — what may be received, qualified, scheduled and logged, and where outbound calling begins — is set out there rather than repeated here.
What owners ask about the first ring
How would we even know what we are missing now?
You would not, and that is the honest starting point rather than a sales line. The first thing this desk produces is a count — how many calls arrived, how many were answered, how long the rest waited before giving up. Almost every owner is surprised by the second number, not because the business is badly run but because nothing in the current setup was ever asked to produce it.
Does the caller know they are not speaking to your office?
They reach your company, in your company name, working from your rules. Nothing is framed as a third party because functionally it is not — the same system, the same booking constraints, the same note the next person reads. If a caller asks the question directly they get a straight answer.
What gets written down about a call?
Who rang, on what number, what they wanted in their own words, what they were told, and who now owns the next step. The last of those is the one most often left out, and it is the one that decides whether anything happens. A note with no owner is a note that ages.
Do you record calls?
Only if you tell us to, and only on the rules you set with your own adviser. Whether a recording is permitted turns on where the parties are and whose consent is needed, and that is a legal question about your business rather than a setting in a system. We hold the instruction; we do not make the determination.
What happens to a call that needs a real answer about a roof?
It is qualified and routed rather than guessed at. The address, the age of the roof, what the caller has already noticed, whether there is active water coming in — captured before the handoff, so the person who does know the answer spends their time on the answer instead of on collecting the question.
We already have voicemail. Is that not the same thing?
It records that somebody chose not to leave a message, which is most of them. The gap between a line that is answered and a line that offers to take a message is not politeness; it is whether an event enters your records at all. A message left is a lead. A message declined is nothing, and nothing is not something you can review on Friday.
The recording statutes named here
- 18 U.S.C. 2511 — Interception and disclosure of wire, oral, or electronic communications prohibited — U.S. House of Representatives, Office of the Law Revision Counsel
- Florida Statutes section 934.03 — Interception and disclosure of wire, oral, or electronic communications prohibited — Florida Legislature
Count the calls you never heard about
A fortnight of arrivals against answers is enough to settle the argument in either direction, and it costs you nothing to find out which.