# Scale Plan vs Pro Plan

Wrangle offers two flexible plans designed to meet different team needs. Whether you're just getting started or need advanced features for a larger operation, here's what each plan includes.

### The Key Differences

#### Scale is Pro + AI and integration superpowers

Scale takes everything in Pro and adds the automation and connectivity that help larger teams move faster:

**AI does the heavy lifting** Scale includes AI-powered features that handle repetitive work for you. [Smart Replies](https://docs.wrangle.io/tickets/ai-powered-ticketing/smart-replies) suggest responses to common questions, while [agentic features](https://docs.wrangle.io/tickets/ai-powered-ticketing/ai-ticket-deflection) can automatically route, categorize, and even respond to tickets based on patterns it learns from your team.

**Connect to your existing tools** Native integrations with Zendesk, Jira Service Management, and Notion mean tickets and documentation flow seamlessly between systems. No more copy-pasting or losing context when issues move between teams. Plus, API access lets you build [custom workflows](https://docs.wrangle.io/integrations/slack-workflow-builder#getting-started) for any other tools in your stack.

**Make Wrangle truly yours** White-label the Wrangle bot so customers see your company name instead of "Wrangle" in Slack channels. Route tickets with custom emoji that match your team's workflow. Get a dedicated CSM and personalized training to ensure your rollout succeeds.

**Scale smarter with user groups** Organize agents into groups (like "Tier 1 Support" or "Security Team") to route tickets more intelligently and manage permissions at scale.

### When to choose Scale

You'll get the most value from Scale if you:

* **Handle high ticket volume** where your agents could benefit from AI automation to save time and energy on repeat requests
* **Work across multiple tools** and need tickets synced between Slack and your other systems
* **Support external customers** in Slack Connect and want [white-labeling](https://docs.wrangle.io/account-administration/appearance-white-labeling)
* **Need custom workflows** that require [API access](https://docs.wrangle.io/integrations/wrangle-api) or [emoji-based routing](https://docs.wrangle.io/tickets/setting-up-your-inbox/ticket-lifecycle/ticket-creation#custom-emoji-for-ticket-creation)
* **Want hands-on support** with a dedicated CSM during rollout

### When Pro is enough

Pro gives you everything you need for solid ticket management if you:

* **Run a lean team** that doesn't need advanced automation
* **Work primarily in Slack** without requiring external integrations
* **Want core features** like SLAs, workflows, private tickets, and analytics

### Try before you decide

<figure><img src="/files/z7JYUlSl1rjyA8cPaJrc" alt="Wrangle free trial banner"><figcaption></figcaption></figure>

**All trial users start with Scale**, so you can test AI features, integrations, and advanced customization before committing to a plan.

**Already on Pro and curious about Scale?** We'll grant you temporary access to test Scale features. Just [ask our team](https://docs.wrangle.io/more-help/contact-us).

Still have questions? [Contact](https://docs.wrangle.io/more-help/contact-us) our team or [schedule a demo](https://www.wrangle.io/request-a-demo-of-wrangle-slack).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.wrangle.io/tickets/scale-plan-vs-pro-plan.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
