FreeScout — Free self-hosted help desk & shared mailbox (Zendesk / Help Scout alternative)
C-Rank Grade: B (Solid) - 45/100
External PR Merge Rate: 11%
Response Time: 2d
First Timer Success: 29%
freescout-help-desk/freescout has a recorded first-timer success rate of 28.6%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in freescout-help-desk/freescout respond to incoming external pull requests in approximately 38.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 45.4 places freescout-help-desk/freescout in the B tier.
The external contributor pull request merge rate for freescout-help-desk/freescout is 11.4%, based on public PR activity from non-core contributors.
freescout-help-desk/freescout currently has 10 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/freescout-help-desk/freescout?utm_source=github&utm_medium=badge)
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Make FreeScout design look more modern by changing only CSS and keeping same blue-white-grey color scheme.
Just wanted to check if notifications are meant to fire for members of the destination mailbox when we move a ticket from our mailbox to theirs? We've moved a few and had members say they never got a notification. Cheers Ben -- PHP version: 8.0.30 FreeScout version: 1.8.235 Database: MySQL Are you using CloudFlare: No Are you using non-official modules: Yes
PHP version: 8.4.24 FreeScout version: 1.8.234 Database: MySQL Are you using CloudFlare: No Are you using non-official modules: Yes
PHP version: 8.4.21 FreeScout version: 1.8.223 Database: MySQL Mail server: Zimbra Are you using CloudFlare: No Are you using non-official modules: No Summary We are seeing duplicate conversations/messages created in one FreeScout mailbox when an email is sent from one FreeScout mailbox to another FreeScout mailbox, with a Zimbra distribution list in CC. This does not appear to be an SMTP resend issue. FreeScout sends the email once, but during fetching/importing it creates many artificial fs-* Message-IDs and repeatedly imports the same logical email into the target mailbox. This looks related to the multi-mailbox import logic in app/Console/Commands/FetchEmails.php. Possibly related to issues such as #5368 and #5434, but the trigger here is a distribution list / alias in CC that expands to many addresses, some of which are also FreeScout-monitored mailboxes. Setup We have several FreeScout mailboxes on the same instance, for example: Mailbox A: [email protected] Mailbox B:
Hi all, It seems that the To, CC and BCC fields seem to have issues with screenreaders in the new conversation form. Search and autosuggestion/completion seems not to work. At least it seems not to work in the demo, which seems to run still on version 1.8.207. Would be cool if someone could have a look into this and maybe also update the demo to the recent version. We plan to use FreeScout in our office and i am one of the admins who should be fully use it with a screenreader. I am using NVDA (https://www.nvaccess.org/) under Windows. Though it should be also possible to replicate the issue with Orca on Linux, VoiceOver on Mac and others. Greetings and thanks, Simon
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to freescout-help-desk/freescout, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of freescout-help-desk/freescout acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 11.4% were successfully merged into the primary branch.
freescout-help-desk/freescout has a recorded first-timer success rate of 28.6%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 45.4 places freescout-help-desk/freescout in the Solid tier.
The external pull request merge rate is 11.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, freescout-help-desk/freescout currently has 10 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for freescout-help-desk/freescout are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.