Fesk
  • Features
  • Pricing
  • FAQ
  • Documentation
  • Get Started Free
  • Sign In
  • Go to App

Getting Started

  • Quick Start
  • Creating Tickets
  • Getting Around
  • Keyboard Shortcuts

Account & Security

  • Account & Security
  • Single Sign-On (SSO)

User Guide

  • The Board
  • List View
  • Working with Tickets
  • Rich-Text Editor
  • Resolution Types
  • Ticket Templates
  • Canned Responses
  • Time Tracking
  • AI Features
  • Ticket Translation
  • Customer Portal
  • Profiles & Account Switching
  • Knowledge Base
  • Saved Views
  • Dashboards
  • Activity Feed
  • Search
  • Notifications
  • Push Notifications
  • Install & Offline Use
  • Collision Detection
  • Reports
  • Team Workload
  • Ticket Linking
  • Bulk Operations
  • Ticket Merging

Admin Guide

  • Workspace Setup
  • User Management
  • Ticket Types & Custom Fields
  • Workflow Statuses
  • Email Integration
  • Email Notification Templates
  • Public Contact Form
  • Automation
  • AI Ticket Workflows
  • Recurring Tickets
  • Import / Export
  • SLA Policies
  • Customer Satisfaction
  • Webhooks
  • Connectors
  • AI Configuration
  • Audit Logs
  • Data & Privacy
  • Billing & Subscription
  • Workspaces

API & Developers

  • API Overview
  • Interactive API Reference

Install and Offline Use

Fesk can be installed as a browser app and keeps a limited read-only workspace available when the network drops.

Installing Fesk

Use your browser's Install app or Add to Home Screen action while signed in. The installed app opens in its own window and uses the same account, workspace, and notification settings as the website.

What remains available offline

Previously loaded app assets and recently viewed ticket data may remain available from the local cache. Fesk shows an offline or connection state when it cannot reach the server.

Actions that change data—creating or editing tickets, replying, moving cards, uploading files, and changing settings—require a connection. Fesk does not present a change as saved until the server confirms it. Reload after reconnecting if the screen does not refresh automatically.

Shared and public devices

Cached data belongs to the browser profile. Sign out when using a shared device and remove the installed app or site data if the device should no longer retain workspace content.

For background alerts after installation, see Push Notifications.

Fesk

A shared ticket board for support teams.

Product

  • Features
  • Pricing
  • Documentation
  • Status

Company

  • Contact

Resources

  • Help Center
  • FAQ
  • API Docs

Legal

  • Privacy Policy
  • Terms of Service
  • Security
  • GDPR
  • Data Processing Agreement
  • Legal Notice

© 2026 Fesk. All rights reserved.