For visitors who aren’t already in an active chat, the widget defaults to a screen that shows multiple choices: “Help Center” (with a search box), and “New Conversation.”
If the customer disables the “Knowledge Base” in Admin → Widget Settings, then “Help Center” goes away - yet the widget still requires the user to read/understand the interstitial screen and click “New Conversation.” There’s no way to reliably link to/show the chat pane.
This is most relevant when the Tawk customer uses the “Direct Chat Link” triggered by a link/button on the customer’s site. For example, I’d like to design a “Start chat” or “We’re online - ask us anything” link into our site design, but that isn’t possible - the link can’t actually drop the user into a chat session. There is no way to directly link to a chat session, only to the multi-function Tawk home screen.
Some possible ways to improve this, including one - (A) - that seems like a quick win and should be the default now:
A. When displaying the widget in the “Direct Chat Link” URL, the only enabled module in Widget Settings is Chat, and there are no recent chats, show the new chat pane by default. Don’t make the user work through another screen (that only has 1 relevant choice) and click “New Conversion” - that just decreases conversion.
It seems like this should be the default, in that the whole point of a “Direct Chat Link” would be to link to chat. If Tawk also wants to offer a “Direct Support Link” (that shows all support modules like the current link does), great, but there should be a legitimate direct link to chat.
B. A bit more work but also more flexible: in the “Direct Chat Link” (and maybe also the Tawk_API.showWidget() function), let the implementer specify the initial screen. For example: https://tawk.to/chat/abc-def-123?show=chat (and if other modules might benefit from being directly reachable, other arguments like https://tawk.to/chat/abc-def-123?show=kb).
(If you wanted to offer that functionality through the JS API as well, the equivalent could be Tawk_API.showWidget('show': 'chat') or maybe a separate Tawk_API.switchScreen('chat') function. Not at all required though.)
(B) seems like a question of work for benefit, but (A) seems like a more thoughtful default for existing users.