Workaround for Maximum contacts in queue limit

0

Hi,

We have implemented Service Voice with Amazon Connect and hit a snag when queue limit reaches 9 (Maximum contacts in queue limit for our instance) and call disconnects for all the other incoming callers with what aws calls is a reorder tone. Has anyone encountered this situation before? We do not want the call to get disconnected, rather prompt caller with a message that all the agents are busy. Also, does AWS increase the service quotas to higher numbers so this is not an issue? Any inputs and help is deeply appreciated.

3 Answers
0

You're correct that Amazon Connect, like most AWS services, has quotas in place that can be adjusted. The Administration Guide has information on quotas and how to request an increase; see https://docs.aws.amazon.com/connect/latest/adminguide/amazon-connect-service-limits.html for details. ('Concurrent active calls per instance' is the relevant quota here.) Note that the queue limit for an individual queue can be set lower than this value, so you can choose to handle that situation in your flows via the 'At capacity' branch of the 'Transfer to queue' block.

AWS
answered a year ago
  • Thank you for your response. I have been trying to poke around 'Route based on Queue Capacity' and is trying to figure out where does the transfer to queue block needs to be added. Does it need to be at the beginning of the first IVR?

  • The transfer to queue block will place the contact into queue. It's not usually at the beginning of the IVR as you'd typically want to play an initial message, check hours of operation, get input from the caller etc. You need to set the working queue before using a transfer to queue block.

    If you'd like some more general information, a good starting point is the workshop at https://catalog.workshops.aws/amazon-connect-getting-started/en-US. (The agent experience is different compared to Service Cloud Voice but the configuration interface and concepts still apply.) This also includes links to other training materials.

0

Hi,

You are right on the reorder tone. As per the documentation [1], "Incoming calls: The next incoming call gets a reorder tone (also known as a fast busy tone), which indicates no transmission path to the called number is available".

I think what you are looking for is in the same page as well [2] where you can define the maximum number in a queue. You can then define a routing for when the queue is full [3].

Note: By default you cannot set Maximum contacts in the queue to be greater than your Concurrent calls per instance service quota. For information about default service quotas and how to request an increase, see Amazon Connect service quotas [4].

[1] https://docs.aws.amazon.com/connect/latest/adminguide/set-maximum-queue-limit.html#when-queue-full

[2] https://docs.aws.amazon.com/connect/latest/adminguide/set-maximum-queue-limit.html#cap-queue

[3] https://docs.aws.amazon.com/connect/latest/adminguide/route-based-on-queue-capacity.html

[4] https://github.com/awsdocs/amazon-connect-admin-guide/blob/master/doc_source/amazon-connect-service-limits.md

profile pictureAWS
EXPERT
answered a year ago
0

For Service Cloud Voice, 10 is the default. Which you will need to raise per documentation from SF SCV as well.

https://help.salesforce.com/s/articleView?id=sf.voice_setup_aws_service_quotas.htm&type=5

here are other limits in the page, please increase for all of them as you need them in product. The default limits are for testing environments usually

profile pictureAWS
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions