1 / 7

Five Key Pitfalls to Avoid When Building a Speech Application

In this insightful guide, Michael Perry, Director of Voice/IVR Solutions at Avaya, outlines five critical mistakes to avoid when developing a speech application. He emphasizes the importance of effective planning and stakeholder agreements, the pitfalls of porting applications without evaluating business processes, the necessity of comprehensive testing beyond unit tests, careful localization practices, and understanding the importance of training for ongoing support. By addressing these areas, you can streamline your development process and enhance the user experience.

gaius
Download Presentation

Five Key Pitfalls to Avoid When Building a Speech Application

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Five Things to avoid when building a speech application Michael Perry, Director Voice/IVR Solutions - AVAYA

  2. #1 Plan the work / work the plan • What are the success metrics? • Internal agreement with stakeholders / external agreement with vendors • How are you going to measure? • At launch • 30 days post launch • Ongoing

  3. #2 Don’t port applications • Good luck with that business case…. • Where is the payback? • Use this as an opportunity to refresh the business process, not the technology!

  4. #3 Unit Testing is enough….right? • Test all applications at load • If you don’t have a Hammer, use a 3rd party service

  5. # 4 Press dos for Spanish • Approach localization the same way you would native languages • Use native speakers to validate where possible • Don’t use 5 words when 3 will work

  6. # 5 Training….who needs it? • Don’t choose between a great design and an application you can’t support • Make self maintenance a goal • Always get the application source code

  7. Contact Michael Perry mperry@avaya.com 303-538-1219 Thank you

More Related