GitHub Service Desk
GitHub doesn't have a Service Desk. Scitor is it.
GitLab has had Service Desk built in for years — a unique email address per project, tickets created as issues, replies over email. GitHub has nothing equivalent. Scitor is a GitHub App that adds exactly this: customer emails become GitHub Issues, your team replies with /send, and customers get professional email responses. No new tool. No new login. No per-agent pricing.
< 5 min setup · Free plan available · No credit card required
What GitLab Service Desk does (and why GitHub users want it)
GitLab has shipped a feature called Service Desk since GitLab 9.1. The concept is simple: every GitLab project gets a unique email address. When a customer emails that address, GitLab automatically creates a confidential issue. Your team responds from inside GitLab. The customer only ever sees email — they never need a GitLab account.
It is one of GitLab's most-requested features for a reason. It closes the loop between "customer reported a problem" and "the team that fixes problems" without forcing customers to sign up for a developer platform.
GitHub has no equivalent. A GitHub community thread asking for this feature has sat unanswered for years. Scitor is the answer.
The Service Desk workflow, on GitHub
How Scitor gives GitHub the Service Desk it's missing
Install the GitHub App
Install Scitor from the GitHub Marketplace and select which repositories should receive support tickets. Takes under 2 minutes.
Forward your support email
Point your existing support@yourcompany.com address at Scitor. Every incoming email becomes a GitHub Issue with sender info, attachments, and AI labels.
Reply from GitHub
Write a GitHub comment, add /send on its own line. Scitor converts Markdown to HTML and emails the customer from your domain. They never see GitHub.
GitLab Service Desk vs Scitor
A direct look at what each tool offers for email-based support on GitHub.
| Feature | GitLab Service Desk | Scitor (GitHub) |
|---|---|---|
| Email → issue creation | ✓ | ✓ |
| Reply by email | ✓ | ✓ |
| Customers need an account | No | No |
| Custom email domain | ✓ | ✓ |
| AI triage (summary, sentiment, labels) | ✗ | ✓ (Pro) |
| SLA tracking | ✗ | ✓ (Pro) |
| CSAT surveys | ✗ | ✓ (Pro) |
| Knowledge base from Markdown docs | ✗ | ✓ (Pro) |
| AI chatbot on your docs site | ✗ | ✓ (Enterprise) |
| Web dashboard (non-GitHub UI) | ✗ | ✓ (app.scitor.io) |
| CRM / contact database | ✗ | ✓ (Enterprise) |
| Config as Code (.github/scitor.yaml) | ✗ | ✓ |
| GitHub Actions automation | ✗ | ✓ |
| Active development | Deprioritized (rebuilding) | ✓ |
| Pricing | Free (included in GitLab) | Free / $9 / $19 per month |
GitLab Service Desk is currently not under active development while GitLab rebuilds it inside their work item framework. Community contributions are accepted but new features are not planned on the current implementation.
Built for GitHub teams that need what GitLab has had all along
Scitor is a fit if:
- Your codebase and project management already live in GitHub
- Your customers contact you by email (the primary support channel for B2B SaaS and developer tools)
- You want support tickets and code in the same place — no context switching
- You don't want to pay per agent or set up a separate helpdesk system
Scitor is not a fit if:
- You need phone support
- You need live chat
- You need social media ticketing
- It is specifically built for email-based support on GitHub
Give GitHub the Service Desk it's missing
Scitor installs in under 5 minutes from GitHub Marketplace. The free plan includes unlimited inbound emails, GitHub Issues integration, slash commands, spam detection, and a web form widget. No credit card required.