Related
Recommended
Marcus Webb (Staff)

As we move into the second half of 2026, we wanted to take a moment to reflect on what we have built together over the past twelve months — and share where we are headed next.

The Releases That Shaped This Year

It has been a busy twelve months. Here are the highlights:

  • FieldPulse 3.2 introduced Route Optimization, one of our most requested features. Dispatch teams now save hours every week with intelligent routing that accounts for traffic, technician skills, and job priority.
  • FieldPulse 3.3 delivered enhanced mobile capabilities including Offline Mode on iOS and Android, giving technicians reliable access to work orders even in remote or low-connectivity environments.
  • We launched Customer Portal Beta, allowing your clients to track job status, view appointments, and access documentation without picking up the phone.
  • Photo Annotation Tools arrived in field documentation, making it easier for technicians to mark up images and communicate clearly with office teams.
  • SLA Breach Alerts and Escalation Rules gave operations leaders proactive visibility into service level commitments.

What We Learned From Our Customers

Behind every feature is a conversation. This year, we conducted over 200 customer interviews and reviewed thousands of support interactions. Three themes emerged:

1. Offline-first is non-negotiable. Field operations do not happen in conference rooms with reliable Wi-Fi. We doubled down on our commitment to offline-first architecture, and it will remain central to our roadmap.

2. Integration complexity is painful. Many of you are running FieldPulse alongside five or more other systems. We heard you — and we are responding.

3. Adoption at scale is hard. Rolling out new software to fifty-plus field technicians requires more than a training video. We published Tips for Rolling Out FieldPulse to a Field Team of 50+ based on what worked for customers like you.

Looking Ahead: Priorities for H2 2026

Here is what we are focusing on next:

  • Deeper Integrations: We are expanding our partnership ecosystem. Expect native connectors to additional accounting platforms and expanded webhook capabilities for custom workflows. Read more about our integration strategy.
  • Advanced Reporting: The reporting engine is getting a ground-up rebuild. Early access will open to select customers in Q3. A peek behind the curtain.
  • AI-Powered Dispatch Assistance: Intelligent suggestions for job assignment based on historical patterns, technician performance, and real-time conditions.
  • Customer Portal General Availability: Taking the beta learnings and delivering a fully featured client experience.

Thank You

This product only exists because of the feedback, patience, and partnership of customers like you. Every feature request submitted, every bug report filed, every late-night support chat — it all shapes what we build.

We are excited for what comes next.

— Marcus

  • 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.

  • 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.

  • in reply to Keiko Tanaka

    Keiko — excellent question. The AI assistance layer will be opt-in and explainable. Every suggestion will include a confidence score and the factors that informed it (proximity, skill match, historical performance, etc.).

    We are also building an override mechanism so dispatchers retain full control. Happy to connect you with the product team for an early look when we open the beta.

  • 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.