Call queueing puts your callers in a waiting queue until the next representative becomes available to answer the call. This feature is automatically available in all non-legacy Gruveo accounts.
Queueing Explained
If all users assigned to a permanent Gruveo link are busy, then any new callers are put on a waiting queue for that link. Once a user becomes available, their device starts ringing with the first call from the queue.
If a Gruveo user has more than one permanent link assigned, their call queue is comprised of the queues for each of their assigned links.
The caller gets shown their position in the queue, updated in real time. If they decide not to wait and hang up, they will still be invited to leave a message (provided that at least one of the users behind the link has the Text Mail feature enabled). Likewise, your operators get to see the number of callers currently in the queue.
Example
To better understand how call queueing works, consider the following scenario.
- Alice and Bob are both assigned the @acme.sales permanent link. Additionally, Bob is assigned the @acme.bob link.
- Caller A calls @acme.sales. Both Alice's and Bob's devices ring with the incoming call. Alice answers it.
- Caller B calls @acme.sales. Since Alice is already on a call with Caller A, only Bob's device rings with Caller B's call. Bob answers that one.
- Caller C calls @acme.sales. Alice and Bob are both busy, so Caller C is put on a waiting queue for @acme.sales. Both Alice and Bob get a message saying that there's now one caller in the queue.
- Caller D calls @acme.bob. Since Bob is busy, Caller D are put on a waiting queue for @acme.bob. Bob's queue is now displaying 2 calls (Caller C and Caller D) and Alice's is displaying one (Caller C).
- Bob ends his call with Caller B. Since Bob is now available, his device starts ringing with call from Caller C on @acme.sales. Bob answers the call. Alice's queue is not displaying any calls now.
- Bob ends his call with Caller C. His device now starts ringing with the call from Caller D on @acme.bob.