CRM and Job Management
Customer Follow Up for roofing contractors
Saying you will get back to somebody takes a second. Everything that has to happen afterwards falls on a different day.
Commitments that exist outside a conversation
What was promised, captured in the words it was made in and attached to the job it belongs to. Paraphrase loses the thing you will be held to; “I will find out” and “I will call you Tuesday” are not the same undertaking.
An owner and a date on each one, chosen deliberately. A commitment belonging to everybody belongs to nobody, and a due date inherited from a default is a due date nobody has agreed to.
And the customer told the outcome. Not the record updated — the person informed, because they cannot see your record and have no way to distinguish handled from forgotten.
The gap between meaning it and doing it
Nobody in a roofing company decides not to follow up. The commitment is made sincerely, usually by somebody standing in a driveway or holding a phone between two other things, and at that moment they fully intend to do it. What happens next is not a change of mind. It is that nothing outside their memory is holding the promise, and their memory is about to be overwritten by the rest of the day.
This is why the failure is so hard to see from inside. Ask anybody whether they follow up and the honest answer is yes — they can each remember doing it. What nobody can see is the ones that did not happen, because a forgotten commitment leaves no trace at all. There is no queue of missed items to look at. The only person holding the evidence is the customer, and their evidence is a feeling about your company.
Roofing sharpens it in a specific way. Much of what gets promised is conditional and slow — I will check whether that is covered, I will find out what the lead time is, I will let you know when the crew frees up. Each depends on somebody else, which means it cannot be closed immediately, which means it must survive a gap. Anything that has to survive a gap needs to live somewhere other than a head.
So the work is not diligence and it is not attitude. It is a small mechanical habit: capture it when it is said, give it an owner and a date, and close the loop out loud. The people were never the problem.
What makes a follow-up land
Three things separate follow-up that works from follow-up that is technically performed, and none of them is effort.
Specificity does most of it. A promise recorded as “call back” is already half lost; a promise recorded with what the customer is waiting to hear can be completed by somebody who was not there. That matters because the person who closes it frequently is somebody else.
A due date has to be somebody’s decision. Dates that arrive by default — a week from now, because that is what the system suggested — are dates nobody chose and nobody defends. A date somebody set against what they actually expect to know by then is one they will act on.
Closing the loop is where it is usually lost. A loop is not closed when the work is done; it is closed when the customer knows it is done. That last step is skipped more than any other because internally it feels redundant — the thing is finished, the record says so. To the customer nothing has happened at all.
None of this touches what may be sent to whom or by which channel. Those are real constraints with real rules behind them, and they belong to the desks that own them and to your own decisions rather than to this page.
Downstream of everything the company says
This desk sits inside CRM and Job Management, and the department boundary — including how customer information is held and where administering it stops — is set out there rather than repeated here. What is particular to this page is that it collects the exhaust of every other conversation: promises get made in sales, in scheduling and on site, and all of them land here.
What owners ask after a complaint
We are not ignoring anybody. Why do we still get "nobody got back to me"?
Because those are the same thing from the customer’s side. Somebody said they would check and meant it, then the day ended. No decision was made to drop it; there was simply nothing outside a conversation holding the commitment. The customer cannot tell an oversight from indifference, and has no reason to try.
What is actually captured?
What was promised, in the words it was promised in, who owns it, and when it is due. The wording matters more than it sounds — "I will find out" and "I will call you Tuesday" create different expectations, and the second is the one you will be measured against.
Do you talk to our customers?
Where you want us to, and the boundary is worth stating. The channel rules — what may be sent, to whom, by which method — belong to other desks and to your own decisions. What this function owns is that the commitment exists somewhere findable with a date on it, and that somebody closes it out. Which of those closes happen by phone, by email or by you is yours to set.
Why does the customer need to hear the outcome?
Because from where they are sitting, a resolved issue and a forgotten one look identical until somebody says otherwise. Work that was genuinely done and never reported reads as neglect, and it is the most avoidable kind of dissatisfaction there is — the job was done and the credit was lost in the last ten seconds.
Our jobs are one-off. Is follow-up worth anything?
It is worth more, not less. A repeat business gets second chances; a roofing company mostly gets one, and what is left afterwards is what the customer says about you. The follow-up after the work is finished is the last thing that happens and disproportionately the thing that gets described to a neighbour.
What happens to promises nobody can keep?
They surface, which is the useful part. A commitment with an owner and a date either gets done or becomes visible as something that will not be, and both are better than a slow fade. Where the honest answer is that it is not happening, telling the customer that is a far smaller cost than letting them keep waiting.
Every rule here is about the channel
There is no statute standing behind this page, and reaching for a nearby one would leave a reader worse informed than an honest blank. The reason for the absence is worth more than the citation would be. Following up with a past or prospective customer is not itself regulated. Every regulated aspect of it is about the CHANNEL rather than the practice, and each channel is already argued by a sibling: telemarketing scope by customer-support/speed-to-lead-response, the delivery restrictions by the customer-support department page, commercial email by marketing-support/email-marketing, and message classification by customer-support/appointment-scheduling. Asking for a review after a job is argued by marketing-support/review-reputation-management. There is no document left that is about following up rather than about how you reached somebody, and reaching for one of the above would be leaf-to-leaf axis collision.
What it is held to instead: Every promise made to a customer has an owner and a date, and the customer hears the outcome rather than being left to infer it.
Where the regulated part of this subject lives: customer-support/speed-to-lead-response for contact scope; marketing-support/email-marketing for commercial email.
Ask what you promised somebody last week
If nobody can produce the list, the ones that were kept were kept by memory, and memory is not a system.