August 2026 Local Business Pro updates
The release work that matters is rarely one shiny button. It is the set of improvements that make a service business easier to move, run, bill, schedule, and support without asking the team to hold the operation together with memory.
This August release brings meaningful progress across that system: controlled provider migrations, configurable automation behavior, more consistent invoice setup, clearer payment choices, safer scheduling, stronger contact handling, and better estimate-work protection.
Move the history you need to operate
Teams changing systems can now evaluate a controlled Housecall Pro import path and a first-class FieldPulse import workflow. Both stories are deliberately honest: a migration needs source evidence, review, a dry run, and readback. The product should not promise that every historical file is automatically perfect.
Configure more useful field workflow behavior
The new Functions and On My Way update gives operators typed, validated automation configuration and permission-gated ETA/location activity where the workflow supports it. That is a stronger foundation than opaque automation: teams can see what a Function needs before they rely on it.
Make the revenue workflow more consistent
New invoice defaults give eligible future invoices a more reliable starting point without rewriting history. The separate payment-choice update makes configured card, cash, ACH, and eligible Stripe surcharge behavior easier to explain across supported documents and checkout.
Reduce everyday operational friction
The scheduling-confidence update makes business-timezone history, schedule confirmation, contact authority, and calendar recovery more deliberate. The contact-import update strengthens supported file handling while making resolved customer context easier to open from a conversation. And estimate-work protection helps prevent accidental loss during a critical selling workflow.
The throughline: clearer ownership
None of these changes claim that software can replace operational judgment. A migration still needs review. A payment policy still needs a business decision. A calendar move still needs an owner. An automation still needs the right configuration and permission.
What the team delivered is more valuable than a long list of isolated fixes: Local Business Pro gives more of those decisions a clear place to happen, a clearer record afterward, and fewer silent ways to go wrong.
What requires setup or approval
These updates do not all activate in the same way. The Housecall Pro migration path is a controlled canary rollout; payment choices depend on business configuration and eligible provider conditions; and ETA/location activity depends on a supported workflow, permissions, and device context. Each linked release article explains its own operating boundary so teams can decide what is ready to evaluate now.
