ChatGPT for Contractors: 25 Prompts You'll Actually Use

Most contractors don't need a hundred ways to use ChatGPT. They need five or ten good ones.

Search "AI prompts for contractors" and you'll find plenty of lists. Most of them were clearly written by someone who has never chased down a quiet estimate, argued with a supplier about a backordered part, or tried to explain to a homeowner why a repair costs what it costs. They're full of things nobody in this business is losing sleep over: mission statements, inspirational social posts, generic marketing plans.

This list is different. Every prompt here is built around something that actually happens inside a contracting business. An estimate that went quiet. A one-star review sitting on your Google profile. A call that didn't book and nobody can say why. A process that only lives in one technician's head. A job posting that hasn't produced an applicant in three weeks.

Bookmark it. Better yet, forward it to whoever else in your business could use it, your office manager, your dispatcher, your service manager, your spouse if they help with the books. Someone on your team is going to need one of these prompts before the week is out.

(If you want the longer argument for why this matters in a home service business specifically, we wrote the field guide on it.)

A Few Ground Rules Before You Start

ChatGPT is good at drafting, organizing, and finding patterns in messy information. It doesn't know your company, your customers, or your local code. Treat everything it writes as a draft. A few habits worth building before you start pasting things in:

Don't paste anything you wouldn't want to see in a data breach. Remove information ChatGPT doesn't need. Names, addresses, payment information, account numbers, and other identifying information usually aren't necessary to get a useful answer. When in doubt, take it out.

Read before you send. ChatGPT doesn't know if you already promised a customer a discount, or if your service manager already had this exact conversation with an employee last month. It only knows what you tell it.

It doesn't replace licensed judgment. None of the prompts below ask ChatGPT to make a technical, code, or safety call. Keep it that way. That's still your technician's job, not a chatbot's.

GET THE JOB

An estimate that doesn't close isn't dead. It's usually just stuck. These four prompts cover the two moments that decide whether a job comes back to life: the follow-up, and figuring out why estimates aren't converting in the first place.

1. Follow Up on a Quiet Estimate Without Sounding Desperate

Use this when an estimate has gone quiet and you want to check in without sounding like you're begging for the job.

COPY + PASTE THIS:

I'm a [TRADE] contractor. I sent the estimate below to a customer [NUMBER] days ago and haven't heard back.

ESTIMATE / SCOPE OF WORK:
[ESTIMATE]

WHAT I KNOW ABOUT THE SITUATION (include anything that applies):
- What the customer originally called about
- Anything they said about budget, timeline, or other bids they're getting
- Whether this is a repair, a replacement, or a "nice to have"

Before you write anything, tell me:
1. What's the most likely reason this estimate has gone quiet (price, timing, comparing bids, they forgot, something changed)?
2. Is there a question I should be asking them that I haven't asked yet?

Then draft a short follow-up email and a short text message version. Keep the tone like someone who does good work and has other customers to take care of, not someone chasing the sale. No exclamation points. No "just following up!" Don't offer a discount unless I tell you to. If you don't have enough information to know why this stalled, ask me before you draft anything.

MAKE IT BETTER: Paste in exactly what the customer said when you scoped the job, not just the estimate total. Their actual words matter more than the price.

2. Turn a Technical Estimate Into Something a Homeowner Understands

Use this when your estimate is accurate but reads like a parts list, and the customer needs to understand what they're paying for.

COPY + PASTE THIS:

Here is a technical estimate for a [TRADE] job. The customer isn't in the trade and won't understand terms like [example: "condenser," "manifold," "load calc"].

ESTIMATE:
[ESTIMATE]

Rewrite this as a short, plain-English explanation I can send or hand over alongside the itemized estimate. For each major line item, explain in one or two sentences what it is, why it's needed, and what happens if it's skipped. Don't invent technical justifications I haven't given you. If something needs an explanation you don't have (why a part failed, what code requires it), list it as a question for me instead of guessing. Keep the whole thing under one page and write it like you're talking to a smart neighbor, not an engineer.

MAKE IT BETTER: Tell it who's reading this. A first-time homeowner needs more explaining than a repeat customer who's had five service calls with you.

3. Find Out Why Your Estimates Aren't Closing

