[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)

# Assign Podium Inbox conversations by topic

> Read unassigned Podium conversations, sort them by what the customer asked and assign each to the right teammate, then get a list of what is left.

Source: https://cotlet.dev/integrations/podium-api-mcp-server/assign-inbox-conversations

Texts and emails land in the Podium Inbox all day, and the unassigned ones wait until someone opens each thread to see whether it is billing, scheduling or a complaint.

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

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

Hosted · nothing to install or maintain

## Can Podium do this on its own?

Podium has Escalation Rules, open to all users, and Auto-Assign, for Inbox Pro users only (checked 23 Oct 2026). A rule assigns a conversation to a specific user or to the next available user in the queue. Podium's article describes no rule that reads what the customer wrote, and none of the 17 OAuth scopes in its API covers assignment.

## How you do it in Podium today

1. Open the Inbox and find the conversation.
2. At the top right of the conversation, click the + Assign icon. A dropdown lists all users in the Podium account.
3. Select the teammate. Their name appears in the conversation header as the owner.
4. To change the owner, click the current name and pick another user. To assign several people, click the Assignment field in the header and tick their names.
5. Every new thread needs this click, and the work grows with the volume of messages.

## How to assign Podium Inbox conversations by topic

Prompt

```
List unassigned Podium conversations at Riverside Dental. Assign billing questions to Dana Reyes, scheduling questions to Sam Ortiz, and tell me about anything else.
```

1. 01  
### Collect unassigned threads  
list\_conversations runs with assigned\_to unassigned and follows next\_cursor to the end, so the whole queue is judged as one batch.
2. 02  
### Read each thread  
get\_conversation returns the messages. The agent reads the contact's last messages and the channel, because a text that says "can I move Friday" and an email that disputes a charge need different people.
3. 03  
### Match topic to person  
The agent applies the mapping in your prompt, for example billing to Dana Reyes and scheduling to Sam Ortiz. A thread that fits no topic, or fits two, stays unassigned and goes on your list with a one-line reason.
4. 04  
### Assign  
assign\_conversation sets the owner, with one name or several when you ask for it. It reaches no customer, so it runs without waiting for your OK.
5. 05  
### Check before changing  
Right before assigning, the agent reads the conversation again. A thread a teammate took in the meantime is left alone.

### What you get back

Example data

```
Unassigned conversations: 14
Assigned 11:
- Dana Reyes (billing): 4
- Sam Ortiz (scheduling): 7
Left for you 3:
- Marcus Webb: asks if you take Delta Dental
- Unknown number: "STOP"
```

### Other ways to ask

- Every morning at 8, assign the unassigned conversations from the last 12 hours and send me the list.
- Assign anything that mentions a refund or a complaint to me and tell me how many there are.
- Show unassigned conversations grouped by topic, and assign nothing.

## What Podium allows, and what to know first

- Podium lets you assign one conversation to several teammates at once, using the Assignment field in the conversation header.
- Escalation Rules are available to all Podium users; Auto-Assign is available to Inbox Pro users only.
- An escalation rule assigns to a specific user or to the next available user in the queue when Auto-Assign is on.
- The assign dropdown lists all users in the Podium account, so the names in your prompt must match that list.

assign\_conversation changes only your own Podium data and reach no one else, so it runs without asking first.

Sources: [Podium Knowledgebase: Managing Conversations in Podium](https://podium.my.site.com/knowledgebase/s/article/Managing-Conversations-in-Podium) · [Podium Knowledgebase: Setting Up Auto-Assign & Escalation Rules](https://podium.my.site.com/knowledgebase/s/article/Setting-Up-Auto-Assign-Escalation-Rules) · [Podium developer docs: OAuth scopes](https://docs.podium.com/docs/oauth-scopes)

## Call assign\_conversation from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/podium/conversations/conv_91d3/assign \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"users":["Sam Ortiz"]}'
```

Example response

```
{
"conversation_id": "conv_91d3",
"assigned_to": [
"Dana Reyes"
],
"status": "assigned"
}
```

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

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

## Podium tools this automation uses

__Cotlet Podium tools used to assign Podium Inbox conversations by topic__
| Tool | Parameters |
| -------------------- | ------------------------------------- |
| list\_conversations | location, assigned\_to, limit, cursor |
| get\_conversation | conversation\_id, limit |
| assign\_conversation | conversation\_id, users |

[All 14 Podium tools with descriptions](https://cotlet.dev/integrations/podium-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Podium to Cotlet?

Yes. You sign in to Podium yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Podium 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 Podium automations

- [Reply to Podium Google reviews with AI](https://cotlet.dev/integrations/podium-api-mcp-server/reply-to-google-reviews.md)
- [Send Podium review invites from a customer list](https://cotlet.dev/integrations/podium-api-mcp-server/send-review-invites.md)
- [Podium API and MCP server: every tool](https://cotlet.dev/integrations/podium-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Podium.

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

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

---

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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

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.