Slash Commands

Scitor uses slash commands in GitHub Issue and Discussion comments to perform actions. Simply type the command at the beginning of a line in your comment.

Email commands

/send

Reply to the original sender of an email. The text below the command becomes the email body.

/send

Hi there! Thanks for reaching out.

We've investigated your issue and found that...

Best regards,
Support Team

Scitor will:

  • Send the reply to the original email sender
  • Add a πŸš€ reaction to your comment on success
  • Post a confirmation comment (unless disabled)

/sendall

Reply to the sender and all CC/TO recipients from the original email.

/sendall

Hi everyone,

Here's an update on the issue you reported...

Info

Both /send and /sendall count toward your monthly outbound email limit (100 on Free, 500 on Pro).

Formatting tips

  • Write your reply in Markdown β€” it’s converted to rich HTML email
  • Images are supported β€” they’re embedded inline in the email
  • Private repository images are automatically fetched and included

Sender management

/block-sender

Block the sender of the current email from creating future issues. Their email address is hashed and stored securely.

/block-sender

Warning

Blocked senders’ emails are silently dropped. They will not receive any notification that they’ve been blocked.

/unblock-sender

Remove a sender from the block list.

/unblock-sender

Configuration commands

/set-from-address

Set a custom sender email address and display name for outbound emails.

/set-from-address support@yourcompany.com "Acme Support"

Without domain verification, only @scitor.io and @mail.scitor.io addresses are allowed.

/skip-success-comment

Toggle the confirmation comment that appears after a successful /send.

/skip-success-comment true

Set to false to re-enable confirmation comments.

Documentation commands

/docs build

Manually trigger a rebuild of your documentation site from the current default branch.

/docs build

Tip

You usually don’t need this β€” docs rebuild automatically when you push changes to the docs folder. Use this command to force a rebuild after changing your scitor.yaml configuration.

/docs status

Show the current build status, site URL, and custom domain information.

/docs status

/docs domain add

Register a custom domain for your documentation site.

/docs domain add support.yourcompany.com

After running this command, add a CNAME DNS record pointing your domain to docs.scitor.io, then verify with /docs domain verify.

/docs domain verify

Verify that your custom domain’s DNS is correctly configured.

/docs domain verify

/docs domain remove

Remove your custom domain and revert to the default URL.

/docs domain remove

Domain commands

Authenticate and manage a custom sender domain for outbound emails. See Custom Email Domain for the full setup guide.

/authenticate-domain

Start the domain authentication process by generating the required DNS records (three CNAME records that set up DKIM signing and a branded return-path).

/authenticate-domain mail.yourcompany.com

Scitor will respond with the CNAME records you need to add to your DNS provider. You don’t need a separate email delivery service account β€” Scitor handles sending for you.

/verify-domain

Check that your DNS records are correctly configured after adding them.

/verify-domain

/delete-domain

Remove your custom domain and revert to the default Scitor sender address.

/delete-domain

CSAT commands

Info

CSAT commands require the Pro plan and CSAT enabled in your scitor.yaml. See Customer Satisfaction for setup.

/csat

View your CSAT metrics: total surveys sent, response rate, average rating, and rating distribution.

/csat

/csat skip

Skip the satisfaction survey for the current ticket. Use this for internal issues, test tickets, or situations where a survey would be inappropriate.

/csat skip

Forms

/create-form

Create an embeddable web form for collecting support requests.

/create-form Contact Form

Returns an embed code (iframe) that you can add to your website.

Reports

/generate-report

Generate a monthly activity report with a visual chart.

/generate-report
/generate-report january
/generate-report 3

Supports month names (e.g., β€œfebruary”) or numbers (1-12). Defaults to the current month.

The report shows daily counts for:

  • πŸ“₯ Inbound emails
  • πŸ“€ Outbound emails
  • πŸ“‹ Form submissions

SLA commands

Info

SLA commands require the Pro plan and an sla section in your scitor.yaml. See SLA Tracking for full details.

/sla

Show the current SLA status for a ticket, including priority, deadlines, and time remaining.

/sla

/sla reset

Reset the SLA timer with fresh deadlines based on the current priority.

/sla reset

/sla pause

Manually pause the SLA timer. Useful when waiting for external input.

/sla pause

/sla resume

Resume a paused SLA timer.

/sla resume

Priority Commands