Use this monthly or quarterly, when you want a real look at your close rate instead of a gut feeling.

COPY + PASTE THIS:

I'm a [TRADE] contractor trying to understand why some estimates close and others don't. Below is a list of recent estimates with what I know about each one.

ESTIMATES:
[FOR EACH ONE, NOTE: AMOUNT, SCOPE, OUTCOME, AND ANY CUSTOMER FEEDBACK]

Analyze this list and tell me:
1. Any patterns in what separates the estimates that closed from the ones that didn't (price range, job type, how fast I followed up, objections raised).
2. Whether there's a common objection or hesitation showing up more than once.
3. What's genuinely a pattern versus what's unclear from this data.

Do not calculate a close rate or percentage unless I've given you clean win/loss numbers for all the estimates. Do not assume price is the reason unless the data actually supports it. If you need more information to spot a real pattern, tell me what to add next time.

MAKE IT BETTER: The more estimates you paste in, at least ten to fifteen, the more real the pattern will be. Three examples is a guess dressed up as an analysis.

4. Build a Follow-Up Sequence for Unsold Estimates

Use this when you're tired of manually remembering to follow up and want a simple sequence you or your office manager can send on a schedule.

COPY + PASTE THIS:

I want a follow-up sequence for estimates that haven't closed, for my [TRADE] company [COMPANY NAME]. Build [NUMBER, e.g. 3-4] messages spaced over [TIMEFRAME, e.g. 3 weeks], alternating between email and text where it makes sense.

Each message should:
- Have a different purpose (a friendly check-in, answering a likely objection, a final low-pressure close)
- Not repeat the same opening line as the others
- Sound like it's coming from a person, not an automated system
- Avoid fake urgency or discounts unless I specifically want one included

Here's what I know about why estimates like this usually stall: [OPTIONAL: paste common objections, e.g. "price," "wants to think about it," "comparing bids"]

Give me subject lines, send timing for each message, and the message content. Ask me anything you need to know about my business or tone before you draft this.

MAKE IT BETTER: If you already ran prompt #3, paste that analysis in here. The sequence will address real objections instead of generic ones.

TAKE CARE OF THE CUSTOMER

Every contractor eventually gets the message that ruins an evening: a customer who's furious, a price complaint that's really about something else, an employee reply that's about to make things worse if it goes out as written. These prompts are for writing, while calm, what you'd otherwise write while upset.

5. Respond to an Angry Customer

Use this when you've got an angry email, text, or voicemail and need to respond without making it worse.

COPY + PASTE THIS:

A customer sent me the message below. I need help responding.

CUSTOMER MESSAGE:
[CUSTOMER EMAIL]

WHAT ACTUALLY HAPPENED (my side, as much detail as I have):
[YOUR NOTES ON THE SITUATION]

Before drafting a response, do this:
1. Identify the customer's actual complaint, separate from how upset they sound.
2. Separate the emotional issue (how they feel they were treated) from the operational issue (what actually went wrong, if anything).
3. Identify anything my company should reasonably take responsibility for, based only on what I told you.
4. Flag anything that needs a manager's decision before I respond (refund, discount, redoing the work, anything with financial or legal weight).

Then draft a calm, concise response. Do not admit fault I haven't told you we're at fault for. Do not offer a refund, credit, or free work unless I've told you that's on the table. Do not make up details about what happened. Keep it short. It should sound like someone who takes this seriously, not a corporate apology letter.

MAKE IT BETTER: Include the full back-and-forth, not just their angriest message. Something earlier in the thread often explains what actually set them off.

6. Handle a Price Objection ("Too High" or "Someone Quoted Less")

Use this when a customer pushes back on your price or says a competitor came in lower, and you want to respond with confidence instead of caving.

COPY + PASTE THIS:

A customer is objecting to my price. Here's what they said:
[CUSTOMER MESSAGE OR SUMMARY]

