What Fesk does
Handle tickets, email, deadlines, and reporting from the same workspace.
Tickets on a board
Every ticket is a card in one of four lanes: Open, Work in Progress, Waiting, or Closed. Dragging a card changes its status. Each card shows its priority and warns when an SLA deadline is close. Admins can rename and reorder the lanes in Settings → Board.
Connect your support inbox
Point a support inbox at Fesk over IMAP and SMTP, or sign in to Gmail or Microsoft 365 with OAuth and skip the app passwords. Incoming mail shows up on the board within a minute or two, and replies go back out from the same address, threaded to the original ticket. Fesk watches your SPF, DKIM, and DMARC setup and warns you in settings when something's off, so you hear about deliverability from us, not from a customer's spam folder.
Rules for repetitive work
Every rule reads the same way: a trigger, optional conditions, and the actions that follow. Assign each Critical ticket to the on-call lead. Close anything idle for two weeks with an internal note. Ping a channel when a key customer writes in. You build the rule once and it runs on every ticket that matches.
Deadlines you can see coming
Set response and resolution targets per priority, and Fesk tracks each ticket against them. Timers follow your business hours, so a ticket that lands at 5pm Friday doesn't quietly burn its budget over the weekend. You can give customers on your premium support offering tighter targets than your public inbox. A breach that's close shows on the card; one that already happened shows on the dashboard and in the reports.
AI with review and controls
Suggest Reply drafts an answer from the ticket, its conversation history, and relevant published knowledge-base articles. An agent reviews it before sending. Autonomous mode can close stale tickets or answer common questions under rules you define. It unlocks in stages: 14 days on Assist before Semi, then another 7 days before Full. Every autonomous action appears in the audit queue, and a kill switch stops work in progress. AI can be disabled without affecting the rest of Fesk.
Fewer dropped handoffs
Mention a teammate, add an internal note, and follow ticket changes in real time. Fesk also shows when another agent has the ticket open or is writing a reply.
Wire it into what you already run
Fesk currently provides outgoing webhooks, a REST API with read and write access, and sign-in through Google Workspace or Microsoft 365. API keys handle authentication for custom integrations. The API is included on every plan. If you need a ready-made connector for a particular service, tell us; customer requests guide what we build next.
Reports you can inspect
The dashboard shows ticket volume, backlogs, and team response times. Reports export to CSV, and the API provides the underlying data for your own analysis.
Try Fesk with a few real tickets
Create a workspace, invite your team, and see how your queue looks on the board.