# Unassigned ticket can not be closed

**URL:** https://community.sendbird.com/t/unassigned-ticket-can-not-be-closed/9859
**Category:** API
**Created:** [July 31, 2024, 2:34pm UTC](https://community.sendbird.com/t/unassigned-ticket-can-not-be-closed/9859 "2024-07-31T14:34:34Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Guy\_Guy](https://avatars.discourse-cdn.com/v4/letter/g/94ad74/32.png) [@Guy\_Guy](https://community.sendbird.com/u/Guy_Guy)
#### Post date: [July 31, 2024, 2:34pm UTC](https://community.sendbird.com/t/unassigned-ticket-can-not-be-closed/9859/1 "2024-07-31T14:34:34Z")

</div>

**[Problem]**  
It appears we can’t close an unassigned ticket via API.  
However, there is a flow in Desk that auto closes a ticket after some time (even if it is not assigned?)

* * *

**[SDK Version]**  
REST API

**[Reproduction Steps]**

1. Try to close an unassigned ticket via REST API

```auto
{
  "code": "desk400100",
  "detail": "Unassigned ticket can not be closed."
}

```

**[Current impact]**

1. A ticket can be opened without an agent being assigned, and it needs to be closed the same manner.

---

<div class="post-metadata">

### Author: ![Ian](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/ian/32/2077_2.png) [@Ian](https://community.sendbird.com/u/Ian)
#### Post date: [October 17, 2024, 1:57am UTC](https://community.sendbird.com/t/unassigned-ticket-can-not-be-closed/9859/2 "2024-10-17T01:57:53Z")

</div>

Hi @Guy_Guy,

Sendbird Desk is designed in a way to prevent “no response” scenarios, which is why you are unable to close unassigned tickets.

---

<div class="post-metadata">

### Author: ![Guy\_Guy](https://avatars.discourse-cdn.com/v4/letter/g/94ad74/32.png) [@Guy\_Guy](https://community.sendbird.com/u/Guy_Guy)
#### Post date: [October 28, 2024, 7:32pm UTC](https://community.sendbird.com/t/unassigned-ticket-can-not-be-closed/9859/3 "2024-10-28T19:32:27Z")

</div>

Hi @Ian  
One can argue that the action/intent of closing a ticket _is_ a response.

For example: a scenario where a chat bot resolves your inquiry without escalating to a human agent. The chatbot is just another member on the channel, not a Desk agent.

In this case, when the bot concluded a resolved issue, we would have loved to be able to resolve/close the ticket.

---

<div class="post-metadata">

### Author: ![Ian](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/ian/32/2077_2.png) [@Ian](https://community.sendbird.com/u/Ian)
#### Post date: [October 28, 2024, 10:14pm UTC](https://community.sendbird.com/t/unassigned-ticket-can-not-be-closed/9859/4 "2024-10-28T22:14:26Z")

</div>

@Guy_Guy,

Is your bot using the chatbot interface from Sendbird Chat? Sendbird Desk supports the use of bots as well. Using the Sendbird Desk bot interface, you can assign the ticket directly to the bot itself, allowing you to close the ticket in the bot’s name.

---

<div class="post-metadata">

### Author: ![Guy\_Guy](https://avatars.discourse-cdn.com/v4/letter/g/94ad74/32.png) [@Guy\_Guy](https://community.sendbird.com/u/Guy_Guy)
#### Post date: [October 29, 2024, 8:03am UTC](https://community.sendbird.com/t/unassigned-ticket-can-not-be-closed/9859/5 "2024-10-29T08:03:32Z")

</div>

What is the Chatbot Interface from chat? Not the AI Chat…  
We can’t use the Desk bot do to implementation restrictions (insufficient payload structure).
