Turn customer emails into GitHub Issues. No new tool to learn.
Scitor converts inbound support emails into GitHub Issues with AI triage. Your team replies with /send — customers get a professional email. Stay in your workflow.
Cannot export invoices as PDF
#204
From: Rachel Nguyen ( rachel@brightlabs.io )
Hi, when I click "Export to PDF" on the invoices page, the button spins for a few seconds and then nothing happens. No file downloads. This is blocking our monthly accounting close.
I tried Chrome and Firefox, same result on both. The CSV export works fine.
📎 Attachments
- console-errors.png
🤖 AI analysis — negative · bug-report
Customer cannot export invoices as PDF. The export button loads but does not download a file. CSV export works. Blocking their monthly accounting close.
Labels
Assignees
Built for teams that already live in GitHub
Open-source maintainers
Triage bug reports and support questions without leaving your repo.
Dev tool startups
Run customer support from GitHub Issues instead of paying for Zendesk.
Platform & infra teams
Let internal users email you — issues land in your team's repo, labeled and prioritized.
GitHub-native customer support
One tool for code and customer support
Login not working on Safari #847
Developer support without the learning curve
Set up your GitHub helpdesk in five minutes
Install the GitHub App
Install Scitor from the GitHub Marketplace and pick which repositories should receive support requests. Scitor posts setup instructions with your unique email address.
Forward your support email
Set up forwarding from your existing address
(e.g. support@yourcompany.com)
to the Scitor address. You can also embed a support form on your
website with a single JavaScript snippet.
Reply from GitHub
When a customer emails you, it appears as a GitHub Issue. AI adds
a summary and labels. Your team writes a response, adds
/send,
and the customer gets a professional email.
Proven in practice
How it works in practice
< 5 min
Time to set up your first support repo
0 new tools
Your team stays in GitHub
$0
Free tier with unlimited inbound emails
Pricing
Simple, transparent pricing
Start free. Upgrade when you need AI triage, a knowledge base, or CRM features.
Free to start · Installs in under 5 minutes · No credit card required
Free
$0 /month
Everything you need to run customer support from GitHub. No credit card required.
- Unlimited inbound emails
- 100 outbound emails / month
- GitHub Issues & Discussions
- Slash commands (/send, /block-sender, etc.)
- Web form widget
- Spam detection & sender blocking
- Attachment handling
Pro Popular
$9 /month
AI-powered triage, a hosted knowledge base, and higher limits for growing teams.
- Everything in Free
- 500 outbound emails / month
- AI triage — sentiment, category & summary
- Auto-labels for priority & routing
- Custom sender domain
- Knowledge base — Markdown to hosted docs site
- SLA tracking & escalation
- CSAT surveys & saved replies
Or type /upgrade on any GitHub Issue
Enterprise
$19 /month
CRM-lite features, customer history, and unlimited outbound for teams that need full visibility.
- Everything in Pro
- Unlimited outbound emails
- Contact database — auto-created from inbound emails
- Customer history on every ticket
- Tags, notes & company tracking
- VIP domain detection
- /customer commands for CRM management
- Priority support
Frequently asked questions
-
What do I need to get started?
-
A GitHub repository with Issues enabled. We recommend a dedicated support repository so your product code stays separate. Install the Scitor GitHub App, and you'll receive a unique email address to forward your support emails to.
-
How do I reply to a customer?
-
Write a comment on the Issue with your response, then add /send on its own line. Scitor converts your Markdown to HTML and emails it to the customer. Use /sendall to reply to all participants in the thread.
-
Can I send emails from my own domain?
-
Yes. Configure a custom sending domain through your email provider so replies come from your brand address instead of a Scitor address. This improves deliverability and looks professional to your customers.
-
What happens to email attachments?
-
Incoming attachments are uploaded to secure cloud storage and linked directly in the Issue body. When replying, drag and drop files into your GitHub comment — images will be inlined and other files attached to the outgoing email.
-
How does the AI triage work?
-
Scitor runs every incoming message through AI at the edge to generate a one-line summary, detect sentiment (positive, negative, neutral), and classify the category (bug report, feature request, billing, etc.). It then creates and applies GitHub labels automatically so you can filter and prioritize without reading every message.
-
How is spam handled?
-
You can block specific senders with the /block-sender command on any Issue. Future emails from that sender are silently dropped. Your email provider's built-in spam filtering also applies before messages reach Scitor.
-
Does Scitor store my emails?
-
No. Email content passes through Scitor to create the GitHub Issue, but the message body is not stored on our servers. Only attachments are persisted in cloud storage. Your actual support conversations live in your GitHub repository — not in a third-party database.
-
Can I use Discussions instead of Issues?
-
Yes. Add a .github/scitor.yaml file to your repository with integration: discussions. Incoming messages will create Discussions instead of Issues, which is better for Q&A-style threads where community members can also help answer.
-
What commands are available?
-
Core commands: /send (reply to sender), /sendall (reply to all), /reply (send a saved reply template), /block-sender, /unblock-sender, /create-form (generate an embeddable web form), /generate-report (monthly metrics with charts), /skip-success-comment (hide confirmation messages), and /set-from-address (custom sender).
-
What does 'Scitor' mean?
-
Scitor is a Latin word meaning 'to seek to know; to ask, inquire.' It seemed fitting for a platform that helps people ask questions and find answers.
Your customers deserve fast answers. Your developers deserve focus.
Scitor lets both happen. No new tool to learn, no tickets to manage outside of GitHub, no context switching. Install the GitHub helpdesk your team actually wants to use.
New email from sarah@acme.com
Hi, I can't log in on Safari (iOS 17). I've tried clearing cookies and reinstalling the app. The login button just spins forever. This is blocking my whole team.
AI Analysis