Sendbird Desk enables strong customer engagement through live, in-app support. The Desk SDK lets you easily initialize, configure, and build the customer support-related functionality into your iOS applications. This page shows requirements and a brief overview of the Desk SDK.
The requirements of Desk SDK for iOS are:
iOS 8.0 or higher
SendBird iOS SDK 3.0.90 or higher
Our sample app demonstrates the core features of Sendbird Desk SDK. Download the app from our GitHub repository to get an idea of what you can do with the actual SDK and to get started building your own project.
Note: The fastest way to see our Desk SDK in action is to build your app on top of our sample app. Make sure to change the application ID of the sample app to your own when initializing the Desk SDK. Go to Create a Sendbird application from your dashboard section to learn more.
Sendbird Desk works based on Sendbird Chat platform, which means the interactions between users are built and provided by Sendbird Chat. Your customers can request support through various ways, such as in-app chats from different OS platforms or social media like Facebook and Instagram, and we call them channels. When a customer requests support from a channel, it is delivered to an agent by admins or internal rules, and agents can handle the conversation in the Sendbird Dashboard.
In Sendbird Desk, Ticket is a unit of customer’s inquiry. In other words, when a customer or agent starts a conversation, the corresponding ticket is also created. There are 5 types of ticket status that are changed according to the conversation progress. For example, when a conversation between customer and agent ends, the ticket status is also changed to closed. Admins who are an agent with additional privileges to manage overall dashboard settings can manage tickets by their status, creation date, assignees, and more.
Desk related events are delivered to the Chat SDK's event delegates registered to your client app. While the
SBDMain instance in a client app is connected to Sendbird server, the event delegates receive callbacks from the server through
channel:userDidEnter:, and other event callback methods. By using event callback methods of the delegates, your app can implement appropriate responses and actions correspondingly such as updating a ticket closure request on the UI level.