Learn how to use the Talkative Agent Console to handle live chat, video and more. This guide will show you the key features of the console and help you confidently manage customer interactions!
📽️ Talkative Agent Training Video (45 Minutes)
Watch the full training session covering all aspects of the Agent Console and how to use it effectively.
Availability Status
The availability dropdown controls your active status and will control certain behaviours on the console.
- When you want to receive chats, you should set yourself as ‘Online’.
- When you’re taking a break you should set yourself as ‘Unavailable’ or a similar status.
- And when you’re finished for the day you should be set as ‘Offline’
To change your status, click the dropdown at the top of the page

When you are set as ‘Offline’ or ‘Unavailable’ the system will show a red banner at the top of the page to remind you!
Extra settings
At the top of the console section, there are some additional settings and troubleshooting tools.
Clicking on the cog icon you’ll find:
- Notification and video testing
- Language cache clearing (for if translation is having issues)
- Agent training (If configured by the account holder)
Next to the cog, there us also the aggressive notifications toggle. Useful if you want interactions to continually ring when needing to be accepted

Accept interaction
When you have set yourselve as online, you’ll soon start to receive interactions.
An interaction will appear in the pending section, on the bottom left hand side of the console.
To accept the interaction, click the green tick button.

Make sure to accept the interaction as soon as possible. If the interaction times out you may automatically be set offline!
Messaging/Attachments/Emojis
When you’re in an interaction with a customer, you’ll be shown the chat window.
Here you’ll see any messages that you or the customer sent. It’ll even show messages that we’re sent before you handled the interaction!
When on this page you can:
- Send messages by clicking the message textbox and hitting the send button or tapping enter on your keyboard
- Attach files using the paperclip icon
- Add emojis to your messages

AI Reword
If enabled, you can also reword your message that has been drafted in the message text box.
Simply type out a draft message, then click the robot icon.
Select the reword type you want, then a suggestion will appear on the “Copilot” section of the console.
Here you can click to fill the chatbox or send the message.
Can’t see this setting? Reach out to your account holder.

Video Calling
When chatting to a customer on an interaction, you may want to escalate the chat to a video/voice call.
To start a video chat, click the video icon at the top of the page. Then click either ‘Voice Only’ or ‘Voice and Video’
This then sends a notification to the customer asking if they want to join the call.

Transfer
If you need someone else to handle the interaction, perhaps someone with a different skillset, you can transfer the interaction elsewhere.
To transfer an interaction, click the transfer button at the top of the console.


Then select whether you want to transfer to a specific agent, or anyone within a specific queue.
Customer View
If you want to see what webpage your customer is currently on, click the customer view button.
This will display an Iframed version of the webpage the customer is currently looking at.
Agents cannot see any session data that relates to that customer. For example, agents cant see if the customer has items in their shopping basket.

Internal Messages
When handling an interaction, you can send ‘Internal Messages’. An internal message is a way of contacting your supervisor mid interaction or for just generally making notes.
To send an internal message, click the internal messages bar on the top of the console page.
This will open a new text box, where you can send and receive messages.


The internal messages bar will show the last message sent/recieved
Once a internal message has been sent a supervisor can see the messages in the ‘Chat Monitoring’ in ‘Live Dashboards’ and also within the interaction logs for future review.
Customer Disconnected Notification
During an interaction you the queue name at the top of the page may change to orange.
This means that the customer has disconnected and is no longer on the chat.

A customer is considered present if they have an active websocket connection. The disconnect message appears when they close the tab/browser or lose internet connection.
Information Tab
If you need to know more information about the user you’re chatting with, use the Information tab.
Clicking “Information” at the top of the console page will show various information about the user.
This page shows information on:
- Where the interaction was started from
- What URL’s the user has been accessing
- The interaction ID and References
- Any interaction data that has been collected in a pre chat form
- The customers IP address, location operating system and browser version
- What peripherals the user has access to
- What features the customer can engage with

History Tab
If you want to check previous engagements with a particular user, use the History tab.
Clicking “History” at the top of the console page show you a list of any recent interactions you or any other agents have had with this user.
This is useful to see what was said in previous engagements if the user is following up on something.
The history tab will show previous messages, and what channels were used to communicate previously.

Copilot
If you need some help sending a message back to a user. Consider using our Copilot.
Copilot can be accessed from the “Copilot” tab from the top of the console page.
When a customer sends a message, Copilot will generate a suggested reply based on the dataset configured.
From here, you can fill your textbox and make some adjustments to the suggestion, or send what it suggests straight to the customer.

If you don’t see the Copilot section, contact your Talkative Account Holder
Navi
Similar to Copilot, Navi can also support you while you are working with a user.
Navi allows you to to directly ask questions to an AI assistant, which will provide an answer based on your companies database, and the context of the current interaction.
You can start a conversation with Navi by navigating to the Copilot tab, and clicking the Navi button at the bottom of the screen.

