What should a contractor's AI teammate hand off to a person?

Which messages a contractor's AI teammate should hand off right away, and how to write rules a teammate can follow.

What should a contractor's AI teammate hand off to a person?

A contractor's AI teammate should hand off anything involving money, safety, legal commitments, schedule changes, customer complaints, and any request to speak with a responsible person. The teammate can organize each request, gather the relevant details, and draft a response for your consideration. A person then decides what happens next, and that boundary remains in place for as long as the business operates.

Hey Button runs on OpenClaw, an open automation framework, with models like Claude and GPT answering through it. That architecture matters for a hand-off list, because the list performs reliably only when the teammate is configured around your actual jobs, your crew's routines, and the approval rules you establish. This guide explains which situations belong with you immediately, how to articulate those rules in clear language, and when this approach is an unsuitable fit for a trade business.

Why does a contractor need a written hand-off list?

A written list gives the teammate one rule set to apply to every message, including the late Sunday evening when you are unavailable and the crew is off the clock. Contractors receive correspondence at unpredictable hours, often from a driveway, a job site, or a truck between appointments. A roofer in Fort Wayne might receive a message about a ceiling stain during a January thaw, and the message may look routine until it mentions dripping near a light fixture. A written hand-off list converts that judgment into a consistent rule the teammate applies every time.

Without a list, the teammate relies on general instructions, and general instructions produce inconsistent outcomes. One day a sensitive message reaches you appropriately. The next day a comparable message receives a courteous draft that promises a same-day visit nobody has actually scheduled. A specific list prevents that inconsistency by identifying categories of concern in advance. Each rule states what the teammate should do, what it must never do, and who must receive the message.

A well-constructed list stays short enough to review in five minutes. It concentrates on situations that could cost money, create liability, or damage a customer relationship that took years to build. Everything else functions as an ordinary draft-and-approve item, which the teammate handles under your review rather than under your undivided attention. If you run a construction or remodeling business, see how Button works for contractors and remodelers.

Which money questions should always go to you?

Any message containing a dollar amount belongs with a person. That category includes quotes, deposits, change orders, payment arrangements, refunds, credits for a missed service day, and requests to reduce an outstanding balance. The teammate can assemble the factual background for each question. Where it has access to your job records, it can pull the job name, the scope recorded in the original estimate, and any photographs the customer already sent. It should not state a price, offer a discount, or propose a payment term on its own, because each of those decisions belongs to the person who owns the account.

Pay particular attention to the indirect form of money questions. A customer who asks, "Could you do it for less if I pay in cash?" is asking about price, even though the word discount never appears. A customer who asks, "When would the second half become due?" is asking about payment terms in substance. Your list should include phrasing of this kind, because a rule that detects only the word "price" overlooks most of the financial questions customers actually send.

The teammate can still assist with administrative work surrounding money without making the underlying decision. Where it can see invoice data, it can flag an invoice that has remained unpaid beyond your normal window, or draft a neutral acknowledgment stating that you will review the question and respond promptly. Establishing the amount, approving any credit, and agreeing to the terms remain your responsibility.

A practical starting list for money triggers includes these categories:

  • Any request for a quote revision, discount, credit, or payment arrangement
  • Any question about a deposit, an invoice, a late fee, or a payment schedule
  • Any mention of a refund, a chargeback, or a payment that did not clear
  • Any change order that adds scope after the work has already begun

What about safety, hazards, and emergencies?

Hazard messages reach you immediately, with no draft attached. If a customer describes a gas odor, exposed wiring, water penetrating a ceiling, a tree resting on a roofline, or a downed line beside a driveway, the teammate must not draft a reassuring reply and defer action until morning. Your rule should direct the teammate to flag the message at the top of your review queue, so that you read the customer's exact words before anyone pulls an address or the account history into the picture. A landscaper in Northeast Indiana may hear about a limb across a driveway after a storm, and that message needs the same treatment as a gas odor.

Treat the teammate as an organizer rather than an emergency service, and write a rule that tells it to stop drafting on any hazard-related message and wait for your direction. Emergency contact information should reach the customer through a message you approved in advance, not through an improvised reply composed during a crisis. Anyone facing immediate danger must contact emergency services first, and your published instructions should state that plainly and prominently.

Hazard rules should extend to the job site itself. A crew member's text reporting a leaking fuel container, a cracked ladder, or a neighbor's complaint about an unsafe arrangement should reach you before anyone responds. The teammate can read the message and flag it immediately, which keeps it from waiting in an ordinary queue. A licensed person must decide what the crew does next, because that decision carries regulatory obligations and personal liability that no software configuration can assume.

When does a complaint become a human responsibility?

A complaint becomes your responsibility once the customer uses forceful language, threatens a public review, mentions an attorney, or says payment will be withheld. Before that point, the teammate can respond to a mild concern with a neutral, courteous draft, provided you approved the tone beforehand. Most complaints start as mild concerns. The grass was trimmed unevenly, the crew left debris near the curb, or an invoice appears higher than the customer expected.

