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

# Reply to Accelo client tickets with AI

> Find Accelo tickets waiting on your reply, draft the answer from the thread and send it after your OK. Runs daily, you approve each message.

Source: https://cotlet.dev/integrations/accelo-api-mcp-server/reply-to-client-tickets

A client wrote on a ticket yesterday and nobody answered. The Last Contact Date column shows the gap, but each reply still means opening the ticket, rereading the thread and typing.

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

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

Hosted · nothing to install or maintain

## Can Accelo do this on its own?

Accelo sends replies as email activities from the ticket, progressions can email resolution details when a status changes, and the API creates an email activity against a ticket (checked 17 Oct 2026). A progression sends the text an admin set up in advance. None reads the thread and writes the answer, and the MCP page lists no write for replies.

## How you do it in Accelo today

1. Open Tickets and add the Ticket Last Contact Date column, which shows the days since the client was contacted, or filter by Ticket Overdue.
2. Open a ticket and read the thread of messages on it.
3. Click Message (or + Add Activity and choose Email) at the top of the ticket.
4. Fill the To field with the client contact, write the reply and click Send. A timer starts by itself and the time defaults to billable.
5. Checking which tickets wait on you is the part that gets forgotten between meetings.

## How to reply to Accelo client tickets with AI

Prompt

```
Find open Accelo tickets where the client wrote last and nobody replied for a day. Draft a short reply that answers the question, and send it only after I approve each one.
```

1. 01  
### Find tickets waiting on you  
list\_tickets filters open tickets by last interaction, so only tickets where the gap is real are in the list.
2. 02  
### Read the whole thread  
get\_ticket returns the messages in order. The agent checks the last one came from the client, so a ticket a colleague already answered is skipped.
3. 03  
### Draft from the thread  
The reply answers what the client asked in your wording. A question that needs a decision, a refund or a date is listed for you and not answered.
4. 04  
### Send after your OK  
reply\_to\_ticket sends the email to the ticket contact. Each call asks for your OK until you switch confirmation off for reply\_to\_ticket, because the client receives it.
5. 05  
### Note what was sent  
The agent reports the ticket, the contact and the first line of each reply, so you can see what went out.

### What you get back

Example data

```
Waiting on us: 6
Replies sent after your OK 4, e.g. #1042 to Dana Whitfield, export error answered with the workaround
Skipped 1 (a colleague replied since)
Left for you 1:
- #1038 asks for a refund of last quarter
```

### Other ways to ask

- Every Monday, list tickets where the client has waited more than 3 days and send nothing.
- Reply only on tickets in the Support request class and draft the rest as notes for me.
- Draft replies for today's waiting tickets as a table and send none.

## What Accelo allows, and what to know first

- The Ticket Last Contact Date column shows the number of days since the client was contacted about the ticket.
- You can only send Notes to colleagues, so a reply to a client is an Email activity.
- An activity against a Ticket is billable by default, and a ticket in a locked state cannot be changed.
- The API sends an activity when it is eligible to be sent, unless block\_send is set to 1.

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

Sources: [Accelo Help: Add an activity](https://help.accelo.com/guides/user/messages-and-tasks/messages-notes-and-emails/add-an-activity/) · [Accelo Help: Ticket list](https://help.accelo.com/guides/user/modules/tickets/view-a-ticket/ticket-list/) · [Accelo Help: Create Activity action](https://help.accelo.com/guides/settings-and-configuration-guide/triggers-and-business-processes/business-processes/progressions/create-activity-action-2/) · [Accelo API reference: Create an Activity](https://api.accelo.com/docs)

## Call reply\_to\_ticket from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/accelo/tickets/1042/replies \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"Hi Dana, thanks for the details. The export fails above 5,000 rows. Until we ship the fix, export in two batches by date. I will update this ticket when the fix is live."}'
```

Example response

```
{
"activity_id": 5562,
"ticket_id": 1042,
"medium": "email",
"to": "dana@example.com",
"sent": true,
"date": "2026-10-16T09:05:00Z"
}
```

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

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

## Accelo tools this automation uses

__Cotlet Accelo tools used to reply to Accelo client tickets with AI__
| Tool | Parameters |
| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
| list\_tickets | standing, status, assignee\_id, company\_id, priority, submitted\_after, last\_interaction\_before, limit, cursor |
| get\_ticket | ticket\_id |
| reply\_to\_ticket | ticket\_id, body, cc |

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

## Frequently asked questions

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

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

- [Triage new Accelo tickets with AI](https://cotlet.dev/integrations/accelo-api-mcp-server/triage-new-tickets.md)
- [Log time in Accelo with AI](https://cotlet.dev/integrations/accelo-api-mcp-server/log-time-on-tickets-and-projects.md)
- [Accelo API and MCP server: every tool](https://cotlet.dev/integrations/accelo-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Accelo.

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

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

---

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.