opendesk
When a customer emails your support address, starts a live chat, or asks a question from your help center, opendesk lands it in one shared ticket inbox where every change appears live for the whole team. Agents work a single queue where tickets carry status, priority, assignee, team, tags, and an SLA clock, with internal notes, merging, snoozing, and bulk edits for busy days. Customers chat through a widget that offers identity verification, typing indicators, and 14 languages, and each widget can route to its own team and topics. Support leads publish collections and articles to a public help center, set SLA targets per priority, run automation rules on ticket events, and read reports on volume, response and resolution times, breaches, and CSAT. Ollie, the built-in AI, uses that help center to answer chats, draft replies, summarize threads, triage tickets, and translate both ways, through any Anthropic or OpenAI-compatible provider including local models. Admins can switch it off. Replies leave from your own address through Google, Microsoft, or any SMTP server. Developers connect Linear, GitHub, Jira, Sentry, Slack, Stripe, and any MCP server, or build on the REST API, signed webhooks, and a realtime socket. Desktop apps for macOS, Windows, and Linux and a native iPhone app keep agents reachable. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
Deploy