🎉

Installation Complete

Scitor has been installed and is ready to use. Check your repository for a welcome issue or discussion with your unique email address and setup instructions.

1

Check your repository

Scitor created a welcome issue (or discussion if enabled) in your repository. It contains your unique inbound email address and setup instructions.

2

Forward your support emails

Set up email forwarding from your support address (e.g. support@yourcompany.com) to the Scitor inbound address. Each email will automatically become a new issue.

3

Reply to customers

Use slash commands in issue comments to interact with tickets. You can also use @scitor command syntax. Type /help in any issue to see all available commands.

Command Description
Email & Replies
/sendReply to the original sender
/sendallReply to sender + CC recipients
/reply <name>Send a saved reply template
/block-senderBlock a sender from creating issues
Ticket Management
/priority <level>Set ticket priority (urgent/high/medium/low)
/assignAuto-assign based on routing rules Pro
/assign @userAssign a specific user Pro
/followup <duration>Schedule a follow-up (e.g. 3d, 1w)
/slaView or manage SLA tracking Pro
/csatView CSAT summary or skip survey Pro
Setup & Tools
/authenticate-domainSet up a custom email domain Pro
/create-form <name>Create an embeddable support form
/generate-reportGenerate monthly metrics report
/docsManage knowledge base site Pro
/helpShow all available commands
4

Configure with scitor.yaml (optional)

Create a .github/scitor.yaml file in your repository for advanced configuration. All settings are optional — Scitor works out of the box with sensible defaults.

General

Scitor auto-detects whether your repo has Discussions enabled at install time and uses that as the default integration type. You can override this here.

# .github/scitor.yaml

integration: issues      # "issues" or "discussions" (default: auto-detected at install)
ai: true                 # AI summaries, sentiment & categorization (default: true, requires Pro)

Priority

priority:
  auto_assign: true      # Auto-assign priority from AI analysis (default: true)
  default: medium        # Fallback when AI is unavailable: urgent | high | medium | low

SLA Tracking Pro

sla:
  first_response:        # Max time to first agent reply
    urgent: 1h
    high: 4h
    medium: 8h
    low: 24h
  resolution:            # Max time to resolve the ticket
    urgent: 4h
    high: 1d
    medium: 3d
    low: 7d
  business_hours:        # Only count time during work hours (optional)
    timezone: Europe/Amsterdam
    start: "09:00"
    end: "17:00"
    days: [mon, tue, wed, thu, fri]
  warning_threshold: 0.8 # Fraction of SLA time to trigger warning (default: 0.8)
  escalation:
    on_breach:
      - label: "sla:breached"
      - assign: oncall-team  # Assign a user or team on breach
    on_warning:
      - label: "sla:warning"

Routing & Auto-Assignment Pro

routing:
  auto_assign: true      # Auto-assign on inbound triage (default: false)
  rules:                 # Match by AI category or label
    - category: billing
      assignees: ["finance-team"]
    - category: bug-report
      assignees: ["engineering"]
    - category: feature-request
      assignees: ["product"]
    - label: "priority:urgent"
      assignees: ["senior-support"]

Automated Follow-ups Pro

follow_up:
  auto:
    enabled: false             # Enable automatic follow-ups (default: false)
    waiting_on_customer: 3d    # Follow up when waiting on customer
    waiting_on_agent: 1d       # Reminder for agent response
    max_follow_ups: 3          # Max follow-ups before stopping
    auto_close_after: 7d       # Auto-close after silence (optional)

Customer Satisfaction Surveys Pro

csat:
  enabled: false         # Enable CSAT surveys (default: false)
  delay: 1h              # Delay after issue close before sending survey
  scale: 5               # 5 (star rating) or 2 (thumbs up/down)
  exclude_labels:        # Skip survey for issues with these labels
    - spam
    - duplicate
    - internal

Saved Replies

replies:
  path: .github/scitor/replies  # Folder with reply Markdown templates
  ai_suggest: true               # Suggest matching replies on triage (Pro)
  ai_suggest_threshold: 0.75     # Confidence threshold for suggestions (0–1)

Knowledge Base Pro

docs:
  path: docs             # Folder containing documentation Markdown files
  title: "My Docs"       # Site title (default: repository name)
  theme: default         # default | minimal | corporate
  color: "#4F46E5"       # Primary brand color
  search: true           # Enable search (default: true)
  homepage: cards        # "cards" (grid) or "classic" layout
  domain: docs.example.com  # Custom domain (optional)
  contact:               # Embedded contact form (optional)
    placement: [footer, floating]

Contacts & CRM Enterprise

contacts:
  auto_create: true      # Auto-create contacts from inbound emails
  auto_company: true     # Auto-detect company from email domain
  show_context: true     # Show customer history on new tickets
  company_domains:       # Manual domain → company mapping (optional)
    acme.com: "Acme Corp"
  vip_domains:           # Domains to auto-tag as VIP (optional)
    - important-client.com
Back to Scitor