Garrison Phoenix HVAC Microsites for Owned Lead Generation

The 10 p.m. call from a Phoenix house that won't cool down

No-cool calls keep coming after sunset, because some summer nights in Phoenix barely cool off at all. Each area site needs an after-dark page that says who answers and when.

It's 10 p.m. in late July. A homeowner has watched the thermostat sit at 88 since dinner. The unit hums along, but the air from the vents feels like a warm breath. The kids have dragged their pillows onto the tile floor because it's the coolest spot in the house. Mom grabs her phone and types something short and a little desperate.

What happens next depends on the site we build for you. If it tells her who answers at night and whether a tech can still come out, she dials you and knows what to expect. If it shouts about round-the-clock service and a voicemail picks up, you've lost her and annoyed her in the same minute.

• Who picks up after 8 p.m., in plain words: a person, an answering service or a callback.
• The latest hour a tech can still head out, and what happens to calls after that.
• Whether night visits cost more, said the way your office already explains it.
• A couple of safe first checks, like the breaker and the thermostat batteries, signed off by your lead tech.
• A line telling anyone who feels sick from the heat to call 911 before calling any contractor.

Same size, same spot: where Phoenix draws its permit line on a change-out

Phoenix lists a like-for-like swap of an air conditioner or evaporative cooler as work that needs no permit. Change the size, capacity or location and that changes too, so pages should say which job it is.

Homeowners hear two stories about permits. One company says every swap needs a permit. Another shrugs and says nobody pulls permits for AC. Both can leave a buyer feeling tricked later. The calm paragraph we write, matched to the city's own list, makes you the company that explained it, and that trust walks into the estimate with you.

We'd write that paragraph once with your office manager, then check it against the city's guides before it goes on any site. If your company prefers to pull a permit on every change-out anyway, the page says that instead. It just has to match what really happens on install day.

Can the page say no permit is needed in big letters?

We'd keep that out of headlines. The exemption hangs on details your estimator checks in person, like the unit's capacity and where it sits. A bold promise copied onto a dozen sites turns into a problem the first time a job doesn't qualify.

Who asks the city's counter questions?

Phoenix asks them of anyone requesting a permit-exempt approval for an AC replacement, and a single yes means a permit. Your office already knows that drill. The site's only job is to never contradict it.

Evaporative cooler owners want a page written for them

Phoenix permit rules still name evaporative coolers, so some of your callers own one. If your techs work on them, a cooler page catches questions your AC pages miss.

A cooler owner doesn't search like an AC owner. They're more likely to type words like pads, pump and float valve. If every page on your network talks about refrigerant and compressors, they head back to the results and call whoever wrote about coolers. When your techs service them, that's a job you'd have happily taken, gone to someone else.

The page doesn't need to be long. It needs to sound like someone who has climbed onto a roof in June to swap pads, and it needs a clear way to book that visit. We'd build it from a short talk with the tech who does most of your cooler work.

• Is it worth fixing an old cooler, or is it time to replace it?
• Can you add refrigerated air and keep the cooler for spring?
• Will my ducts handle a switch to AC or a heat pump?
• Why does the house feel sticky when the cooler runs in August?
• What does a spring cooler start-up include, and when should I book it?

Should the cooler page mention the rental cooling rule?

Only in passing, with a link to your landlord page if you have one. We keep this page about the homeowner standing under a dripping cooler, since that's who reads it.

What if we'd rather move cooler owners to refrigerated air?

Then we say so kindly, and we explain what the switch involves at your company. We won't knock the cooler they own today. Nobody likes being told their house is wrong.

Split the Phoenix area sites by the equipment your techs keep finding

Let each area site open with the setup your techs meet most in that part of town, whether that's rooftop package units, older coolers or rental duplexes.

Our first stop is your dispatch history, since it already knows which areas lean which way. A tech who spent June on flat roofs in one part of town has a different story than one who spent it swapping cooler pads. We'd sort last summer's tickets by area and equipment before writing a word. Where one kind of job clearly leads, that area site opens with it. If an area's tickets look just like its neighbor's, that's a sign to start the network with fewer sites.

When a condenser goes quiet after a monsoon cell rolls through

A storm page is for the night a unit stops right after a cell passes. It should say what's safe to check, what to leave alone and when you'll call back.

• One first check your lead tech signs off on, like whether the breaker or the outdoor disconnect tripped.
• A clear line to leave the unit alone if it's sitting in water or a panel cover blew off.
• What to tell your office on the phone: when it stopped, whether the lights flickered and what the outdoor unit is doing.
• Whether your techs want homeowners to clear leaves and dust from the condenser, or wait for a visit.
• Your after-storm callback promise, worded so your dispatcher can keep it on a busy night.

Storms and heat land in the same weeks here, so a storm call usually comes from a house that's already warm. We keep the page short on purpose. Someone reading it may be sitting in a stuffy living room with a phone at twenty percent. They need your number, a safe check or two and an honest word about when you'll call back. Everything else can wait for a calmer day.

Should the storm page mention power surges?

Only in your lead tech's words. A surge is one possible reason a unit quits after a storm, and your tech finds the real one on site. The page can ask people to mention flickering lights on the phone without guessing at the cause.

What if the storm knocked out power to the whole street?

Then the page says your techs can't help until the power's back, and it tells people what to watch for once it returns. We'd keep that wording plain, since it saves your dispatcher a lot of confused calls.

