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.

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 team already lives in GitHub. Your helpdesk should too.

Every support tool pulls your developers out of their workflow. Scitor keeps them in it. Incoming emails become GitHub Issues. Your team replies with a comment and /send. AI triages automatically. No new logins, no context switching, no tickets falling through the cracks.

Install from GitHub Marketplace See how it works

Login not working on Safari #847

bug-report negative high-priority scitor-customerops[bot] opened this issue 5 minutes ago

scitor-customerops[bot] commented 5 minutes ago

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 from accessing the dashboard.

AI Analysis

Summary: User unable to log in on Safari iOS 17, login button unresponsive

Sentiment: negative Category: bug-report

Space ←→

Stop context switching

One tool for code and customers

Most helpdesks add another dashboard your team has to check. Scitor removes it. Support requests flow into the same repository where you track bugs, plan features, and ship code. Everything your team needs to help a customer is already in their workflow.

Emails become Issues automatically: Forward your support address to Scitor. Every incoming email creates a GitHub Issue with the full message, sender info, and attachments — no manual copying, no lost context. Customer replies thread back to the same Issue.
Reply without leaving GitHub: Write your response as a GitHub comment and add /send. Scitor converts your Markdown to a professional HTML email and delivers it. The customer sees an email from your team, not a ticket system. Use /sendall to reply to everyone in the thread.
AI triages before you read a word Pro: Every incoming message is analyzed by AI at the edge — generating a summary, detecting sentiment, and classifying the request type. Labels like bug-report, negative, or billing are applied automatically so your team can prioritize by filtering, not by reading every message.
Capture requests from your website too: Not every customer uses email. Type /create-form and Scitor generates an embeddable JavaScript widget for your website — with screenshot capture for bug reports. Submissions create Issues just like emails do, so your team handles everything in one place.
Use the tools GitHub already gives you: Because support requests are standard GitHub Issues, your team gets labels, milestones, project boards, assignments, notifications, and search — for free. Trigger GitHub Actions to auto-assign, send Slack alerts, or run custom triage workflows. No helpdesk has this level of programmability.
Attachments just work: Incoming email attachments are stored in the cloud and linked in the Issue. When your team replies, they drag and drop files into the GitHub comment — images are inlined, other files are attached to the outgoing email automatically. No file-size workarounds or external links.
Configure with a YAML file, not a dashboard: Drop a .github/scitor.yaml file in your repo to configure everything — integration type, AI analysis, custom from addresses, and more. It's version-controlled, auditable in pull requests, and lives next to your code. No clickops.
See where your time goes: Type /generate-report to get a monthly breakdown of incoming emails, outbound replies, and form submissions — rendered as charts directly in a GitHub comment. Spot trends and measure volume without any external analytics tool.
Host your knowledge base from the repo Pro: Write support docs as Markdown in a docs/ folder. Scitor compiles them into a searchable, themed website — complete with navigation, syntax highlighting, and your branding. Every push to main auto-deploys in seconds. Use a custom domain or our hosted URL.
Spam blocked before it reaches your team: Every incoming message is scored for spam at the edge using AI. Issues are tagged spam:high, spam:medium, or spam:clean. Pair it with a GitHub Action to auto-close and block repeat offenders — zero manual effort.
SLA tracking & escalation Pro: Set response and resolution targets per priority level. Scitor tracks deadlines with business-hours support, warns you at 80% elapsed, and applies sla:breached labels when targets are missed. Pause timers automatically when waiting on the customer.
AI ticket priority Pro: AI automatically assigns priority levels (urgent, high, medium, low) based on content analysis. Use the /priority command to override. Priority integrates with SLA tracking to set appropriate deadlines.
Scheduled follow-ups: Schedule follow-up messages with /followup or enable auto follow-ups to nudge customers who haven't responded. Includes configurable templates and auto-close.
Saved replies: Store reusable response templates as Markdown files in your repo. Use /reply billing-faq to expand variables, render the template, and send it as an email — all in one command. AI suggests matching replies on new tickets.
Customer Satisfaction (CSAT) Pro: Automatically survey customers after ticket resolution. Track satisfaction scores, response rates, and rating distributions. Included in monthly reports.
Contact Database Enterprise: Automatically build a contact database from inbound emails. Add tags, notes, and company associations. Detect VIP customers from configured domains.
Customer History Enterprise: See a customer's full ticket history when a new issue arrives. Scitor automatically posts a context comment with past interactions, CSAT scores, and notes — so your team never asks "who is this?" again.

No migration, no learning curve

Up and running 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.

Pricing

Simple, transparent pricing

Start free. Upgrade when you need AI triage, a knowledge base, or CRM features.

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

Get started for free

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

Upgrade to Pro

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

Upgrade to Enterprise

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. Just install and go.

Install from GitHub Marketplace View on GitHub