Your Scitor App is installed!

[scitor-customerops]

Welcome to Scitor! 🎉

Your Scitor App is now connected to this repository. Scitor converts incoming emails and web form submissions into GitHub Issues (or Discussions) so your team can manage support requests directly from GitHub.

⚠️ This repository is public. Support issues contain sensitive customer data such as email addresses and names. We strongly recommend using a private repository for customer support. Anyone can view issues in a public repository, and users can also submit issues directly, bypassing your support email workflow.

Quick Start

Your inbound email address:
6j5ng84s70mzjrn@parse.scitor.io

Forward your support emails to this address (or set it as a forwarding address in your email provider), and Scitor will create a new Issue for each email.

Replying to customers:
Type /send as a comment on any Issue created by Scitor to send an email reply to the original sender. Use /sendall to include CC recipients.

Key Commands

All commands can be used with /command or @scitor command syntax. Type /help on any issue to see the full list.

Command	Description
/send	Reply to the original sender
/sendall	Reply to sender + CC recipients
/reply <name>	Send a saved reply template
/block-sender	Block a sender
/priority <level>	Set priority (urgent/high/medium/low)
/assign	Auto-assign based on routing rules (Pro)
/assign @user	Assign a specific user (Pro)
/followup <duration>	Schedule a follow-up (e.g. 3d, 1w)
/create-form <name>	Create an embeddable support form
/generate-report	Generate monthly metrics report
/help	Show all available commands

Integration Type

Scitor automatically detects whether this repository has Discussions enabled at install time. If Discussions are available, Scitor will create Discussions for incoming emails; otherwise, it will use Issues. You can override this by adding integration: issues or integration: discussions to your .github/scitor.yaml config file.

Configuration

Customize Scitor by creating a .github/scitor.yaml file in this repository. All settings are optional — Scitor works out of the box with sensible defaults.

# .github/scitor.yaml
# integration: issues    # override auto-detected type (issues or discussions)
ai: true                 # AI summaries & categorization (Pro)

priority:
  auto_assign: true      # Auto-assign priority from AI
  default: medium        # Fallback: urgent | high | medium | low

routing:                 # Auto-assign team members (Pro)
  auto_assign: true
  rules:
    - category: billing
      assignees: ["finance-team"]
    - category: bug-report
      assignees: ["engineering"]

See the full configuration reference for all available options including SLA tracking, CSAT surveys, follow-ups, knowledge base, saved replies, and CRM contacts.

Custom Domain

To send emails from your own domain instead of no-reply@scitor.io:

1. Comment /authenticate-domain yourdomain.com on any Issue
2. Add the DNS records Scitor provides
3. Comment /verify-domain to validate
4. Comment /set-from-address support@yourdomain.com "Your Company"

---

📚 Documentation: support.scitor.io · Type /help on any issue for a quick command reference