[tawk.to] Apollo AI tips - Chat transfers, Escalations and more

Hello, community,

Earlier today we shipped an update for our Shortcuts system which finally allows AI to escalate and transfer chats. Here is how:

Shortcuts included in AI Data Source can have Actions and Elements attached to them.

Here are some examples of Shortcut setups for potential AI scenarios:

  1. Apollo sends visitor a ticket form to fill out:


    With this setup, if a visitor mentions ‘’Error 123’’ in chat, AI will send the pre-defined message along with an in-chat ticket form that the visitor can fill.

  2. Apollo transferring chat to a Property Member:


    And this is how it would look in chat from Agents point of view:

    Chat itself would be in Red on the active chat list for the assignee:

  3. Apollo sending an informative image in chat:


    Simply add the image you want AI to send as Element->File when creating a Shortcut.

  4. Apollo offering a ticket form and attempting to transfer the chat to an agent in case someone is online to help:

To have all Property Members who are currently online notified, you can create a Department with Everyone in it. To do this, go to User Management-> Departments.


Note that you might need to refresh the dashboard for newly created departments to show up on the assignee dropdown menu.

Hope these example setups serve as inspiration for your own creative AI flows.
As always, let me know at ralfs@tawk.to if you have any questions or if you notice any bugs or issues.

2 Likes

awsome!!! you guys rock!!! just a little problem if I activate the second escalation toggle.
the chat automaticlly transfers whenever the pre chat info is sent. also there is no notitication on the mobile app for the transfer chat.

Also i have a question what if there are no operators online. Apollo would still transfer the chat and the user will be there waiting

anyways thanks for the new features, but I guess they still need to be polished.

Hi Leo,

If your pre-chat form only has Name and Email it will most likely not find match to visitors contact information in your Data Source, therefore meeting the conditions to transfer the chat.

I understand that this might be bit too sensitive and we will adjust the logic for it.

A workaround for now could be a combination of Base Prompt instruction and a Shortcut that has Ticket or Transfer Actions. It could be something along the lines of

  • If answer is not included in given knowledge or is not related to say, ''Unfortunately, I will not be able to assist you with this, but my colleagues should be able to help.
    [option] Can you give me a contact form that I can fill?
    [option] Can you transfer me to a human agent?
    ‘’

Afterward, you can create Shortcuts with the questions above in the AI question field with the corresponding actions- A ticket form for when a user asks for a form to fill and a Transfer Chat action shortcut for a human transfer question.

Hope this helps.

1 Like

Thanks not what I was hoping for, guess I will keep that toggle disabled,
Apollo should greet visitors as usual and asks how can It help.?
not trying to answer a name and an email of a pre chat form at a start of a conversation because that makes the human handover sadly not usable.

I used this prompt as workaround along with the new transfer action shortcut

"- Always greet the user by saying exactly this: :wave:Hello! Please select a topic or write your question and present the following options:
[option] A
[option] B
[option] C
[option] D
[option] E

the this other prompt " If the answer is not included in the provided knowledge, say exactly “Unfortunately I do not have that information at this time.” and add [option] Speak to an agent now."
then use a shortcut to transfer the chat

Also I noticed that apollo fails to answer 95% of the time even if the anwser of the question is on the knowledge if that toggle is activated. and always transfer the chat

When can we expect an Article with the necessary steps and examples in the Help Center?

Hi,

Chat Transfer is fundamentally an action launched by Shortcuts and you can instruct AI on when to do it by adding AI Question field to the Shortcut with relevant keywords it must look out for in visitors message.

If you use Base Prompt to introduce buttons when no answer is found in given knowledge, you can have AI react to those buttons:

For transfer the Shortcut would look like this:

And for Ticket form, it would look like this:

Sometimes with pre-chat forms, AI might need a looser ‘‘given knowledge’’ restriction in Base Prompt so it would not automatically assume that there is no answer the moment visitor inquiry does not include any matching keyword.

Hope this helps.

Great to see, that the AI bot gets smarter! I like the idea to give the customer a contact form, if the AI Bot does not find an answer. Two problems here:

  1. the ticket form is not completely in the language of the property: it says “Subject”, “Message” and “Your request has been sent”. I guess these words are hardcoded or can I edit this content of the ticket form somewhere in the dashboard?

  2. It is great, that the bot shows the ticket form, if he knows no answer. But is it also possible to only show the form, if no human supporter is online and ELSE try to switch over to a human supporter?

2 Likes

I was wondering the same about the ticket form language. I do not use the tickets because the emails are not in the property language as well. Been waiting to change the language for too long to no avail :frowning:

thanks… for the workaround. I’ll try it.

Yup I wish we could change this to spanish.

2
mensaje

1 Like

Ralph,

How can I set AI to looser “given knowledge” restriction? Do you have an base prompt example?

