- Newest
- Most votes
- Most comments
It would be nice if AWS pushed an update before the deprecation, but the good thing is that you have all the source code and can make the necessary updates to support the newer versions. For us, it's been just manually updating the affected Lambdas.
david
For the IVR, I'm not really sure what your plans are with it. If you are just transcribing the audio related to a call, it's better to just use contact lens through your contact flow. It is though a heavy cost (speaking from a small dev shop perspective); so you are going to have to see if it's worth it. https://docs.aws.amazon.com/connect/latest/adminguide/contact-lens.html
I believe the voicemail stack is on github and does contain node versions(16) that are not deprecated. You can use the provided deployment folder they have to update the voicemail stack. You do this by essentially putting all of the templates in S3 then calling the master template within the stack that contains the voicemail. https://github.com/amazon-connect/voicemail-for-amazon-connect.
I'm unclear how you would update salesForce as I haven't dealt with that solution. Most of our planned integrations (at least my company) have moved away from these solutions and developed our own way of doing it.
If you feel like you are overwhelm from doing this, it might be best to reach out to an amazon connect partner and use their custom solutions for these types of things. https://aws.amazon.com/connect/partners/ I believe most of them offer some type of voicemail implementation as well as a portal for handling voicemail. And other features as well.
Relevant content
- Accepted Answerasked 2 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a month ago