Installation & Setup
Add Treqdesk to your Slack workspace and complete the onboarding wizard — from first click to first ticket.
Go from zero to your first tracked ticket in under five minutes. This page covers both the Slack installation and the onboarding wizard that configures your workspace.
Prerequisites
- You must be a Slack workspace admin (or have permission to install Slack apps); this is separate from Treqdesk roles
- Your workspace must be on a Slack plan that supports app installations
Part 1 — Install the bot
Click "Add to Slack"
Visit the Treqdesk landing page and click the Add to Slack button. Slack will open its OAuth authorization screen.
Review and authorize permissions
Slack will show you the permissions Treqdesk needs:
| Permission | Why Treqdesk needs it |
|---|---|
| View messages and reactions | Detects 🎫 reactions to create tickets from messages |
| Post messages | Posts ticket cards to triage channels and sends notifications |
| Open modals | Displays ticket details, leaderboards, billing, and management UIs |
| Read channel info | Determines which channels are configured as source or triage channels |
| Manage reactions | Adds lifecycle reactions (⏳, 👀, ✅) to ticket messages to show status |
Click Allow to authorize.
Redirect to the onboarding wizard
After authorization:
- Your browser redirects automatically to the Treqdesk Onboarding Wizard
At this point, setup is not complete and you hold the Owner role. No channels are monitored yet.
Until the wizard is complete, every Treqdesk feature is blocked except Billing & Seats and Upgrade to Pro in the App Home. Trying to use /mytickets, /team-leaderboard, or the 🎫 reaction will show an error asking you to finish setup.
Part 2 — Complete the onboarding wizard
Only the person who installed Treqdesk (the Owner) can complete the onboarding wizard. If someone else needs to finish setup, the Owner should share the onboarding URL directly.
Welcome
A brief intro screen. Click Continue.
Billing email
Enter an email address for subscription management and receipts. A team alias like billing@yourcompany.com works fine — it doesn't need to be a personal address.
Create your first support team
Configure your first support team. You can create more later via /manage-team.
| Field | What it does |
|---|---|
| Team name | A label that appears on ticket cards and in the leaderboard (e.g., "Engineering Support") |
| Triage channel | The Slack channel where ticket cards are posted. Agents manage tickets from here. Use a dedicated, low-traffic channel. |
| Source channels | Channels Treqdesk monitors for 🎫 reactions. A reaction in a source channel creates a ticket routed to this team. |
| Agents | Workspace members who can be assigned tickets on this team. |
Keep the triage channel dedicated — don't use a high-traffic general channel. Ticket cards generate noise and will overwhelm an active channel.
Bot channel invite
For public channels, the bot joins automatically. For private channels, it will try to join as well. If it cannot, invite it manually with /invite @Treqdesk.
Review and confirm
Review your configuration and click Complete Setup. This marks your workspace as active and starts monitoring your source channels.
Choose your plan
| Free | Pro | |
|---|---|---|
| Monthly tickets | 25 | Unlimited |
| Agent seats | 2 | Variable (based on purchase) |
| Support teams | 1 | Unlimited |
| Price | $0 | $5/agent/month or $55/agent/year |
See Billing & plans for full pricing and subscription details.
You can start on Free and upgrade at any time via the Upgrade to Pro or Billing & Seats buttons in the App Home.
Troubleshooting
"This app is not authorized" — The OAuth flow was interrupted. Click Add to Slack again and make sure you click Allow on the Slack consent screen.
"You don't have permission to install apps" — Ask your Slack workspace admin to install Treqdesk themselves or grant you the required app-installation permission.
Bot not reacting to 🎫 after setup — The bot must be a member of every source channel. For private channels, run /invite @Treqdesk directly in the channel. The bot cannot monitor channels it hasn't been invited to.