From Bright Pattern Documentation
< 3.13:Agent-guide
Revision as of 22:56, 26 August 2016 by Sasha (talk | contribs) (Created new topic from branched topic Documentation:ServicePattern:agent-guide:HowtoMakeYourselfNotReady:3.12)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
• 3.10 • 3.11 • 3.12 • 3.13 • 3.14 • 3.15 • 3.16 • 3.17 • 3.18

Contents

How to Make Yourself Not Ready

During your working session, you may need to make yourself temporarily unavailable to handle interactions, in order, for example, to take a scheduled break, to have a meal, or to attend a meeting. You may be required to indicate a specific reason for becoming unavailable every time you make yourself Not Ready. You can make yourself Not Ready if your current state is either Ready or After Call Work. You can also change reasons for being Not Ready.


To make yourself Not Ready:

  1. Click the User Status Indicator/Selector.
  2. From the drop-down menu, select Not Ready or any specific reason for becoming Not Ready, such as Break or Lunch – the exact set of reasons is specific to your contact center.

You can also press F8, select desired not ready state with the cursor keys and press Enter.


Making yourself Not Ready


Your state changes to Not Ready. You will not receive any service calls while you are in this state. You will have to manually make yourself Ready when you are ready to take service calls again. See How to Make Yourself Ready for more information.


Note that you can request Not Ready to be your next state while you are in the Busy state, i.e., while actively handling an interaction. Your current state will not change, but the system will note your desired next state and will switch you this state after you finish processing of the current interaction. The requested Not Ready state will be displayed as Next under the current state display.


Not Ready state selected as next state


Note: If you have two or more active interactions on your desktop, you will only be switched to the requested Not Ready state after you finish processing all those interactions. However, you will stop receiving new interactions as soon as you request Not Ready.


< Previous | Next >
< Previous | Next >