首頁(yè)>>廠商>>IVR系統(tǒng)平臺(tái)廠商>>Pronexus

[英文]測(cè)試你的IVR-關(guān)鍵步驟
Nicholas Doyle 2011/01/26

An important piece of any project plan and development cycle should always be a formal testing process. It’s surprising how often we see this skipped over or skimped on. It’s important to not only test the call flow itself, including all the branches and options, but also unexpected inputs and error conditions, and finally load testing.

We see many IVR systems where the only testing done was a handful of test calls to verify the call flow. Some common issues that should be considered include:

1、What happens if the caller hangs up unexpectedly?

2、What about if the caller enters the wrong number of digits, or the wrong termination digit?

3、What happens if there are no digits entered, how many times does the system retry? If the retries fail, does the system gracefully end the call or transfer to an agent?

4、If the system is using ASR, how does it handle background noise or speakerphone calls?
Is it able to differentiate the responses of callers with different accents?

5、Does the system gracefully handle prompt playback failures or text-to-speech errors?
Finally, especially in IVRs which integrate with other business systems, databases, or web services, it is essential to do proper load testing and determine how the system performs under a large call volume. Do database/web service calls return in a timely fashion? Are your business systems (CRM, etc) negatively impacted by the load from the IVR with a large amount of incoming calls?

6、Proper and thorough testing before putting the IVR system into production can really make the difference between a stable, smooth launch and unexpected outages and frustrated callers down the road.

CTI論壇報(bào)道