All use cases
Invoicing & Money

A developer built a small plumbing company a booking and invoicing system. The AI chatbot was the part nobody used

Pay-by-link invoices, estimates customers approve online, and one dispatcher screen made the difference. Customers still preferred to call or text.

Real storyDone with A custom booking/invoicing system (Stripe payment links, online estimate approval, tech dashboard) with an AI chatbot
TradesAll trades

What they did

In r/smallbusiness, u/EarlyNeedleworker, a web developer, wrote that he "spent the last few months building a custom system for a small US plumbing business: online booking, estimates, invoices, Stripe payments, and a dashboard for the techs." He said: "Going in, I assumed the fancy stuff would matter most. It didn't."

How it went

What he says made a difference: "Online payment links on invoices. Customers paid faster when they could tap a link instead of mailing a check or calling in a card." "Estimates customers can approve online. Before, estimates sat in email and got forgotten." And "One screen for the dispatcher," which "cut down the 'where is everyone?' phone calls." What they barely used: "the AI chatbot. Customers still preferred calling or texting." His takeaway: "small service businesses don't need more software, they need fewer steps between 'customer wants it' and 'customer paid.'" He gives no numbers. In the comments, u/Both_Walk5427 said a small HVAC outfit he knew lost jobs because customers "opened the email, meant to reply, and just... didn't," and u/JayleaKryska50 put it simply: "when water is actively dripping on the floor nobody has the patience to argue with a bot."

Worth knowing

This is the developer's account, not the plumber's, and there are no figures for how much faster people paid. The useful part is the order of operations: before you add an AI chatbot, make it one tap to pay and one tap to approve an estimate, and put every job on one screen. A couple of commenters (one works on a chat product, so weigh it) suggested that if you do add AI, give it one narrow after-hours job, like collecting the problem, address, a photo and a time window, rather than open-ended chat. Card processing fees are real; one commenter's view was that getting paid faster is usually worth it.

Try it yourself

You are an office assistant for a small Wisconsin plumbing or HVAC shop. You help me cut steps between "customer wants it" and "customer paid." You draft; I review and send. TASK: Look at how my customers get from first call to paid, find the steps that slow us down, and draft the messages that remove them. CONTEXT (fill in the [BRACKETS]): - [SHOP]: Example: Oconomowoc Rooter & Drain (fictional), 3 trucks - [HOW WE QUOTE + INVOICE TODAY]: Example: estimates as PDF by email; invoices mailed or emailed; customers pay by check or call in a card - [WHAT MY SOFTWARE CAN DO]: Example: our field-service app can send a pay link and an "approve estimate" link, but we've never turned them on - [OPEN ESTIMATES]: paste a list (customer first name, job, amount, date sent). Example: (fictional) Dana, water heater swap, $2,150, Oct 20 - [UNPAID INVOICES]: paste a list (first name, amount, days late) STEPS: 1. Write out our current path from call to paid as numbered steps. Mark every step where we wait on the customer or chase them. 2. For each wait step, say whether [WHAT MY SOFTWARE CAN DO] could remove it (pay link, approve link, text instead of email). 3. Draft a short text for each open estimate in [OPEN ESTIMATES], under 300 characters, with a placeholder [APPROVE LINK]. 4. Draft a friendly pay-by-link reminder for each item in [UNPAID INVOICES], with a placeholder [PAY LINK]. Firmer wording only past 30 days. 5. List three things I should check in my software settings this week. RULES: - Use only the names, amounts and dates I give you. Never invent a price, discount or due date. - No pressure language, no fake urgency. Plain, neighborly tone. - Don't recommend adding a chatbot unless I ask. - Every message starts with DRAFT - REVIEW BEFORE SENDING. OUTPUT FORMAT: Part A: current path with wait steps marked. Part B: what my software can fix. Part C: estimate texts. Part D: invoice reminders. Part E: three settings to check. FOLLOW-UPS TO TRY NEXT: - "Write the one-sentence line I put on every invoice explaining the pay link and card fee." - "Draft a 4-question after-hours text-back: problem, address, photo, best time window." - "Here are last month's estimates. Which ones went quiet longest, and what should I say?" FILLED-IN EXAMPLE (fictional Wisconsin business): - [SHOP] = Oconomowoc Rooter & Drain (fictional) - [HOW WE QUOTE + INVOICE TODAY] = PDF estimates by email, checks by mail - [WHAT MY SOFTWARE CAN DO] = pay links and approve links, not turned on - [OPEN ESTIMATES] = 6 estimates, oldest Oct 12 - [UNPAID INVOICES] = 4 invoices, one 45 days late
Open the full playbook

Want help getting this working? Rise Systems in Oconomowoc sets these up.

Want this running in your business without the DIY? Rise Systems in Oconomowoc sets these up.

Free 15-minute AI check-up
Read the original

Source: Reddit · October 31, 2026

Related
HV
Follow up on every unsold estimate

A 3-message follow-up sequence you can send by hand or load into your software.

HVACPlumbingElectricalGarage doorsAuto repairAuto bodyMediumPlaybook
Wisconsin Trades AI editorial·Oct 2026