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

# Answer eDesk where-is-my-order tickets with AI

> Reply to eDesk shipping questions with the real tracking code and delivery date from the order, and keep late parcels for yourself. Runs daily.

Source: https://cotlet.dev/integrations/edesk-api-mcp-server/answer-where-is-my-order

Every day a share of marketplace tickets ask where a parcel is, and an agent opens each one, finds the order, reads the tracking and types the same answer again.

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

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

Hosted · nothing to install or maintain

## Can eDesk do this on its own?

eDesk answers the plain case itself (checked 20 Oct 2026): a Message Rule with a Rule-only template sends the same delivery text when the ticket type and order status match. The template does not read what the customer asked and does not compare the date with today. Nothing in eDesk sorts late parcels from on-time ones before replying.

## How you do it in eDesk today

1. An agent opens the ticket and reads the Order information in the sidebar: order number, shipping status, tracking number and link if available, and estimated delivery.
2. In the Reply box the agent clicks the Template icon, or types an underscore, and picks the delivery template. Snippets such as #tracking\_code# fill in from the order.
3. An admin can send the answer automatically: a Message Rule with the ticket type Shipping query and the order status Order shipped or In transit binds a Rule-only template with Bind an Autoresponder.
4. For tracking links, an admin opens All Orders, selects an order of that courier and clicks the pen icon next to the tracking code to add a link that eDesk reuses for the courier.
5. Tickets the rule does not match, such as a parcel past its date or an order without tracking, wait for an agent to read them.

## How to answer eDesk where-is-my-order tickets with AI

Prompt

```
For Shipping query tickets in to do, check the order. If it is on time, reply with the tracking code and expected delivery date in my Delivery update wording. If it is late or has no tracking, leave it for me with a note.
```

1. 01  
### Find the questions  
list\_tickets with type Shipping query and status to\_do returns tickets that wait for a reply. Tickets that already have a reply are not touched.
2. 02  
### Read the ticket and its order  
get\_ticket gives the message and the linked order. When eDesk linked none, the agent searches list\_orders with the order number the customer typed, and leaves the ticket for you if there is no match.
3. 03  
### Judge the order  
get\_order returns the status, the ship date, the tracking and the expected delivery dates. The agent sorts the order: on time, past its latest expected date, or no tracking. Only the first group gets an answer.
4. 04  
### Use your wording  
list\_templates returns your Delivery update template once per run. The agent keeps its sentences and puts the real order number, ship date and tracking code in place of the snippets.
5. 05  
### Reply and park  
reply\_to\_ticket sends the answer with send status waiting, so the ticket drops out of To Do and returns there if the customer writes back. Every reply asks for your OK until you switch confirmation off.

### What you get back

Example data

```
Shipping query tickets waiting: 9
Replied 6, e.g. #48210 (Royal Mail HB204418830GB, due 14 Oct)
Left for you 3:
- #48221 past its latest delivery date
- #48224 order has no tracking code
- #48226 no order found for the number given
```

### Other ways to ask

- Only reply on the Amazon UK channel and list the other channels.
- Reply to Shipping query tickets on eBay and tag the late ones with Late parcel.
- List every Shipping query ticket with the order status and expected date, and send nothing.

## What eDesk allows, and what to know first

- A Rule-only template that uses order snippets needs at least one Order Status in its Usage Conditions, for example #dispatched\_on# needs Order Shipped, so orders in other statuses fall through to a person.
- eDesk customer-name and shipping-address snippets do not fill in on Amazon channels because of Amazon PII restrictions, so replies on Amazon leave them out.
- eDesk links an order to a ticket by matching details such as an Order Reference, and the Order Lookup setting can limit matching to orders within a set number of days.
- The send status defaults to Resolved unless your user setting says Waiting, and a customer reply reopens the ticket in To Do.
- After one tracking link is set for a courier name on All Orders, eDesk fills in a tracking link for every order with that courier.

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: [eDesk Help: Exploring the ticket view](https://support.edesk.com/ticket-view) · [eDesk Help: Replying to a ticket](https://support.edesk.com/mailboxtickethandling/respond) · [eDesk Help: Common uses of Message Rules](https://support.edesk.com/common-uses-of-message-rules) · [eDesk Help: Tracking code mapping](https://support.edesk.com/tracking-code-mapping) · [eDesk Help: Creating manual usage templates](https://support.edesk.com/smarttools-templates/creating-manual-usage-templates) · [eDesk Help: Setting up your company details](https://support.edesk.com/setting-up-company-settings)

## Call reply\_to\_ticket from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/edesk/tickets/48210/replies \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"Hi Emma, your order 203-7718305-2294466 was dispatched on 9 October with Royal Mail. Tracking code: HB204418830GB. It should reach you by 14 October. Reply here if it has not arrived by then.","send_status":"waiting"}'
```

Example response

```
{
"message_id": 771209,
"ticket_id": 48210,
"kind": "reply",
"status": "waiting",
"sent_at": "2026-10-20 09:05:00"
}
```

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

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

## eDesk tools this automation uses

__Cotlet eDesk tools used to answer eDesk where-is-my-order tickets with AI__
| Tool | Parameters |
| ----------------- | -------------------------------------------------------------------------------- |
| list\_tickets | status, query, type, channel\_id, owner\_id, tag, updated\_before, limit, cursor |
| get\_ticket | ticket\_id |
| get\_order | order\_id |
| list\_templates | query |
| reply\_to\_ticket | ticket\_id, body, send\_status |

[All 11 eDesk tools with descriptions](https://cotlet.dev/integrations/edesk-api-mcp-server.md#tools)

## Frequently asked questions

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

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

- [Triage new eDesk tickets with AI](https://cotlet.dev/integrations/edesk-api-mcp-server/triage-new-tickets.md)
- [Follow up on waiting eDesk tickets with AI](https://cotlet.dev/integrations/edesk-api-mcp-server/follow-up-waiting-tickets.md)
- [eDesk API and MCP server: every tool](https://cotlet.dev/integrations/edesk-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to eDesk.

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

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

---

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.