One July Tuesday on a Phoenix dispatch board, told two ways

Here's a hot day with shared leads and then the same day with area sites routed to your office. The numbers are made up, and the pattern is the part worth noticing.

We'll be honest with you: the after column isn't magic. It still takes a CSR who answers fast and a schedule with room in it. What changes is the race. A shared lead starts a sprint against other shops the second it lands. A call from your own site starts with the homeowner already reading your name and holding your number. You're the only company in that conversation.

We can't tell you how many calls a Phoenix site will bring in its first summer, and anyone who names a number without seeing your market is guessing. Our promise is smaller and firmer: every call that does come in lands on your line, with its source attached.

Do the calls pass through a call center first?

No. They ring the number you pick, whether that's the office line, a dispatch cell or an answering service you already pay for. We test each route before a site goes live.

What if two area sites bring in the same homeowner?

Then you've got one customer who read two of your pages, which is fine. Both sites carry your name, so there's no bidding war and nothing to split.

The March shopper who nursed a tired unit through last summer

Some homeowners limp an old system through August and start shopping once the weather turns kind. Pages written for that calm buyer can win replacement jobs your summer pages never see.

Picture a couple who spent last summer babying a 15-year-old unit through two repairs and one very long weekend. In March, with the windows open, they finally have the energy to shop. They aren't rushed. They'll read three or four pages before they call anyone, and they'll remember which company explained things without leaning on them.

That buyer wants to know how the install will go and which kinds of systems you put in. They don't want a countdown clock or a coupon that expires at midnight. A spring planning page from us gives them room to think, and it gives your advisor a warmer first meeting.

• Why replacing before the heat returns can mean an easier install week, in your office's own words.
• What install week looks like when the new unit sits on the roof, from roof access to who needs to be home.
• The system types you actually install, with no brand names you don't carry.
• What changes if the old system was an evaporative cooler, like new ductwork or an outdoor pad, in your estimator's words.
• A way to book a spring visit that doesn't feel like walking into a sales trap.

Won't a spring page just bring price shoppers?

Some, sure. We'd rather meet them in March with a clear page than in July when your advisors are buried. A few will become the easiest installs of your year.

How soon before spring should that page go live?

Well before the first warm weekend. That gives it time to settle in and gives your advisors a chance to read it and tell us what we got wrong.

Whose name sits on the domain, the phone number and the call log

Owning your inquiries starts with dull paperwork: who controls each domain, which number rings and where call records live. Settle all three before the first Phoenix site launches.

1. List every number a customer might dial Your main line, the dispatch cell, the after-hours service and any tracking numbers. We map which site shows which one.
2. Decide on tracking numbers with your eyes open A tracking number shows which site sent a call. We set it to forward to your line and tell you who holds that account.
3. Ask who holds each domain Before any site launches, ask us, or any vendor, who controls each domain and what happens to it if you stop paying. Get that answer before you sign.
4. Send the records somewhere you can reach Call logs and form entries go to an inbox or sheet your office owns, so the history stays with your company.
5. Test again after every change A new dispatcher, a new cell phone or a new answering service means we call every route again.

The ten-minute briefing your CSRs get before any site goes live

Your CSRs should know what each site promised before the first caller quotes it back to them. A short briefing keeps the phone answer and the page saying the same thing.

1. Show them the sites on a phone We pull up two area sites on a phone in front of the team, since that's how most callers will see them.
2. Read the after-dark promise out loud If the page says a same-night visit for calls before 9 p.m., everyone on the phones hears that exact line.
3. Walk through the permit paragraph CSRs get the same plain words the replacement page uses, so a homeowner never hears two versions.
4. Agree on the out-of-area answer When someone calls from outside your map, the CSR knows the polite answer and whether to take a message.
5. Say how calls get tagged We explain what the tracking shows, so nobody has to ask every caller where they found you.

We know this sounds small, and it is. It's also where plenty of good websites fall apart. A page promises one thing, the person on the phone says another, and the homeowner decides neither can be trusted. Ten minutes with your team before launch, and again whenever a page changes, keeps everyone telling the same story.

Bring last July's no-cool log and your after-hours rotation to the first call

The two most helpful things you can bring are last July's no-cool calls and the list of who covers nights. Together they show where a Phoenix network should start.

Your no-cool log tells a story no agency could make up. It shows which areas called at 10 p.m., which ones waited until morning and which ones your techs couldn't reach in time. We haven't run a Phoenix heating and cooling network, so that log will be the first real data this one sees. Our part is making each site worth reading, keeping your name and license class on it and routing every call and form to your team.

• Last July's no-cool calls, with the area and the hour each one came in
• Your after-hours rotation, including who covers weekends and holidays
• Any cooler or package-unit work you'd like us to bring in more of, or less of
• Your ROC license class and number exactly as the state lists them

Who will I actually be talking to?

Jeff Clerisier. He took his first freelance web clients in 2016 and founded our company in March 2018. Jeff works from Indianapolis, so a Phoenix network would be planned over a phone or video call from day one.

What will an HVAC network cost?

We price heating and cooling networks one at a time, after the free strategy call. By then we'll know how many areas you want covered and which calls you'd like more of.

Is there anything I can do before we talk?

Run your current website through our free scan, which is powered by Jev. You'll get a ranked to-do list for the site you already have, whether or not you ever build microsites.