A ticket system only works if people use it - and people already know how to send an email. Connecting one support mailbox to Faveo so that mail becomes tickets, and replies go back as mail, is the setup that makes the whole helpdesk real.
You can install the finest helpdesk in the world, and the office will still phone you - unless asking for help is as easy as sending an email. Faveo's email integration is built for exactly this: users write to [email protected], a ticket is created automatically, agents work inside Faveo, and replies travel back as ordinary email. The user never learns any new software. Here is the plumbing, set up in the right order, with the one hidden setting that decides whether it works at all.
Portals and web forms are useful, but email is the channel nobody needs training for. A user in a panic about a dead printer will not open a portal, create an account and fill a form - they will send a mail or make a call. Email to ticket meets them where they already are, while still giving the IT team everything a ticket system promises: a number, an owner, a priority and a written history.
It also protects the team. When support lives in personal inboxes, a question asked to one technician is invisible to everyone else and dies when that person is on leave. A shared support mailbox feeding one Faveo queue means any agent can pick up any ticket, and the boss can see the real workload for the first time.
Start outside Faveo, in your mail system. Create a dedicated mailbox for support - support@ or helpdesk@ on your company domain. Three rules for this mailbox:
If your mail provider uses two-step verification, look for its app password option for connecting applications like Faveo - the normal account password may be refused by design.
Email in Faveo has two directions, and both must be set - half-configured email is the classic broken helpdesk.
Send yourself a test from the Faveo settings if your edition offers a test-mail option, and check the mailbox itself in a normal mail client to confirm the credentials work outside Faveo too.
Here is the honest secret of every email-to-ticket problem: Faveo fetches mail through its scheduled tasks - email fetching, SLA monitoring and auto-close all run from the server's scheduler (cron). If that background job was never set up during installation, the mailbox is connected, the settings look perfect, and no ticket ever arrives.
So the diagnosis order is always the same. First, is mail actually landing in the mailbox? Check it in a webmail client. Second, is the scheduler running on the server? Third, are the mailbox credentials still valid - a changed password breaks fetching silently. Work through those three in order and you will find almost every real fault. Also accept the design: fetching is periodic, so a ticket appearing a minute or two after the email is normal behaviour, not a bug.
Prove the loop end to end, exactly as a user will experience it:
One warning to finish: think before enabling aggressive auto-responses. If two automated systems ever mail each other - your helpdesk and a customer's - they can create a mail loop of endless tickets. Keep auto-responses simple, watch the queue closely in the first week, and the loop will never start.
The video connects Faveo and sets up the system on screen - watch the email and setup parts before you connect your own support mailbox.
Watch Full VideoYes, a normal mailbox is a normal mailbox - you connect it with its IMAP and SMTP details. If the account has two-step verification, the provider may require an app password for third-party applications; create that in the mail account's security settings and use it in Faveo instead of the main password.
Because fetching is scheduled, not instant. Faveo checks the mailbox in cycles through its background task, so a short delay is the design working as intended. If tickets never appear at all, the problem is different - usually the scheduler is not running or the mailbox credentials are wrong.
Yes. You can connect more than one mailbox and map each to its department, so accounts queries and IT problems land in different queues from the start. For a small office, begin with one shared support address and add department mailboxes only when the volume makes routing worth it.