In a continuation to the previous articles of Dynamic VoiceXML and PHP in entreprise, there is many small points that I wanted to add to show what was missing on this application, what could we optimize etc.
Certainly this example was carried out just to illustrate a more complex example of VoiceXML application development with database interaction, but you notice well that one can better do.
Database error messages :
The first point that came in mind is error messages, and the line :
Could be replaced with a voice message indicating this error. The application in this case will read the error message to the enduser and will tell him that there was an error in database, he can try later, then hangs up.
Service without content
When a service is added and the administration didn’t add any content this service should not be listed at all since the beginning or could be listed as an announce of a new service coming soon. This will depend from the application and how we decide to implement it. So it will be great if we can manage this also in the code.
Database choice
The system will be able to possibly run on other database types, or on different databases. In this case it is enough to personalize the TO address of each menu on the level of the navigation form.
Conclusion
In this part we’ve just enumerated some enhancement of the application itself, there is more things that we can do of course. I’ll try to answer to these features in the next articles and talk about testing VoiceXML IVR applications, how to debug code, … Comments are welcome.
