Host FreeScout without installing anything
A shared support inbox on your own address: every email becomes a conversation someone owns, with internal notes the customer never sees.
Starting at €8.99/month
Introduction
FreeScout installed, updated and backed up by us, on a machine in France. A shared inbox and a complete customer support desk: conversation assignment, internal notes, saved replies and follow-up. You install nothing and configure no server: the application is online a few minutes after you order, under your own name.
The plan that suits it is App Confort at €8.99/month incl. VAT — 4 GB of memory. FreeScout is a Laravel application on a MySQL database, and its background job is to poll your IMAP mailboxes constantly: downloading messages, decoding them, extracting attachments, rebuilding threads. Add full-text search across several years of correspondence and it becomes clear why the theoretical 1.5 GB minimum gets tight as soon as three people work on it.
Nothing changes for the people writing to you: FreeScout plugs into the address you already have, collects over IMAP and replies through your SMTP server. Customers keep writing to contact@your-domain and receive an ordinary email, with no ticket number glued to the subject line and no portal to log into. It is on the team's side that everything changes.
What FreeScout can do
Your IMAP mailboxes, not an address of ours
Each mailbox in the application maps to an address you already own — support@, sales@, contact@ — polled over IMAP and served by your own outgoing server. You keep your domain name and your sender reputation.
Internal notes the customer never sees
This is the real difference with an ordinary shared mailbox: the team discusses a case inside the thread itself, with no risk of an unfortunate reply-all. The customer only sees the replies addressed to them.
Assignment and collision detection
A conversation belongs to someone, and the application warns you when a colleague is already drafting a reply on the same thread. Two people no longer answer the same question ten seconds apart.
Saved replies, tags and customer history
Recurring answers are written once and reused, conversations are filed by tag and folder, and a customer record gathers all their past exchanges, whichever mailbox they arrived in.
What people actually use it for
After-sales for an online shop
Two people share returns and delivery-tracking enquiries. The question "has anyone already answered this one?" disappears: the conversation has an owner and a status.
Support for a software vendor
Requests are tagged by version and by module. When a fix ships, one search brings back every customer who reported the problem so they can be told.
Volunteers taking turns on contact@
In a charity nobody is there every day. The internal note "I called, he will ring back on Thursday" lets the next volunteer pick the case up without asking the person to explain it all over again.
Keeping sales enquiries apart from support
An agency runs sales@ and support@ in the same instance, with different teams on each. Every mailbox keeps its own signature and its own saved replies.
Tracking requests from the public
A local authority department wants to know how long a request takes to handle, without forcing residents through a portal with credentials. They send an email, and that is all.
Hosted in France
In our own datacentre in Nouvelle-Aquitaine, which we operate ourselves. Exchanges with your customers, attachments included, stay in the country.
Frequently asked questions
Nothing. You choose the application, fill in the fields it asks for — often an email address and a name — and it goes online. Access arrives by email with the address and the credentials.
No, and that is the point. FreeScout connects over IMAP to the mailbox you already have and replies through your own outgoing server. Your customers keep writing to the same address and receive a normal email, with no ticket reference in the subject and no account to create on a portal.
Not through an importer built into the core. What FreeScout does do is collect whatever is in the IMAP folder from a date you set: if your old exchanges are still on the mail server, they show up in the application. In practice, people keep the old tool read-only for a few months and let the history rebuild itself through new conversations.
The core is: shared mailboxes, assignment, internal notes, saved replies, tags, search, customer records, API. Alongside it the project runs a store of paid modules — knowledge base, live chat on your website, satisfaction surveys, extra channels. You only need them the day you want them: the application is complete without.
Yes, they are part of the service. A self-hosted application left un-updated is a security risk, not a saving.