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

# Close resolved Gladly conversations

> Close Gladly conversations that sit in Waiting after your reply and leave a note on each. Runs daily from Claude Code, n8n or a script, hosted.

Source: https://cotlet.dev/integrations/gladly-api-mcp-server/close-resolved-conversations

Emails you answered days ago stay in Waiting until someone closes them, so the Waiting tab fills with finished work.

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

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

Hosted · nothing to install or maintain

## Can Gladly do this on its own?

Gladly moves a Conversation to Closed when an Agent clicks Close or Close & Next, and closes abandoned calls on its own (checked 20 Oct 2026). Replied emails stay in Waiting until someone acts. The REST API can set a Conversation to closed, but there is no rule in Gladly that closes Waiting Conversations after a quiet period, and no MCP server.

## How you do it in Gladly today

1. Administrators and Team Managers click the Waiting status tab on the home page.
2. Open each Conversation and check whether the customer replied after your last message.
3. Click Close & Next to close it and get the next Customer, or the up and down carets to choose Close alone.
4. If there was no reply to the Customer, Gladly asks you to confirm closing without a reply.
5. A Conversation closed too early can be opened again with Reopen a Closed Conversation, so the check repeats for every single one.

## How to close resolved Gladly conversations

Prompt

```
Look at the Waiting conversations in the Email Inbox. Close the ones where the customer has not written back in the last 3 days and say how many you closed.
```

1. 01  
### List the Waiting queue  
list\_conversations with status waiting returns the replied emails, ended chats and ended calls that were not closed. Only Administrators and Team Managers see this tab.
2. 02  
### Check the quiet period  
get\_conversation returns the timeline. The agent compares the date of the last customer item with your cut-off and skips any Conversation where the customer wrote last.
3. 03  
### Leave a note first  
add\_note records "Closed after 3 days without a reply" on the timeline. Notes cannot be edited, and only Administrators can delete them, so this call asks for your OK.
4. 04  
### Close  
close\_conversation closes the Conversation. It asks for your OK, because a reply may still be pending on a phone call, and Gladly does not allow closing during an active call.
5. 05  
### Report what stayed open  
Conversations with a recent customer message or an active call stay in Waiting and are listed with the reason.

### What you get back

Example data

```
Waiting in Email Inbox: 31
Closed 22, each with a note
Stayed open 9:
- Ola Berg: customer replied yesterday
- Dana Reyes: call in progress
Oldest closed: 12 days without a reply
```

### Other ways to ask

- Close Waiting conversations older than 7 days and add no note.
- List what would be closed, but change nothing, so I can review it first.
- Every Friday, close Waiting chats from this week and send me the count.

## What Gladly allows, and what to know first

- Gladly shows Conversations as Waiting after an email reply, an ended chat or an ended call, before they are closed.
- Gladly cannot close a Conversation while a phone call is active.
- Closing a Conversation without a reply to the Customer asks for confirmation in the Gladly app.
- A closed Conversation can be opened again, and Gladly has a Reopen a Closed Conversation help page for it.
- Gladly Notes are internal, cannot be edited, and only Administrators can delete them.

add\_note and close\_conversation ask for your OK by default. To run it daily without you, switch confirmation off for those tools in your dashboard.

Sources: [Gladly Help: Close a Conversation](https://help.gladly.com/docs/close-a-conversation) · [Gladly Help: Conversation Status (New, Open, Waiting, Closed)](https://help.gladly.com/docs/conversation-status-new-open-waiting-closed) · [Gladly Help: Why can't I close a Conversation?](https://help.gladly.com/docs/why-cant-i-close-a-conversation) · [Gladly Help: Add a Note to a Conversation](https://help.gladly.com/docs/add-a-note-to-a-conversation)

## Call close\_conversation from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/gladly/conversations/ZbT9m2QxR7iKd4WnHq0LpA/close \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"conversation_id": "ZbT9m2QxR7iKd4WnHq0LpA",
"status": "closed"
}
```

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

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

## Gladly tools this automation uses

__Cotlet Gladly tools used to close resolved Gladly conversations__
| Tool | Parameters |
| ------------------- | ------------------------- |
| list\_conversations | status, inbox\_id, cursor |
| get\_conversation | conversation\_id |
| add\_note | conversation\_id, body |
| close\_conversation | conversation\_id |

[All 13 Gladly tools with descriptions](https://cotlet.dev/integrations/gladly-api-mcp-server.md#tools)

## Frequently asked questions

### Does the customer get a message when the agent closes the conversation?

No. Closing only changes the status in Gladly. If the customer writes again, the conversation can reach your team again; how long a closed conversation can reopen depends on your Conversation Reopen Window setting.

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

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

- [Triage new Gladly conversations](https://cotlet.dev/integrations/gladly-api-mcp-server/triage-new-conversations.md)
- [Create follow-up tasks in Gladly](https://cotlet.dev/integrations/gladly-api-mcp-server/create-follow-up-tasks.md)
- [Gladly API and MCP server: every tool](https://cotlet.dev/integrations/gladly-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Gladly.

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

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

---

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.