Version 1.0 - Updated October 30th, 2006

Version 8.2 plans for Intelec and I-Tel

This is the second update to Version 8.0 and we continue to add functionality based on the database changes introduced in Version 8. Following are some of the changes we have planned. We expect a significant percentage of the following to be in Version 8.2. Based on our analysis, we may deliver some of the changes in a later release. Our target date for general release of Version 8.2 of Intelec is March 2007.


Hardware and operating system requirements

• Your iSeries or AS/400 must be at V5R3 of the IBM operating system.
  
• Memory/ Storage – This update will not take any significant disk space.

Intelec software

• You must be on Version 7.2 or a later version of Intelec.
  

Preprocessing required

As with other releases we do not expect you to have to "prepare" for the update other than for reviewing the documentation of the changes.

Backups required

You would be expected to have a recent backup of the Intelec data and programs. We will be asking you to take a backup of the data prior to installing the update.

Following are the proposed changes.

Bankruptcy

There will be changes to searching and displaying information at the account level.

System Controls

• There will be a new option at the description code level to remove a group of description codes
• At client level, allow commission rate to be increased (using fee code or client setup) if an address is changed. A change of address would be defined as a change of the street address (1st part of the text), city, state or zip code.
  

Data base issues

• Update Tab+ logic when phone numbers are added (check all programs).
• Add medical database changes
• Use 8.0 changes to design compliance changes

Smart Codes

• For the duplication option, we will add a "Same group" option
• On the X-logic, we check for the existence of a phone. That will be modified to include cell phone.
• At the linked accounts level, we will allow you to check for any phone (including cell) and specifically, home, work or cell phone.
• In the case where a Smart Code is disabled, we will provide a method of sending the message to one or more additional users other than INTELOPR.
• We will provide an option to look at age of oldest open account.
• Smart codes needed - add a "date within" feature
• Actions - allow key actions at on the action line
• Option to remove a cell phone number
• Picture of Smart Code before and after an update
• Add to decision-making
  • Has credit card information?
  • Skip tracing data?
  • Attorney?
  • Legal information (F6)?
  • Cosigners?
  • Bankruptcy?
• Show page number on Smart Code screens
• Ability to apply a Smart Code when a collector views an account that they are not responsible for
• Ability to apply a Smart Code when a collector views an account and does not do anything (in addition to the account viewed note)
• For smart codes applied by the system, make sure the area that applied the smart code can be determined
• Smart code decision made, but no note added? Show the decision made in audit notes
• Smart codes to display a user-defined window (e.g. full legal, additional contacts or skip tracing screens)
• Multiple smart codes or audit option for Smart Codes - Allow a date and time when Smart Codes will be applied
• We will provide an option to apply a Smart Codes to a file of case numbers (Company, case number, Smart Code to apply)
• Multiple Smart Code Simulation - Give option to list the accounts that will be selected and processed, along with as much detail on decisions that will be made.
  

Management features

• Add support for up to 6 Smart Code Series. Allow use from client master and Smart Codes.
• Comprehensive, on-line view of collector productivity including productivity and payment information
• Special menus - option for user to set up menus and select any options on those menus, later associating a menu with a User ID or group profile
• We will look at how we can send a message to a manager if a collector is on the system and has not done anything (maybe has been on the same account) for more than xx minutes.
• Scripting
  • Presently, we can not apply Smart Codes (function keys related to Smart Codes) from rule-based scripting. Adding this feature will be analyzed.
  • Develop options to allow scripts to be displayed based on the script that was last displayed (daisy-chaining of scripts)
• Develop options to allow a user to select standard (or custom) reports to be scheduled during nightly processing, with the required parameters being set up in a system control file.
• Security
  • Presently when a user is not allowed to access an account, the summary information can be displayed. We will add options to display no information, but to say that the account may exist but that the user is not allowed to display the information. We will also have option to only display the case number and name
  • Expanded field level security to limit access to fields or groups of fields (information groups) on the account detail screens. We will refer to these options as security profiles.
  • We will allow a security profile to be tied to a client or user.
  • We will allow you to set up a date range and a temporary security profile to be used for a specific individual or client
  • Allow and iSeries output queue to be defined at the User ID level
  • Develop a user activity log (menu options accessed by date and time)
  • Introduce customized menu option security at User ID or security profile level
• Settlements
  • Include additional balances types (include all reportable balances) in settlement
  • Offers across client numbers (if linked accounts is across clients) – There was a discussion about allowing multiple settlements across a linked group. There are no plans to make this change. You can set up SIF's at the individual account level, or for all of the accounts in a linked group (It was assumed that in this case you would link accounts based on the same client group or client code.) If you link across clients, it will be necessary to unlink the accounts or use a single settlement for all of the accounts (usually with a manually entered settlement percentage since different clients will be involved).
  • Allow collectors to see Settlement Analysis
• Special transfers
  • Add client group
  • Add collector group code
  • Add Internal & External Score
  • Add Number of attempts
  • Add number of contacts
• There was a discussion of the need to group clients (similar to collector group code) to group different clients together like medical clients, say by zip code. This can be accomplished using the consolidation options at the client level. If this is not satisfactory, we can look at other options at the client level.
• Add the "Process Log" as a menu item
• Develop set of compliance rules to be enforced by the system. E.g. do not call home or work number unless xx days have passed since the last contact (maintained at the state level). These decisions will be made based on feedback from our clients.

Payment processing

