A Top-Five U.S. Bank: Large Header, Small Body Lists

There are also "large header, small body" list items. For these, it's often better to just broadcast the list to callers and let them interrupt the system when they've found the item they want. Although this forces callers to be paced by the system (rather than allowing them to pace the interaction themselves ), this technique can be useful if interesting information is contained in that short description.

For example, a typical banking application might read out a list of transactions to callers, allowing them to interrupt when they want more information. In this situation, the preview information is the bulk of what most callers want to know, as in the following example.

SYSTEM:	OK, I've got all your recent transactions for the past 60 days, ordered newest first. If you want me to stop reading them say "I'm done," and if you want to find out more about one of them say "Describe it." Here goes: An ATM withdrawal, in the amount of $100, was made on July 26th. An automatic withdrawal in the amount of $243.35 was made on July 21st. An ATM withdrawal in the amount of $60 was made on July 12th. A ”
CALLER :	(Barges in) Describe it.
SYSTEM:	OK. A withdrawal in the amount of $60 was made from a non “U. S. savings bank, located at <text-to-speech engine reads: "One Financial Center, Boston, Mass.">. The next transaction .

In this example, the caller gets the bulk of the information in the list item, but has the option to get more information by simply saying a phrase.