Answering the phone outside office hours is a strategy here, not a courtesy
A round-the-clock economy produces serious buyers at times a standard call schedule treats as noise.
A dealer coming off a swing shift researches a roof at one in the morning. A housekeeping supervisor starting graveyard makes calls at three in the afternoon. Neither is going to keep trying you at ten on a Tuesday.
Pull a month of call data by hour and by outcome before you change anything. Most roofers are surprised by where the misses cluster, and the answer is rarely the hour they assumed.
Then close the gap with the cheapest tool that works. An answering service briefed on your qualifying questions, an automatic text back on missed calls, or a booking form showing real inspection windows. Any of the three beats a voicemail box nobody checks until morning.
Whatever you choose, make the first response say something useful: what happens next, when a human calls, and what to have ready. Speed matters, but a fast reply that says nothing still loses to a competitor who answered live.
Ask what the roof is made of before anyone quotes a range
One question early sorts the inquiry, picks the right estimator and keeps your team from quoting numbers they will have to walk back.
Tile, foam or coating, shingle, low-slope commercial. The answers point to different crews, different lead times and very different money. Homeowners often do not know the term, so teach the intake person two plain follow-ups and a request for a photo.
Add the community name and the year the house was built. Together with the covering, those three answers tell an experienced dispatcher most of what the site visit will find.
Write the script down and hold everyone to the same order. Consistent intake is what makes your reporting mean anything later, and it is the only way to spot which question is losing people.
Never let a phone estimate become a promise. A range with the conditions attached is fine. A number without a site visit is a change order waiting to happen and a review waiting to be written.
Confirm the appointment the way a guard-gated community requires
Plenty of valley inspections fail before anyone climbs, because nobody arranged the access.
Gate codes, guest lists, call boxes and visitor passes are ordinary here. An estimator sitting outside a gate for fifteen minutes is a lost slot, a late arrival at the next address, and a homeowner who now thinks you are unreliable.
Build access into the confirmation. Ask how the estimator gets in, whether the owner needs to add a visitor, and get a mobile number that will be answered from the truck. Send it the day before and again the morning of.
Route by proximity, not by call order. The valley grid and the 215 make the difference between four roofs walked and two, and the second estimator hour of the day is the one that quietly disappears.
Track show rate as its own number. It is usually the largest single leak in a roofing pipeline and the easiest to fix without spending anything.
Your quote gets forwarded to an architectural committee, so write it to survive the trip
With associations as common as they are, the document that closes the job is often read by people who never met you.
Write the proposal so a homeowner can forward it without editing. Clear scope, materials named with specifications attached, color and profile, what happens to the existing covering, cleanup, warranty terms and your license and insurance documentation.
Say which parts of the submittal you prepare. Handing the owner a ready folder is a real reason to choose you, and it shortens the step that adds the most calendar time to a valley re-roof.
Keep association claims out of it. Requirements are set per community and change, so the proposal should point owners to their own documents rather than assert what a board will approve.
Then follow up on a schedule that assumes waiting. A check-in that offers to answer a committee question is welcome. A discount reminder while somebody waits on a volunteer board is not.
Cycle time, not close rate, is what an approval step quietly damages
Close rate hides the delay, and the delay is where valley roofing jobs actually die.
Measure the stages: inquiry, contacted, roof walked, proposal delivered, approval pending, signed, installed. Then measure how long each one holds a job. Aging is the diagnostic; totals only tell you something went wrong somewhere.
Expect the approval stage to be slow and plan the follow-up around it rather than treating every stalled job as lost. A proposal sitting in a committee queue is not the same as a homeowner who chose your competitor, and treating them alike wastes your best follow-up energy on the wrong file.
Count roofs walked per estimator day and contracts per roof walked. The first is a routing and access problem, the second is a proposal and pricing problem, and lumping them together makes both invisible.
Segment by area at least coarsely. Work in Henderson, in the northwest and in unincorporated Clark County can differ enough in drive time and permitting that a single blended number describes nobody.
Change one thing in the intake, then wait a full month before judging it
A single metro does not produce the sample size for small tests, so make big changes slowly and read them honestly.
Split testing a headline requires traffic that most roofing companies here will never have. Testing a rewritten phone script, a new confirmation sequence or a restructured proposal is different, because the effect is large enough to see without a statistics package.
Run one change at a time and give it a month or a full cycle, whichever is longer. Two changes at once tells you nothing except that something moved.
Listen to call recordings before you invent hypotheses. Twenty or thirty recordings usually reveal the exact question that ends conversations, and it is almost never the question you expected.
Write down what you changed and when. Six months of dated changes next to staged pipeline numbers is a better decision-making tool than any testing platform you could buy at this volume.
Questions we actually get
- We get plenty of leads but not enough signed jobs. Where do we look first?
- Show rate on inspections, then proposal follow-up. Most roofers here lose more jobs to appointments that never happened than to price. Count how many booked inspections turned into a walked roof, and how many proposals got a second contact within a week. Those two numbers usually explain the gap before anything else does.
- Is it worth paying for after-hours call answering?
- Look at your own missed-call data by hour before deciding. In a market with this many shift workers, the overnight and early-afternoon misses are often real buyers rather than wrong numbers. If the volume supports it, an answering service briefed on your qualifying questions is usually cheaper than the jobs it recovers.
- How do we follow up without pestering someone waiting on their association?
- Change the purpose of the contact. Offer to answer a committee question, supply another specification sheet, or confirm a color option. Useful contact is welcome; a discount reminder to somebody waiting on a volunteer board reads as pressure and tends to end the conversation.
- Should we run A/B tests on our website?
- Usually not at a single metro's volume, at least not on small changes. The traffic will not settle a headline question in a reasonable window. Test the things with large effects instead: the intake script, the confirmation sequence, the structure of the proposal. Change one, wait a full cycle, then judge it.
- What should our CRM actually track for this market?
- Covering type, community name, whether an approval step applies, access details for the appointment, and a timestamp on every stage. Stage aging is the report that matters here, because the local delay is procedural. Without dates on each stage you cannot tell a stalled job from a lost one.
