Getting Started with Ticket Agent

Head to the Ticket Agent homepage and click Request Access. You can sign in with your Google or Microsoft account — no separate password to remember.

Once you're in, you'll land on the admin dashboard. This is your control center for managing customers, viewing conversations, and tracking metrics.

Ticket Agent lives where your team already communicates. Right now, we support Slack and Microsoft Teams.

For Slack

1. Go to Settings in the admin dashboard
2. Under Integrations, click Connect Slack
3. Authorize Ticket Agent in your Slack workspace
4. Choose which channels the bot should listen in, or let team members DM it directly

For Microsoft Teams

1. Go to Settings → Integrations → Connect Teams
2. Follow the prompts to install the Ticket Agent app in your Teams environment
3. Team members can start a conversation by messaging the bot directly

Ticket Agent creates tickets directly in your project management tool. We support Jira, Linear, and GitHub Issues.

1. Go to Settings → Integrations
2. Select your ticketing platform and authenticate
3. Choose the default project or board where new tickets should be created
4. Optionally configure a ticket template to match your team's conventions

Every ticket Ticket Agent creates includes a structured summary with request context, business impact, current and desired behavior, acceptance criteria, and relevant code areas. No more "the button is broken" tickets.

This is what makes Ticket Agent different from a simple chatbot. When you connect your GitHub repository, the agent can browse your codebase to understand current implementation details.

1. Go to Settings → Integrations → Connect GitHub
2. Select the repositories the agent should have access to
3. The agent will use this context when creating tickets — adding relevant file paths, current behavior descriptions, and implementation notes

Now for the fun part. Open your connected chat platform and send a message to the Ticket Agent bot. Try something like:

Here's what happens next:

1. The agent asks follow-up questions — in plain language. It might ask which customers are affected, when the issue started, or what browser they're using. No jargon.
2. The agent researches your codebase — it looks at the relevant code to understand the current export implementation and adds technical context to the ticket.
3. The agent shows you a summary — before creating anything, it presents a structured preview of the ticket and asks for your approval.
4. The ticket is created — once you approve, a well-structured ticket appears in your project management tool, ready for an engineer to pick up.

The whole process typically takes about 2 minutes. Compare that to the usual back-and-forth between a requester and an engineer, and you'll see why teams love it.

Now that you've created your first ticket, here are some things to explore:

• Review your metrics — the dashboard tracks clarification turns, completion rates, satisfaction scores, and more. Use these to measure impact.
• Customize templates — tailor the ticket output format to match your team's conventions. Add custom fields, labels, or sections.
• Invite your team — share the bot with non-technical stakeholders who regularly submit requests. The fewer vague tickets in your backlog, the better.
• Set up webhooks — get notified about new conversations and tickets through your preferred channels.