Product News - All Comments

RE: Year in Review: What We Shipped and What's Coming

Carla Jimenez (Staff) — Tue, 21 Apr 2026 09:20:00 GMT

Josh, thank you for sharing that — we love hearing when features translate to real outcomes in the field.

For anyone considering the Customer Portal beta, we want to make sure you are set up for success. The onboarding process includes a guided setup call, and we have seen the best adoption when customers involve their client-facing teams early.

If you would like to discuss whether the portal makes sense for your client base, feel free to reach out directly. We are here to help you think through the rollout.

RE: Year in Review: What We Shipped and What's Coming

Josh Mercer — Mon, 20 Apr 2026 18:45:00 GMT

Pro tip for anyone still on 3.1: the offline improvements in 3.3 are worth the upgrade alone. We run crews in rural areas with spotty coverage and it has eliminated most of the sync headaches we used to see.

Also, the photo annotation tools have cut down on callbacks since techs can mark exactly what they are looking at. Small feature, big impact.

RE: Year in Review: What We Shipped and What's Coming

Keiko Tanaka — Mon, 20 Apr 2026 14:30:00 GMT

Strong recap. The offline-first commitment is particularly relevant for our distributed teams.

On AI-powered dispatch: what guardrails are you considering for automated assignment? We will need transparency into decision logic before rolling this out at scale.

RE: Performance and Reliability Improvements — Fall Release

Anita Sharma — Mon, 13 Apr 2026 08:15:00 GMT

Is there a detailed changelog available regarding which specific API endpoints were optimized? Our integration relies heavily on the /workorders and /technicians endpoints, and we would like to document any behavioral changes for our internal records.

RE: Performance and Reliability Improvements — Fall Release

Carla Jimenez (Staff) — Sun, 12 Apr 2026 16:08:00 GMT

Hi Mike, glad to hear you're seeing the improvement! We want to make sure you're set up for success with these changes — if your team notices any lingering slowness during peak dispatch hours, feel free to reach out and we can take a closer look at your account specifically. Thanks for the feedback!

RE: Performance and Reliability Improvements — Fall Release

Mike Dolan — Sun, 12 Apr 2026 14:22:00 GMT

Dispatch board is actually usable in the morning now. About time.

RE: Why We Rebuilt the Scheduling Engine from Scratch

Keiko Tanaka — Sun, 05 Apr 2026 16:45:00 GMT

Appreciate the transparency on the eighteen-month timeline. From an operational planning perspective, can you share whether the automated scheduling suggestions you mention will require opt-in configuration, or will they be surfaced automatically to dispatchers?

RE: Why We Rebuilt the Scheduling Engine from Scratch

Brandon Okafor — Sun, 05 Apr 2026 14:22:00 GMT

We have 340 technicians and the load times were killing us. This is exactly what we needed.

RE: What's New in the Mobile App — Q3 Update

Deja Washington — Sun, 29 Mar 2026 09:22:00 GMT

Thanks so much for this recap Eli! Really appreciate the transparency on the gotcha with older app versions — we'll make sure our team is updated before Monday. Quick question: is the predictive sync thing going to be optional? We have some techs on limited data plans and want to make sure we're not surprising them with downloads.

RE: What's New in the Mobile App — Q3 Update

Art Kowalczyk — Sat, 28 Mar 2026 18:12:00 GMT

In my experience "automatic" offline mode usually means it waits too long and you've already lost data. We'll see if this one's different.

RE: What's New in the Mobile App — Q3 Update

Tyler Hatch — Sat, 28 Mar 2026 16:34:00 GMT

yo the photo annotation is huge ngl. my guys been using markup apps forever and its always a mess. havent seen the auto offline thing trigger yet but ill keep an eye out

RE: Photo Annotation Tools Added to Field Documentation

Lindsey Park — Thu, 19 Mar 2026 08:17:00 GMT

Sorry if this is a silly question, but I wanted to make sure I understand — when you save the annotated version, does that count against our storage limit as a completely separate file? Or is it more like a layer on top? We take a lot of photos in our line of work and I am just trying to figure out if we need to be more careful now about how many versions we are keeping. Thank you so much for any clarification!!

RE: Photo Annotation Tools Added to Field Documentation

Sam Kowalski — Wed, 18 Mar 2026 16:45:00 GMT

lol finally no more trying to describe which wire is which over the phone

RE: Photo Annotation Tools Added to Field Documentation

Josh Mercer — Wed, 18 Mar 2026 14:22:00 GMT

Been using this in beta for a few weeks. Pro tip: the yellow highlighter shows up way better than red on photos taken in direct sunlight. Also if you need to annotate a whole sequence of photos the same way, do your markup on the first one, save it, then use that as reference for the rest — keeps things consistent for the office folks reviewing later.

RE: How We're Approaching Integration Partnerships in 2025

Omar Hassan — Sat, 07 Mar 2026 08:44:00 GMT

From a governance perspective, the 12-month deprecation commitment is welcome. However, it is worth noting that the phrase "breaking API changes" requires precise definition. Does this include:

Removal of fields from response payloads (i.e., additive-only guarantees)?
Changes to enum value sets (e.g., job.status gaining new states)?
Modifications to webhook delivery ordering or retry semantics?

The RFC should reference specific sections of the RFC 7807 problem details specification if you're adopting standard error formats, which would assist in automated client adaptation.