Aastra OpenAttendant 210 User Guide OpenAttendant 205 - Page 9

OpenAttendant Structure menus simply and clearly. Only use a few menu levels. (We recommend no more than three such levels.) Callers must try to find a "way" through the menus and draw a menu map in their heads. Too many levels may well disorientate them. Avoid any complex structuring of a voice portal's menus. Build the menu levels in a straightforward sequence, one on top of the other. Help callers to get their bearings quickly. Allow the caller to listen to the announcement again (action: "Repeat menu") before moving on to the next menu. Provide the caller with the option to return to the starting point or to go back a menu (actions: "Jump to menu" and "Menu back"). Include confirmation messages at the points of your voice portal where callers could ask themselves whether their last input was correct (e.g. "Your order has now been taken"). Backing Up Voice Portals Backing up a voice portal configuration The voice portal's configuration (the whole system, including its menus, actions and reactions) is saved in the OpenCom 100 / Aastra 800's overall configuration. After you have configured or changed a voice portal, you should save the current configuration in the System: Data Backup menu. Backing up used audio files The audio files you are using in the Voice Portal are saved on the installed memory card (with an Aastra 800 on the hard disk drive). You can save your Voice Portal audio files to a drive or a data medium: either as multiple files or as an archive. The archive contains all the audio files currently stored on the memory card (with an Aastra 800 on the hard disk drive). You can archive the saved files and restore them to the communications system (via the Menu System: Components) at a later stage, so that you have a data backup e. g. in case the memory card needs to be replaced or formatted. Further information on data backup can be found in the OpenCom 100 / Aastra 800 online help. 5