A straightforward test clarifies most cases. If a reasonable business owner would contact the customer directly before replying, the teammate should hand the message off. Experienced operators recognize these messages almost immediately, yet the difficulty lies in articulating that instinct precisely enough for a teammate to apply it consistently across customers and seasons. Draw examples from your own correspondence. A brief collection of genuine messages, each labeled "hand off" or "draft," conveys the rule more effectively than several pages of abstract policy language.

Repeated complaints warrant a separate rule, since a second message concerning the same job within a few days indicates that the initial response failed to resolve the underlying concern. Even when the second message sounds composed, the teammate should route it to you, because persistence often signals that the customer no longer expects a useful answer from the business.

Which scheduling and warranty questions need a person to decide?

A person decides every change that moves a visit to a new day. Scheduling is where small commitments quietly break. A customer requests moving a Tuesday visit to Thursday. The crew is already fully booked, yet a draft reply says, "No problem, see you Thursday," because nobody verified the calendar before the message went out. The teammate can record the request, identify the existing booking, and draft a response asking the customer to wait while the change is confirmed. It should not confirm a new appointment independently.

Separate schedule changes into three categories to keep the rules unambiguous. A minor same-day adjustment, such as moving an arrival from morning to early afternoon, may qualify as a draft-and-approve item after you have reviewed several examples. Relocating a visit to another day, adding an unplanned visit, or canceling a recurring service always returns to you. Weather-driven changes, such as a freeze-delayed pour in Fort Wayne or storm response across Northeast Indiana, also remain with you, because those decisions depend on field conditions that no inbound message can fully capture.

Contractors also encounter questions that sound simple yet carry substantial legal weight. "Does this cover the roof if it leaks again?" "Are you licensed and insured for this kind of work?" "Will you repair it at no charge?" The teammate should route each of these to you. A confident-sounding answer that implies coverage can produce a dispute you never intended to begin, and a customer who relied on a hastily approved draft will remember the implied promise.

Licensing and insurance questions merit a specific rule. Your list can include license numbers, certificate language, and coverage summaries that you verified in advance, so the teammate can share approved facts accurately. It should not characterize your coverage in its own words or assert that a particular project is covered. Those determinations depend on policy terms and project details, and only you can make them responsibly.

Warranty requests follow the same logic. The teammate can collect the purchase date, the work performed, the photographs, and the customer's account of the problem, which reduces repetitive back-and-forth considerably. A person then determines whether the warranty applies. Write that rule explicitly, because an accommodating system will naturally lean toward agreement, and generosity in this area can cost real money.

How do you write a hand-off rule the teammate can follow?

Write rules as concrete situations instead of broad principles. "Never discuss sensitive issues" offers almost nothing a teammate can test. "If a customer mentions a gas odor, water entering a ceiling, or a downed line, flag the message for me and do not draft a reply" identifies precisely what to recognize and precisely what to do about it.

Each rule benefits from three components: a trigger, an action, and a boundary. The trigger describes the situation using the words a customer would plausibly employ. The action specifies what the teammate does, whether that means flag, draft, gather, or organize. The boundary specifies what it must not do, such as quoting a price, confirming an appointment, or characterizing coverage. Three concise sentences per rule usually suffice for a trade business, and ten carefully constructed rules cover most of an ordinary inbox.

Derive the first version from your own history. Retrieve a recent batch of customer messages and sort them into three groups. The first group contains messages you would have handled without deliberation. The second contains messages you would have wanted to examine more closely. The third contains messages that required a direct conversation before anyone responded. The second and third groups become your initial hand-off rules, and the first group shows where the teammate can operate with reduced supervision.

Share the draft rules with the people who answer messages and drive the trucks. A crew lead frequently observes hazards, neighborhood patterns, and recurring complaints that never reach the office. A brief conversation can add a rule that would otherwise require weeks of errors to discover, and it gives the crew a meaningful stake in how the system functions.

A hand-off list that routes everything to you defeats its purpose. The objective is to return your evenings and reserve your attention for work that genuinely requires it. Many messages should flow through the teammate with little or no friction. Examples include requests for the business address, questions about office hours, requests for an approved service area list, basic descriptions of standard services, and questions about when crews typically work in a particular neighborhood. Those items suit draft-and-approve well, and as confidence accumulates, you may allow a few of them to send without review.

Organizational work also transfers well to the teammate. It can consolidate new requests into one list, identify which requests lack an address or photographs, and draft a short note requesting the missing information. You can also write standing details into the rules, such as a preferred contact window or a gate instruction, so that the crew does not ask the same question twice.

The table below shows a practical division between tasks the teammate initiates and decisions that remain with you.

Message typeTeammate's first stepWho decides
Quote request for a standard serviceGather address, scope, and photos, then draft a replyYou approve the reply and any price
Question about business hoursDraft from the hours you approvedYou approve the first several, then adjust
Deposit or invoice questionPull invoice details and draft a neutral replyYou
Gas odor, exposed wiring, or active leakFlag at the top of your review queueYou, immediately
Request to move a visit to a new dayNote the existing booking and draft a hold replyYou
Warranty or insurance questionGather purchase date, work performed, and photosYou

How do you keep the rules working when you are away?

Start with draft-and-approve, review every draft for the first few weeks, and keep a short log of two kinds of miss. The first is a message that should have reached you but did not. The second is a message that reached you without requiring a decision. Each missed hand-off becomes a new rule or a sharper version of an existing one, and each false alarm clarifies a boundary. Both kinds of error produce useful information.

Monitor the queue as well as the drafts, because when the same message type arrives every day, an approved template can let you clear those items in seconds. When almost nothing reaches the queue for a week, confirm that the rules still trigger on realistic examples, because silence reassures you only after the rules have been tested. The client portal displays what the teammate is doing and why, which makes this review considerably faster than reconstructing events from scattered records.

Run a short test every month. Compose three or four realistic messages covering money, safety, scheduling, and a complaint, and verify that the teammate routes each one as you intended. The exercise requires roughly fifteen minutes and detects the drift that accumulates when prices, crews, or service areas change without anyone updating the instructions.

Vacations, family obligations, and busy field weeks all create gaps in review, so plan for them before they occur. Designate one backup person who can review drafts and approve replies, and confirm that this person understands the hand-off rules as thoroughly as you do. Provide a written summary covering money, safety, and complaints, because those messages cannot safely wait.

When nobody is available to review, change the teammate's access to read-only until you return. Under read-only access, the teammate cannot send replies to customers, so nothing leaves the business until a person has examined it. That single adjustment prevents the most common absence problem, which is a backlog of unapproved drafts or a customer who received a promise nobody intended to make.

How should a contractor start this week?

Begin with ten rules rather than fifty, because a short list gets tested and revised while a long one gets ignored. Organize them under the categories in this guide: money, safety, complaints, scheduling, legal and warranty questions, and everything else. Write each rule as a trigger, an action, and a boundary. Test the rules against messages from the past month, and revise any rule that catches the wrong messages. Then set access to draft-and-approve, review the first batch carefully, and refine the rules as the real queue reveals what matters most.

If you would like Hey Button's help converting your inbox into a first draft of those rules, the logical next step is a brief intake conversation. The how-it-works page explains how that setup begins and what it covers. The access levels page describes read-only, draft-and-approve, and full access, so you can decide how much latitude the teammate should have before any message reaches a customer.

Frequently Asked Questions

Usually not all of them. Many owners let routine questions, such as hours or service areas, go out after review, then keep money and safety behind approval. They widen access only after drafts consistently need little editing. Set the first review window to a week, then extend it once the queue stays quiet and accurate.
Hand off any message that mentions a hazard, such as a gas odor, exposed wiring, or water coming through a ceiling. That rule takes the least time to write and prevents the most serious outcome. Pair it with your emergency number in an approved message, so a customer in danger never waits on a draft.
Review the queue during the first few weeks and log two kinds of misses. Note messages that should have reached you but did not, and messages that reached you without needing a decision. Test several realistic examples each month. Rules that route the right messages during testing usually hold up well in daily use.
Not on its own. With job records in hand, the teammate can attach the original estimate and photos, and it can draft a neutral holding reply for your approval. Put the approved price range in your rules, so it never invents a figure, and leave the final number to you.
No. The teammate organizes requests, drafts replies, and flags urgent messages, but a person still makes the decisions that matter. Plan for a person to cover live contact with customers. Treat the teammate as the organized inbox behind that person, one that keeps the queue clear and the record current.
Should a contractor let an AI teammate reply to every customer message?
Usually not all of them. Many owners let routine questions, such as hours or service areas, go out after review, then keep money and safety behind approval. They widen access only after drafts consistently need little editing. Set the first review window to a week, then extend it once the queue stays quiet and accurate.
What is the first hand-off rule to write if I only have time for one?
Hand off any message that mentions a hazard, such as a gas odor, exposed wiring, or water coming through a ceiling. That rule takes the least time to write and prevents the most serious outcome. Pair it with your emergency number in an approved message, so a customer in danger never waits on a draft.
How do I know my hand-off rules are working?
Review the queue during the first few weeks and log two kinds of misses. Note messages that should have reached you but did not, and messages that reached you without needing a decision. Test several realistic examples each month. Rules that route the right messages during testing usually hold up well in daily use.
Can the teammate quote a price or offer a discount?
Not on its own. With job records in hand, the teammate can attach the original estimate and photos, and it can draft a neutral holding reply for your approval. Put the approved price range in your rules, so it never invents a figure, and leave the final number to you.
Does an AI teammate replace the person who handles the front desk?
No. The teammate organizes requests, drafts replies, and flags urgent messages, but a person still makes the decisions that matter. Plan for a person to cover live contact with customers. Treat the teammate as the organized inbox behind that person, one that keeps the queue clear and the record current.

Hey Button

Want a teammate that handles this for you?

Answer a few questions about your business and Hey Button will show you what an AI teammate would take off your plate, with you approving anything that goes out.

Start the questionnaireSee what teammates do
Lucas M. Button

Written by Lucas M. Button

Founder, Hey Button

Lucas builds AI teammates for small businesses across Northeast Indiana and writes about what works, what doesn't, and what to hand off first. More about Lucas