[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Tag and assign new Help Scout conversations with AI

> Sort new Help Scout conversations by what the customer means: add tags, assign them to the right teammate, leave unclear ones untagged. Runs daily.

Source: https://cotlet.dev/integrations/help-scout-api-mcp-server/tag-and-assign-conversations

New emails pile up in the Unassigned folder overnight, and someone has to open each one, guess the topic, add a tag and pick an owner before the real work starts.

Cotlet does it in your own Help Scout account with search\_conversations, get\_conversation, tag\_conversation and assign\_conversation, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=help-scout) [All Help Scout tools](https://cotlet.dev/integrations/help-scout-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Help Scout do this on its own?

Help Scout covers part of this natively (checked 16 Oct 2026). Automatic workflows add tags and assign to a user, and to a team on the Plus or Pro plan, but only by the conditions you write, such as subject, body text, customer email or domain. They match words, not what the customer means. The official MCP is read-only for new connections, so an agent cannot tag or assign through it.

## How you do it in Help Scout today

1. Open the Unassigned folder and open a conversation. Click the Add tag icon, start typing and pick an existing tag from the drop-down, or choose Create tag.
2. Click Assignee in the Details card at the top of the sidebar and pick a User or search by name. From a folder, select the conversation and use the Assign icon in the menu that appears.
3. To handle many at once, run a search, select several conversations and use the bulk action menu to assign, change the status or tag them.
4. Teams that want less clicking build a workflow with the Add Tag(s) and Assign to User actions, set to run when a conversation meets the conditions.

## How to tag and assign new Help Scout conversations with AI

Prompt

```
Go through unassigned active conversations in the Support inbox. Tag each one billing, bug, how-to or sales by what the customer means, and assign bugs to Sam and billing to Maria. Leave anything unclear untagged and tell me.
```

1. 01  
### Collect the untouched queue  
search\_conversations runs status:active assigned:Unassigned in the Support inbox and pages through the cursor, so a long weekend backlog is sorted as one batch.
2. 02  
### Read the customer's message  
get\_conversation brings the first customer thread and any notes. The agent classifies by meaning, for example a refund request that never says the word refund, and quotes the line it relied on.
3. 03  
### Keep to your tag list  
tag\_conversation only adds tags from the list in your prompt. A conversation that fits none of them stays untagged with a reason, so Help Scout does not collect a new near-duplicate tag every day.
4. 04  
### Assign by your rule  
assign\_conversation hands bugs and billing to the teammates you named. If the person is a Light User, who cannot have conversations assigned, the agent reports it instead of failing silently.
5. 05  
### Skip what moved  
Right before each change the agent checks that the conversation is still unassigned. One a teammate took in the meantime is logged as already handled and left as it is.

### What you get back

Example data

```
Unassigned active conversations: 14
Tagged and assigned 11:
- bug (4) to Sam, e.g. #48240 "Export button does nothing"
- billing (5) to Maria, e.g. #48244 "Charged twice in October"
- how-to (2), left unassigned for the reply job
Left untagged 3 (unclear):
- #48251 "Quick question about the thing from last week"
Already taken by a teammate: 0
```

### Other ways to ask

- Tag every conversation from customers at @acme.io as vip and assign it to Maria.
- Only tag, never assign, and list the tag counts for the week.
- Find conversations tagged billing that are still unassigned after two days and assign them to the Account Owner.

## What Help Scout allows, and what to know first

- Help Scout allows as many tags on a conversation as you need, and tagging needs the Add or remove conversation tags permission; creating a new tag needs Create, edit, merge, delete tags.
- Account Owners, Administrators and Users can assign conversations and receive them; Light Users can do neither.
- Assigning to a team is available only on the Plus or Pro plan.
- A workflow runs only once on any given conversation, even if it still matches later, and can hold up to 30 conditions.
- Deleting a tag in Help Scout removes it from every conversation with no undo, so the agent adds and removes tags on conversations but never deletes a tag itself.

tag\_conversation and assign\_conversation change only your own Help Scout data and reach no one else, so they run without asking first.

Sources: [Help Scout Docs: Create and manage tags](https://docs.helpscout.com/article/13-create-and-manage-tags) · [Help Scout Docs: Assign conversations](https://docs.helpscout.com/article/842-assign-conversations) · [Help Scout Docs: Automatic workflows](https://docs.helpscout.com/article/1399-automatic-workflows) · [Help Scout Docs: Search in Help Scout](https://docs.helpscout.com/article/771-search-in-help-scout)

## Call tag\_conversation from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/help-scout/conversations/48244/tag \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"add":["billing"]}'
```

Example response

```
{
"conversation_id": 48244,
"tags": [
"billing"
],
"added": [
"billing"
],
"removed": []
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is help\_scout\_write → tag\_conversation. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/help-scout-api-mcp-server.md#automations)

## Help Scout tools this automation uses

__Cotlet Help Scout tools used to tag and assign new Help Scout conversations with AI__
| Tool | Parameters |
| --------------------- | ----------------------------- |
| search\_conversations | query, inbox, limit, cursor |
| get\_conversation | conversation\_id |
| tag\_conversation | conversation\_id, add, remove |
| assign\_conversation | conversation\_id, assignee |

[All 14 Help Scout tools with descriptions](https://cotlet.dev/integrations/help-scout-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Help Scout to Cotlet?

Yes. You sign in to Help Scout yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Help Scout once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Help Scout automations

- [Reply to Help Scout conversations from your Docs articles](https://cotlet.dev/integrations/help-scout-api-mcp-server/reply-from-help-docs.md)
- [Update Help Scout Docs articles after a product change](https://cotlet.dev/integrations/help-scout-api-mcp-server/update-docs-articles.md)
- [Help Scout API and MCP server: every tool](https://cotlet.dev/integrations/help-scout-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Help Scout.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Help Scout.

[Sign up free](https://cotlet.dev/app/signup?app=help-scout)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.