Context: [what was quoted, what's included, and, if you know it, what the competitor is offering or leaving out]

Help me respond. First, tell me:
1. Is this objection actually about price, or about something else (trust, timing, not understanding what's included)?
2. If they mentioned a competitor's price, what's the fair way to address it without insulting the competitor or badmouthing anyone?

Then draft a response that explains the value of what's included (materials, warranty, licensing, timeline, whatever I tell you applies) without sounding defensive or like I'm justifying myself. Do not offer to match or beat the competitor's price unless I say that's an option. Do not guess what's included in the competitor's quote if I haven't told you. Keep it short enough to read in one sitting.

MAKE IT BETTER: Tell it what actually makes your quote different: warranty length, licensing, materials, timeline. "We do quality work" won't hold up against a real number.

7. Rewrite a Defensive Employee Reply Before It Goes Out

Use this when a technician, CSR, or office manager drafted a reply to a customer complaint that's technically not wrong, but is going to make things worse if it goes out as written.

COPY + PASTE THIS:

An employee drafted the reply below to a customer complaint. I think the tone is going to escalate things even though the facts might be right. Here's the situation and their draft:

CUSTOMER'S ORIGINAL MESSAGE:
[CUSTOMER MESSAGE]

EMPLOYEE'S DRAFT REPLY:
[EMPLOYEE DRAFT]

Tell me first what in the draft is likely to make the customer angrier, even if it's factually accurate. Then rewrite the reply to keep the same facts and the same position, but with a tone that de-escalates instead of defends. Don't soften facts or concede something we didn't do wrong. Don't add promises or offers the original draft didn't include. I want a version I can send back to the employee as an example, not just a fix for this one message.

MAKE IT BETTER: Ask it to add a short note explaining what changed and why. That turns this into a training moment instead of just a rewritten email.

PROTECT YOUR NAME

Reviews do two jobs. They tell future customers whether to call you, and if you actually read them instead of just responding to them, they tell you what's really happening in your business. Businesses that respond to all their reviews, not just the good ones, earn meaningfully more trust than businesses that stay silent or only reply to praise, according to BrightLocal's most recent consumer review research. These three prompts cover both jobs.

8. Respond to a One-Star Review

Use this when a negative review is sitting on your profile and every day it goes unanswered looks worse.

COPY + PASTE THIS:

Here's a negative review of my [TRADE] company:

REVIEW:
[REVIEW TEXT]

WHAT I KNOW ABOUT THIS JOB (as much as you have):
[YOUR NOTES: what happened, whether the complaint is accurate, anything already resolved]

First, tell me what the reviewer is actually upset about, and whether it's a service issue, a communication issue, a price issue, or a misunderstanding. Then draft a public response that:
- Is calm, brief, and doesn't argue with the reviewer publicly
- Doesn't admit fault I haven't confirmed
- Doesn't promise a refund or resolution I haven't approved
- Invites them to continue the conversation privately (phone or email) if there's more to work out
- Doesn't sound defensive or like a form letter

Future customers will read this response too. Write it with that in mind.

MAKE IT BETTER: If the complaint is accurate and you've already fixed the underlying problem, say so. "We changed X because of this" convinces future customers far more than a generic apology.

9. Turn a Customer Complaint Into a Process Fix

Use this after a complaint or negative review, when you want to fix what caused it instead of just responding to it.

COPY + PASTE THIS:

Here's a customer complaint or negative review about my [TRADE] company, along with what I know about what actually happened:

COMPLAINT OR REVIEW:
[REVIEW OR CUSTOMER COMPLAINT]

WHAT I KNOW ABOUT WHAT HAPPENED:
[YOUR NOTES: what the technician, CSR, or office did, the timeline, anything already confirmed]

Analyze this and tell me:
1. What actually failed, based only on what I've told you.
2. Whether this looks like a communication problem, a process problem, or an individual performance problem, and why.
3. Where in our current process this should have been caught before it reached the customer, if you can tell from what I've given you.
4. One specific, concrete change to the process, not a vague "communicate better," that would prevent this from happening again.
5. A short internal message I could send the team explaining the change and why it's happening, without naming or blaming a specific employee.

Don't guess at details I haven't given you about what happened on the job. If you don't have enough information to identify what failed, tell me what to find out before drawing a conclusion.

MAKE IT BETTER: Run this on a complaint the moment it happens, not weeks later. The details that actually explain what went wrong fade fast.

10. Find the Operational Problem Hiding in Your Reviews

Use this when you want to know what your reviews are actually telling you about your business, beyond the star rating.

COPY + PASTE THIS:

Here are [NUMBER] reviews of my [TRADE] company, a mix of positive and negative:

REVIEWS:
[REVIEWS]

Read through all of them and identify:
1. Any complaint or issue that shows up more than once, even if worded differently each time.
2. Anything customers consistently praise, so I know what to protect and repeat.
3. Anything that sounds like an operational problem (scheduling, communication, cleanup, pricing clarity) rather than a one-off bad day.

Only flag something as a pattern if it actually shows up multiple times. Don't stretch a single review into a trend. If the reviews are too few or too vague to draw a real conclusion, tell me that instead of forcing an answer.

MAKE IT BETTER: Pull reviews from every platform you're on, Google, Facebook, Yelp, Angi, not just one. Patterns hiding across platforms are easy to miss if you only look at one at a time.

FIND THE LEAK

Before you buy another lead, find out where the last one went. Most contractors can tell you exactly what they spent on marketing last month. Very few can tell you what happened to every call it generated. These four prompts use calls you already have sitting in a phone system or CRM, not new leads you'd have to pay for.

11. Break Down One Call That Didn't Book

Use this when you've got one call transcript or a set of notes from a call that should have booked and didn't, and you want to know why.

COPY + PASTE THIS:

Here is a transcript of a call to my [TRADE] company that did not result in a booked job:

CALL TRANSCRIPT:
[CALL TRANSCRIPT]

Analyze the call and tell me:
1. What the customer actually wanted, and whether that was clearly understood by whoever answered.
2. The moment the call started going sideways, if there was one (unanswered question, price mentioned too early, no urgency created, unclear next step).
3. Whether the call ended with a clear next step (scheduled appointment, callback time, follow-up promised) or just trailed off.
4. One specific thing that could have been said differently, based only on what's in this transcript.

Don't guess at information that isn't in the transcript, like whether the customer called someone else. Base everything on what was actually said.

MAKE IT BETTER: Paste the transcript with speaker labels if you have them (caller vs. CSR). It sharpens the analysis noticeably.

12. Find the Pattern Across a Week of Calls That Didn't Book

Use this when you have several calls that didn't turn into jobs and want to know if there's a pattern instead of just bad luck.

COPY + PASTE THIS:

Here are transcripts (or notes) from [NUMBER] calls to my [TRADE] company that did not result in a booked job:

CALLS:
[PASTE MULTIPLE CALL TRANSCRIPTS OR SUMMARIES, LABELED]

Look across all of them and tell me:
1. Any question customers asked that didn't get a clear answer, if it comes up more than once.
2. Any point in the call where bookings seem to fall apart most often (price mentioned, availability, no urgency, call handed off, no follow-up scheduled).
3. Whether this looks like a training issue, a scheduling issue, a pricing issue, or something else, based only on what's in these calls.

Do not estimate how much revenue this is costing me. I haven't given you pricing or close-rate data to calculate that honestly. Just tell me what you see in the calls themselves, and be clear about which patterns are strong (showing up in most calls) versus weak (only one or two calls).

MAKE IT BETTER: Five to ten calls is enough to start seeing a real pattern. One or two calls will just tell you a story about that one call.

13. Coach a CSR From an Actual Call

Use this when you want to give a CSR or dispatcher specific, useful feedback instead of a vague "be more friendly on the phone."

COPY + PASTE THIS:

Here is a call transcript between [CSR NAME OR ROLE] and a customer:

CALL TRANSCRIPT:
[CALL TRANSCRIPT]

I want to coach this person, not criticize them. Identify:
1. What they did well on this call, specifically, not generic praise.
2. One or two specific moments where a different response could have moved the call forward (booked the appointment, answered a concern, created urgency).
3. Exact alternative phrasing they could use next time, based on what actually happened in this call.

Write this as notes I could use in a short one-on-one conversation, not a formal performance review. Keep the tone the way you'd want feedback delivered to you: direct, specific, and focused on what to do differently, not just what went wrong.

MAKE IT BETTER: Do this with a call that went well too, occasionally. Coaching that only shows up around mistakes starts to feel like it's always bad news.

14. Turn a Batch of Calls Into a Missed-Opportunity Report

Use this when you want a simple summary you can actually act on, or hand to a manager, after reviewing a stretch of calls.

COPY + PASTE THIS:

Here are transcripts or notes from [NUMBER] recent calls to my [TRADE] company, a mix of booked and unbooked:

CALLS:
[PASTE CALLS, LABELED BOOKED/NOT BOOKED IF KNOWN]

Build me a short report with:
1. Calls that clearly should have booked and didn't, with a one-line reason for each, based only on what's in the transcript.
2. Any recurring question customers asked that the team should have a better answer ready for.
3. Any scheduling or follow-up gap that shows up more than once (no callback given, no appointment offered, vague timeline).
4. Two or three specific, practical fixes based only on what you found in these calls, not general call-center advice.

Keep it to one page. This is going to a busy owner or manager, not a report nobody reads.

MAKE IT BETTER: Run this monthly in the same format so you can compare one month to the next instead of just getting a one-time snapshot.

RUN THE OFFICE

The stuff that keeps a business from depending on one person's memory doesn't have to take a full day to write. These three prompts turn what's already in your head, or a technician's notes, into something the next person can actually follow.

15. Turn Messy Technician Notes Into a Real SOP

Use this when a technician's rough notes from a job, or a voice memo transcript, need to become a repeatable process for the whole team.

COPY + PASTE THIS:

Below are rough notes from a technician describing how they handle [PROCESS, e.g. "a no-heat call in winter," "closing out a job with the customer"]. I want this turned into a standard operating procedure the rest of the team can follow.

NOTES:
[TECHNICIAN NOTES]

Turn this into a clear, numbered SOP. For each step, include what to do and, where it matters, why it matters, so it's not just a checklist nobody understands. Flag anything in the notes that's unclear, contradictory, or missing a step, instead of guessing what was meant. Don't add technical steps, safety procedures, or code requirements that weren't in the original notes. This should reflect exactly what this technician actually does, written clearly enough for someone newer to follow.

MAKE IT BETTER: Include the "why" behind steps if the technician mentioned it, even offhand. That context is usually what separates a real SOP from a generic checklist.

16. Get a Process Out of Someone's Head and Onto Paper

Use this when your best person does something well and consistently, but it's never been written down, and if they left tomorrow, that knowledge leaves with them.

COPY + PASTE THIS:

I need to document a process that currently only exists in [EMPLOYEE NAME OR ROLE]'s head: [PROCESS, e.g. "how we handle a same-day emergency call," "how we quote a re-pipe"]. I'm going to describe it to you in my own rough words, the way they'd describe it to me, and I want help turning it into something documented.

HERE'S WHAT I KNOW ABOUT HOW THEY DO IT:
[YOUR ROUGH DESCRIPTION, AS DETAILED AS YOU CAN MAKE IT]

Ask me clarifying questions first if there are gaps or steps that don't make sense, rather than filling them in yourself. Once you have enough, write this up as a clear process document with numbered steps, noting any decision points where the process branches depending on conditions.

MAKE IT BETTER: Record yourself talking through the process out loud on your phone, then paste in the transcript instead of typing from memory. You'll catch details you'd otherwise leave out.

17. Figure Out Why Nobody Buys Your Maintenance Agreement

Use this when your maintenance agreement isn't selling the way it should, and you want to know if the problem is the price, the pitch, or the agreement itself.

COPY + PASTE THIS:

Here's my [TRADE] company's maintenance agreement, along with how we currently sell it:

AGREEMENT TERMS AND WHAT'S INCLUDED:
[SERVICE AGREEMENT]

PRICING:
[PRICE, PAYMENT STRUCTURE]

HOW WE CURRENTLY EXPLAIN IT TO CUSTOMERS:
[HOW CSRS OR TECHS PITCH IT, e.g. "at the end of a service call," "over the phone when booking"]

OBJECTIONS WE HEAR MOST OFTEN:
[COMMON PUSHBACK, e.g. "I don't need it," "too expensive," "I'll just call if something breaks"]

Analyze this and tell me:
1. Whether the core problem looks like value (it doesn't offer enough), clarity (customers don't understand what they're getting), positioning (it's being pitched at the wrong moment or by the wrong person), price, or how it's being presented, based only on what I've given you.
2. Any language in the agreement itself that's confusing or hard for a customer to understand at a glance.
3. Anything in the agreement that could carry legal weight and should be reviewed by an attorney before I change it (cancellation terms, liability language, automatic renewal, anything binding). You are not a lawyer and this isn't legal advice.
4. One or two specific changes, to the pitch, the pricing presentation, or the agreement language, that would address the real problem you identified.

Don't assume price is the issue unless the objections I gave you actually point there.

MAKE IT BETTER: Ask three technicians or CSRs how they'd explain the agreement in one sentence, and paste in all three. If they can't agree on what it actually offers, that's usually the real problem.

LEAD THE TEAM

Managing people is the part of this business nobody trains you for. These aren't scripts to hide behind. They're a way to think something through before you're standing in front of the person it's about.

18. Prepare for a Difficult Conversation With an Employee

Use this when you need to talk to an employee about a performance issue, attitude problem, or repeated mistake, and want to walk in prepared instead of winging it.

COPY + PASTE THIS:

I need to have a difficult conversation with an employee about [SITUATION, e.g. "showing up late repeatedly," "a customer complaint," "not following the process for X"]. Here's the background:

SITUATION:
[YOUR DESCRIPTION OF WHAT'S HAPPENED, INCLUDING ANY PRIOR CONVERSATIONS ABOUT IT]

Help me prepare. First, tell me:
1. What the actual issue is, separate from how frustrated I am about it.
2. Whether this looks like a first conversation, a repeat issue, or something that may need documentation for HR or legal reasons, based on what I've told you.

Then give me a short outline for the conversation: how to open it, the specific points I need to make, and a question or two to ask the employee so it's a conversation and not a lecture. Do not draft anything that threatens termination or discipline unless I tell you that's already been decided. Keep this focused on the specific behavior, not the person's character.

MAKE IT BETTER: If this isn't the first time you've addressed this issue, say so and include what was said last time. That changes how direct the conversation needs to be.

19. Find the Jobs You're Probably Losing Money On

Use this when you want to know if certain jobs are quietly costing you money, without pretending ChatGPT is your accountant.

COPY + PASTE THIS:

Here's data on a set of recent jobs for my [TRADE] company. For each one, I've included what we quoted, what it actually took to complete (hours, materials, any callbacks), and anything unusual that happened:

JOBS:
[FOR EACH JOB: QUOTED PRICE, ACTUAL HOURS, ACTUAL MATERIALS COST IF KNOWN, CALLBACKS, ANYTHING UNUSUAL]

Look across these jobs and tell me:
1. Which jobs, based only on the numbers I gave you, look like they made the least sense financially, and why.
2. Any pattern in job type, size, or scope that shows up more than once among the weaker-performing jobs.
3. Any pattern in callbacks that suggests a job type is chronically underquoted rather than just unlucky.

Do not calculate profit margins, hourly rates, or a dollar figure for what this is costing me unless I've given you complete cost data for every job. If my numbers are incomplete, tell me exactly what's missing before drawing a conclusion. You're not an accountant and this isn't a substitute for a real look at my books, just a way to spot a pattern worth investigating further.

MAKE IT BETTER: Include jobs that went well alongside the ones that didn't. A pattern only means something if you can compare it to what a job is supposed to look like.

20. Build a Simple Weekly Scorecard From What You Already Track

Use this when you want one simple view of how the business is doing each week, without buying another piece of software.

COPY + PASTE THIS:

I want to build a simple weekly scorecard for my [TRADE] business. Here's what I currently track or have access to (be specific: jobs booked, revenue, calls answered, estimates sent, callbacks, whatever you actually have):

WHAT I TRACK:
[YOUR LIST]

Help me design a one-page weekly scorecard using only the data I actually have. For each number, tell me why it's worth tracking weekly and what a meaningful change, up or down, would actually tell me. Don't recommend metrics I don't have a way to measure yet. If there's an obvious gap, something important I'm not tracking at all, point it out, but don't build the scorecard around data I don't have.

MAKE IT BETTER: Be honest about what you can pull consistently every week without extra effort. A scorecard that takes an hour to fill out gets abandoned by week three.

HIRE PEOPLE WHO STAY

Every contractor in the country is fighting over the same small pool of good technicians. The Bureau of Labor Statistics projects roughly 81,000 electrician openings and 44,000 plumber, pipefitter, and steamfitter openings a year through the rest of the decade, most of it driven by retirements, not new demand. These two prompts are for the parts of hiring most owners either skip or copy from a template that sounds like every other listing on the internet.

21. Write a Job Posting That Doesn't Sound Like Everyone Else's

Use this when your current job posting isn't bringing in applicants, or reads exactly like every other "growing company seeking motivated technician" listing.

COPY + PASTE THIS:

I need a job posting for a [POSITION, e.g. "residential service technician"] at my [TRADE] company, [COMPANY NAME], in [CITY]. Here's what I know about the role and what makes working here different:

ROLE DETAILS:
[PAY RANGE, SCHEDULE, BENEFITS, REQUIRED EXPERIENCE/LICENSING]

WHAT'S ACTUALLY TRUE ABOUT THIS JOB (be specific, not generic):
[e.g. "we don't do on-call rotation," "trucks are stocked so techs aren't running to the supply house mid-job," "owner is on jobs weekly, not just in an office"]

Write a job posting that leads with what's specifically true about this job, not generic phrases like "competitive pay" or "great team environment" unless I've given you specifics to back that up. Don't invent perks or claims I haven't told you about. Keep it honest, specific, and written the way you'd want a job posting written for you if you were the technician reading it.

MAKE IT BETTER: List the three real reasons a good technician stayed at your company for years, if you can think of them. That usually beats anything generic.

22. Build Interview Questions That Actually Tell You Something

Use this before interviews, when you want questions that reveal something real instead of ones people have rehearsed answers for.

COPY + PASTE THIS:

I'm hiring a [POSITION] for my [TRADE] company. Here's what matters most for this role and where past hires have worked out or not:

WHAT MATTERS FOR THIS ROLE:
[REQUIRED SKILLS, EXPERIENCE, TRAITS THAT HAVE MATTERED IN THE PAST]

Build me [NUMBER] interview questions focused on job-related qualifications, experience, and documented criteria. Do not include questions related to age, family status, religion, disability, national origin, or any other protected characteristic, or that could be used to screen for one indirectly. For each question, tell me briefly what a strong answer sounds like versus a weak one, based on what actually matters for this role. Include at least one question that surfaces how someone handles a mistake or a difficult customer, since that comes up constantly in this trade.

MAKE IT BETTER: Tell it about a hire that didn't work out and why, in skills-related terms, not personal ones. It can build a question specifically designed to catch that gap next time.

MARKET WITHOUT SOUNDING LIKE EVERYONE ELSE

Three prompts here, not ten. Most contractor marketing content is generic because it starts from the company instead of the customer, or from the calendar instead of what's actually happening outside. These three start from the customer.

23. Turn This Week's Weather Into a Useful Customer Email

Use this for a seasonal email that's actually about something happening right now, not a generic "fall HVAC tips" template.

COPY + PASTE THIS:

I want to send a customer email tied to the actual weather and season right now, not a generic seasonal template. Here's what's going on:

CURRENT SITUATION:
[WHAT'S ACTUALLY HAPPENING: e.g. "first hard freeze expected this weekend," "we've had three weeks of 95-degree heat," "heavy rain in the forecast all week"]

SERVICES THIS IS RELEVANT TO:
[WHAT YOU WANT TO PROMOTE OR REMIND CUSTOMERS ABOUT, RELATED TO THIS WEATHER]

SERVICE AREA:
[CITY/REGION]

WHAT I WANT THE CUSTOMER TO DO:
[GOAL, e.g. "book a tune-up before it gets worse," "know we're available for emergency calls," "just stay informed"]

Write a short email that connects this specific weather situation to a real, useful reason to reach out, not manufactured urgency or scare tactics. It should read like it was written this week, about this weather, not recycled from a template. Keep the call to action clear and low-pressure.

MAKE IT BETTER: Check the actual forecast before you run this, not just the season. "It's fall" produces a generic email. "First hard freeze this weekend" produces a useful one.

24. Turn Real Customer Questions Into Content Ideas

Use this when your technicians and CSRs answer the same customer questions over and over, and none of that knowledge has ever turned into a blog post, FAQ page, or social post.

COPY + PASTE THIS:

Here is a list of questions our technicians and office staff get asked regularly by customers:

QUESTIONS:
[LIST OF REAL CUSTOMER QUESTIONS, AS MANY AS YOU HAVE]

For each question, suggest a content format it would work well as (a short blog post, an FAQ entry, a one-minute video script, a Google Business Profile post) and a working title. Group any questions that are really the same question asked different ways. Don't invent new questions I haven't given you. I want this grounded in what customers are actually asking, not generic industry topics.

MAKE IT BETTER: Ask your CSR or dispatcher to jot down every question they got asked this week before you run this prompt. A real week of questions beats trying to remember them from memory.

25. Rewrite Website Copy Around the Customer's Problem, Not Your Company

Use this when your website talks about how long you've been in business and how professional your team is, and not much about what the customer is actually trying to solve.

COPY + PASTE THIS:

Here is the current copy from my website's [PAGE, e.g. "homepage" or "AC repair page"]:

CURRENT COPY:
[YOUR CURRENT WEBSITE COPY]

Rewrite this to lead with the customer's problem (why they're on this page, what's going wrong, what they're worried about) before talking about my company. Keep every factual claim I've given you (years in business, certifications, service area, guarantees) but don't invent new ones. Cut generic phrases like "quality service" and "customer satisfaction is our priority" unless there's something specific backing them up. Write it the way you'd explain it to a neighbor whose AC just died on the hottest day of the year.

MAKE IT BETTER: If you have a competitor's copy that's outperforming yours, or copy from a company you admire, paste it in as a reference for tone only, not content to imitate.

Frequently Asked Questions

Is ChatGPT actually useful for a home service business, or is this just hype?
Contractors don't need AI to run the business. For the specific work in this list, drafting, organizing, and analyzing messy information, it's genuinely useful. It won't book jobs or fix a furnace. It will help you respond to a one-star review faster than staring at a blank screen for twenty minutes.

Do I need the paid version of ChatGPT, or does the free version work for this?
The free version handles almost everything on this list: writing, rewriting, and basic analysis. The paid version is worth it mainly if you're regularly pasting in large amounts of data at once, like a full week of call transcripts, or you're using it daily across a team and want more consistent access. Start free. Upgrade if you outgrow it.

Is it safe to paste customer information into ChatGPT?
Be conservative. Remove information ChatGPT doesn't need to do the task, names, addresses, payment information, account numbers, and other identifying details usually aren't necessary to get a useful answer. Never paste payment information, social security numbers, or full account numbers. If your company handles sensitive customer data under a specific compliance requirement, check with whoever manages that before pasting anything into any AI tool. When in doubt, take it out.

Can ChatGPT replace my CRM, field service software, or answering service?
No. ChatGPT doesn't store your customer data, schedule jobs, or answer the phone. It's a tool for the writing, organizing, and analysis work that happens around those systems, not a replacement for them.

Will using these prompts make my emails and reviews sound like AI wrote them?
Only if you send the first draft without reading it. Every prompt in this list is built to produce something you edit, not something you paste and send blind. Read it out loud before you send it. If it doesn't sound like you, change the words that don't.

What's the fastest way to actually start using this?
Pick the prompt that solves the problem sitting in front of you right now, not the one that sounds most impressive. Angry email in your inbox? Start with #5. No urgent problem today? Start with #21 or #24. Most contractors get more value from using three of these consistently than from bookmarking all twenty-five and using none of them.

Start With the Problem You Have Right Now

None of this replaces the fundamentals. A contractor who answers the phone, follows up on estimates, and treats customers well was going to be fine with or without ChatGPT. What these prompts do is make the ordinary parts of that work faster and a little less error-prone, on a Tuesday afternoon when you've got four other things happening at once.

If you use even five of these regularly, you'll notice something. A lot of what "growing the business" actually requires isn't new leads. It's paying closer attention to the ones you already have.

Before you buy another lead, find out where the last one went.