Customer Support

Customer Service for roofing companies

Nobody rings a roofing company for a chat. They ring because of something somebody there already told them, and the first job is finding out what that was.

Three things that arrive together

The promise the caller is holding you to, retrieved from the job record rather than reconstructed on the call. Not what the contract technically says — what was actually said, by whom, and when, because that is the thing being disputed and the contract is rarely where it lives.

A resolution path with an owner, routed by who is able to decide it — frequently not the person who answered, and occasionally you. A question that costs money is a question for somebody with authority over money, and pretending otherwise just adds a call.

The loop closed on the customer, who is told the outcome in words rather than left to work it out from the absence of further trouble. That is the cheapest of the three and the one most often skipped.

You inherit a commitment you cannot see

A roofing sale is made in a driveway or at a kitchen table. Somewhere in that conversation a person said something specific — that the gutters were included, that the crew would be finished by Friday, that the old satellite dish would go back up. Weeks later somebody rings about exactly that, and the entire question is whether it was said.

This is what makes the desk structurally different from the one that answers new enquiries. A new caller has no history, so the conversation creates the record. An existing customer arrives with a history that already exists somewhere and may not be written anywhere, and the desk is working from the wrong end of it.

The failure mode follows from that. It is not rudeness or slowness; it is a competent, courteous person asking a customer to explain their own job back to them. Which reads as indifference even when it is simply an absence of notes — and reads worst to precisely the customers who have already explained it twice.

So the work is unglamorous and mostly retrieval. Find what was agreed. Find what has happened since. Establish which of the two the caller is actually unhappy about, because those need different people. The step that ends it is telling them what will happen and by when.

What customer service produces, and what holds each piece up A horizontal spine carries three labelled artifacts produced by customer service: the promise the caller is holding you to, a resolution path with an owner, and a loop the customer heard close. Beneath each artifact a vertical line drops to a second tier naming what holds it up — respectively what was actually said, retrieved from the job record, routed by who can decide it rather than by who picked up, and the outcome told to the customer instead of left to be inferred. Across the foot of the diagram a separate band states the judgement this function does not make, which is whether to grant a request that costs you money. The diagram shows structure only and contains no figures. What this desk produces The promise the calleris holding you to A resolution path withan owner A loop the customerheard close what was actually said,retrieved from the jobrecord routed by who can decideit rather than by whopicked up the outcome told to thecustomer instead of leftto be inferred Every item above sits on the one below it. Outside this desk Whether to grant a request that costs you money
Each artifact on the spine has something underneath holding it up. That is the whole design: customer service is not an argument, it is a set of items that can each be traced to how they were arrived at, so that the second conversation starts from the record and not from scratch. The band across the bottom is the part that stays outside the work.

Some calls start a clock

One class of inbound call carries a date that matters independently of how the conversation goes. A buyer changing their mind about a contract signed at home is the common one, and it is governed rather than negotiated. The Federal Trade Commission’s rule at 16 CFR 429.1 prescribes the words that must appear on the notice a buyer receives: “You may CANCEL this transaction, without any Penalty or Obligation, within THREE BUSINESS DAYS from the above date.”

States write their own versions and they do not all count from the same event. One worked example is Florida Statutes section 501.025, under which the right runs “until midnight of the third business day after the day on which the buyer signs an agreement or offer to purchase.” Same shape, different anchor, and other states differ again.

The operational consequence is narrow and it is the whole reason this appears on a customer service page. When somebody calls to cancel, the date and time of that call is the fact. It is captured before anything else, it is routed rather than discussed, and nobody on the desk offers a view on whether the window is open — because that determination depends on the transaction, the state and the notice actually given, none of which is a desk’s to decide.

This describes a federal rule and one state’s statute to show that such windows exist and differ. It is not legal advice, it makes no determination about your contracts, your notices or any customer’s rights, and coverage and timing vary. Those questions belong with your own counsel.

The desk that hears the consequences

This function sits downstream of most of Customer Support, which carries the boundary for the department and the line on outbound contact. It is also where the results of every other department show up first, which makes it a useful place to listen.

What owners ask about their own customers

What can this desk actually settle without asking us?

Anything already decided and written down — what the contract covers, what the schedule says, what the warranty terms are, what was promised on a previous call. What it cannot settle is anything that costs you money or changes an agreement. Those come to you with the history attached rather than as a question you have to research first.

Our salespeople promise things verbally. How does that work?

Poorly, and honestly that is true whoever answers the phone. If a commitment exists only in one conversation between two people, the customer will describe it one way and the file will not contradict them. What this desk can do is make the pattern visible, because it sees every one of these arriving. What fixes it is upstream.

Do you handle complaints or just enquiries?

Both, and the distinction matters less than owners expect. Most calls that arrive angry are enquiries that were not answered the first time. The useful split is not complaint against question — it is whether the answer already exists somewhere in your records or has to be created by a decision.

What if somebody rings to cancel?

We capture it as a dated fact and route it immediately, without discussion. When a cancellation request was made can matter a great deal, and the worst possible handling is a helpful conversation that leaves no record of the date. That is a timing question with legal weight, and it is not one for a desk to interpret.

How do we stop hearing the same complaint from three people?

By closing the loop on the customer rather than on the ticket. The most common cause of a repeat call is that something was resolved internally and nobody told the person waiting, so they escalate — reasonably — to whoever will pick up. Telling the customer the outcome is a step, not a courtesy.

Will our customers notice the change?

The thing they usually notice is not being asked to explain their own history. Reaching somebody who already knows what job this is, what was agreed and what happened on the last call is a different experience from reaching somebody pleasant who has to start over. That is a records outcome more than a manner one.

Pick your last unhappy customer and read the file

If it does not tell you what was promised, the call was never winnable — and that is a records problem wearing a service problem’s clothes.