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

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.

Brandon, thanks for calling this out! We know batch operations are a gap right now, especially for operations teams managing high volumes. I'm curious—would you want to see this as multi-select checkboxes with a bulk action dropdown, or something more like drag-to-reschedule for date ranges? Both are on our radar and your input helps us prioritize!

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.

In my experience voice notes that auto-transcribe. I'm typing on a phone all day with greasy hands or gloves on half the time. Taking photos is fine but sometimes I need to explain what I'm seeing. Every other app has this by now.

^^ this tbh. voice to text would save me so much time lol

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.

Happy to help here, Art and Sam! This is a popular request and I can confirm it's in our backlog. In the meantime, a few teams have found success using their device's built-in voice-to-text in the keyboard (microphone icon on iOS/Android) when adding notes — not perfect, but might bridge the gap.

We're evaluating transcription accuracy across field conditions (background noise, accents, technical vocabulary) to make sure we deliver something reliable when we ship it.

Executive dashboard with predictive metrics. Right now I can see what happened yesterday. I need to see what's about to break.

Specifically: which jobs are trending toward SLA breach based on current status and typical completion times for that job type. The data is all there. Give me early warning instead of post-incident reporting.

This would change how we manage operations from reactive to proactive.

A predictive SLA view would be valuable from a governance perspective as well. It is worth noting that any predictive capability introduces compliance considerations around algorithmic transparency — i.e., can we explain why a job was flagged as at-risk?

From a governance perspective, I would recommend:

• Clear documentation of the prediction methodology
• Human override capability with audit trail
• Confidence scoring rather than binary at-risk/not-at-risk classification

Happy to discuss further if this moves into design phase.

Valid points, and I appreciate the rigor. Confidence scoring would actually be more useful than binary flags for my use case — lets me prioritize which jobs get attention first.