Garrison Phoenix Foundation Repair Microsites for Inspection Requests

Out here, water is usually what sets a foundation worry in motion

Some Arizona soils sink when they get wet, so a Phoenix foundation site should ask about water early, without ever pretending a web page can diagnose a house.

Think about a homeowner in Maryvale. Maybe the sprinkler valve stuck open over a long weekend, or a downspout has been emptying beside the slab for years. A few weeks later, a crack shows up over the laundry room door, and the late-night searching begins.

Your site can't say the water caused it. Only your evaluator can make that call, standing in the house with a level and a flashlight. What the site can do is ask the question your evaluator would ask anyway: has anything been getting wet lately? That one question saves a phone call, and it tells the homeowner you know how desert ground behaves.

• Has a sprinkler, drip line or pool had a leak in the last year?
• Do your downspouts empty right beside the house?
• Has water pooled against the walls after a storm?
• Has anyone done plumbing work under or near the slab lately?
• Is there a spot in the yard that stays damp while the rest dries out?

Should the water page tell people how to fix their drainage?

Only with advice your evaluator wrote or approved. A simple tip, like keeping downspouts from dumping against the wall, might be fine if your team stands behind it. Anything bigger points to a visit, where someone can see the yard.

What if a homeowner says nothing has gotten wet?

That's a perfectly good answer, and the form accepts it without fuss. Plenty of foundation questions have nothing to do with a leak. The water questions just help your scheduler, and nobody gets judged for their answers.

Earth fissures belong on a calm map link, far from any scare headline

Arizona maps earth fissures tied to heavy groundwater pumping. A foundation site can point people to those maps quietly and leave every judgment about a house to a visit.

Should every town site talk about fissures?

Only the towns where your team says the subject really comes up. A fissure page on a site for a town nowhere near a mapped one would just worry people for no reason, and worried people don't read carefully.

A homeowner asks if there's a fissure under their house. What does the page say?

It points them to the state's public maps and explains that your evaluator looks at the house itself. The site never answers yes or no from a zip code, and neither should anyone on your phones.

Do fissure questions change how a request gets routed?

If your office wants them flagged, yes. We add a checkbox for people who've read about fissures near them, and your scheduler sees it before calling. What happens next is your team's call.

We keep fissure talk short and sourced on purpose. The topic sounds dramatic, and dramatic topics tempt marketers to crank up the fear. That's the fastest way to lose the calm, careful homeowner you actually want on your schedule. A link to the state's own map, sitting beside a friendly explanation of your visit, does far more for trust than a red banner ever could.

Six starter pages for a Phoenix foundation site, and the line each must never cross

Start with six pages tied to questions your evaluators say they hear. Each one gets approved by the person who does the visits, and each has one claim it must never make.

1. A short interview We talk with your evaluator for half an hour about what Phoenix homeowners get wrong, what they ask and what your crew does.
2. A first draft We turn those answers into pages in your company's voice, keeping their phrases where they're clearer than ours.
3. A red pen pass Your evaluator marks anything that sounds off. Technical lines change only when they say so.
4. A final check and launch We test links, forms and numbers on each town site, then publish and note the date for the next check.

Six pages per town site is a starting point we can keep accurate. Each town's version gets its own photos, its own job stories and notes that fit the houses there, so the network never reads like one page stamped over and over. We'd rather grow the set slowly, as your office spots new questions, than bury a homeowner in forty thin pages on day one.

The warranty page, and the two years Arizona gives homeowners to file a complaint

Arizona's contractor registrar takes complaints about repair work for two years after the work was last done. A warranty page should never blur that or hint at a shorter clock.

1. Start from the paper Send us your written warranty. We summarize from that document alone, never from memory or a competitor's page.
2. Say it in kitchen-table words What's covered, for how long and what the homeowner does to use it. Short sentences, with no legal fog.
3. Show who stands behind it Your company's legal name and ROC number sit right beside the warranty summary, where nobody has to hunt.
4. Keep the state in the picture If your team is comfortable with it, add one neutral line saying licensed Arizona contractors answer to the ROC. It reads as confidence.
5. Offer the full document Link the complete warranty or offer it on request, so the summary never has to carry the fine print.

Some owners flinch at mentioning the ROC on their own site. We get it. But a homeowner facing a big structural bill will likely search your name before signing anyway. Finding the state's role explained calmly on your page shows them a company that's comfortable being checked. If that line doesn't feel right for your business, we simply leave it out.

A patio pulling away from a Laveen house, before and after

This made-up request shows how a water-first form and a calm page change the very first phone call for a Phoenix foundation crew.

The small detail doing the work here is the photo of a downspout. People often can't describe their problem, but they know it when they see it. We ask your crew for plain pictures of the things homeowners overlook: a gutter outlet, a planter bed hugging the wall, a patio seam. Those pictures turn a vague worry into a specific request your scheduler can act on.

Does every town site need its own photos of downspouts and patios?

Ideally, yes, taken on jobs in or near that town. Until you have them, we'd rather use one honest photo on several sites, labeled plainly, than a stock picture of a house that isn't in Arizona.

What if the homeowner in a story like this turns out to have a bigger problem?

Then your evaluator says so on the visit, the way they always would. The page only helped them describe what they saw. It never promised a small fix.

Six kinds of callers, and the page each one should land on

Plenty of people who search foundation repair in Phoenix don't own the house in question. Match each kind of caller to a page that speaks to their situation.

