Software
Roofle management for roofing contractors
The first line of the job record was typed by a homeowner who has never met you, about a roof they have never been on.
Making an entry worth picking up
Checking what arrived: an address that resolves, contact details that work, a property that exists. Clearing duplicates before three people ring the same household, and clearing obvious junk before it teaches everybody to stop reading the list.
And preserving the part most likely to be lost — what the customer actually said. Their description sits beside the tidied record rather than being replaced by it, so whoever calls can hear how this person understands their own problem before saying anything about it.
A stranger starts the record before anyone answers
Every other record in a roofing company begins with one of your people. Somebody takes a call, walks a property, opens a job — and whatever is written first is written by a person who knows what the company needs to know.
Here the record opens before any of that. A homeowner sitting at home answers a few questions about a building they own, in their own words, with their own idea of what is wrong and how big it is. Then the entry exists, and everything your company subsequently does is layered on top of an account written by somebody with no reason to describe it the way you would.
That has a specific consequence, and it is not that customers are unreliable. It is that the record carries two different kinds of content which look identical on screen: facts that can be corrected, and the customer’s understanding, which cannot be corrected because it is not a claim about the roof — it is a claim about what they think they need.
Confuse the two and you lose the more valuable one. Tidying a description into internal vocabulary produces a cleaner record and destroys the only evidence of what the customer expects — which is exactly what the person making the first call needs in front of them.
An open door, and everything that walks through it
What it does well is remove the wait. A homeowner who wants an answer at nine on a Sunday gets one, and the company hears about them immediately rather than after they have tried somebody else. For a trade where speed of response decides a large share of the work, that is the whole argument.
What comes with it is everything else that fills in a form: people outside the service area, people comparing idly, the same household three times because the page was refreshed, and occasional nonsense. None of that is a fault of the arrangement — it is what an open door produces.
The judgement left to a person is which entries deserve what. That depends on the company’s capacity this week, what it is trying to sell, and where it will actually travel — commercial facts a desk applies and does not decide. Getting it wrong in the cautious direction is expensive and silent: a real customer filtered out never complains.
Your dashboard, your enquiries, your settings
A login you issue at a level you pick. Not a shared credential. Where entries are edited before anybody speaks to the customer, knowing who changed what is how a disputed record is untangled.
Enquiries stay in your account. No exported list, no copy at our end, nothing to hand back if this ends.
The configuration is yours. What the tool asks a homeowner, and what it tells them, are commercial decisions. We will say where they are producing unusable entries and implement what you choose.
Roofing Back Office is not affiliated with, endorsed by, or certified by any software vendor named on this site. All product names and trademarks are the property of their respective owners.
Agreeing what gets corrected and what is left alone
The opening work is a short convention: which fields are corrected on sight, which are queried, and which are never touched. The last category is the one companies have usually never considered, and it is where the customer’s own description belongs.
With it comes a response expectation — how quickly an entry has to be dealt with to still be worth something. That is a commercial decision, not a technical one, and it determines whether this arrangement produces work or a longer list of people who went elsewhere.
Duplicate and junk handling settles last, because the rules only become obvious once a few weeks of real entries have been worked. Deciding them in advance produces a filter tuned to what somebody imagined arrives.
What owners ask about entries they did not open
Do you answer the enquiries?
Handling what arrives — checking it, tidying it, routing it, chasing what is missing — is this desk’s work. The conversation that follows is a customer-facing function with its own arrangements. What matters at the join is that whoever picks up the phone is looking at an entry that has already been made sense of rather than raw text somebody typed at midnight.
What does a customer usually get wrong?
Not wrong exactly — approximate, and in their own terms. Their idea of the roof size, their description of the problem, sometimes an address that is nearly right. None of that is a complaint about customers; it is what a stranger describing their own property looks like. The mistake is treating it as a specification rather than as an opening statement.
Should we change what the entry becomes before we call?
Correct the facts, keep the words. Fixing an address or removing an obvious duplicate is housekeeping. Rewriting what the customer said into internal language destroys the one piece of evidence about what they actually think they need — and that is the thing worth having in front of you on the call.
How much of what arrives is junk?
Enough that clearing it is a standing task rather than an occasional one, and the specific mix differs by company and season, so any figure quoted at you is somebody else’s. What matters operationally is that junk and duplicates are cleared quickly, because an unfiltered list stops being looked at, and a list nobody looks at is the same as no list.
Does this connect to the system we already run?
Usually, and where it does the important question is what happens at the join — which fields carry across, what gets dropped, and whether the customer’s own description survives the trip. That last one is nearly always the casualty, and it is the field most worth protecting.
What do we keep if this ends?
Everything, because it was always in your account. What transfers is the working convention: what gets corrected, what gets preserved verbatim, what counts as a duplicate, and how quickly an entry has to be dealt with to still be worth anything.
Read what your last customer actually typed
If their own words are no longer in the record, the person who called them was working from a summary of a stranger.