Trengo automation · runs weekly
Close resolved Trengo conversations with AI
Conversations sit in Assigned to me long after your team wrote last, and nobody closes them until someone sorts the folder by hand.
Cotlet does it in your own Trengo account with list_conversations, get_conversation, set_reminder and close_conversation, called by your AI agent, an n8n workflow or a script.
Hosted · nothing to install or maintain
Can Trengo do this on its own?
Trengo closes a conversation when an agent clicks it, in bulk for up to 50 at a time, or through a rule with the action Close ticket (checked 20 Oct 2026). A rule can combine Last message direction equals outbound with Elapsed time is 5 hours, so it closes on silence, not on what the customer wrote. Nothing in Trengo reads the thread to see whether the matter is settled.
How you do it in Trengo today
- An agent opens Inbox > Assigned to me and opens each conversation to see who wrote last.
- If the customer has what they need, the agent clicks the checkmark above the ticket, or sends a last message with Send and close.
- To close many at once, the agent clicks the coloured circles in front of the tickets, or the circle left of With selected to take 50, and picks an action from the arrow.
- For a conversation that waits for the customer, the agent clicks the Bell icon and picks a date and time; the ticket moves to the Reminders folder and comes back then.
- Deciding which conversations are really finished is still a read of each thread, so the folder grows between sorting sessions.
How to close resolved Trengo conversations with AI
Every Friday, go through my Trengo conversations where our team wrote last more than 3 days ago. Close the ones where the customer confirmed it worked, set a reminder for Monday 9:00 on the ones still waiting for the customer, and skip any with a note to wait.- 01
Find the quiet ones
list_conversations with folder assigned_to_me and last_message_from team returns conversations where your team wrote last. The agent keeps those whose last message is older than your window, using last_message.at, and follows next_cursor to the end.
- 02
Read how it ended
get_conversation shows the customer's last message and your last reply. A thank you, "that worked" or an answer with no open question counts as settled. A question you asked that nobody answered does not.
- 03
Respect the notes
The same call returns internal notes. A note such as "waiting for finance" keeps the conversation open, and the agent lists it for you instead of closing it.
- 04
Remind instead of closing
set_reminder puts a reminder at the time in your prompt on conversations still waiting for the customer. It reaches nobody and one more call clears it, so it does not wait for your OK.
- 05
Close the settled ones
close_conversation runs once per conversation and asks for your OK by default. Journeys, rules or a CSAT survey you built may react to a closed conversation, and the agent cannot see them, so the close is the call you approve.
What you get back
Our team wrote last, more than 3 days ago: 13
Closed 9:
- Customer said thanks or confirmed the fix
Reminder set for Monday 9:00 on 4:
- Our question about an order number is still unanswered
Left for you 0Other ways to ask
- Close every conversation labelled Delivery where the customer confirmed the parcel arrived.
- Show me the conversations you would close with the customer's last line, and close nothing.
- Every Monday, set a reminder for Thursday on conversations where I asked for an order number and got no reply.
What Trengo allows, and what to know first
- Trengo bulk actions close, assign, mark as spam or delete up to 50 conversations at a time, and a deleted ticket cannot be retrieved.
- A Trengo reminder reopens the ticket at the date and time you choose and keeps it in the Reminders folder until then.
- AI Journeys has a Conversation closed trigger, and AI Labeling uses it to tag closed conversations, so a close can start a journey of yours.
- Closed conversations stay searchable by ticket number, name, phone number, email address or keyword; only deleted tickets do not appear in results.
close_conversation asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.
Sources: Trengo Help: Closing a conversation · Trengo Help: Bulk actions in your inbox · Trengo Help: Setting a ticket reminder · Trengo Help: Rules explained · Trengo Help: AI labeling in Journeys · Trengo Help: Searching a conversation
Call close_conversation from a script
curl -X POST https://cotlet.dev/api/v1/trengo/conversations/5120302/close \
-H "Authorization: Bearer $COTLET_API_KEY"{
"conversation_id": 5120302,
"status": "closed",
"closed_at": "2026-10-20T09:10:00Z"
}MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is trengo_write → close_conversation. Example data.
Schedule it in n8n, Make, Zapier or cronTrengo tools this automation uses
| Tool | Parameters |
|---|---|
| list_conversations | folder, label, last_message_from, cursor |
| get_conversation | conversation_id |
| set_reminder | conversation_id, remind_at, clear |
| close_conversation | conversation_id |
Frequently asked questions
Is it safe to connect Trengo to Cotlet?
Yes. You sign in to Trengo yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Trengo 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.
Give your agent access to Trengo.
Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Trengo.