A typical Caller ID application involves performing a database query based on a Caller ID number. When the database record is found, the customer’s record is presented on the user’s screen. The data from the unit is read from the serial port, the Caller ID number is extracted, and a database query is performed.

Since the unit is designed to always send Caller ID information no setup toggles have to be defined. If you do not want to monitor outbound calls, you must set the upper case "O" toggle. Also, detailed information (On Hook, Off Hook, and Ring) can be sent by the unit by setting the lower case "d" toggle. The unit can also send an "end of call" record that includes call duration and number of rings before answer. If this information is not required, set the lower case "a" and upper case “S” toggle.

The Caller ID number, by definition, is the phone number of the specific phone line used to originate the call. Many businesses have more than one phone line with each having a separate number. You should make provisions in your software application to look up the same database record for multiple Caller ID numbers. This is typically accomplished by using a cross-reference list for each database record. A new Caller ID number from a existing customer can be added to the cross-reference list by the employee answering the call. Eventually, all numbers from a particular customer will be cross-referenced to the main database record.

This cross-reference list can also be built automatically from the Caller ID name information. Fortunately, the Caller ID name generated by the phone company is based on billing records and spelled the same no matter which phone line is used to originate the call. Therefore, if the Caller ID name is contained in the database, the cross-reference list can be appended automatically.

The employee using the software will want some manual control popping up new database records. An example is an order taker adding notes to a customer’s record after a call is completed. Manual control prevents a new call from changing the screen before they are finished. One method to accomplish this is to display the Caller ID name and number on a small window in the corner of the screen and allow the user to choose when to pop up the new record.

When only call logging is required and reporting will be performed afterwards, the unit can be set to report only "end of call" records (lower case "a" and "s" toggle set). The information reported in the end record contains the same information as the start record and but adds the call duration and the number of rings before answer.

The only instance when the above statement is not true is when the lower case "t" toggle is set. Lower case "t" instructs the unit to capture touch-tones digits after an inbound call has been answered. These digits are placed in the Caller ID name field on the "end of call" record and substitute for the Caller ID name. If your application requires that the Caller ID number, Caller ID name, and inbound touch tones are reported, then the unit must be set to report both "start of call" and "end of call" records. This would require the upper case "A" toggle to be set.

A typical example of this type of application is in the real estate industry. Agents record details for listed properties on a system where potential clients can call in to find out more information. These callers maneuver through voice menus using touch-tones to listen to specifics on various properties. By capturing the Caller ID number, Caller ID name, and the menu choices, the agent can turn potential clients into sales leads.

For this type of application, the unit needs to set to capture "start of call" and "end of call" records as well as touch tones pressed after the call is answered. Set the upper case "A" and the lower case "t" toggles. Both the "start of call" and "end of call" records must be captured when the Caller ID name and touch tone digits dialed are required. These digits are placed in the Caller ID name field on the "end of call" record and substitute for the Caller ID name.

Usually this application does not require monitoring outbound calls, so the upper case "O" toggle would be set.