Find your fit
Who it is for
A small support team that wants control of its own help desk can start with the email-first core, using multiple agents and mailboxes without a listed core seat limit. Check who will run the server and maintain its mail connection before moving live support.
A team sharing an email address can leave internal notes, move conversations between mailboxes and use the concurrent-open warning to reduce overlapping replies. Pilot the handoff with two agents so everyone understands when a conversation changes owner.
Organizations that need automated routing, customer login, a knowledge base or reporting should budget the corresponding modules. Make a feature list before treating the whole deployment as free.
The work it supports
Core capabilities
Shared email handling. Connect a support address and work from a common conversation queue. FreeScout lists SMTP, IMAP and POP3 integration; validate the chosen provider and both inbound and outbound mail before cutover.
Conversation coordination. Agents can add internal notes and forward, merge or move conversations. Agree when to merge threads and which mailbox should own a request after transfer.
Collision warning. The app indicates when two agents open the same conversation. Use this as a prompt to coordinate the reply, then test how it behaves when an agent leaves a draft or switches conversations.
Search and basic responses. The core feature list includes search and automatic replies. Check that search finds representative older conversations and that the auto reply says only what your team can actually deliver.
Workflows are an extension. The separate Workflows Module can sort messages, assign them and send predefined replies through configured rules. Define the desired triggers and owners before buying it, then verify behavior on test mail.
Customer-facing extensions. The End-User Portal and Knowledge Base are separate modules. The former supports customer ticket submission and reply after email login; the latter supports self-service or an agent help center. Test permissions and customer visibility before launch.
Reporting is an extension. The Reports Module adds conversation, productivity and satisfaction views. Check whether its definitions match the measures your team uses; core mail handling does not itself establish these reports.
Understand the offer
Pricing and getting started
The downloadable core is free and described without agent, ticket or mailbox limits. Self-hosting still requires infrastructure and an operator; estimate that work and its costs before choosing it for live support.
Feature extensions are sold separately. The official modules page describes lifetime licenses with updates for one instance, and a non-refundable payment policy. Confirm the current total for the exact modules and number of deployments, including any test instance, before paying.
Workflows, customer portal, knowledge base and reports are each listed as modules. The broad homepage feature list should not be read as a promise that these are in the free core.
Look a little closer
Before you choose
Run a pilot with real examples of incoming email, one internal note, one conversation transfer and one outbound reply. Check the team's mail routing and handoff before moving its public support address.
Have two agents open the same conversation and decide who responds. This checks whether the collision warning is useful in the team's daily process.
List the exact modules needed for automation, customer access, articles and reports. Compare their one-instance lifetime purchases with the self-hosting effort so the total matches the support workflow rather than the free-core headline.
6 distinct sources behind this profile. Research observed Oct 18, 2026. Features and offers can change.
View sources and research →
