Wishlist: what feature would make the biggest difference for your team?

Hey everyone! Wave

We're always looking for ways to make FieldPulse work better for the teams using it every day. While we have a roadmap we're excited about, we want to make sure we're building what you actually need.

So here's the question: if you could wave a magic wand and have one new feature (or big improvement to an existing one), what would it be?

We're especially interested in hearing:

  • What pain point this would solve
  • How often it comes up in your daily workflow
  • What you're doing as a workaround today

No idea is too small or too ambitious—we want to hear it all! This thread will be shared directly with our product team, so your voice will absolutely be heard.

Looking forward to learning what's on your wishlist! Pencil

Parents
  • Bulk editing on the dispatch board. Every time we have a weather delay or need to shift 15+ jobs, we're clicking into each one individually. My team can't move forward until this is done and it takes 45 minutes. Should take 5.

  • Same pain here. We end up exporting to Excel, making changes, then re-importing which feels ridiculous for a cloud platform. The checkbox + bulk action model would work better for us because we often need to reassign to different techs, not just shift dates. Drag-to-reschedule is nice for visual but doesn't handle the reassignment use case.

    One thing I'd add: if you do this, please include a confirmation modal with a summary of what's changing. We've had too many accidents with bulk operations in other tools.

  • Gwen, Brandon — appreciate the detailed feedback here. This aligns with what we're hearing across the customer base.

    Current thinking: We're exploring a multi-select interaction with staged changes (think: shopping cart pattern) where you can review everything before committing. This would support:

    • Date/time shifts
    • Technician reassignment
    • Status updates
    • Template application

    No committed timeline yet, but this is in active discovery. We'll be reaching out to a few of you for interview sessions if you're open to it — powerful insights like these help us build something seamless rather than assuming we know the workflow.

Reply
  • Gwen, Brandon — appreciate the detailed feedback here. This aligns with what we're hearing across the customer base.

    Current thinking: We're exploring a multi-select interaction with staged changes (think: shopping cart pattern) where you can review everything before committing. This would support:

    • Date/time shifts
    • Technician reassignment
    • Status updates
    • Template application

    No committed timeline yet, but this is in active discovery. We'll be reaching out to a few of you for interview sessions if you're open to it — powerful insights like these help us build something seamless rather than assuming we know the workflow.

Children
No Data