The friendly, start-from-scratch guide for contact-centre agents and team leads — signing in and setting your status, taking and making calls, handling WhatsApp, web chat, SMS, email and social messages, looking after customers, wrapping up neatly, and reading your own numbers. Every screen is reproduced and clearly labelled, with simple steps, worked examples and a Try it exercise on every task. No prior training needed.
This manual is organised into the chapters listed below. Use the chapter and section numbers (for example § 4.2) as the stable reference throughout — printed page numbers depend on your browser’s print engine and zoom.
Each chapter shows you a branded picture of the real CloudCX Agent Desktop screen — with numbered labels — then walks you through it in plain, numbered steps, with at least one worked example and a Try it exercise to practise. Watch for the four coloured callouts (Note, Tip, Warning, Danger): they carry the little bits of judgement around each task.
Welcome to CloudCX — your one screen for talking to customers. From a single window in your web browser you will answer phone calls and reply to WhatsApp, web chat, SMS, email and social messages, all in one place, without juggling apps. That window is called the Agent Desktop and it lives at agent.cloudcx.app. This first chapter is a gentle warm-up: what CloudCX does for you, how to sign in (including the extra security code some accounts use), what to do if you forget your password, and a friendly first look at the desktop so nothing feels strange on day one. No prior training is needed — if you can use a web browser, you can use this.
This is the handbook for the people on the front line: agents who handle customer interactions, and the team leaders who work alongside them. You do not need to be technical. Every task is shown as a labelled picture of the real screen, then simple numbered steps, a worked example, and a short Try it exercise to practise. Read it cover to cover as a course, or jump straight to the task you need.
In a traditional contact centre, calls live in one app, WhatsApp in another, email in a third — and you spend the day switching between them and losing track. CloudCX puts all of those channels into one workspace so you handle every conversation the same way, side by side. While you talk to a customer, the desktop also shows you who they are and what they contacted you about before, so you never start from scratch.
Voice calls, WhatsApp, web chat, SMS, email and social messages all arrive in the same Inbox on the left. Each is tagged with its channel colour so you can tell them apart at a glance.
When an interaction opens, the right-hand panel shows the customer’s details and their recent history — no looking them up by hand.
Optional Analyze and Summarize buttons can read the conversation and suggest a reply or a tidy summary, so wrap-up is faster. You stay in control — nothing is sent without you.
Everything runs in your web browser — there is nothing to install. You sign in at the start of your shift, set yourself Available so work can be routed to you, and sign out (or go Offline) when you are done. The rest of this manual walks through each part in turn; this chapter just gets you in the door.
The Agent Desktop works best in an up-to-date Chrome, Edge or Firefox. For phone calls your browser will ask once for permission to use your microphone — choose Allow, or you will be able to see calls but not speak on them (covered in Chapter 3).
The very first thing you see is the sign-in card. Until you sign in, the rest of the desktop stays hidden — that is on purpose, so nobody can see customer conversations over your shoulder before you have logged in. Let us learn this manual’s style on the simplest screen in the book: a labelled picture first, then numbered steps, then a worked example.
Type agent.cloudcx.app yourself, or use a bookmark you made — never sign in from a link in an unexpected email or message. Genuine sign-in only ever happens on this address, and the page shows the PROTECTED banner. If anything looks different, stop and tell your team leader.
Here is the whole sign-in, start to finish. It takes about ten seconds once you know your details. Follow the steps in order; the bold phrase at the start of each step is the action, and the rest is the detail.
The desktop remembers you on the same computer and browser for the rest of your shift, so you don’t have to sign in again every time you refresh the page. It will ask you to sign in again after you sign out, on a different computer, or if a lot of time has passed. Always sign out at the end of your shift on a shared machine (see § 1.7).
If the username or password don’t match, a small red message appears at the top of the card and the workspace stays hidden. Two messages are worth knowing:
One of the two doesn’t match. Re-type carefully — watch for Caps Lock and stray spaces. After a few tries, use Forgot password? (§ 1.5).
Your details are right, but the account is switched off or paused. This is not something you can fix yourself — contact your team leader or administrator to re-activate it.
Maya is a new support agent. Her supervisor gave her the username maya.s and a starting password, and told her the desktop is at agent.cloudcx.app. It is 9 a.m. and she is starting her first shift on a fresh laptop.
maya.s; in Password she types her password, then selects Sign in.Result: Maya is signed in and ready for work in under a minute. Had she fat-fingered her password she would have seen “Incorrect username or password” and simply tried again.
Do this with the details your team leader gave you, ideally on the computer you’ll use day to day.
Done when: the full workspace is showing, your name appears top-right, and your status reads Available.
To keep customer data safe, some accounts add a second step after the password — a short, one-time code that only you can get. This is called two-factor authentication (2FA). It is switched off by default, so most agents will never see it; if your account has it on, sign-in simply asks for the code after your password is accepted. There are two kinds, and your account uses one of them.
A free app on your phone (such as Google Authenticator or Microsoft Authenticator) shows a fresh 6-digit code that changes every 30 seconds. You read the current code and type it in. Nothing is sent to you — the app and the system stay in step on their own.
The system emails you a 6-digit code the moment you sign in. Open your inbox, find the message titled “Your CloudCX sign-in code”, and type the number in. The code lasts 10 minutes, then expires.
Either way, the screen looks the same: after you select Sign in, a single box appears asking for the code. Type the six digits and submit again.
Give it a few seconds, then check your Spam or Junk folder. To stop inboxes filling up, the system won’t send a brand-new code more than once a minute — so if you just asked for one, the one already in your inbox still works. The newest code is always the one to use.
These codes are for you alone. No genuine CloudCX person, and no real email, will ever ask you to read out your sign-in code. Only ever type it into the Agent Desktop’s own code box. After a handful of wrong tries a code stops working for safety — just request a fresh one and try again.
It happens to everyone. There is a simple, safe way to set a new one yourself — you do not need to wait for anyone. Selecting Forgot password? on the sign-in card opens the reset page, where you ask for an email link and then choose a new password.
For safety, each reset link works only once and only for about one hour. If you see “This reset link is invalid or has expired,” simply request a fresh one from the reset page and use the newest email. If no email ever arrives, the address may not be the one on your account — ask your team leader to confirm it.
Choose something long but memorable to you, and don’t reuse the password from another website. If your workplace uses a password manager, save it there so you never have to do this again.
Take a breath — the desktop only looks busy. It is really just three columns with a strip of controls across the top, and the same layout stays put all day. Get comfortable with the parts now and every later chapter will feel familiar. The picture below is what you see straight after signing in, with nothing selected yet.
If the Inbox is empty and the middle says No interaction selected, you haven’t done anything wrong — it simply means no work has been routed to you yet. As soon as a call rings or a message arrives, it will pop into the Inbox. Setting yourself Available (Chapter 2) is what tells the system you’re ready to receive it.
When your shift ends, sign out cleanly so no work is routed to an empty chair and nobody can use your session. There is a small sign-out button at the top-right of the desktop, next to your name.
Stepping away for lunch? You don’t have to sign out — just set yourself On Break (Chapter 2). That pauses new work but keeps you logged in, so you’re ready in one click when you’re back. Sign out only at the end of your shift, or on a shared machine.
Throughout this manual you’ll see coloured boxes set apart from the main text. Each one carries a particular kind of advice — learn to recognise them at a glance, because the most useful tips and the most important cautions live inside them.
Helpful background or a “good to know” — it explains how something behaves. Safe to skim; notes never ask you to do anything risky.
A shortcut or a smarter way to do something. Optional, but worth picking up — tips are the little tricks experienced agents use to work faster.
Take care here. The action can affect a live customer or be a nuisance to undo — for example hanging up a call by mistake. Read it fully before you act.
Stop and double-check. This is something serious or hard to take back — like sharing a security code or sending the wrong reply to a customer. Be sure before you continue.
The dashed pink box is your hands-on exercise. Each one gives you a small task to practise and tells you what “done” looks like. Do them as you go — they’re the fastest way to get confident on the desktop.
Every chapter from here follows the same friendly rhythm, so once you’ve done one you know how they all work:
A couple of small conventions help you read quickly: bold means a button or label exactly as it appears on screen (for example Sign in); pink web addresses are pages to visit; keys like Enter are keyboard keys; and cross-references use the section number, e.g. “see § 1.4”, never a page number — printed page numbers shift with your printer and zoom.
Here is the road map for the chapters to come — roughly the order of a real shift.
Setting yourself Available, On Break, Wrap-up or Offline, and a full tour of every part of the workspace.
Answering, muting, holding, transferring and ending phone calls with the on-screen softphone.
Handling WhatsApp, web chat, SMS and social messages — replying, using quick canned replies, and juggling several at once.
Reading and replying to emails, and making the most of the customer details and history on the right.
Closing an interaction neatly — choosing an outcome, adding tags and notes, and the optional AI summary.
Reading your own stats — how many you’ve handled, how quickly — and what they mean.
A five-minute warm-up to make the desktop feel like home. Do it on the computer you’ll use for shifts.
Done when: you can sign in and out without help, name all six parts of the desktop, and you’ve saved the bookmark.
Now that you can get in and out, Chapter 2 shows you how to set your status so work reaches you at the right times — and takes you on a proper tour of every part of the Agent Desktop.
This is your home screen for the whole shift. The agent desktop is the one window where every customer reaches you — phone calls, web chat, WhatsApp, SMS, email and social — and where you reply, look up who they are, and wrap up the work. This chapter walks you around it slowly, naming every button so that nothing on the screen is a mystery.
You do not need to memorise anything yet. Just follow along, and where you see a Try it box, do it on the real screen as you read. By the end you will be able to point at any part of the desktop and say what it does.
The three columns that make up the desktop; how to set whether you are Available for work; how to read your inbox and pick a conversation; the difference between the chat view and the phone view; where to find who the customer is; how the built-in AI Assist helps you; and how to wrap up a conversation when you are done.
You reach the agent desktop in your web browser at agent.cloudcx.app. Sign in with the user name and password your team leader gave you. (If your company uses its own web address, your team leader will tell you what to type instead — the screen looks exactly the same.)
A simple USB or Bluetooth headset makes every call clearer for you and the customer, and keeps your hands free to type notes. Plug it in before you sign in so the browser picks it up.
The whole desktop is laid out the same way all day, so once you know where things live you never have to hunt. Across the top is a thin top bar. Below it are three columns, left to right:
Figure 2.1 shows the desktop with a live chat open. The numbered markers point at the parts we will cover one by one through this chapter.
The middle column adapts to the channel. For a chat, WhatsApp or SMS it shows a message thread. For a phone call it becomes a softphone with a dial-pad and call buttons. For email it shows the email and a reply box. Same place — different tools for the job. We look at each below.
The top bar runs across the very top of the screen. It is small, but it controls the single most important thing about your shift: whether new work is sent to you. Figure 2.2 names each piece.
| State | Dot | New work? | Use it when… |
|---|---|---|---|
| Available | Green | Yes | You are ready — calls and chats will be routed to you. |
| On Break | Amber | No | Lunch, comfort break or a meeting — you are paused. |
| Wrap-up (ACW) | Blue | No | You just finished and need a moment to write notes before the next one. |
| Offline | Grey | No | End of shift, or signed out of the queue. |
If you are not Available, no new calls or chats come to you — even if customers are waiting. Always set yourself Available at the start of your shift, and remember to come back from On Break afterwards.
Open the status menu and select On Break. Notice the dot turn amber and the timer reset. Now set yourself back to Available — you should see the green dot and the SIP status confirm you are ready for calls.
The left column is your inbox: one tidy list of every conversation assigned to you, no matter which channel it came from. A phone call, a WhatsApp message and an email all sit in the same list, each with a small coloured icon so you can tell them apart at a glance.
At the top of the inbox are two helpers. Work-mode tabs switch between your normal Inbox and the outbound Campaign dialer (used only if your team makes outbound calling campaigns). Below them, channel filters let you show just one channel — for example only the chats — when the list gets busy.
The full set of channel filters you may see is: All, Voice, Chat, WhatsApp, SMS, Email, Messenger, Instagram, X and Social. Your team leader decides which channels your team handles, so you may not see all of them.
When several conversations are waiting, the rows tagged wait are the ones a customer is sitting on. Picking those first keeps everyone’s wait time short — and that is what your team is measured on.
Tap the Chat filter and watch the list shrink to only chats. Tap All to bring everything back. Then select any row — the conversation opens in the middle column. You have just picked up your first interaction.
When you open a chat, WhatsApp or SMS conversation, the middle column becomes a familiar messaging view. Their messages sit on the left in light bubbles; your replies sit on the right in dark bubbles. You type at the bottom, and there are quick replies just above the box for things you say all the time.
Let’s answer Aisha’s chat from start to finish.
Internal notes (the dashed amber bubbles) are private to you and your supervisors. They are perfect for “applied a credit” or “customer was upset” — context the next agent will thank you for. Your typed replies, of course, do go to the customer.
For a phone call, the middle column becomes a softphone: a phone built right into your browser, so you make and take calls with your headset — no desk phone needed. You will see the caller, a running call timer, the call buttons, and a dial-pad you can open when you need to type numbers.
| Button | What it does |
|---|---|
| Answer | Picks up an incoming call (green button, shown only while ringing). |
| Decline | Refuses an incoming call so it goes back to the queue. |
| Mute | Turns your microphone off so the caller cannot hear you. Tap again to unmute. |
| Hold | Pauses the call — the caller hears hold music while you check something. |
| Keypad | Opens the number pad to type digits during a call (e.g. an extension or menu option). |
| Transfer | Sends the call to another agent or team. |
| Conference | Brings a third person onto the same call. |
| Video | Starts a video call where supported (a small movable video window appears). |
| Hang up | Ends the call (pink button). |
Mute silences only your microphone — you can still hear the caller, and they keep talking. Hold pauses the whole call and plays hold music to the caller. Use Hold when you step away to look something up; use Mute for a quick cough or a word with a colleague.
With the softphone showing, tap Keypad to slide open the number pad, then tap it again to close it. You don’t need to be on a call — this just shows you where the dial-pad lives for when you do need it.
The right column tells you who the customer is the moment you open their conversation, so you never have to ask “can I take your account number?” when we already know them. It also holds the clever AI Assist helper and your wrap-up form. Figure 2.6 names each card.
A two-second look at the right column — their name, VIP flag and last interaction — lets you open with “Hello again, Aisha, I see you called us a couple of weeks ago…”. Small touches like that make customers feel known.
AI Assist lives in the right column and reads the conversation for you. It cannot send anything to the customer on its own — it only suggests — so you are always in control. It has two buttons:
Reads the conversation and tells you the customer’s mood, the main topics, and a suggested reply you can drop straight into the message box.
Writes a short summary of everything said so far — ideal for a long chat, a transfer, or your wrap-up notes.
AI suggestions are a starting point, not a script. Read every suggested reply, fix anything that isn’t quite right, and make it sound like you. You are responsible for what the customer receives.
When you finish helping a customer, you record how it went in the Wrap-up form at the bottom of the right column. This takes a few seconds and keeps everyone’s records accurate. Pick an outcome, add a tag or two, type a short note, and save.
The outcome choices you will usually see are Resolved, Callback scheduled, Pending customer, No interest and Wrong number. Your team may add a few of its own — if you are unsure which to pick, ask your team leader.
Short on time? Tap Summarize in AI Assist, then paste that summary into the wrap-up notes and tidy it. You get an accurate record in seconds.
With a conversation open, choose an Outcome of Resolved, tap the billing tag, type a one-line note, and select Save. That is a complete wrap-up — you have now used every part of the desktop.
You have toured the whole agent desktop. Carry this map with you:
Now that you know your way around, the next chapters take each task in turn — handling your first chat, taking and making calls, and using AI Assist well — with more worked examples and Try-it exercises.
The telephone is still where most contact-centre conversations happen, and CloudCX turns your browser into a full softphone — no desk phone, no extra app to install. This chapter walks you through a real voice call from start to finish: going Available so calls reach you, the screen-pop that announces an incoming caller, answering and using the on-call controls (mute, hold, keypad), passing a caller to a colleague with a transfer or a conference, hanging up, and finishing with the all-important disposition and wrap-up. We also cover placing your own outbound and campaign calls. Every screen is shown exactly as it appears in your Agent Desktop, with numbered labels, and every task ends with a hands-on Try it exercise.
Everything in this chapter takes place in your Agent Desktop at agent.cloudcx.app, in the centre Voice panel. Voice calls ring through the softphone built into the page, so the only equipment you need is a headset and a quiet room. If you have not signed in or set up your headset yet, do that first (see § 2.1) and return here.
Because the call runs inside your browser, CloudCX needs permission to use your microphone, and you want the caller’s voice in your headset — not on a speaker the rest of the office can hear. Get this right once and you can forget about it.
The most common cause is a blocked microphone. Click the small padlock (or camera/mic) icon in your browser’s address bar, set the microphone to Allow, then reload the page. The Agent Desktop also shows an inline notice in the Voice panel when it cannot reach your microphone — if you see Tap anywhere to enable call audio, just click once anywhere on the page.
Top-centre of the desktop is a small status pill that reads SIP off, connecting, or SIP ready. This is your softphone’s connection to the phone network. You can only take or make calls when it shows SIP ready (a green dot). If it stays on connecting for more than a minute, reload the page; if it still will not connect, tell your team lead — your extension may need re-provisioning.
Calls are handed out by the routing engine (the ACD), and it only sends work to agents whose status is Available. Your status lives in the green pill at the top-left of the desktop, next to the CloudCX logo. Think of it as your “ready” sign: when it is green, you are in the queue and the next caller can ring through to you.
| Status | Colour | New calls? | Use it when… |
|---|---|---|---|
| Available | Green | Yes | You are ready to take the next caller. |
| On Break | Amber | No | You step away — lunch, comfort break, a meeting. |
| Wrap-up (ACW) | Blue | No | You are finishing paperwork right after a call. The desktop puts you here automatically when a call ends (see § 3.7). |
| Offline | Grey | No | You are signed out of the queue at the end of your shift. |
If you stay Available but are not at your desk, the system will route a real customer to you and the call will ring out unanswered. That hurts your team’s answer rate and the customer’s experience. Always drop to On Break before you step away, even for a moment.
1) Confirm the top-centre light reads SIP ready. 2) Click the status pill and choose Available — watch it turn green and the timer start. 3) Now click it again and choose On Break; notice the colour change to amber. 4) Switch back to Available. You have just done the single most important thing an agent does at the start of every shift.
When the routing engine sends you a call, two things happen at once: your headset rings, and a screen-pop card slides in at the top-right of the desktop. The card tells you, before you even answer, who is calling and which queue the call came from — so you can greet the customer the right way. This is the moment to take a breath and read the card.
CloudCX checks the caller’s number against your customer records. If it finds a match, you get the gold ★ matched tag and the person’s name — greet them by name. If there is no match, the card simply shows the phone number, and the right-hand Customer panel will be blank until you look them up. Either way, the call is real and routed to you.
Clicking Decline pushes the customer back into the queue to wait again for the next agent — it does not make the call disappear. Only decline when you genuinely cannot take it (for example, your headset just failed). Repeatedly declining is visible to your supervisor and lengthens the customer’s wait.
When you accept a call, the centre of the screen switches to the Voice panel: the caller’s name and number, a live call timer, a gently moving sound wave, and a row of round control buttons. The same right-hand Customer panel fills with the caller’s record, recent history, and AI Assist. Everything you need is on one screen.
A control that is switched on glows pink and shows its state in the timer line, so you always know where you stand.
Mute = the caller hears nothing (and may think they have been cut off). Hold = the caller hears music and knows you are still there. For anything longer than a couple of seconds, prefer Hold.
Sometimes you have to navigate an automated menu on the customer’s behalf — “press 1 for accounts”. Click Keypad to open the dial-pad; the buttons now send touch-tones down the live call instead of starting a new one. Click Keypad again to close it.
Ask your trainer to place a practice call to your extension. 1) When the screen-pop appears, click Accept. 2) Say hello, then click Mute — ask your trainer to confirm they hear silence — and click it again. 3) Click Hold; your trainer should now hear music. 4) Click Hold again to resume, then leave the call up for the next exercise.
Not every call is yours to finish. When a customer needs a different team or a specialist, you can hand the call over with Transfer, or bring a colleague onto the line with Conference. CloudCX gives you two ways to do this, and choosing the right one is a key agent skill.
You hand the caller straight to another extension or queue without speaking to the receiver first. The caller leaves your screen immediately and rings the destination. Fast, but the receiver gets no warning — best for “you need the Sales queue” situations.
You put the caller on hold, bring the colleague onto the line to brief them, then drop out — so the customer never repeats themselves. In CloudCX you do this with the Conference button (below). It is the courteous choice for anything sensitive.
The Transfer button does a blind transfer. When you click it, a small box asks for the destination — type the colleague’s extension, a queue extension, or a full phone number — and confirm. The caller is sent there at once and your screen clears into wrap-up.
2010), a queue, or a full number.Once you confirm a blind transfer, you are off the call — you cannot pull the caller back. If you are not sure the other team can help, do a warm transfer (next) instead, so you can check before you let go.
The Conference button brings everyone into a shared room where all three of you can hear each other — you, the customer, and the colleague you add. Use it two ways:
If the customer simply needs another team and you are confident that team can help → blind Transfer (fast). If the matter is sensitive, the customer has already explained a lot, or you want to make sure the colleague can actually take it → Conference as a warm transfer (courteous). When in doubt, go warm.
With your practice call still up: 1) Tell the “customer” you are bringing in a colleague. 2) Click Conference and have your trainer join as the second extension. 3) Briefly explain the “issue” to the colleague while all three are connected. 4) Click Hang up — confirm the customer and colleague remain on the line. You have completed a warm transfer.
When the conversation is finished, end the call with the red Hang up button. As a courtesy, let the customer hang up first where you can — it reassures them the call is genuinely complete and there is nothing else they wanted to add.
You do not have to remember to go into Wrap-up — ending a call does it for you. A short confirmation reads “Call ended — wrap-up started”, the right-hand Disposition panel becomes the centre of attention, and a Wrap-up timer begins. Complete the disposition (next section) before you return to Available.
The disposition is your short, structured record of what happened on the call: the outcome, a few tags, and a line of notes. It lives in the lower part of the right-hand Customer panel. Filling it in takes a few seconds and matters enormously — it is how the business knows whether problems are being solved, how the next agent picks up where you left off, and how your own handled-call count is credited.
| Outcome | Pick it when… |
|---|---|
| Resolved | The customer’s issue is fully handled and nothing further is needed. |
| Callback scheduled | You agreed to call the customer back at a set time. |
| Escalated to Tier-3 | You passed it to a higher specialist team to continue. |
| Pending customer | You are waiting on the customer for something (a document, a decision). |
| Sale / upsell | The call resulted in a sale or an added product. |
| No interest | On an outbound or offer call, the customer declined. |
| Wrong number | The number was not the intended person, or a misdial. |
If you click Save without choosing an Outcome, the desktop will prompt you to pick one first — a call with no outcome cannot be properly counted or reported. Never skip the disposition; an empty record is worse than no record, because it hides what really happened.
You are on the Support queue. A returning customer, Sofia Pereira, calls about a double charge on her account. Here is the whole call as you would handle it in CloudCX.
That is one complete, well-handled voice call — from the green status pill to a clean, searchable record on the customer’s history.
End the practice call from § 3.5 with Hang up. In the Disposition panel: 1) set Outcome to Resolved; 2) click the technical tag; 3) type a one-line note such as “Training call — reset password.”; 4) click Save & next and confirm your status returns to Available.
So far the customer called you. You can also call out — either a one-off number using the keypad, or as part of an outbound campaign where the system feeds you a list of people to contact. Outbound work lives in its own Campaign mode, kept separate from your inbox so the two never get tangled.
Switch the left-hand work mode from Inbox to Campaign (the two tabs above the inbox list). Pick a campaign, and the centre shows the next person to call, a Dial button, and — after the call — a disposition form tailored to outbound work.
In a preview campaign you see each lead first and click Dial when you are ready — good when you need a moment to read the account. In an auto-dialer campaign the system dials for you and simply connects you when someone answers; you just keep the Campaign tab open and handle each connected call. The disposition step is the same either way.
After each outbound call you record a result, just like an inbound call — but with codes geared to outreach. Pick an outcome code (sale, callback, no interest, not available, wrong number, do not call, voicemail), add free-text disposition and notes if useful, and — if you promised to ring back — tick Schedule a callback and set the date and time. Click Save & next to record it and pull up the next lead.
If a customer asks not to be contacted again, you must mark the outcome Do not call. This both respects their wishes and keeps your organisation compliant with calling regulations. Never leave such a request un-recorded.
1) Click the Campaign tab and select your training campaign. 2) Read the next lead’s name and number, then click Dial (your trainer plays the customer). 3) Hold a 20-second “offer” conversation and hang up. 4) In the disposition form, set the outcome to callback, tick Schedule a callback, choose a time tomorrow, and click Save & next. Confirm the next lead appears.
When your campaign session is over, click the Inbox tab to return to normal incoming work. Remember your status still controls the queue — set yourself Available for inbound calls, or On Break / Offline if you are stepping away or signing off for the day.
Voice is only half the job. All day, customers also reach you by web chat, WhatsApp, SMS, email and social — and CloudCX brings every one of those into a single screen called the Inbox. In this chapter you will learn to claim a conversation, reply with confidence, save time with quick replies, send and receive files, hand a conversation to a teammate, and close it cleanly so it counts toward your numbers.
Everything here happens in your Agent Desktop at agent.cloudcx.app — the same window you used for calls in Chapter 3. You do not switch apps, tabs, or logins to move between channels. One inbox, one reply box, one wrap-up. If you can send a text message on your phone, you already know most of this.
It simply means every channel lives in one list. A WhatsApp message, a website chat, and an email all appear as cards in the same Inbox, sorted by who is waiting longest. You handle them with the same handful of actions — claim, reply, close — no matter which channel they came from. Voice calls appear here too, but you answer those with the softphone you met in Chapter 3.
The Agent Desktop is split into three columns. The left column is your Inbox (everyone waiting). The middle column is the conversation you are working on right now. The right column is the Customer panel — who they are, AI help, your private notes, and the wrap-up form. You will spend your whole shift moving left-to-right: pick from the Inbox, talk in the middle, finish on the right.
Priya Nair · [email protected] · waiting 0:41
A chat is not a live call — nobody hears you typing and there is no awkward silence. You can take a few seconds to read, check the account, and craft a clear reply. You can even handle two or three chats at once if your team allows it, because customers expect a short pause between messages.
Every conversation card carries a small coloured dot and icon so you can tell at a glance which channel it came from. The colour is the same everywhere in CloudCX, so you will learn it fast. Here is what each one is, and the one thing to remember about each.
| Channel | Colour | What it is | Good to know |
|---|---|---|---|
| Web chat | Blue | The chat bubble on the customer's website or help centre. | Fully live — the customer often watches you type. Reply quickly. |
| Green | Messages from the company's WhatsApp Business number. | Customers can attach photos. Replies are plain text + emoji. | |
| SMS | Amber | Plain text messages to/from a phone number. | Text only — no pictures or files. Keep it short and clear. |
| Violet | A normal email thread with a subject line. | Slower-paced. You reply in full sentences and can attach files. | |
| Social | Pink | Direct messages from Facebook Messenger, Instagram and X. | Friendly, short replies. Treat like chat with a public brand voice. |
The Inbox also shows Voice (pink). Those are phone calls — you answer them with the softphone from Chapter 3, not the reply box. Everything else in the list is a message you type.
Channels are switched on by your administrator. If your company has not connected WhatsApp or Instagram yet, those filters will simply stay empty — that is normal, not a fault. New channels can be added at any time and will start appearing automatically.
Each card in the Inbox tells you everything you need before you even open it.
The wait time pill turns amber, then red, as a customer waits. Always pick the oldest red card first — that is the person who has been waiting longest and is most likely to be frustrated. Your team's targets are based on these wait times.
A new message can arrive two ways. Often the system assigns it straight to you (it picks an available agent automatically) and it lands in your Inbox with an unread badge. Other times a conversation sits in the shared Inbox as open, and you claim it — which simply means "I've got this one." Either way, opening and replying is the same.
When you claim a conversation it becomes yours — your teammates see it is taken so two people never reply to the same customer. When you close it (§4.6) it leaves the active Inbox.
With a trainer playing the customer from a test web-chat widget:
Above the message box is a row of quick replies — ready-made phrases for the things you say most often. One click drops the phrase straight into your message box, where you can add a name or detail before sending. They save you typing the same sentence fifty times a day, and they keep everyone's wording consistent and on-brand.
The quick replies you see change with the channel — friendlier wording with emoji for WhatsApp and social, a bit more formal for SMS and chat. Here are typical sets:
"Thanks for your patience!" · "Could you share a screenshot?" · "I've escalated this for you." · "Is there anything else?" · "Let me check that now."
"Hi! How can I help? 👋" · "Please share a photo." · "Your reference is #…" · "Thanks, all sorted! ✅"
"Reply YES to confirm." · "Your offer is applied." · "Thanks for your message." · "Visit our help center."
"Sorry for the trouble!" · "Please DM us your details." · "We're on it 🙏" · "Thanks for reaching out!"
A quick reply is a starting point, not the whole message. Adding the customer's name and one specific detail turns a generic line into a reply that feels personal — and customers can always tell the difference. Use the AI Analyze button (§4.7) when you want a suggested reply tailored to what they just asked.
Your administrator or team lead manages the quick-reply library for the whole team. If a phrase is missing or out of date, tell your supervisor — agents use them but don't edit the list.
In a test chat, a customer asks "Can you check why my payment failed?"
Sometimes words aren't enough — a customer sends a photo of a damaged product, or you need to send them a receipt. The paperclip (Attach) button next to the message box handles both.
Never send a file that contains another customer's details, and double-check you picked the right file before sending — you can't un-send a message. SMS does not support attachments at all; if a customer on SMS needs a document, ask them for an email address and switch to the email channel, or send a secure link.
Replying is the same everywhere, but each channel has its own personality. A few habits make you look polished on every one.
The customer is on the site right now, watching for your reply. Acknowledge within a few seconds ("Let me check that…") even before you have the full answer, so they know you're there.
People treat WhatsApp like texting a friend. A friendly tone and the odd emoji are welcome. They can send photos — ask for one if it helps ("Could you snap a photo of the label?").
Text only, no pictures, and messages can be capped in length. Keep each reply to one clear idea. Spell out next steps plainly: "Reply YES to confirm your appointment."
Slower-paced and more formal. Use full sentences, keep the subject line, answer every question in one go, and let the signature sign off for you. You can attach files freely.
These are private direct messages, but you're speaking as the brand in public-facing space. Be friendly, brief and positive. If a conversation needs personal details (an order number, an address), it's already a private DM — but never paste card numbers or passwords. Move anything truly sensitive to a secure channel.
Email looks a little different from the chat channels. Instead of a stream of bubbles, you get the subject line, the full message thread, and a dedicated reply box with a Send reply button and your signature attached automatically.
The right-hand Customer panel follows every conversation you open. It shows who the customer is, gives you AI help, holds your private notes, and is where you wrap up. Three parts matter most while you're messaging.
Analyze reads the conversation and gives you the customer's mood, a short summary, and a suggested reply. Summarize writes a tidy recap for your notes. Always read AI text before sending.
A private notepad on the customer. Only agents and supervisors see it — the customer never does. Jot anything the next person should know.
The customer's last few interactions across all channels, so you have instant context without asking them to repeat themselves.
Some questions belong to someone else — a billing dispute, a technical fault, a VIP who needs a team lead. In messaging you don't "blind-transfer" the way you do on a call; instead you hand the conversation off so the right person picks it up, and you leave a note so they're not starting cold.
The Transfer and Conference buttons you met in Chapter 3 are for live phone calls. For chats and messages, handing off means reassigning the conversation (with a note) — the customer simply keeps messaging in the same thread, now answered by the new agent. No call, no hold music.
When the customer's question is answered, finish the conversation properly. A clean close means your work counts correctly in the reports and the next person who meets this customer knows what happened. It takes about thirty seconds.
If you close a conversation and the customer replies again, it simply re-opens in the Inbox — but it's smoother for them if you wait a moment after your final message before closing. When in doubt, ask "Anything else?" first.
Let's put the whole chapter together. It's a busy Tuesday. Meet Aisha, an agent who is Available and has three conversations land almost at once. Follow exactly what she does — this is the rhythm you'll use every day.
Aisha never left one customer staring at silence. She acknowledged fast, used a quick reply to buy a moment, leaned on AI for the slow email, and closed each conversation with the right outcome so the reports stay accurate. That's the whole job — calm, fast, and tidy.
Ask your trainer to send you three test conversations on different channels at the same time. Your goals:
Next up, Chapter 5 takes you outbound — making calls and working campaign lists from the same desktop. Everything you've learned about wrap-up and dispositions carries straight over.
Every time a call rings or a chat lands, CloudCX tells you who you are talking to — their name, company, a private notes pad, and a timeline of every past call and message with your team. That information lives in the Customer panel down the right-hand side of your desktop. This chapter teaches you to read that panel at a glance, look up a customer by phone or email, follow their history across every channel, and keep their details tidy — all without leaving the conversation you are working on.
Everything in this chapter is on the right-hand Customer column of your Agent Desktop at agent.cloudcx.app. It is headed Customer // context and it fills in automatically the moment you open or answer an interaction — you never have to go looking for it.
The Customer panel is your cheat-sheet about the person on the other end. CloudCX keeps a small, friendly address book (a lightweight CRM) behind the scenes. When an interaction arrives, the desktop takes the caller’s phone number or the chatter’s email and quietly matches it to a saved contact — or creates a fresh one if this person is new. You then get four things stacked top-to-bottom, each in its own card:
The profile at the top: a coloured avatar with their initials, their name, the phone/email this interaction came in on, and a VIP ribbon if they are a priority customer.
The CRM record card: company, job title and any extra fields your team tracks (such as account tier or account number).
Recent interactions: a timeline of past calls and messages with your whole team, newest first, colour-coded by channel.
The Internal notes pad: a place to jot things for yourself and your colleagues. The customer never sees these.
Make it a habit: as a call or chat arrives, your eyes go to the Customer panel first. A two-second glance at the name, the VIP ribbon and the last interaction lets you open with “Hi Maria, welcome back — I can see you spoke to us yesterday about your invoice” instead of “Can I take your name?”.
You do not need to understand databases or fill in forms to use any of this. The panel does the looking-up for you; your job is to read it, lean on it during the conversation, and tidy a detail or add a note when it helps the next agent. The rest of this chapter walks each card in turn.
Here is the whole panel as it looks while you are on a live call with a returning customer. Every part is labelled; we will explain each numbered marker underneath, then take the cards one by one in the sections that follow.
When nothing is selected, the profile simply reads “No customer” and “Select an interaction”. That is normal — the panel is just waiting. The instant you open a chat or answer a call, it fills itself in. There is no “load” button to press.
You may wonder how the panel fills itself in. When an interaction arrives, CloudCX takes its contact point — the phone number for a call or SMS, the email for an email, the handle for chat — and looks for a saved contact that matches. If it finds one, you see their full profile. If it doesn’t, it quietly creates a new, blank contact so there is always something to attach your notes and outcome to. This is automatic; you never press a button to make it happen.
For a voice call, the match shows up the instant the phone rings: a card slides in with the caller’s name and number, the queue they came through, and — if CloudCX recognised them — a small green matched contact tag. That tag is your signal that the full profile is already waiting on the right; you will greet a known customer by name.
You don’t need to worry about formatting. CloudCX compares numbers by their digits only, so +1 415 555 0182, 14155550182 and (415) 555-0182 all find the same customer. Spaces, brackets, dashes and the country-code plus sign make no difference.
The matched name tells you who this number/email usually belongs to — not necessarily who is holding the phone right now. For anything sensitive (billing changes, account access), still verify identity per your team’s policy before acting. The panel is a helpful head-start, not a security check.
The CRM record card is the customer’s saved details. It is deliberately small — just enough to help you serve them well. Below is every field you may see and what it means. Most contacts will only have a few of these filled in; blanks simply mean nobody has captured that detail yet.
| Field | What it is | Example |
|---|---|---|
| Name | The person’s full name (shown big in the profile at the top). | Maria Rossi |
| Phone | Their phone number. Stored loosely so any format matches. | +1 415 555 0182 |
| Their email address. | [email protected] | |
| Company | The organisation they belong to. | Vela Logistics |
| Title | Their job title or role. | Operations Lead |
| Tier / custom fields | Extra labels your team tracks, such as account tier or account number. A tier shows as a small coloured pill. | Enterprise |
The little #code in the corner of the card is the record’s reference number. You rarely need it day-to-day, but it is handy when a supervisor asks you to quote the exact record, or when two people share a very similar name.
Name, Company and the VIP ribbon. These shape how you greet and prioritise.
Tier and custom fields. An Enterprise tier may mean different handling or SLAs — follow your team’s playbook.
If this is the customer’s first ever contact, CloudCX creates a contact on the spot with only the
phone number or email it received. The name may be blank and the Company field a dash (—). That is
completely normal. As you learn who they are, you can fill the details in — see § 5.6.
The Recent interactions card is a single, merged timeline of this customer’s past contacts with your whole team — not just with you. Phone calls and every digital channel (chat, WhatsApp, SMS, email, social) are woven together and shown newest first. This is how you avoid making a customer repeat themselves: one look tells you what they last needed and whether it was sorted.
Each row has four parts: a coloured dot for the channel, the title of the interaction, a small status line, and the time it happened. The colour of the dot tells you the channel at a glance:
Take a closer look at three example rows. The numbered markers below explain the parts.
If the top row says WhatsApp · resolved · yesterday, you can open with “I see we sorted your delivery question on WhatsApp yesterday — is this about the same order?”. Customers love not having to start over, and you save handle time.
The timeline stitches together past messages (chat, WhatsApp, SMS, email, social) and past calls that share this customer’s phone or email. Calls are matched by number whether the customer rang in or your team rang out. If a customer has a phone but no email saved, you will only see their phone-based history — add their email (§ 5.6) to pull their message history together with their calls.
Most of the time the panel fills itself in. But sometimes you want to look someone up on purpose — for example a customer emails from one address but rings from a number you don’t recognise, and you want to check it’s the same person. You can search the address book by name, phone or email.
Keeping details accurate helps the next agent and powers the history timeline. To change a detail, click the value in the CRM record card, type the new value, and it saves when you click away. You can also add an internal note at any time.
The CRM record is shared. When you fix a name or company it is saved against the contact for everyone — so make sure you are editing the right person, and only enter details you are confident about. If unsure, jot it in Internal notes instead, where it is clearly a note rather than a fact.
A customer who only ever called will have just their phone on file, so you only see calls in their history. If they mention their email, add it to the CRM record — from then on their emails, chats and WhatsApp threads line up alongside their calls in one timeline.
Let’s walk a complete, everyday situation from start to finish. A call rings in. The screen-pop shows a number you don’t recognise and no matched-contact tag — so CloudCX has no saved customer for it. During the chat the caller mentions she is Maria from Vela Logistics and usually emails you. Here is how you turn a blank panel into a tidy, joined-up customer record.
Maria Rossi, click away. The avatar now reads MR and the panel greets her by name.Vela Logistics and Email to [email protected]. Each saves as you click away.Prefers email follow-ups; verify before billing changes. so the next agent has the context.Result: a caller who arrived as an anonymous number leaves as a complete, named customer whose calls and emails are joined into one history — so the next time she rings, the very first agent greets her by name and sees the whole story.
Notice you never opened a “new contact” form. CloudCX created the contact for you the instant the unknown call arrived; all you did was fill in the blanks. That is the normal flow — serve the customer first, tidy the record as you go.
With a training conversation open (or any live one your supervisor allows), answer these out loud, top to bottom, using only the Customer panel:
Success looks like: a one-sentence summary — “This is Maria, a VIP at Vela Logistics on the Enterprise tier; she last resolved a WhatsApp delivery query yesterday, and prefers email follow-ups.”
Now that you can read the customer, the next step is closing the loop. Chapter 6 — Wrap-up & dispositions shows how the outcome, tags and notes you record at the end of an interaction become the status you see in this very history timeline next time. The AI Analyze and Summarize helpers that sit just above the CRM record are covered in the AI-assist chapter.
This chapter is about the three things that help you finish an interaction well: the AI Assist panel that reads a conversation and offers a sentiment read, a summary and a ready-to-edit reply; the voicemail messages that land when a caller could not reach you; and the short satisfaction surveys (CSAT and NPS) you send a customer afterwards to ask “how did we do?”. We finish with what a great wrap-up looks like — the few seconds of after-call work that make your notes, your scores and your customer’s next experience all better. Everything here is optional polish on top of the basics from the earlier chapters; none of it is hard, and every task has a worked example and a hands-on Try it.
You work entirely inside the Agent Desktop at agent.cloudcx.app. The AI Assist panel and the survey action sit in the right-hand customer context column, next to your wrap-up. Voicemail messages appear as items in your inbox on the left, just like any other conversation. Nothing in this chapter requires you to leave the one screen you already know.
Think of these as three moments around an interaction. During a chat or email, AI Assist helps you understand the customer and reply faster. Instead of a live call, voicemail captures what the caller needed so you can call back prepared. After any interaction, a survey lets the customer score how it went. Here is how they fit together:
A small panel that reads the open conversation and gives you the customer’s mood, a tidy summary, and a draft reply you can insert and edit. Works on text channels — chat, WhatsApp, SMS and email.
When a call cannot be answered, the caller can record a message. It arrives in your inbox with the caller’s number, how long it is, and — if your team has it switched on — a typed transcript you can read at a glance.
A one-question (or short) form sent to the customer after you finish. CSAT asks for a star rating; NPS asks how likely they are to recommend you. Their answers become your team’s quality scores.
The disposition panel where you record the outcome, add tags and write a short note. Good wrap-up is what makes the next agent — and future-you — able to pick up the thread instantly.
AI Assist never sends anything by itself. It only ever suggests — you read it, change what you like, and you press send. The same goes for surveys: a customer’s score is theirs, and the AI summary is just a head-start on your wrap-up note. These tools save you time; they never act for you.
Open any text conversation (a web chat, WhatsApp, SMS or email) and look at the right-hand context column. Below the customer’s profile you will find AI Assist — a dark panel with a small spark icon. It has just two buttons, Analyze and Summarize, and it shows its results right underneath them. The panel reads only the conversation you have open; it does not see other customers or other agents’ chats.
Customer was double-charged for the May plan and asked for a refund. Agent confirmed the duplicate, started the refund and gave a 3–5 day timeline. Customer is satisfied.
Thanks for your patience — I’ve confirmed the duplicate charge and started your refund. You’ll see it back on your card within 3–5 business days. Is there anything else I can help with?
AI Assist reads typed conversations — web chat, WhatsApp, SMS and email. It does not listen to or transcribe live phone calls, so on a voice interaction the panel simply has nothing to analyse. For voice, your notes and the wrap-up panel are how you capture the outcome (§ 6.6).
The most useful button on a busy day is Analyze, because it gives you a draft reply you can send in seconds. The golden rule: always read it before you send it. The draft is a starting point shaped by the conversation — you add the human touch, fix anything that is not quite right, and personalise the details.
Use Summarize when you only need the wrap-up paragraph — for example you have already replied and just want a tidy note for the CRM. Use Analyze when you want the full picture and a draft reply. Summaries are a great way to start your wrap-up note instead of facing a blank box.
Priya picks up a web chat. The customer, Daniel, has typed three messages in a row about being charged twice and is clearly annoyed. Here is how AI Assist helps her turn it around.
On a practice chat or a test conversation (never a live customer for your first go):
Success looks like: a reply that sounds like you (not a robot), an accurate summary in your notes, and a tag that matches the topic.
A suggested reply can occasionally get a detail wrong — a number, a name, or a promise your team can’t keep. You are accountable for every message sent from your seat. Always read the draft, correct anything that is off, and remove any placeholder before you press send. When in doubt, type it yourself.
AI Assist is a feature your administrator switches on for your organisation. If it is not enabled, you will simply not see the Analyze and Summarize buttons — instead the panel shows a short message. That is normal and nothing is broken; you handle the conversation exactly as you would have anyway.
not enablednothing opentry againtoo little textIf you press Analyze twice on the same unchanged conversation, the second result comes back instantly — CloudCX remembers the analysis for a few minutes. As soon as a new message arrives, the next Analyze re-reads the conversation so the summary and reply stay current. Re-run it whenever the conversation has moved on.
When a call can’t be answered — the queue is closed, everyone is busy, or the caller chooses it — the caller can leave a voicemail. Each message is saved with the caller’s number, how long it lasts, and the time it arrived. If your team has turned on transcription, you also get a typed transcript so you can read the gist without listening first. Many teams also forward voicemails to email; if so, you may get an email copy too.
“Hi, this is Daniel Tan, my account number is 4471. I was charged twice for May and I’d like a refund please. You can call me back on this number any time after lunch. Thanks.”
A transcript is typed automatically and can mis-hear names, numbers or accents. Use it to triage quickly, but if a detail matters — an account number, a callback time — play the recording to be sure before you act on it.
A deleted voicemail is gone. Don’t delete a message until you have called the customer back and recorded the outcome. When unsure, Mark as read instead — it clears the unread badge but keeps the message and its recording safe.
Marcus starts his shift and sees one Unread voicemail. The transcript reads: “Hi, it’s Daniel Tan, account 4471, charged twice for May, please call back after lunch.” Marcus opens Daniel’s profile, sees the duplicate charge in the recent interactions, and at 13:30 presses Call back. He greets Daniel by name, confirms the refund is already moving, sets the outcome to Resolved, writes a one-line note, and marks the voicemail read. Total time: under three minutes — because the transcript let him prepare.
Ask your team lead to leave a test message in your mailbox (or use a training mailbox):
Success looks like: you called back prepared, the wrap-up is filled in, and the message is read but not lost.
After you finish helping someone, you can send a short satisfaction survey so the customer can rate the experience. There are two common kinds, and your team will have a ready-made template for each:
A quick star rating, usually 1 to 5. It measures satisfaction with this interaction. The average of everyone’s stars is your team’s CSAT score.
A 0–10 scale asking how likely the customer is to recommend you. It measures loyalty to the brand, not just one chat. It rolls up into a single NPS number for the team.
You don’t build the survey — that’s set up for you. Your job is to send the right template at the right moment, and a unique link is generated for that customer. They open it, answer, and their score flows back into your team’s quality reports automatically.
Your feedback helps us improve. It only takes a few seconds.
4 of 5 — Good
Anything you’d like to add? (optional) Submit feedback →Each survey link is single-use and private to that customer. If they open it after already submitting, they see a polite “thanks, you’ve already answered” message instead of a second form — so a score can’t be counted twice. You don’t need to do anything to enforce this; it’s built in.
Aisha has just helped a customer reset their account over web chat. Before she closes the conversation she types a warm sign-off — “Glad we got that sorted! If you have a moment, I’d really appreciate a quick rating.” — and then sends the CSAT survey on the interaction. The customer taps 5 stars and adds “super fast, thank you”. A minute later that 5 appears in the team’s CSAT report, and the comment is there for her team lead to read. Aisha sets her wrap-up outcome to Resolved and moves on.
Customers are far more likely to rate you if you ask kindly and explain it’s quick. A simple “If you have a few seconds, a quick rating really helps us” just before you send the link lifts your response rate — and your honest scores are what help the whole team improve.
On a test interaction (so a real customer isn’t surveyed):
Success looks like: a link that worked once, a thank-you on the second open, and a 4 visible in reporting.
Send the survey and let the customer answer honestly. Don’t ask for “a 5” or “top marks”, and never fill one in on a customer’s behalf. Surveys only help the team when the scores are real — a genuine 3 tells you more than a coached 5.
Wrap-up — also called after-call work (ACW) — is the short burst right after an interaction ends, when you record what happened. It lives in the Disposition panel at the bottom of the right-hand column. Three quick fields, and a customer’s story is captured cleanly for the next person who picks it up: the outcome, some tags, and a one-line note.
The outcome is how your team measures what actually happened. Pick the one that tells the truth — these are the choices you’ll see:
| Outcome | Use it when… |
|---|---|
| Resolved | The customer’s issue is fully sorted and nothing further is needed. |
| Callback scheduled | You’ve agreed to call the customer back at a set time. |
| Escalated to Tier-3 | You’ve handed it to a specialist team because it’s beyond front-line. |
| Pending customer | You’re waiting on the customer for information or a decision. |
| Sale / upsell | The interaction ended in a sale or an upgrade. |
| No interest | (Outbound) the customer isn’t interested in the offer. |
| Wrong number | You reached the wrong person, or the number isn’t the customer’s. |
A good note answers one question for the next person: “what do I need to know to pick this up?” Keep it short, factual and specific. A few examples:
“Duplicate May charge confirmed; refund of $24.90 started, 3–5 days. Customer happy.” — says what, how much, what next.
“Sorted it.” or “Spoke to customer.” — the next agent learns nothing and has to ask the customer to repeat themselves.
Don’t face a blank box. On a text chat, click Summarize, drop the summary into the notes, then trim it to one or two sentences and add the next step. You get a complete, accurate note in seconds — and your topics double as your tags.
Wrap-up notes are visible to agents and supervisors. Never write a full payment-card number, a password, a one-time code or any other secret into a note — even if the customer read it to you. Record only what the next agent needs to continue safely.
Put the whole chapter together on one practice interaction:
Success looks like: a personalised reply, an accurate note with the right outcome and tags, a submitted survey score, and a tidy inbox.
You now have the full toolkit for handling an interaction end-to-end. The next chapter looks at your own numbers — the presence states, handle times and CSAT/NPS you can see on your topbar — and how your team lead uses them to support you, not to catch you out.
This last chapter has two jobs. First, it gives team leads a gentle tour of the Supervisor Wallboard — the big live screen that shows the whole team at a glance — and the three ways you can quietly help an agent on a live call: Monitor, Whisper and Barge. Second, it is a handy reference for every agent: the real keyboard shortcuts that genuinely speed you up, a short list of phone and chat etiquette, the everyday problems you will hit on your first week (with the quick fix for each), and a plain “ask-me-anything” FAQ and glossary you can flick back to any time.
Sections § 7.1–7.3 are for team leads and supervisors — you reach the wallboard at a different web address (cloudcx.app/supervisor) and need a supervisor login. Sections § 7.4 onward are for everyone. If you are a front-line agent without a supervisor account, you can skip straight to the shortcuts in § 7.4 — nothing before it is needed to do your day-to-day job.
Being a team lead in CloudCX does not mean learning a new, complicated tool. Your own Agent Desktop works exactly as it always did (you can still take calls and chats). On top of that, you get one extra screen — the Supervisor Wallboard — and the ability to step into a live call to coach. That is genuinely all there is to it. Everything you do is read-only watching, plus three friendly “help” buttons; you cannot break a call or delete anything from this screen.
Keep both open in separate browser tabs during a busy shift: glance at the wallboard to see who needs help, then jump back to your own desktop to take the overflow yourself. The wallboard updates on its own — you never press refresh.
If you have a second monitor, leave the wallboard on it full-screen all day. The live counters, the agent tiles and the queue widgets are designed to be read from across the room.
Sign in at cloudcx.app/supervisor with your supervisor username and password and the whole shift appears on one page. Nothing here is a button you have to press to “load” data — the numbers tick up and down by themselves and the little LIVE badge top-right tells you the page is connected. Here is the screen with every region labelled.
Lower down the same page (not shown) you will also find Voice queues (calls waiting and agents available per queue), a Campaign monitor for any outbound dialling, and the Quality scorecards tools for scoring a recorded interaction. Those are deeper supervisor topics; for day-to-day floor-walking the seven regions above are all you need.
Each agent tile carries one coloured pill. These are the same five states an agent picks from their own presence menu (§ 2), so what you see on the wallboard is exactly what they set on their desktop. Learn the colours and you can read the whole floor in a single sweep.
| Pill | Means | What the agent is doing | What you might do |
|---|---|---|---|
| Available | Ready for work | Logged in, routing on, waiting for the next call or chat. | Nothing — this is the healthy state. |
| On call | On a live call | Talking to a customer right now; the timer shows how long. | This is when Monitor / Whisper / Barge light up (§ 7.3). |
| Wrap-up | After-call work (ACW) | Finishing notes and outcome on the call that just ended. | If wrap-ups run long, check they aren’t stuck (§ 7.6). |
| On Break | Paused | On a break — no new work is routed to them. | Fine in moderation; watch how many are on break at once. |
| Offline | Logged out of the queue | Signed out or not taking work; not counted as staffed. | Nudge them to go Available if a queue is building. |
A timer that keeps climbing well past your team’s average handle time usually means the agent is stuck on a hard call. That is your cue to Monitor first (silent), and only then decide whether to Whisper a hint or Barge in to help. Don’t jump straight to Barge — you’d surprise both the agent and the customer.
These are the three little buttons on every agent tile. Think of them as three levels of help, getting more hands-on each time. They only work while the agent is On call — on any other status they sit greyed out, which is your built-in safety net: you can’t accidentally jump into thin air.
Listen silently. You hear the call; neither the agent nor the customer hears you. Use it to assess before you act.
Coach the agent only. You can speak to the agent and they hear you, but the customer does not. Perfect for a quick prompt.
Join the call. Everyone hears you — agent and customer — turning it into a three-way conversation.
The golden rule is simple: Monitor → Whisper → Barge, in that order, escalating only as far as the call actually needs. Most of the time Monitor alone, or Monitor then a quick Whisper, is enough.
Every action shows a small toast. MONITOR started on Ana K. means it worked. If you instead see something like monitor failed or Couldn’t reach the server, the call probably just ended (the agent hung up) or your connection blipped — refresh the wallboard and try the next live call. See § 7.6.
The situation. You glance at the wallboard and notice Ana’s on call timer has reached 06:30 — well over your 4-minute average. You decide to help.
With a colleague on a test call to a queue (never a real customer), practise the full ladder:
Doing this once on a quiet morning means you’ll be calm and confident the first time a real call needs you.
Monitor, Whisper and Barge are coaching tools. Tell your team that live monitoring happens, use it openly and for their benefit, and follow your local recording and privacy rules. Trust is what makes a contact-center team work.
CloudCX is built to be fast with very few keys to remember. The two that matter most are about sending — learn these and you’ll never reach for the mouse mid-conversation again. The rest are everyday browser keys that make any web app quicker.
| Key | Where | What it does |
|---|---|---|
| Enter | Chat message box | Sends the message you’ve typed. The fastest way to reply — type, Enter, repeat. |
| Shift + Enter | Chat message box | Adds a new line without sending — for a two-paragraph reply. Press plain Enter when you’re ready to send. |
| Enter | Dialler (number field) | Places the call to the number you typed, exactly like clicking the green Call button. |
If your messages keep sending half-finished, you’re pressing Enter when you meant Shift + Enter. Build the habit: Shift + Enter for a line break, plain Enter only when the reply is finished.
Because CloudCX runs in your web browser, the usual browser shortcuts work everywhere in it. These few save real time during a shift. On a Mac, swap Ctrl for Cmd.
| Windows | Mac | Does |
|---|---|---|
| Ctrl + F | Cmd + F | Find text on the page — jump to a name in a long conversation list. |
| Ctrl + C / V | Cmd + C / V | Copy / paste — drop an order number into your notes, or a canned reply into chat. |
| Ctrl + + / − | Cmd + + / − | Zoom in / out — make the desktop bigger if text feels small. |
| Tab | Tab | Hop to the next field in a form (e.g. wrap-up) without the mouse. |
| F5 | Cmd + R | Reload the page — the all-purpose fix if something looks stuck (§ 7.6). |
Ctrl + W closes the browser tab — which would drop you out of an active call or chat. If you ever close it by accident, just reopen agent.cloudcx.app and sign back in; your queue and presence are waiting for you.
The tool only gets you halfway; the rest is how you treat the person on the other end. None of this is rocket science — it’s the handful of habits that turn an “okay” agent into one customers ask for by name.
Voice is personal — tone carries everything.
Text loses tone — be warm and clear on purpose.
Turn each blunt line into something warm. (Suggested rewrites underneath — cover them first.)
Almost everything that goes wrong on your first weeks has a one-line fix. Work down this table top to bottom — the first row solves more issues than all the others combined.
| Problem | Likely cause | Quick fix |
|---|---|---|
| Something looks frozen or odd | The page has been open a long time | Reload the page (F5 / Cmd+R) and sign in again if asked. This is the universal first step. |
| No calls or chats are arriving | Your status isn’t Available | Open the presence menu (top-left of your desktop) and set Available. Check the queue filter isn’t hiding work. |
| Customer can’t hear you / you can’t hear them | Headset or browser mic permission | Check the headset is plugged in and selected; allow the browser’s microphone prompt. Reload and re-test. |
| Incoming call doesn’t ring | Browser tab muted, or volume down | Unmute the tab (right-click it), turn up system volume, and keep the Agent Desktop tab open. |
| Chat won’t send | You typed in the wrong box, or lost connection | Click into the message box, type, press Enter. If nothing happens, reload. |
| Stuck in Wrap-up | Outcome not chosen / Save not pressed | Pick an outcome, add tags/notes if needed, press Save. You’ll return to Available. |
| Supervisor: wallboard not updating | The LIVE link dropped | Reload the wallboard. If the badge isn’t green, check your internet, then sign in again. |
| Supervisor: Monitor/Whisper/Barge greyed out | The agent isn’t on a live call | Wait for a pink on call pill — the buttons only work during a live call. |
| Supervisor: “monitor failed” toast | The call just ended, or a blip | The agent likely hung up. Reload and try the next live call. |
| Can’t sign in | Wrong details, or Caps Lock | Re-type carefully, check Caps Lock, use the exact username your admin gave you. Still stuck? See § 7.7. |
When in doubt: Reload the page, Re-check your status is Available, and Reconnect your headset. Those three Rs clear the large majority of day-to-day hiccups before you ever need to call IT.
The questions new agents ask most, answered plainly. If yours isn’t here, ask your team lead — and tell us, so we can add it.
The words you’ll hear on the floor, in plain English. Keep this page handy for your first fortnight.
That’s the whole manual. You now know how to log in, set your status, handle every channel, read the customer panel, wrap up cleanly — and, if you’re a team lead, watch the floor and coach a live call. Come back to any chapter by its number whenever you need a refresher. Welcome to the team.