LogoLogo
Mluvii webLoginAPIDEMO
English
English
  • ABOUT
  • UPDATES MLUVII
    • 2.125
    • 2.124
    • 2.123
    • Archive
      • 2.122
      • 2.121
      • 2.120
      • 2.119
      • 2.118
      • 2.117
      • 2.116
      • 2.115
      • 2.114
      • 2.113
      • 2.112
      • 2.111
      • 2.110
      • 2.109
      • 2.108
      • 2.107
      • 2.106
      • 2.105
      • 2.104
      • 2.103
      • 2.102
      • 2.101
      • 2.100
      • 2.99
      • 2.98
      • 2.97
      • 2.96
      • 2.95
      • 2.94
      • 2.93
      • 2.92
      • 2.91
      • 2.90
      • 2.89
      • 2.88
      • 2.87
      • 2.86
      • 2.85
      • 2.84
      • 2.83
      • 2.82
      • 2.81
      • 2.80
      • 2.79
      • 2.78
      • 2.77
      • 2.76
      • 2.75
      • 2.72
      • 2.71
      • 2.70
      • 2.68
      • 2.67
      • 2.66
      • 2.65
      • 2.64
      • 2.63
      • 2.61
      • 2.60
      • 2.59
      • 2.58
      • 2.57
      • 2.56
      • 2.55
      • 2.54
      • 2.53
      • 2.52
      • 2.51
      • 2.50
      • 2.49
      • 2.48
      • 2.47
      • 2.46
      • 2.45
      • 2.44
      • 2.43
      • 2.42
      • 2.41
      • 2.40
      • 2.39
      • 2.38
      • 2.37
      • 2.36
      • 2.35
      • 2.34
      • 2.33
      • 2.32
      • 2.31
      • 2.30
      • 2.29
      • 2.28
      • 2.27
      • 2.26
      • 2.25
      • 2.24
      • 2.23
      • 2.22
      • 2.21
      • 2.20
      • 2.19
  • LICENSE TYPES
  • FOR OPERATORS
    • Login
    • Workspace
    • Accept client
    • Client interaction
      • WebChat
      • Client tab
      • Videocall
      • Share
      • Templates
      • Browser
      • End Session
      • Hero Cards
      • E-mail
      • Facebook Messenger
      • Apple Messages for Business
      • WhatsApp
      • VKontakte
      • IP Telephony
      • Telephone campaigns
    • Profile
  • FOR ADMINISTRATORS
    • Company management
      • Licences
      • Users
      • External contacts
      • Performance
      • Operator metrics
      • Dashboards
    • Tenant management
      • Contact directory
      • Sessions
      • All e-mails
      • Operators
      • Campaigns
        • Telephone campaign
          • Campaign Contacts
          • Missed Calls
        • WhatsApp campaign
          • Campaign Contacts
      • Settings
        • Groups
          • By operator utilization
          • To whole group (deprecated)
        • External groups
        • Routing
        • Rules
        • WebChat
        • Forms
          • Forms
          • Hero Cards
        • Chatbots
          • API chatbot
          • Microsoft Bot Framework chatbot
        • WhatsApp
          • Registration process
          • Adding a new phone number
          • Eligible Phone Numbers
          • Pricing
          • Template Messages
            • Conversations
          • Whatsapp ecosystem comparison
          • Data security and GDPR
          • Add WhatsApp widget to website
        • Apple Messages for Business
          • Add Apple widget to website
          • Data security and GDPR
        • Facebook Messenger
          • Add Facebook Messenger widget to website
        • VKontakte
        • E-mails
        • IP Telephony
        • Files
        • Templates
        • Routing visualization
        • Application
          • General
        • Blacklist
        • GDPR
  • FOR IT SPECIALISTS
    • Supported widget methods
    • Add WebChat button to website
    • Add Apple widget to website
    • Customization
      • Customized forms
        • Entry forms
          • Basic entry forms
          • Tenant selection forms
        • Feedback form
          • Basic feedback forms
          • Feedback forms with emojis
          • Feedback form with stars
        • Offline forms
      • Parameters
      • Customized Pop-up
      • Customized functions
      • Customized microsite
    • Public API
      • Authentication
      • Swagger
      • Public API FAQ
      • Webhooks
      • Webhooks FAQ
    • WIDGET API
    • Co-browsing
    • Mobile SDK
      • Android
      • iOS
    • Chatbot connection
      • Microsoft Bot Framework
      • API chatbot
        • API chatbot connection
        • Chatbot API-specific activities and events
      • Supported activities and events
      • Tips and Tutorials
    • Realtime statistics
      • Connection to influx database
      • Existing metrics
      • Examples
      • Grafana
    • Connect Office 365 mailbox
    • Connect Gmail mailbox
    • Software architecture
      • Data encryption
    • Telephony
    • Facebook
    • Files
    • WebChat
    • Cookies
    • Desktop Application
  • SECURITY
  • SYSTEM REQUIREMENTS
    • Minimum HW requirements for operators
    • Minimum SW requirements for operators
    • Supported browsers
    • Audio/Video
    • Supported languages
    • Desktop application
    • Minimum server requirements
    • Mobile application
  • HELPDESK
    • Bug Reporting
    • Manuals
      • Delete browser cookies
      • Delete Local and Session Storage
      • Clear cache memory
      • Add timestamps to logs in the browser console
      • Disconnecting inactive tabs in Google Chrome
    • FAQ
    • Keyboard shortcuts
    • Glossary