Try asking it to summarise the current conversation or suggest the next recommended action with the user!
Ending interaction/Adding Tags
Once you have wrapped up an interaction with a customer, you should end it.
To end an interaction, click the red ‘X’ at the top of the page.
After clicking this, you will be taken to the wrap up page. Here you can add tags to the interaction for future reference and block the customer by their IP address if needed.

The wrap up process may appear different depending on console configuration
Using the Console on iOS or Android mobile device
In addition to Talkative's browser-based agent console for desktop use, the agent console can be used on Android or iOS mobile/tablet devices.
You can either use the browser or download the app.
🤖 Android System requirements
We recommend using Android version 12 or newer being used.
🍎 iOS System requirements
We recommend using iOS version 16.4 or newer being used
📱 Mobile App
🤖 Android Mobile App (recommended) Please download the app from the Google store: EU: https://play.google.com/store/apps/details?id=com.gettalkative.engage.eu US: https://play.google.com/store/apps/details?id=com.gettalkative.engage.us AU: https://play.google.com/store/apps/details?id=com.gettalkative.engage.au
🍎 iOS Mobile App (recommended) Please download the app from to App Store https://apps.apple.com/gb/app/talkative-engage/id1559242610 Choose your region and login
⚠️ Account Holders will need to adjust notification settings for iOS users following the below guide
💻 Browser
To use Talkative on an Android or iOS device, open up Chrome or Safari and login to your usual Talkative URL.
We recommend you tick "remember me" when logging in.
On your device, be sure to accept notifications. We recommend that your Android / iOS settings are such that you will be able to hear notifications, to maximise the chance of being notified when an interaction comes to you.
Next, make sure you are set to "Available" on the queue page. At this point, you can now close your device or use other applications.
You will receive push notifications when:
- you receive a new interaction - note that you typically have a short time to pick up the interaction - when you receive an interaction, you need to be quick!
- you receive a new message
- you have been set to offline (typically because you didn't pick up the chat/video in time)
Depending on your organisation's set up, you may need to log in each morning.
To stop receiving notifications, go back to the web page and set yourself to "offline" or similar.
❓FAQ’s: Agent Console
I can’t see the Users Messages?
Usually, this issue is to do with cookies. Please perform the steps in the following order until the problem is resolved.
- Make sure you are using Google Chrome browser on the latest version
- Turn off any cookie blocking software such as AdBlock and UBlock. Disable these for eu.engage.app, us.engage.app, au.engage.app, euc.engage.app (if you don't know what this means, you likely don't have an ad blocker so can skip this step.
I’m not receiving any Interactions?
There are several reasons you may not be receiving interactions even if you are logged in, and set to online in the queue. Some of the most common answers can be found in the table below.
Agent is not in the correct Groups | The most likely scenario is that the user is not in the correct user group. Interactions are routed to queues, which has the user groups assigned to them. If the user is not a memner of a group, they will not be assigned any interactions. You can assign users to a group via the groups settings. |
Agent has incorrect media channels | Check that the user is set up to work the relevant channels. Via Users in the Settings menu, edit the user and check Twilio Channels |
Mitel is not configured correctly | If you are a Mitel user, check that the Talkative Queue is correctly linked to the Mitel Queue. Verify this via the Edit Queue page. |
What are the minimum network and browser requirements?
Agents need an internet speed of at least 1MB/s to handle video calling. We recommend that agents use the most updated version of Google Chrome.
Why am I offline / unavailable / missing interactions?
These instructions assume your org is using Talkative routing. If you are using 3rd party routing (Mitel, SFDC Omnichannel, etc.), then user presence is governed by those applications rather than Talkative.
To receive interactions, agents will need to be in an Available state from their queue presence.
On the console page, you must select Available status to be active in the queue.

Agents will receive interactions when they are Available. This will only stop when:
- the queue is offline (because of business hours)
- the agent is at capacity (they are handling 1 video call, or perhaps 3/3 chats)
- the agent misses an interaction and the system sets them to Unavailable
- the agent manually changes their status to Unavailable or Offline
Default Behaviour
Closing down the tab/window will not automatically change the agent's status.
Agents should remember to turn themselves offline if they are unable to handle chats.
Optional Behaviour
If your agents are forgetting to manually change their status to offline, Account Holders can change a setting in Settings > General > Company Configs > User Auto-Offline

I have to refresh my screen to show new messages from the customer?
Screen refreshing is a temporary fix. To resolve the issue…
- Log out of your platform and delete cache and cookies on your browser. Log in again. If the issue persists then…
- Check your browser console and network tabs (right click anywhere on the screen and select Inspect). You are looking for Errors or excessive XHR requests to ‘pusher’. Take a screenshot of both tabs and contact support@gettalkative.com
My Console window is cramped / squashed / looks like it doesn’t fit?
Your screen resolution may be too small. Minimum supported screen resolution is 1366 x 768