Thank you!

Hi,
You can find an article on this here:

For now, I would recommend disabling the ‘‘When no information is found’’ Escalate setting when the pre-chat form is enabled as it counts user’s name/email as something not found in given knoweldge.

If you have an existing shortcut that introduces a pre-chat form or transfer action, you can simply assign relevant keywords that should launch that Shortcut using the AI Question field found on bottom of the Shortcut editing window.

Hope this helps.

1 Like

Hello
I tried to follow these steps to activate the escalation but no matter what i do, the bot gets stuck during the escalation. It will mention that it is transferring to an agent but it does nothing.
Can you please confirm that it is working?

Hi weelow,

Could it be that the shortcut that is used for escalation is missing the transfer ‘‘Action’’ field?

If you need help with your personal AI setup, I am happy to help you sort out the configuration if you email me the specific cases at ralfs@tawk.to

Hello @Ralph
Thanks for your reply. My configuration matches exactly what is in the screenshot.
In addition to that, i have enabled escalation and selected the shortcut from the dropdown.

I have a prechat form setup that collects the user’s name and email before the chat starts. Could that be the problem?

The transfer action should be part of the /transfer-to-agent shortcut itself.

Additionally, you might add base prompt instruction to tell Apollo that users start chatting by filling out a form, and in response to this AI should offer assistance.

tawk.to does not send a notification when the chat is escalated. The bot just stays there in the chat doing nothing. As soon as i click the monitoring button and open the chat, i get the notifications.
This means, if an agent is not online or not paying attention, they wont know that a chat is active with the bot.

Hi,

Transfer notifications are only sent to agents who are currently online on the dashboard or tawk.to app and set as transfer assignees.

Hi @Ralph,

I’m trying to work out how best to configure my chatbot using the AI Assistant with human handover/takeover only when absolutely needed.

I can share many of the concerns/queries raised here. I’m not attempting to use the “no response” escalation but I do have significant concerns over the ability to configure/use agent escalation and lead capture.

I’ve been reading your various guides and responses on threads like this one and also https://community.tawk.to/t/ai-assist-collection-of-the-most-useful-base-prompt-instructions-that-you-can-copy/2319, so have had a pretty good play around now with the various options for both lead capture and agent escalation, e.g.

• Pre-Chat form
• Chat Rescuer
• Base Prompt with Shortcuts/Triggers

The main goals are as follows:

  1. Allow the AI Agent to do all the hard work using our training data and base prompt, essentially configuring them as a sales rep with the role of gathering info, qualifying leads, and unlimitedly capturing their details into the CRM at the right (a natural) point in time. We don’t want to scare visitors off by coming across as hard-selling and asking for details upfront.

  2. Allow human agents to proactively monitor AI chats and take over if needed, or allow the visitor to request a human agent if they prefer.

The issues are:

1. LEAD CAPTURE -

I’ve tested the various ways to do this but none of them work in a natural way:

a. BASE PROMPT ONLY -

The issue with using the base prompt to collect details is that this is free text, the CRM (Monitor section and subsequently Contacts/Inbox) doesn’t recognise or store things like “name” or “email” within the contact details/attributes. Therefore, as an admin/agent, I can’t easily tell that a lead has been qualified by the AI and contact details taken. All I see is an unhelpful string as the name e.g. “V1723294151136215”

b. BASE PROMPT + TRIGGERS AND/OR SHORTCUTS

I’ve tried using Chat Rescue and shortcuts to trigger the lead capture form. This does seem to log their name and email correctly in the CRM but there are issues:

i. It doesn’t do this when at the “Monitoring” stage, so I just see that horrible string as the name. It only seems to do this when the chat ends and gets logged in the Inbox/Contacts sections. This means, there’s no way to easily tell the contact has been qualified and details have been taken – we need to see this to determine whether it’s a time-waster or genuine lead and worth taking over the chat.

ii. I can’t trigger the form using basic prompt text e.g. “… Then collect the visitor’s details using the /lead-capture shortcut” or any variation on this.

iii. If I use option buttons/shortcuts or the Chat Rescue trigger to generate the form, it kind of breaks up the flow of the conversation and feels unnatural. More importantly, the conversation dies when the user completes the form. It’s meant to happen as part of a natural conversation (sales qualification process), with the ability for the AI to continue the dialogue, e.g. “Thank you for supplying your contact info [name], is there anything else you need?”.

iv. There’s no way that I can find to configure the lead capture form, e.g. choose/add fields, add follow-up instructions (revert back to chat), etc.

v. Even if the visitor manually types a follow-up question after submitting the form, the AI Assistant still has no knowledge of their name, etc.

c. PRE-CHAT FORM