Powered by GitBook
On this page
  • Assignment Rules
  • Among operators
  • Among groups
  • Example
  • Rule evaluation

Was this helpful?

  1. FOR ADMINISTRATORS
  2. Tenant management
  3. Settings
  4. Groups

By operator utilization

PreviousGroupsNextTo whole group (deprecated)

Last updated 11 months ago

Was this helpful?

Interaction is sequentially routed to operators according to priority setting (see ) until one operator accepts it.

It provides with following features:

  • queue size (a widget changes its status to offline when the queue is full)

  • time for accepting the client in seconds, after which the waiting session is offered to another operator (gradually increasing the number of operators, and every single one has the option to accept the waiting session)

  • the value for the "max. time in queue" parameter determines the time for which the waiting session is routed to the next group of operators (within the defined routing rules). The handoff of the waiting session to the next group of operators happens in the case of full utilization of the group in the first place within the given routing.

  • auto pick-up means instant automatic acceptance of the session without clicking on the "Accept" button.

Auto-accept can be used for sessions and e-mails too.

In the group details, you can specify the conditions for selecting individual operators in the session assignment sequence. You can choose from 5 types of priorities, which you can freely remove, add, or change their order by dragging the priority higher in the list. See the example .

Assignment Rules

Sessions are distributed among or . You can set way how it's done by using various conditions and priorities.

Among operators

The overflow setting can only be set according to the “By operator utilization” distribution setting.

  • Maximum time in the queue - If the client waits in the queue (not assigned to the operator) of the fully occupied group for longer than the defined time, the interaction is routed to the next group in the list (that meets the routing conditions).

  • Maximum time to accept - If the operator does not accept the client at a defined time, the client is routed to another operator within the group. Even after that, the operator selected by the routing, in the beginning, has a chance to accept the client.

If field settings (such as Maximum ACW, Maximum number of clients in the queue, or other) are left empty, for the application it will be the same as an infinite value. For example, if you leave Max. number of clients in a queue without a specific value, customers will be routed to a group without any restrictions.

In the subsection, you can disable/enable individual priority rules as well as reorder them. Rules with lower order will be used only when higher order rules fail to select a single operator.

Priority list

Priority
Description
Editable

Currently assigned client count

Sum off all waiting and accepted sessions/emails

Yes

Today assigned client count

Sum of all sessions/emails that were routed to the operator since today's midnight

Yes

Today accepted client count

Sum of all sessions/email that the operator accepted since today's midnight

Yes

Retain last handler

Prefer the most recently contacted operator (if available)

Yes

Random selection

Operator would be selected randomly. This is always the last rule and cannot be changed

No

Among groups

There 3 main conditions that have to be met:

  • all group operators have no free slots

  • The Time in queue parameter is set

The handoff of a waiting client from Group A to Group B happens under one of the following situations:

  • all operators are busy and the group queue is full

  • all operators are in the "Away" state (such group is unavailable)

  • a group is empty (has no operator)

  • no operator from the group is online (the empty group is skipped)

  • all operators have the particular channel turned off

  • the group is out of business hours

Example

Given the following setting:

  1. Retain the last handler

  2. Currently assigned client count

  3. Today assigned client count

  4. Random selection (default system setting)

Situation:

  • A new client entered the queue.

  • Online operators are: Bob, Alice, and Dan

  • Dan is currently speaking to another client

  • Bob has already resolved another interaction earlier in the morning

  • Alice has not had any clients today yet

Rule evaluation

Rule
Bob
Alice
Dan

Prefer last called operator

0

0

0

Number of currently assigned interactions

0

0

1

Number of assigned interaction today

1

0

1

The new client will be routed to Alice. The first 3 rules were sufficient to select a single operator. The fourth rule was not needed.

the group is full

Assignment Rules
below
operators
groups
queue