Manage ticket priority. Priority integrates with SLA tracking β€” changing priority recalculates SLA deadlines based on the new level’s targets.

/priority

Show the current priority of the ticket.

/priority

/priority <level>

Set the ticket priority. Valid levels: urgent, high, medium, low. Swaps the priority label and recalculates SLA deadlines if SLA tracking is active.

/priority high

Follow-up commands

Schedule follow-up messages and automated reminders for tickets.

/followup <duration> <message>

Schedule a follow-up comment to be posted after the specified duration.

/followup 3d Are you still experiencing this issue?
/followup 2h Just deployed a fix β€” checking back soon.

Duration formats: 30m (minutes), 2h (hours), 3d (days), 1w (weeks).

/followup list

Show all pending follow-ups for the current issue.

/followup list

/followup cancel

Cancel all pending follow-ups for the current issue.

/followup cancel

/schedule <datetime> <message>

Schedule a message to be posted at a specific date and time.

/schedule 2025-03-15 10:00 The fix has been deployed to production.

Format: YYYY-MM-DD HH:MM. Uses your configured timezone (from SLA business hours) or UTC.

Saved reply commands

Use pre-written response templates to answer common questions instantly. See Saved Replies for full details.

/reply <name>

Expand a saved reply template and send it as an email to the customer.

/reply billing-faq

/reply <name> draft

Preview a saved reply without sending. The expanded content is posted as a comment.

/reply billing-faq draft

/reply list

List all available saved replies with their descriptions.

/reply list

/reply search <keyword>

Search replies by name, description, or tag.

/reply search billing

CRM commands

Enterprise plan required. These commands are available on the Enterprise plan.

/customer

Show the profile of the customer who sent the current ticket. Displays tags, notes, company, and ticket history.

/customer

/customer note <text>

Add a note to the customer’s profile.

/customer note Prefers email communication. Key stakeholder.

/customer tag <tag>

Add a tag to the customer’s profile.

/customer tag vip

/customer untag <tag>

Remove a tag from the customer’s profile.

/customer untag vip

/customer company <name>

Set the company for the customer.

/customer company Acme Inc

Assignment commands

Info

Assignment commands require the Pro plan. Assignment is only supported for Issues, not Discussions.

/assign

Auto-assign the issue based on routing rules configured in .github/scitor.yaml. Evaluates all routing rules against the current labels and assigns matching team members.

/assign

/assign @user

Assign one or more specific GitHub users to the issue.

/assign @alice
/assign @alice @bob @carol

Multiple users can be listed separated by spaces or commas. Scitor will confirm which users were successfully assigned, and explain if any couldn’t be added (e.g. they don’t have repository access).

/unassign

Remove all current assignees from the issue.

/unassign

/unassign @user

Remove one or more specific assignees from the issue.

/unassign @alice
/unassign @alice @bob

/assignees

List the current assignees of the issue (read-only).

/assignees

Knowledge Base Search

Info

Search commands require the Pro plan and a configured documentation site.

/search <query>

Search your knowledge base for relevant articles. Returns matching articles with snippets and relevance scores.

/search email forwarding setup

/search ai <query>

Search with an AI-generated answer. Uses your knowledge base articles to generate a contextual response, plus lists the source articles used.

/search ai how do I configure email forwarding for my support inbox

The AI answer synthesizes information from your documentation and provides step-by-step guidance when available.

Plan management

/upgrade

View available plans and upgrade your subscription. Shows different options depending on your current plan:

  • Free users β€” See both Pro ($9/month) and Enterprise ($19/month) checkout links
  • Pro users β€” See Enterprise upgrade option via the Stripe billing portal
  • Enterprise users β€” Already on the highest plan

/billing

View your current plan, outbound email limit, and billing provider. Includes a link to the Stripe billing portal or GitHub Marketplace where you can:

  • Upgrade or downgrade your plan
  • Update your payment method
  • View invoices and payment history

/cancel

View cancellation and downgrade options. Links to the Stripe billing portal or GitHub Marketplace where you can:

  • Downgrade to a lower plan (e.g. Enterprise β†’ Pro)
  • Cancel entirely β€” moves you to the Free plan

After cancellation, your documentation site and custom domain will be removed. CRM data is retained but inaccessible until you re-upgrade to Enterprise.

Was this article helpful?

Scitor β€” Turn GitHub into your support platform