--- url: https://docs.codefox.ai/apps/cape/run-the-team.md --- # Run the team This page is the guide for team leads in Cape: watching the team live, helping callers who wait, listening in on calls, handling alerts and reviewing calls afterwards. ## Before you start * You are a **Team lead** in Cape, or you can manage it. **Team** and **Reports** appear in your rail. * To listen in, you have a headset and a microphone, and you are not taking calls in the console yourself. ## Watch the team 1. Open **Team**. The board reads **Live, read every 5 seconds**. 2. Read the figures at the top: **On a call**, **Available**, **Away** (missed calls in a row) and **Offline**. Select a figure to show only those people; select it again for everyone. 3. Read each person's card. It shows their state, such as **Available**, **Ringing**, **On call**, **Wrap-up**, **Away (missed calls)**, **Phone line down** or **Offline**, how long they have been in it, and whether their recording is paused. If the board reads **Updates have stopped**, select **Retry**: the states may be out of date. ## Help a waiting caller Under **Waiting**, each caller shows how long they have waited, the line they called and who the call is being offered to. * **Assign…** offers the caller to one available person. If they do not answer, the caller goes back to everyone. * **Take call** rings the caller on your own console. You must be available there first. * Change the caller's priority with the menu beside them, so they are offered first. ## Listen, whisper or barge On the card of someone on a call: 1. Select **Listen**. You hear the call; nobody hears you. 2. Switch to **Whisper** to talk to your colleague only, or **Barge** to join the call so the caller hears you too. 3. Select **Stop listening** to leave. Your colleague is told that you are listening, unless your managers set the centre to silent listening. A call holds at most three people, and only one lead can coach a call at a time. ## Set someone available or offline * **Set available** brings back someone Cape set to Away after missed calls. * **Force offline** takes someone out of the queue. Type a reason, then select **Confirm**; their console shows the reason. Someone on a call goes offline once the call and its wrap-up end. ## Handle alerts **Alerts** lists what needs a lead, such as missed calls in a row, a caller who may be stuck, a recording that could not be saved or did not start, a recording pause Cape could not confirm or that ran too long, calls Fennec has not taken, and voicemails recovered after an outage. Select **View call** to open the call, and **Acknowledge** once you have dealt with it. ## Reassign callbacks 1. On the **Team** page, find **Callbacks**. 2. Tick the callbacks to move. 3. Under **Reassign selected to**, choose a person or **Team (anyone free)**. 4. Select **Reassign**. ## Review calls 1. Open **Calls**. As a team lead you see every call in the centre. 2. Open a call to play its recording, read the transcript as it plays, read the AI summary, and see the timeline of what happened, including any rule that stopped a call going out. ## Label outcomes without the answer To check how well wrap-up outcomes match what was said: 1. Select **Label outcomes (blind)** on the **Team** page. Cape shows the transcript of a summarised call you did not take, without the outcome the person chose or the AI's suggestion. 2. Under **How did this call end?**, pick the outcome you would choose. 3. Select **Save and next**. Cape shows the next call. ## Troubleshooting ### You’re taking calls in the console. Go offline there to listen in. Go offline in **Console**, then select **Listen** again. ### This call already has three people on it. A call holds three people at most. Wait for someone to leave. ### Someone is already coaching or on this call. Another lead is listening, whispering or barging. Only one can at a time.