Agency and person
Agency name, your role, and the affected user when relevant.
Founder-run product support
Get the next step without losing the work.
Tell Andrew or Sierra what you were doing, where the workflow stopped, and what you expected. We use that context to reproduce the issue and point you to the safest supported next action.
Issue navigator
Start with the surface that stopped you.
Choose the closest path. The useful details beside it help us begin with the actual workflow instead of asking you to repeat the whole story.
- 01
Account access
Sign-in, password recovery, setup links, roles, and questions about authorized access.
Useful contextAffected person, attempted access path, and the message shown.
- 02
Agency setup
Agency Lead setup, staff access, assigned jurisdiction, and rollout configuration.
Useful contextAgency, jurisdiction, intended setup, and the step that stopped.
- 03
Billing and paid users
Subscription status, invoices, billing cadence, purchased quantity, or purchased-user setup.
Useful contextInvoice or event reference, cadence, quantity, and expected account state.
- 04
Field Documents, ScopeBook, and WAP Chat
Approved source processing, jurisdiction-package readiness, activation, source-backed availability, or citation questions.
Useful contextAgency jurisdiction, source or citation, and the readiness state shown.
- 05
Job and Field visit
Address-first Job setup, Field visit capture, Field Visit Readiness, Site Sketch, connected results, or Standalone Work.
Useful contextJob workflow area or connected tool, action attempted, and expected result.
- 06
Assessment Check and closeout
Completed-assessment comparison, Job Work Packet review, Export Job, or supporting-material handoff.
Useful contextJob, assessment input or export step, and the result you expected.
A useful support brief
Send enough context to act.
Do not diagnose the system for us. Describe the work, the stopping point, and the result you expected.
Exact surface
Page, tool, Job step, or account step where the problem occurred.
Expected versus actual
What you were trying to complete and what happened instead.
Safe evidence
Approximate time, browser or device, and a safe screenshot when useful.
Support boundaries
Product help and program authority stay distinct.
Andrew and Sierra can help with
- Product behavior and supported workflows
- Account, role, setup, and agency-access questions
- Billing, source readiness, records, and field-tool use
- Reproducing a defect and identifying the next supported action
Your agency remains responsible for
- Governing requirements and current program material
- Required approvals and official agency decisions
- Qualified calculations, professional judgment, and field verification
- Reviewing work before it becomes an official record or decision
Security concern
Use the security path—not ordinary product support.
Email security@fieldscouts.ai with the affected surface and what you observed. Do not include passwords, secrets, card details, or unnecessary household information.