• Payment entry - Security to stop posting, allowing only entry and edit.
• Payment reversals - Options to automatically omit the reversal and original transaction from the statements
• Option to force a deposit total to be entered and to cancel job if calculated amount does not match
• Option to define a "Original posting date" and to store that and use it for a close date
• Option to stop a payment from being posted with a prior date (before last statement ending date)
• Overpayments - define logic at client level (Whether we report or do not)
• Stop a user from entering balance adjustments
• Paid directs (Payment Codes 11 and 31) – Option to not give collector credit for payment until the agency's client has paid invoice. Similar to holding check before appearing on statements. This will be analyzed.
• Allow split commission to be defied at time of payment entry
• Options to permit collector credit only
  • If positive contact has been made
  • If any contact has been made within xx days
  • If xx number of attempts were made within yy number of days
• Analyze option to bill the client for credit card fees using, say payment code 54
• Analyze option to bill debtor for credit card fees. How will that be tracked and accounted for? Review for direct checks too.
• Develop an optional 2nd level of the open-item receivables system - storing the details of each invoice (individual transactions) and allowing payments to be applied to each item.
• Options to charge a bad check fee based on debtor state (Add a fee to a balance type for Type 21 transactions)
  

Account list for audit

• Add account status code
• Legal/pre-legal - include or omit
• Smart code - Needed, not needed?
• Default to interactive option
• Omit follow-up's
• Cell phone option
• Show company name on screen
• Option to select linked balances. If this option was selected, we would look at all of the linked accounts regardless of client or collector. We would also want to make sure that only one account was selected per debtor for the list
• Add "On Contact Series" to selections
• Add "On Smart Code Series" to selections
• Add option to look for a Smart code that was applied
• Add option to select a split collector code
  

Reports

• There will be changes to store active amounts on the placement history and to re-define "active" numbers
• Client A/R inquiry - add a date range option
• Add salesman code selection to client analysis reports
• Management Menu (14 – 1 - 8) Quick View option - Add a column that says minutes since last Smart Code was applied. On he same option, if a collector has 2 sessions the statistics many not be computing correctly. We will review this.
• Post dated Check Inquiry by client and owner (2 – 7 – 12) – Add column to show potential commission.
• On the placement history by client type, allow the client type to be selected
  

Working accounts

• Allow users to disable the automatic credit card option for payment arrangements
• Add fax and e-mail address to attorney screen and possibly F6 screen
• Additional phone numbers in Tab+ window
  • Validate the Tab+ phone codes is user is on I-Tel. Do not allow numbers to be entered as the phone code.
  • Option to select / sort by phone code for Tab+ phone information
  • When an account is displayed, if there is no phone number and there is Tab+ data, bring the information into the account
  • System control option to indicate that existence of good numbers with a specific phone code should display the Tab+ window automatically
• Add a warning window for attorney and credit card deletion
• Add notes for changes to ACat, QCat and Account Status code
• Show case number notes inquiry
• Stop collector from adding notes from the special notes screen (F9, F11, F6)
• The option to keep a list of bad addresses was discussed. This will be analyzed. The challenge is to know when an address is determined as being bad, versus when it was changed because there may have been an incorrect spelling within the address.

I-Tel enhancements

• The following were discussed at the User Conference. While all of the changes may not be in Version 8.2, we will commit to getting them into the product.
• Queue selection – We will review the ability change a campaign from predictive to agentless, without having the need to set up separate names for the campaigns.
• Beep Detection – We talked about controlling the length of time before AMD starts playing a message. (We already have some control of this but will do more research)
• Campaigns based on right party contact (RPC) number. In Version 8.1, you can define a RPC at the smart code level. We keep track of that information at the account level. We could create a campaign based on RPC's - we will analyze this area. It is likely that this will be an option within the queue consolidation features.
• Ability to route an inbound call the the owner/worker on the account (intelligent routing). In the longer term, we expect to provide features that will allow inbound calls to be routed based on many options e.g. Client, balance, scores, existence of a P/Arrangement, last contact date, last worked date etc.
• Campaign Analysis – Presently, there are many reports based on the campaign (Promises, direct checks, credit cards etc.) . We will provide the same analysis based on the time (hour) of day. (promises etc.) allowing users to obtain business intelligence about best times to call.
• We discussed options that would analyze a campaign in real time, list the details and allow you go to the audit screen for those accounts on the campaign.
• Status viewer - We will work towards displaying that information from within Intelec.
• We would like to have an option that warns a collector that they have been on a call for xx minutes and to set a time limit for the length of a call.
• We talked about the need to flag cell phone as "do not call" (permission denied). This can be handled by removing the cell phone number from the account. It would be stored in the system as a "bad number'.
• We discussed the possibility of creating a database of cell phone exchanges. This may or may not be possible.
• Queue consolidation
  • Option to only select accounts with phones
  • Set up days of the week on which the options should be run
• For call recording, we talked about making it easier to find an inbound call.

Other areas

• Letters
  • show reason for failed letter in audit notes
  • show letter translation in audit notes
  • Letters to multiple cosigners. Analyze return mail options.
  • Apply smart code if a letter fails
  • Analyze the printing of attorney name on letters
  • Allow once per account - look at all the letter history
  • Presently, letter text is set up within Intelec. We will give you an option to create that text (with merge codes) in a word document and upload that into Intelec.
• Credit card report - display a window for option being run
• Commercial accounts - enhance the display and printing of names
• Skip tracing - follow system parameters to audit phone number changes from zero to value
• Collector inquiry - sort by collector, positioning options and selections (e.g. reporting group)
• Add a menu option to access the sales module (Presently done by using "SA" from any menu)
• We will document change of client address in client notes, if this is not presently being done
• Provide access to the CPT4/ICD-9 codes from the 1500/UB92 screen, when a user is accessing the codes

© Quantrax Corporation, Inc. Please sent comments to ranjand@quantrax.com