Support process
Where to go when something blocks you, and how to report issues so they resolve fast.
Last updated June 1, 2026
Support exists for the moments when Forest is blocking your work and you need it unblocked. This is distinct from product feedback, which shapes the roadmap over time.
When to use support
Reach out to support when you hit an error, lose access, see data that looks wrong, or cannot complete a task you should be able to complete. If the product is working as designed but you wish it worked differently, that belongs in the feedback process instead.
How to report an issue
A good report shortens resolution time. Include:
What you were trying to do, in one sentence.
Where in Forest you were, described generally (your dashboard, the CAMP assessment, the Forest Map).
What you expected versus what happened.
The specific capability, domain, or score involved, if any.
When it happened, so we can match it to system activity.
Because scoring is deterministic, an issue tied to a specific capability and its maturity and criticality values is usually reproducible on our side. That reproducibility is what lets us confirm a fix rather than guess at one.
Note the time and the exact capability before you retry. Retrying can change inputs and obscure what went wrong.
What to expect back
We acknowledge issues, tell you whether we can reproduce them, and give you a path forward. If something requires a product change rather than a fix, we move it into the feedback track and tell you so.