Support & Feedback

Viewing documentation for: Parent

All Roles Treasurer Leader Parent Scout

Parent focus

Focus on family account visibility, event registration, and payment request workflows.

  • Confirm how family-level balances and member registrations are managed.
  • Use support links when household access or invitation issues appear.

Use this page when you need help, want to report a bug, or want to request an improvement.

TroopForge support starts with the in-app feedback form in the footer, then escalates by role based on the workflow impacted.

Support Channels in TroopForge

  • Primary path: in-app footer Send Feedback form.
  • Best for: bugs, workflow confusion, missing access, and enhancement requests.
  • Feedback link appears only when signed in.

Submit Feedback from the App Footer

  1. Open footer link Send Feedback.
  2. Complete Name (recommended for follow-up clarity).
  3. Complete Email (required) so the team can respond.
  4. Describe the issue in Description (required) with expected vs actual behavior.
  5. Use Add a screenshot when the issue is visual or tied to a specific page state.
  6. Submit with Send Feedback, or use Cancel to close without sending.

If the form does not open, refresh once and retry from the same page. If it still fails, include that detail in your next report.

Support Request Template

  1. Role and account context (treasurer/leader/parent/scout).
  2. Exact page and action taken.
  3. Exact error text or warning text.
  4. Expected result versus actual result.
  5. Whether issue is blocking troop operations (for example, payment or invitation flow).

Parent/Scout Escalation Scenarios

Registration and payment request issues

  • Unable to register for an event due to form or role restrictions.
  • Payment request status not changing after submission.
  • Confusion about owed now vs owed later for staged events.

Household and account visibility issues

  • Missing family/member records that should be visible to your household.
  • Notification delivery gaps after preference updates.
  • Account hold or balance changes you cannot reconcile.

What Happens After Submission

  • Reports are triaged by severity, reproducibility, and troop operational impact.
  • Critical blockers (access, payments, data integrity) are prioritized first.
  • Feature requests are reviewed for repeat demand and roadmap fit.

Known Limits of the Feedback Form

  • One submission should focus on one issue to keep triage clean.
  • Do not include sensitive payment credentials in reports.
  • Use clear reproduction steps for intermittent issues.

Related Documentation