## TL;DR
Install the ServiceNow Slack app (or use an integration hub spoke), connect it with OAuth, and give users a simple command or workflow to file a ticket from any channel. Route ticket notifications to a helpdesk channel. Start with creation only; bidirectional updates come later.

## The error
```text
(Integration task; no error.)
```

## Steps
1. Choose the integration: the ServiceNow app for Slack (official) or a custom IntegrationHub spoke. Expected: chosen. Prefer official for maintenance.
2. Configure OAuth between Slack and ServiceNow with a dedicated integration user. Expected: connected. Scope the permissions to ticket create/read/update.
3. Design the intake: a slash command or workflow form capturing short description, category, and urgency. Expected: simple form. Keep it to three fields; more kills adoption.
4. Set up notifications: new tickets and major updates post to the helpdesk channel. Expected: configured. Agents triage from Slack without opening ServiceNow.
5. Pilot with one team, then announce org-wide with a 30-second how-to. Expected: adopted. Measure tickets created via Slack vs portal.

## When to use
- Users live in Slack
- Reducing ticket-filing friction

## When not to use
- Orgs not on Slack
- Sensitive ticket types (keep those in the portal with proper access controls)

## Compatibility
- Slack, ServiceNow with IntegrationHub or the official app

## Variants
### Modal forms vs slash commands
Modals guide better; slash commands are faster. Offer both.
### Bi-directional sync
Comments sync both ways is phase two; get creation working first.

## Why it happens
Ticket portals have friction; chat has none. Meeting users in Slack captures tickets that would otherwise become hallway requests with no record.

## Edge cases
- Prevent ticket spam from threads; one ticket per issue, link duplicates.
- Audit who can create tickets via Slack; it is the same as portal access.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_KHiQHmle0zWZjTkEKyZgIA