[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 stale Jitbit tickets automatically

> Close Jitbit tickets that went quiet after your last reply, with an internal note and no closed email. Runs weekly, customer replies stay open.

Source: https://cotlet.dev/integrations/jitbit-api-mcp-server/close-stale-tickets

You answered a customer, they never wrote back, and the ticket still sits in Unclosed. Weeks later it clutters every view and counts as open work.

Cotlet does it in your own Jitbit account with list\_tickets, get\_ticket, reply\_to\_ticket and close\_ticket, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can Jitbit do this on its own?

Jitbit lets you close tickets by hand, in bulk from the list, or with an automation rule on the trigger "Ticket has not been updated for 30 minutes or more" (checked 22 Oct 2026). A rule fires on a time condition and does not look at who wrote last or what the thread says. The official MCP cannot close a ticket.

## How you do it in Jitbit today

1. A technician opens the Tickets page and clicks the Unclosed tab, which lists all active tickets the user may see.
2. To find the quiet ones, the technician sorts by the last updated column or uses the advanced filter with a last-updated date.
3. For each ticket the technician opens it and rereads the thread to check that the customer did not write last.
4. Then the technician clicks Close in the ticket buttons, or Close silently in the more menu, which skips the Ticket closed email.
5. Several tickets can be ticked in the list and closed together with the bulk actions.
6. The checking is the part that gets skipped, so quiet tickets stay open for months.

## How to close stale Jitbit tickets automatically

Prompt

```
Find Jitbit tickets nobody has touched for 14 days where we sent the last reply. Add an internal note saying why, then close them without the closed email. Show me anything where the customer wrote last.
```

1. 01  
### Find the quiet tickets  
list\_tickets runs with mode unclosed and updated\_before set to your cutoff, so only tickets that really went quiet are in the list.
2. 02  
### Check who wrote last  
get\_ticket returns the comments in order. If the last public comment is the customer's, the ticket is skipped and listed for you.
3. 03  
### Leave the reason  
reply\_to\_ticket posts an internal note with for\_techs\_only set to true, saying the ticket is closed after no answer since the last reply. It is visible to technicians only.
4. 04  
### Close it  
close\_ticket closes the ticket with silent set to true when you asked for no email. Every call asks for your OK until you switch confirmation off for close\_ticket.
5. 05  
### Report what stayed open  
The agent lists tickets that were skipped and why, so a customer reply never gets closed over.

### What you get back

Example data

```
Unclosed tickets quiet for 14 days: 9
Closed silently 6, e.g. #4871 "Invoice copy", last reply from us 21 days ago
Skipped 3 (customer wrote last):
- #4902 "Still broken"
- #4915 "Re: export question"
- #4920 "Follow-up"
```

### Other ways to ask

- Every Friday, list unclosed tickets quiet for 30 days with the last message and close nothing.
- Close quiet tickets in the Onboarding category only, and send the normal closed email.
- Before closing, add a public reply asking if the problem is solved, and close the ticket a week later if nobody answers.

## What Jitbit allows, and what to know first

- Close silently appears in the more menu only if the "ticket closed" email notification is enabled in your helpdesk.
- The Close button changes the ticket status to Resolved, and Re-open brings a resolved ticket back to In process.
- The Unclosed tab shows all active tickets the user may see, and the ALL tab includes closed ones.
- Time-based automation rules run only once per ticket, so a rule cannot nag a quiet ticket again and again.
- A public comment is emailed to the ticket followers, by default the submitter and the assigned person, while a note for technicians only stays inside the helpdesk.

reply\_to\_ticket and close\_ticket ask for your OK by default. To run it weekly without you, switch confirmation off for those tools in your dashboard.

Sources: [Jitbit Helpdesk Docs: Ticket page](https://www.jitbit.com/docs/viewissue/) · [Jitbit Helpdesk Docs: Tickets grid (list)](https://www.jitbit.com/docs/activetickets/) · [Jitbit Helpdesk Docs: Automation Rules](https://www.jitbit.com/docs/adminrules/) · [Jitbit Helpdesk Docs: MCP Server](https://www.jitbit.com/docs/mcp/)

## Call close\_ticket from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/jitbit/tickets/4871/close \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"silent":true}'
```

Example response

```
{
"ticket_id": 4871,
"status": "Resolved",
"notification_sent": false,
"closed_at": "2026-10-22T09:04:00Z"
}
```

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

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

## Jitbit tools this automation uses

__Cotlet Jitbit tools used to close stale Jitbit tickets automatically__
| Tool | Parameters |
| ----------------- | ---------------------------------------------------------------------------------------------- |
| list\_tickets | mode, category, status, priority, tag, company, updated\_before, updated\_after, limit, offset |
| get\_ticket | ticket\_id |
| reply\_to\_ticket | ticket\_id, body, for\_techs\_only |
| close\_ticket | ticket\_id, silent |

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

## Frequently asked questions

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

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

- [Triage unassigned Jitbit tickets with AI](https://cotlet.dev/integrations/jitbit-api-mcp-server/triage-unassigned-tickets.md)
- [Merge duplicate Jitbit tickets with AI](https://cotlet.dev/integrations/jitbit-api-mcp-server/merge-duplicate-tickets.md)
- [Jitbit API and MCP server: every tool](https://cotlet.dev/integrations/jitbit-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Jitbit.

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

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

---

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.