Labels

Scitor automatically creates and manages GitHub labels on your issues and discussions. Labels are applied based on AI analysis (Pro plan) and spam scoring, making it easy to filter and prioritize support requests.

Label categories

Sentiment labels (Pro plan)

Applied based on AI analysis of the email’s emotional tone.

Category labels (Pro plan)

Applied based on AI classification of the email’s content.

Spam labels (all plans)

Applied based on the email’s spam score from the email provider.

SLA labels (Pro plan)

Applied automatically when SLA tracking is configured. See SLA Tracking for details.

Priority labels (Pro plan)

Used with SLA tracking to set per-ticket response/resolution targets.

Automatic label creation

Scitor creates labels automatically when they’re first needed. If a label already exists in your repository (with a different color or description), Scitor will not overwrite it.

Labels are cached for performance, so the first email in a new repository may take slightly longer to process.

Using labels for workflows

Filter issues by priority

Use GitHub’s built-in filters to find high-priority support requests:

is:issue is:open label:sentiment:negative
is:issue is:open label:category:bug-report
is:issue is:open label:spam:clean label:sentiment:negative

Combine with GitHub Projects

Create a GitHub Project board with columns like:

• Triage — New issues without response
• Urgent — sentiment:negative + category:bug-report
• Feature requests — category:feature-request
• Billing — category:billing

Use GitHub Projects’ built-in automation rules to move issues based on labels.

Automate with GitHub Actions

name: Escalate negative bugs
on:
  issues:
    types: [labeled]

jobs:
  escalate:
    if: |
      contains(github.event.label.name, 'sentiment:negative') &&
      contains(join(github.event.issue.labels.*.name, ','), 'category:bug-report')
    runs-on: ubuntu-latest
    steps:
      - name: Assign to senior team
        uses: actions/github-script@v7
        with:
          script: |
            await github.rest.issues.addAssignees({
              owner: context.repo.owner,
              repo: context.repo.repo,
              issue_number: context.issue.number,
              assignees: ['senior-dev']
            })