• The homeowner who just noticed something, sent to the cracks and sticking doors page
• A buyer holding an inspection report, sent to a page on what your visit adds
• A landlord with a tenant's complaint, sent to a page on arranging access
• An HOA board member worried about shared walls, sent to a page on who you work with
• A seller getting ready to list, sent to a page on paperwork they can pass along
• A neighbor who saw your truck down the street, sent to the about page with your license

We don't build all six on day one. We start with the two or three kinds of caller your office already hears from most, then add the rest only if they show up. There's no point writing a landlord page for a crew that doesn't want landlord work. And if HOA calls make up half your year, that page moves to the front of the line.

Should we write a page for real estate agents?

If agents already send you work, it can help. Keep it practical: how to book a visit for a client, what your evaluator provides afterward and how quickly your office usually responds, in your real numbers.

Won't landlords and HOAs expect different prices?

Maybe, and that's a conversation for your office. The pages stay out of pricing and focus on how to get a visit booked and who needs to be there.

What your scheduler should see before dialing a Phoenix request

A good callback starts with the homeowner's own answers on screen. We set up the request so your scheduler never has to ask the same question twice.

What lands in front of the scheduler when a form comes in?

The site and page it came from, the homeowner's water answers, what they noticed, when they noticed it and any photos. It arrives by text and email at once, so a busy morning doesn't bury it.

What about people who call instead of filling out the form?

Each site has its own tracked number, so the scheduler sees which town site the caller came from before picking up. The water questions then happen live, on the phone.

Can the site answer when someone calls after hours?

It can tell them what happens next, whatever your after-hours setup is. Voicemail, a cell phone or an answering service all work, as long as the page says which one they'll get.

What does the scheduler see when a home buyer writes in with an inspection report?

A buyer tag, the town and whatever line they typed about the report. Nothing gets uploaded on first contact. A buyer may be working against a deadline in the purchase contract, so ask for that date on the callback. Where those requests sit in the day's pile is your office's call, and we set the tag to match.

Picture two callbacks. One opens by mentioning the downspout that empties right beside the patio. The other opens with a vague question about what's going on. The first homeowner hears that someone read what they wrote. That small moment of being listened to can decide who gets the visit and who gets a polite maybe. We build the plumbing so your scheduler can have that moment every time.

Numbers worth watching once the Phoenix sites are running

Watch requests per site, how many mention water and how many turn into visits and signed work. The water share shows whether the pages ask the right things.

Our tracking tags each request with the site and page it came from. The form answers add another layer, since you can see how many callers ticked a water box and whether those requests book more often. If they do, the water pages deserve more attention. If requests from one town stay near zero for months, we'll look at it with you and talk honestly about whether that site earns its place.

How long before the numbers mean anything?

Longer than anyone likes. Foundation work has a slow path from first worry to signed job, so give it a few seasons before judging a site. We won't pin a date on it for you.

What if hardly anyone ticks a water box?

Then either your callers really aren't seeing water trouble, or the questions are worded so people skim past them. Sit with your scheduler and read ten forms. If people ticked no and then mentioned a dripping sprinkler on the phone, the question needs plainer words, and we'll rewrite it with your evaluator.

• Requests per town site, by call and by form
• The share of requests with at least one water box ticked
• Visits booked, and visits that actually happened
• Proposals written after a visit, and proposals signed
• Requests turned away, with a one-word reason

Job photos that hold up under harsh Phoenix sunlight

Midday glare flattens cracks and washes out slabs. A few easy habits give your sites photos that actually show homeowners what your crew did.

• Shoot outside early in the morning or late in the afternoon, when shadows show texture
• Shade a hairline crack with a clipboard so it shows as a dark line instead of vanishing in the glare
• Stand back for one wide shot so people know which wall they're looking at
• Shoot the shady side of the house first, while the crew is still unloading
• Turn the flash off on bright stucco, which throws it back as a white blotch

Your crew's phones can handle every item on that list. We sort the photos by town, write a short caption for each in plain words and pair them with a job story your evaluator checks. A homeowner who sees a real Phoenix patio, shot in honest light, trusts that page more than any glossy stock image of a perfect slab.

How many photos should a crew send per job?

Eight to ten is plenty. We'd rather have a handful of clear, well-framed shots than fifty blurry ones taken from the truck window.

Can we use photos from jobs outside Phoenix?

Yes, as long as the caption says where the job was. We never pretend a Mesa or Glendale job happened in a Phoenix neighborhood, and we'd ask you to hold us to that.

Things a Phoenix foundation owner should ask us before saying yes

Put these to us on the free call. Jeff Clerisier, who opened our doors in March 2018 and still leads it, will be the one answering them.

Who rewrites the water page if our evaluator disagrees with it?

Your evaluator wins every time. We're based in Indianapolis and would plan a Phoenix network remotely, and we won't dress that up. So corrections travel however your evaluator likes: a call from the truck, a marked-up printout or a text with a photo of the page. We rewrite the lines they flag and send the new version back for a yes.

If we change our minds about mentioning fissures, how does that come off the sites?

Tell us, and the fissure page, its map link and the checkbox on the form come down from every town site together. We note the date and your reason, so nobody puts it back by accident next year. Past requests keep their old flag, so your tally still makes sense when you look back.

Can you guarantee rankings or a number of jobs?

No. Treat anyone who guarantees those with suspicion. We can promise pages your evaluator approved, routing we've tested and honest counts you can check yourself.

One more thing worth asking any agency: what happens if the fit isn't right? For some foundation companies, a stronger main website would do more than a network of town sites. If that's you, Jeff will say so on the call, and the call still costs you nothing. We'd rather send you away with a clear next step than sell you something your crew doesn't need.