Controls what text appears in the chat subtitle, right below the chat title.
No subtitle is displayed when the conversation has no subject set or when set to null.
Defaults to "subject".
Controls the text direction (for supporting right-to-left languages such as Arabic and Hebrew). TalkJS tries
to determine the appropriate text direction from the parent page, but if that does not work or you want to
explicitly control it, you can override it here. Defaults to "rtl".
"rtl" | "ltr"
Used to control which conversations are shown in the conversation feed, depending on access
level, custom conversation attributes or message read status.
Sets the message input box to the given text.
You can use this to suggest a certain initial message to be sent. The user can still edit it before hitting "send".
Makes the inbox start up with the given Conversation. Can be passed a value of the type ConversationBuilder (returned by getOrCreateConversation) or the string value of the conversation id. Conversation can be deselected on startup by passing a null value. Passing undefined means that the last conversation (or "no chats yet page") will be displayed.
Set this to true to show a translation toggle in all conversations.
Set this to "auto" to show a translation toggle in conversations where there are participants with different locales.
This setting defaults to false, meaning that no toggles will be shown.
In order to use this, you must be on the Premium plan, and set a Google Translate API key in the dashboard.
TalkJS leverages iframes behind the scenes and therefore not all services that you use in your app will work out of the box.
This option adds support for a number of services to help you use them. Let us know if you're missing any.
TalkJS can translate conversations to the current user's locale using Google Translate.
This option specifies which conversations should be translated in this UI. You can pass a boolean to enable/disable
translation for all conversations, "auto" to enable translation on conversations where users have different locales,
or you can pass an array of {@link ConversationBuilder}s or conversation Ids to be translated.
This feature is only available on the Premium plan and above. Make sure you add your Google Translate API key in the dashboard.
Controls whether the user navigating between conversation should count
as steps in the browser history. Defaults to true, which means that if the user
clicks the browser's back button, they go back to the previous conversation
(if any).