• Replies 21 replies
  • Subscribers 2 subscribers
  • Views 14 views
  • Users 0 members are here
Options
Related

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

Carla Jimenez (Staff)

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

  • Sorry if this is a silly question, but is there a way to customize the customer portal more? We've been looking at setting it up but the branding options seem limited and our marketing team really wants it to match our website colors exactly. Also can customers upload documents there or just view things? I couldn't find a clear answer and I've been going in circles with the settings. Anyway if that's not a feature yet it would help us a lot because right now we're handling document collection through email and it's getting messy. Thanks for any info!

  • in reply to Lindsey Park

    Lindsey — current customer portal capabilities:

    Customization: Logo upload, primary color selection, custom domain (Enterprise plan). Full CSS control is not available.

    Document upload: Customers can upload documents to an existing work order. They cannot initiate new document submissions without a work order reference.

    See Customer Portal Setup and Customization for configuration steps.

    Document collection outside the portal is a known gap. Some teams use form builders (Typeform, Jotform) with webhook integration to FieldPulse as an interim solution.

  • in reply to Lindsey Park

    Oh thank you so much Fiona! That's exactly what I needed to know. The form builder workaround is actually a great idea for now — really appreciate you taking the time to explain this!

  • Pro tip: conditional logic in checklists. We do commercial HVAC and the questions I need to answer on a rooftop unit vs a split system vs a chiller are completely different. Right now I have three different checklist templates and I have to know which one to pick before I even see the equipment.

    What I want: one master checklist that asks "What type of system?" and then shows me only the relevant sections based on that answer. Would clean up our template library and reduce mistakes from picking the wrong form.

    I'm aware some form tools do this but having it native in FieldPulse would be huge. The current checklist template setup is solid but this is the gap that's cost us time on site.

  • in reply to Josh Mercer

    yesssss this basically I do electrical and commercial vs residential is so different also sometimes I'm doing panel upgrades and sometimes troubleshooting and the checklist that's useful for one is like completely irrelevant for the other so what I did was I made this giant checklist with everything and I just skip the parts that don't apply but that's basically not a real solution tbh and I worry about missing something because I'm scrolling past so much stuff you know

  • in reply to Josh Mercer

    +1 on conditional logic. Our workaround:

    • Job type drives template assignment (via automation rules)
    • Still requires dispatcher to categorize correctly upfront
    • Fails when job type doesn't predict actual work needed

    Would prefer technician-facing logic that adapts in the field.

  • Okay so we have two actually! First is technician-initiated schedule swaps with approval workflow. Right now when someone needs to swap a job they text me and then I have to do all the reassigning manually and it's just a lot of back and forth especially when it's like a weekend or evening and I'm not at my desk. If they could propose a swap and the other tech could accept and then it just needs my approval that would save so much time!

    Second question — is there any plan for better shift handoff tools? We run 24/7 and our night dispatch leaves notes for day dispatch but there's no structured way to do this in FieldPulse so we use a shared doc and it's getting unwieldy. Thanks so much for gathering all this feedback really appreciate it!

  • in reply to Deja Washington

    shift handoff YES. our night crew leaves stickies on my monitor. actual paper stickies. in 2025. something built in for pass-down notes with timestamp and acknowledgment would help

    technician swaps too but honestly anything that keeps them from calling me at 10pm works

  • ...route optimization that actually accounts for real-world constraints.

    Current version optimizes for distance but ignores:

    - Customer time windows (I set these, system ignores them)

    - Technician skill requirements

    - Equipment needed (van capacity)

    So I get a "perfect" route that has my apprentice doing a job he's not qualified for, or a tech arriving outside the customer's only available window. Then I rebuild it manually anyway.

    Either make it actually usable or let me save my manual routes as templates.

  • in reply to Ray DeLuca

    Same. Route optimization is basically useless for us. Turned it off after two weeks.