Messaging is a "user-based" chat
Live Chat is a "session-based" chat
- Better UI (Native)
- Chat history
- Answer Bot
final String androidChannelKey = '';
final String iosChannelKey = '';
@override
void initState() {
super.initState();
ZendeskMessaging.initialize(
androidChannelKey: androidChannelKey,
iosChannelKey: iosChannelKey,
);
}
just use initialize() one time
@override
void dispose() {
ZendeskMessaging.invalidate();
super.dispose();
}
/// Invalidates the current instance of ZendeskMessaging.
After calling this method you will have to call ZendeskMessaging.initialize again if you would like to use ZendeskMessaging.
This can be useful if you need to initiate a chat with another set of androidChannelKey
and iosChannelKey
ZendeskMessaging.show();
You can use in onTap()
The SDK needs to be initialized before using authentication methods !
// Method 1
final ZendeskLoginResponse result = await ZendeskMessaging.loginUser(jwt: "YOUR_JWT");
await ZendeskMessaging.logoutUser();
// Method 2 if you need callbacks
await ZendeskMessaging.loginUserCallbacks(jwt: "YOUR_JWT", onSuccess: (id, externalId) => ..., onFailure: () => ...);
await ZendeskMessaging.logoutUserCallbacks(onSuccess: () => ..., onFailure: () => ...);
This method can be used to check wheter the user is alreday logged in!
await ZendeskMessaging.loginUser(jwt: "YOUR_JWT");
final bool isLoggedIn = await ZendeskMessaging.isLoggedIn();
// After the user is logged in [isLoggedIn] is true
await ZendeskMessaging.logoutUser();
final bool userStillLoggedIn = await ZendeskMessaging.isLoggedIn();
// After you call the logout method [ZendeskMessaging.isLoggedIn()] will return [false]
There's must be a logged user to allow the recovery of the unread message count!
// Retrieve the unread message count
final int count = await ZendeskMessaging.getUnreadMessageCount()();
// if there's no user logged in, the message count will always be zero.
Allows custom conversation tags to be set, adding contextual data about the conversation.
// Add tags to a conversation
await ZendeskMessaging.setConversationTags(['tag1', 'tag2', 'tag3']);
// Note: Conversation tags are not immediately associated with a conversation when this method is called.
// It will only be applied to a conversation when end users either start a new conversation or send a new message in an existing conversation.
Allows custom conversation tags to be set, adding contextual data about the conversation.
// Allows you to clear conversation tags from native SDK storage when the client side context changes.
// This removes all stored conversation tags from the natice SDK storage.
await ZendeskMessaging.clearConversationTags();
// Note: This method does not affect conversation tags already applied to the conversation.
If you need to catch all events you can attach a global observer to the ZendeskMessaging.
ZendeskMessaging.setMessageHandler((type, args){
print("$type => $args");
});
- Attachment file:
Currently does not support.
The official said it will be launched in the future. - Chat room closed:An agent can not reply to a customer at any time. if the customer is not active in the foreground, the room will be closed automatically. It is inconvenient to track chat history.
- Push Notifications
- Zendesk messaging Help
- Agent Workspace for messaging
- Working with messaging in your Android and iOS SDKs
- You can star and share with other developers if you feel good and learn something from this repository.
- If you have some ideas, please discuss them with us or commit PR.