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

# Follow up on snoozed Kustomer conversations

> Remind customers who have not answered a snoozed Kustomer conversation, quoting what you asked for, then close it after one reminder. Runs daily.

Source: https://cotlet.dev/integrations/kustomer-api-mcp-server/follow-up-on-snoozed-conversations

You asked a customer for an order number and snoozed the conversation until they reply. A week later it is still snoozed, and nobody looks at it until the customer writes angrily.

Cotlet does it in your own Kustomer account with search\_conversations, get\_conversation\_messages, reply\_to\_conversation and mark\_conversation\_done, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can Kustomer do this on its own?

Kustomer snoozes a conversation until a time or the customer's reply, and an admin can build workflows that send a final message and mark it done (checked 17 Oct 2026). The workflow sends the same text to every customer and is built by pasting JSON. None of it quotes what you asked for in that conversation or decides that a second reminder is too much.

## How you do it in Kustomer today

1. The agent clicks Snooze Conversation and picks when it returns to Open: 2 hours, tomorrow morning at 9 a.m., a custom date and time, or when the customer replies.
2. When the snooze expires, Kustomer sends the agent an email and a notification reminding them about the conversation.
3. The agent opens the conversation, rereads the thread to remember what was asked, and writes a reply in the reply editor.
4. If nothing comes back, the agent selects Mark as Done, and the conversation can be reopened if the customer writes later.
5. Admins can build a callable workflow and a scheduler workflow that send a final message and mark snoozed conversations done after a set time, using JSON pasted into the Workflow Editor.

## How to follow up on snoozed Kustomer conversations

Prompt

```
Find Kustomer conversations that have been snoozed for more than 5 days where the customer has not written back. Send one short reminder that quotes what we asked for, then mark them done after a second silence. If we already sent a reminder, list the conversation for me instead.
```

1. 01  
### Find the stale ones  
search\_conversations runs with status snoozed and an update date older than your cutoff, so only conversations that really waited are listed.
2. 02  
### Read the thread  
get\_conversation\_messages returns the messages in order. The agent checks that the last message is yours, so a conversation where the customer already answered is skipped.
3. 03  
### Count reminders  
If an earlier outbound message already is a reminder, the agent does not send another. It lists the conversation for you with the days waited.
4. 04  
### Write the reminder  
reply\_to\_conversation sends a short message that repeats the one question you asked, in your wording, on the channel of the last message. Each reply asks for your OK until you switch confirmation off.
5. 05  
### Close after a second silence  
If your prompt says to finish after another silence, mark\_conversation\_done sets the status to Done. A Done email conversation reopens if the customer replies.

### What you get back

Example data

```
Snoozed for more than 5 days: 8
Reminder sent 4, e.g. Dana Whitfield, waiting 6 days for the order number
Marked done after a second silence 2
Customer replied since, skipped 1
Already reminded, left for you 1:
- Jon Reyes, waiting 12 days
```

### Other ways to ask

- Every Monday, list snoozed conversations older than a week with the question we asked, and send nothing.
- Remind only customers on conversations tagged enterprise, and write to them in a more formal tone.
- After one reminder and 3 more days of silence, mark the conversation done without another message.

## What Kustomer allows, and what to know first

- Kustomer has three main statuses: Open, Snoozed and Done. A sub-status can explain why a conversation is snoozed.
- A snooze ends at the chosen time or when the customer replies, and removing a snooze returns the conversation to Open.
- When a customer replies to an email thread of a Done conversation, Kustomer reopens the same conversation, with no time limit.
- Chat and SMS have a window of about 24 hours of inactivity, after which a new conversation is created.
- A reply is limited to 10,240 characters on email and chat, 1,600 on text/SMS and 2,000 on Facebook DM.

reply\_to\_conversation asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [Kustomer Help: Change conversation or task status](https://help.kustomer.com/en%5Fus/change-conversation-status-HkvUsVS8W) · [Kustomer Help: Resolve snoozed conversations with workflows](https://help.kustomer.com/en%5Fus/resolve-snoozed-conversations-with-workflow-r13UnJayj) · [Kustomer Help: Respond to conversations](https://help.kustomer.com/en%5Fus/respond-to-a-conversation-HJ7isEHUZ)

## Call reply\_to\_conversation from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/kustomer/conversations/6718d2e4a1b2c3d4e5f60733/replies \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"Hi Dana, just checking in. To fix the export we still need the order number from your confirmation email. Reply here when you have it."}'
```

Example response

```
{
"conversation_id": "6718d2e4a1b2c3d4e5f60733",
"message_id": "6720b1c7a1b2c3d4e5f60844",
"channel": "email",
"direction": "out",
"status": "snoozed",
"created_at": "2026-10-17T09:00:00Z"
}
```

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

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

## Kustomer tools this automation uses

__Cotlet Kustomer tools used to follow up on snoozed Kustomer conversations__
| Tool | Parameters |
| --------------------------- | ------------------------------------------------------------------------- |
| search\_conversations | status, tag, customer\_id, updated\_before, updated\_after, limit, cursor |
| get\_conversation\_messages | conversation\_id, direction, channel, cursor |
| reply\_to\_conversation | conversation\_id, body |
| mark\_conversation\_done | conversation\_id |

[All 12 Kustomer tools with descriptions](https://cotlet.dev/integrations/kustomer-api-mcp-server.md#tools)

## Frequently asked questions

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

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

- [Merge duplicate Kustomer conversations with AI](https://cotlet.dev/integrations/kustomer-api-mcp-server/merge-duplicate-conversations.md)
- [Add handoff notes to Kustomer conversations](https://cotlet.dev/integrations/kustomer-api-mcp-server/add-handoff-notes-to-conversations.md)
- [Kustomer API and MCP server: every tool](https://cotlet.dev/integrations/kustomer-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Kustomer.

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

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

---

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.