Replies: 1 comment
-
I'm not sure if this is exactly your situation, but it may give you some food for thought. In our setup, we have full DID numbers for each of our users, but refer to the last 4 digits as extensions. We point all of the numbers to a call flow that runs a Lambda script and chops the last 4 digits and determines the user or queue to transfer to. I have also been practicing a migration path on our test environment going from the old Voicemail for Connect to the new VMX3. I have been playing with two methods: DynamoDB and Tags. Tags
The positive: is this is very easy to manage. You can add the extensions within the Connect portal. DynamoDB
The positive: if you build an index on the agentExtension, the lookups will be way faster than tags. I'll attach a sample Lambda function for Tags, but you'll have to let me know if any interest in DynamoDB. Or, have ChatGPT come up with one (it's pretty good at it). Once you figure out the agentLogin from the extension, set the working queue dynamically to that agent, along with the rest of the VMX3 variables, then invoke the VMX3 module.
|
Beta Was this translation helpful? Give feedback.
-
Hey everyone!
I'm in the process of setting up an Amazon Connect instance for work. Previously, we used an older version that supported extension numbers, which are crucial to our workflow.
We used to use the one prior to these, however, the previous setup used Node.js 16, but I needed to upgrade to Node.js 20, and now everything has stopped working due to this, so I'm looking into this as an alternative.
Does anyone know if the latest version supports extension numbers? Or does anyone have suggestions for getting extension numbers working with this setup?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions