In-app feedback
Frihet includes its own feedback form so you can send suggestions, bugs and ideas directly to the team without leaving the application.
How it works
Open Feedback from the sidebar menu. The form asks for:
- Category: Bug, Feature, Improvement or Other.
- Message: describe your suggestion, issue or idea (up to 5,000 characters).
- Click Send feedback.
Your user, your email, the route of the screen you are writing from and your browser are sent along with your message so the team can reproduce the problem.
Difference Between In-App Feedback, Docs Page Rating, and Direct Support
| Channel | Where to find it | What it sends | Opens a ticket or replies? | When to use it |
|---|---|---|---|---|
| In-app Feedback | Feedback option in the Frihet ERP sidebar menu | Category (Bug, Feature, Improvement, or Other), free text up to 5,000 characters, authenticated user, email, active screen route, and browser | Logged for product and engineering triage (not the urgent support queue) | Report UI bugs or suggest product improvements directly from the ERP screen you are working on |
Docs page-footer rating (Was this page helpful?) | Footer of every guide on docs.frihet.io | Session-anonymous: binary vote (Yes / No) and 4 categorical reasons (Outdated or incomplete, Code or example fails, Missing clear steps, Issue in my account), no free text | No ticket or reply; provides the Contact support with this context link carrying the guide title (subject), route, and selected reason (from=docs:<route>:<reason>) plus a link to the Quick troubleshooting guide | Rate whether a guide helped or jump to contextual support without re-explaining which page you were reading (works even with Do Not Track or content blockers enabled) |
| Direct Support | www.frihet.io/en/contact?topic=support or ayuda@frihet.io | Your message plus the guide context (topic=support, subject, from=docs:<route>:<reason>) when opened from the documentation footer | Yes, opens a support inquiry handled by our team according to your plan priority | Account-specific blockers, billing questions, or compliance inquiries that require a human reply (available even if you use content blockers or Do Not Track) |
What not to include in your message
[!IMPORTANT] Protect your credentials Never paste passwords, full API keys (
fri_...), webhook signing secrets, or.p12/.pfxdigital certificate files and their passwords into the feedback form or support emails. Include only reference identifiers (such as invoice numberF-2026-0142or the HTTP error status returned).
Direct support
For direct support with a human reply instead of product feedback, use the contextual contact form or email ayuda@frihet.io.