Skip to main content

Submitting feedback about Fieldguide

Submit a feature request

Overview

At Fieldguide, we value every piece of feedback from our users to ensure our product continuously evolves to meet your needs. Our team diligently collects feedback from all users, ensuring that every voice is heard.

Through your dedicated Customer Success Manager, we prioritize product suggestions that will have the most significant impact and align with our company's long-term vision. This collaborative process enables us to develop and implement product enhancements that drive value and elevate your experience with Fieldguide.

Submit a feature request by following the steps below.

Submitting an idea

To submit feedback:

  1. Click the Support button on the left-hand navigation bar.

  2. Scroll down in the Support overlay and click Suggest an idea.

  3. Add a title and description to your suggestion, and answer the required “what problem would this solve” question.

  4. (Optional) Provide additional information:

    • Submission category.

    • Frequency of problem.

    • Business impact.

    • An attachment (such as a screenshot).

    • Priority level (Nice to Have, Important, or Blocking/Critical).

  5. Click Create Ticket.

Writing actionable feedback

Above all, we want to know where you’re running issues in Fieldguide and hear your ideas for improvement. That being said, one of the most important things you can do when submitting feedback is to focus on the problem, not just the solution.

That doesn’t mean we’re not interested in hearing your suggestions – we absolutely want to know how you’d solve the problem! But it does mean that suggestions without context are difficult to act on. “I want an in-app tutorial,” for instance, might mean “I don’t know how to use Fieldguide’s advanced features,” “My staff isn’t using tasks correctly,” “My clients don’t know how to respond to requests,” or something else entirely.

Be specific about your use case to increase the chances that our team will see your feedback and act on it.

Did this answer your question?