This is the only way that seems to work as the form is configurable and passes the data to the AI Assistant so it can address them by name, etc. Using this method, the “Monitoring” section seems to instantly assign the visitor’s correct name, which is great! But this would discourage most users from even engaging in a chat for the following possible reasons:

i. Feels intrusive to ask for personal details without any niceties and like a hard sell is coming
ii. The greeting isn’t personal and feels like you’ll end up not reaching a real person (or good AI assistant)

I hope I’m missing something as the pre-chat form capabilities work exactly as needed but we need to be able to control when this happens during the AI assisted dialogue, i.e. so it happens at a natural stage and allows continued conversation with AI Assistant understanding who the visitor is.

2. AI ASSIST, ALERTS/NOTIFICATIONS, AND HUMAN AGENT TRANSFER

I really like how this works and the various options available but the two main issues are:

a. NEW CHAT ALERTS/NOTIFICATIONS

Human agents don’t get an obvious alert or notification to pro-actively monitor and take over AI chats if needed. Alerts only happen when transferring to an agent, then the app makes a ringing sound (sadly, this is less noticeable on the app and I think most agents will miss the alert).

b. HUMAN TRANSFERS -

When transferring to an agent, if they are busy or don’t notice the chat (e.g. on silent), the user is left hanging with no proactive follow up from the AI. This creates a really poor experience for the user and will most likely deter them from using us.

The Chat Rescue would work if we could configure something like, “If no agent response in 30 seconds, return the chat to the AI Assistant”, then ideally, the AI Assistant would determine when to capture the details naturally. Instead, the user completes the form and is left hanging with no AI intervention or ability to add follow-up instructions. It just gives an unhelpful “Your request has been sent”.

Final thoughts

I know there are a lot of alternatives out there, but I felt it was worth the time to document my experience here. I’ve now tested a massive range of CRM/chatbot type solutions that claim to combined AI Assisted Chatbots + Human Live Chat support, e.g. LiveChat/ChatBot, FreshChat, Socialintents, Tidio (Lyro AI), Wonderchat, Landbot, etc. All have their pros and cons, but none of them work as well as Tawk in terms of having a high configurable AI chatbot (prompts, various data sources for training, etc.) and human transfer/Live Chat capability across various channels (dedicated desktop/mobile apps, browser, etc.). Plus, it’s nowhere near as expensive as the others.

I even prefer how we can add sequences using shortcuts/messages within the AI rather than fixed sequence drag and drop workflow style bot builders. The area where I feel it’s weakest is notifications and lead capture. Again, hopefully I’ve missed something?

Thanks,
David

Hi David,

  1. Lead Capture
    To get customer details into the CRM they would have to fill in a form with fields that link to CRM. This can be done through a pre-chat form or a ticket/lead form introduced by a Shortcut. The Base prompt cannot launch Shortcuts directly, but it can introduce a button that links to a Shortcut with the form. The instructions here would involve giving the AI a scenario for when it should send the button and the quoted text that introduces the button. For example:
  • If the user is interested in our services, say, "For this, you would need to get in touch with our team. You can click the button below to be transferred to an agent, or if it is outside of business hours, you can leave us a note.
    [option] Transfer me to an agent
    [option] I am happy to leave a note ‘’

  • After answering the visitor’s inquiry, add to the end of your message: “[option] How do I get started?”

From there, you would connect the button text with the Shortcut’s AI Question field.

  1. Alerts for Currently Active Chats
    By default, AI joins the chat instantly before the incoming chat notification can ring. If the AI is to work alongside human agents, we typically add a ~20-second join delay, allowing the notification to ring so human agents can react to the chat. From there, they can decide if it needs immediate attention and join, or proceed to wait and let the AI join the chat that they can monitor. You can find the join delay setting under the Behavior section in AI settings:

  2. Transfers Outside of Business Hours
    For this, we would add a button to help users get unstuck if they request a transfer in the middle of the night, something along the lines of “Transfer is taking too long,” and link that button to a follow-up Shortcut with a resolution. This can inform the user about business hours, provide an email/phone number to reach out to, or a form to fill out.


Additional notes:

  • The Rescue trigger type cannot be launched if AI has already joined the conversation, as it is designed to be sent if no one joins the chat within a set amount of time.
  • ‘No info found’ escalation setting will only launch if AI has no matches in context selection. If AI gets a partial context match it will refer to the base prompt for what to do if it does not know the answer.

Additionally, I recommend looking into creating scripted button sequences by linking Shortcuts together. People enjoy clicking buttons, so this typically boosts engagement. By using this method, you can hardwire buttons introduced by the Welcome Trigger with Shortcuts that send forms or action transfers. I have a guide that discusses this here: Help Center | tawk.to | Using Suggested Message and AI Assist to create scripted chat sequences

I appreciate the kind words and feedback. Hopefully this helps.
If anything you can always reach out to me directly at ralfs@tawk.to

Best regards,