Over time, they also wanted to migrate from Nuance to Lex, as well, but had competing business priorities. While we initially suggested they move to Amazon Connect, the company was not interested in migrating their contact center at the time due to business constraints. As this is an interesting enterprise calling scenario, I wanted to share how we solved the customer's problem. This on-premises contact center was a combination of Avaya and Microsoft Teams. If payment was successfully received from the customer, but the customer required additional assistance, or if the customer failed to pay their invoice, the customer needed to further route the call to an on-premises contact center with SIP. Based on the customer record, if the customer was past due on their account, they wanted to route the caller to a third party interactive voice response (IVR) system with the Session Initiation Protocol (SIP). The service would first use the customer's caller ID to look up a customer record in RDS. When their customer called the number, they needed a service to dynamically route the call based on customer data. The customer wanted to provide a telephone number to their customers. The use case was simple, yet powerful, and I could not wait to share it with you. The call routing rules were based on a Microsoft SQL Server database stored in RDS. The customer had a unique use case that required dynamic call routing on the PSTN. About a week ago, I had an exciting customer call. I want to share an exciting customer workload that my colleagues and I worked on. These Lambdas can be isolated to a VPC, ensuring that sensitive customer data never leaves your AWS account or VPC. Rather builders just need to know how to write a Lambda in Python or JavaScript and they can dynamically route calls based on business logic that delivers an ideal customer experience. Builders are not required to understand the intricacies of SIP, the public telephone network, or arcane communication platforms provided by old guard communication platform vendors. There is no capital expenditures or complicated equipment to setup. Builders pay by the minute to use our programmable telephony APIs ( SIP Media Application). Customers can build intelligent routing and menus on Voice Connector by creating a SIP Media Application with Lambda. Voice Connector provides connectivity to the public telephone network. The SDK enables a broader set of communication workloads, including the PSTN with Voice Connector. *Except as otherwise noted, our prices are exclusive of applicable taxes and duties.With customers like Blackboard, Slack, and Salesforce, it is easy to assume the Amazon Chime SDK is about building WebRTC based audio and video apps. In this example the cost for Amazon Chime Pro and Business Calling is:Ģ0 users x $3 per day x 5 days per month = $300 per monthġ0 users x $3 per day x 3 days per month = $90 per monthġ0 users x $3 per day x 1 day per month = $30 per monthĪmazon Chime Dial-in US Toll Free = $119.10ġ0,000 minutes x $0.011910 per minute = $119.10Īmazon Chime Business Calling (with text and both inbound and outbound calling features enabled) = $381.16 Users send 10,000 outbound, 7,500 inbound text messages, they receive inbound calls for a total of 11,100 inbound minutes and the make outbound calls for a total of 22,200 outbound minutes all within the US. Using business calling the company provides a business phone number, for all 100 employees. The company uses 10,000 toll free dial in minutes per month for their meetings. There are three types of users in this group, one that hosts daily meetings, one that occasionally (1-3 days per month) hosts meetings and users who do not schedule or host meetings. Consider a company of 100 employees that needs a solution which will allow users to communicate with internal and external colleagues.
0 Comments
Leave a Reply. |