© Quantrax Corporation, Inc.
 Updated - July 20, 2008

We are issuing an update to Version 8.2. This is the first part (the smaller part) of the changes that were to be a part of Version 8.3, which is scheduled to be released in the 2nd quarter of 2008. This update includes several changes that add new functionality and enhance the system. Minor problems identified in prior versions have been corrected and some may not have been documented. Please review the documentation carefully. There are some important operational changes.


  • Phonetic search - We have a new option to search for a debtor! We have added a "phonetic search". All you have to do is key in what the debtor's name sounds like (this only works with debtor name) and the system should show you possible names, regardless of the way you spelled the search name. As an example, keying in HOLYFIELD should being up HOLLIFIELD, HOLIFIELD and HOLLYFIELD! You initiate the new phonetic search by selecting option 2 (name search), entering the name in the search field and then pressing F3 (Sounds like).

    You can also use the normal name search and press F3 AFTER the summary list is displayed on the next screen.

    Here is an example. We searched for HOLYFIELD and got the following.

    Now we use F3 - Sounds like, and get the following! Amazing, isn't it?

    And how does it work? We utilize a very old invention dating back to 1918, that "allows us to index information by how it sounds rather than how it is spelled".

  • User-defined windows - When the Tab-Q option is taken, and user defined windows is selected, if there is data on only one window that code will be filled in the selection field.

  • Linked accounts summary (F5) - If information is changed on an account, the information on the linked does not always change (done for best system performance). There is a new "Refresh" option - You can use F10 to update the information on the screen.
  • Bad numbers in Tab + window - There were some problems with numbers not being updated with the lower case code in the Tab + window. These issues have been addressed.

  • Non-linear arrangements -
    • If a user has access to the area of payments (not the menu), we will allow them to update a non-linear arrangement (e.g. add another payment).
    • We have added a feature similar to direct checks, where you can set up a series of payments. In the 2nd installment area, if you enter a number in the second check date and leave the amount blank, the system will fill up the screen with that number of payments, with the due date calculated based on monthly payments! As with direct checks, the specified number of additional payments is added to the screen. You may ask why this was required for "non-linear" arrangements, whose payments may not be equal in value or at regular intervals. Some companies use non-linear arrangements for all arrangements, for consistency. You would also use the non-linear option for settlements.

  • Changes to account detail screen - We have some very exciting changes!
    • When changing SS#, the recent changes to mask the number did not allow you to change the number in the old manner. This has been addressed. You can key a new number in the format XXX-XX-XXXX or enter a new number XXXXXXXXX in the first 9 positions. (You can use the field exit key when entering the SS# in this manner)

    • What about more ways to help collectors work faster? How about navigating those screens without using function keys? You can now use the Smart Code field to call up the screens that are used to work an account. For function keys,, simply enter the number in the Smart Code field and press ENTER. As an example, 9 ENTER will display the payment arrangements screen! The following codes are also available.
      • AU-Audit notes
      • BK-Bankruptcy search
      • CC-Credit cards
      • NO-Old notes screen (alternate format)
      • UD-User defined windows
      • Uxx, where xx is a user defined window code - Go directly to that window if it exists

    • What about automatically taking users to account-related screens based on a Smart Code? That is now possible. Please check "Smart Codes and knowledge base" for these changes. At the Smart Code level, you can say that a specific screen (e.g. skip tracing, additional contacts, additional information) should be displayed when the Smart Code is used. The user can also be taken to a specific user-defined window, the Tab+, Tab-Q or Tab-* based on a Smart Code. These options add tremendous power to your ability to enforce procedures that may be a part of work flows or due diligence.

    • Due to unexpected problems, you may have seen "Missing notes" in the notes area. If such a condition is detected, we will automatically fix the problem and re sequence the notes.

    • When there was an error condition and a message was displayed, if you corrected the problem, the error message would still stay on he screen. This has been corrected.

    • If you have duplicate phone numbers in the home/work/cell numbers, you will have to correct the problem. This is a new edit we have added.

  • Changes to entering credit card information - We have some major changes! While the process worked, it could be confusing. There were different ways to enter amounts. Collectors could be confused about setting up a single payment and how they set up the amounts for a recurring payment arrangement. The flow has therefore been revised.

    • On the fist screen, the user will not be abe to enter any amounts. Here is a sample of the new screen. The user only enters the credit card information. If the client options are not set up, the user can not key in a "Type".

    • Once you have entered the credit card information, you will be taken to a screen which asks you whether you want to use the credit card for a payment arrangement, or for a single payment. If the user selects the payment arrangement option, they are taken to the payment arrangement screen, and the system will update the credit card screen with the option to retain information and with the flag to use the credit card for the payment arrangement. See the screen below.

    • Here is a sample of the screen displayed if the user does not select a "Y" on the prior screen, and is opting to set up a single payment.

    • And here is the credit card screen after information has been updated. Note that this user can not see the credit card information but can see the last 4 digits of the card number.

    Please make a note of the following changes too.

    • Once information has been entered, you can use F20 to delete the amount (for a single payment). The same option will allow you to delete all of the credit card information baed on the code selected. (Note the sample screen says F4, but this was later changed to F20 for consistency with other delete options within Intelec.) You will be prompted to select Y or A depending on what you wish to do. To delete information, the use must have access to the area or Payment Entry (System Security) or have a Y in the option "Show sensitive info (Y)", also within system security.

    • The "Use for payment arrangements" flag can only be removed by using the option to delete the amount (F20).

    • If a user does not have access to "sensitive information" and they try to access the credit card information, they will see a screen that shows the last 4 of the card number and its expiry date, along with a message that shows the amount of the one-time payment, or that the card is being used against a payment arrangement.

    • If a payment arrangement exists and you try to set up credit card information, the user is notified that the credit card can be used against the payment arrangement. In our initial analysis, we had considered not allowing you to set up a single credit card payment, when a P/A was already set up on the account. For complete flexibility, you need to be able to take a single payment OR use the credit card to pay off all the future installments on a payment arrangement. We will allow you to do that! You will be asked if you want to use the card for the payment arrangement. If you do not select that option, you can set up a one-time payment with the credit card. If you use the card for the payment arrangement, the credit card screen will show the flag indicating that the card is to be used for the P/A.

    • If you go into the credit card screen and a payment arrangement exists, there will be a message in red, warning the user of this.

    • If you go into the payment arrangements screen and a credit card exists, there will be a message in red, warning the user of this.

    • When you are setting up payment arrangements at the debtor-level, the credit card must be set up on the primary account, for payments to be applied using the card (It is possible to set up separate credit card payments for individual accounts within a linked group). If you try to set up a credit card against an account that is not the primary, you will be warned. You can continue if you choose to.

    • If you do not have access to "sensitive information" or the area of payments, you can NOT get to the credit card details once they have been established. What if a debtor calls back and want to change the amount? What we have done is allow collectors only (but ONLY the user who SET UP / CHANGED the credit card information), to go back and update credit card information even if they do not have access to the data. The same collector should have previously accessed the credit card information on the same day. The window that says they do not have the access will have the option F10-Update information. Provided the user is a collector, they will be taken to the screen with all of the information displayed as if they did have access to all of the data.

    • If the down payment on a standard arrangement, or the first payment on the non-linear arrangement, is for today, the credit card logic will usually happen during nightly processing. If we are at the end of the month, you will probably want to run that credit card today. The system will pop a warning window saying that the date of the first payment is today, and that you can have the credit card process today and link the arrangement to the credit card. If the user accepts, the due amount is moved into the "One-time" amount on the credit card screen. That amount will not be picked up again. The reason we do NOT automatically set up the first payment on the credit card is because it is possible that the collector needs to review the information stored (e.g. the card may not have been used for several months.)

    • What if one payment does not get authorized and you want to process the payment again, 2 days after the due date? No problem. There is a function key from the credit card screen, F10, for "adding an amount". This can be used even when the credit card is linked to the payment arrangement. It prompts for the one-time payment amount and will add that to the credit card window. It will be processed when the credit card interface is run the next time.

    • Once a credit card has been linked to a payment arrangement, you can send a letter before the due date, through the payment arrangement features. But in this case, it is not a reminder to pay, but a notification that a credit card will be used against the promise. For this reason, we have different letters that can be generated for credit cards, through the payment arrangements reminder feature.(Payment arrangements System Control file)

    • What if you are using the credit card to make payments on an arrangement, and you want to always process the credit card a few days before the due date? This is also possible - Once the credit card has been set up for use with the payment arrangement, you can use the field to the right of "Use for payment arrangements" to set up the days in advance that the payment should be processed. (Days in advance is the title on the screen). This field is only displayed when the credit card is linked to the payment arrangement. This field is protected if the user does not have access to the "area" of payments within system security. This field must be used with caution, since it changes the payment processing date. This may affect the legal requirements since you may be required to notify the debtor before using a credit card for recurring payments. It is for this reason that there is additional "security" for this field.

    These are very useful changes. Please review them carefully and make sure your collectors understand them prior to using the new features. We do realize that you may feel that there are some very complicated operational issues with regard to setting up a payment. We feel that this is a very complex area because it is integrated with many other areas of the system. It is further analyzed in this paper on "Payment options".

  • Direct checks - Presently, you can set up a series of direct checks for presentation. As each check gets processed, the information is removed from the screen. The checks to be presented remain on the screen. If you have the correct security, you can add (or delete) checks at any time. (There is ann option to automatically extend the checks after 11 have been processed.) If you make any changes or press F12 on the direct checks screen, all the "gaps" on the screen will be filled by moving all of the checks due to be presented into the empty fields. The user will briefly see a message "Order of checks was changed".

  • Timed recalls - (March 4, 2008) If a user accesses a different queue (User ID) from within account processing, the timed recalls would be presented based on the user who was signed on to to the system. In most environments, if a person is working someone else's queue, they would want to see the timed recalls that were set up for that user. This update will address that issue. Within account processing, the timed recalls logic will present accounts to the user, based on the queue they are trying to access. The recalls for the person signed on, are also checked!


  • Expanded (?) logic for Smart Codes - We have added the insurance fields to the data that can be checked. There is a new option to check if the account is a primary. There is also a method of checking the User ID of the person who applied the Smart Code!

  • New category code for Smart Codes - How do you quickly find a group of Smart Codes (e.g. Management codes, codes for a specific client etc.) Not easy, is it? On the first Smart Code screen, we now have a "Category". This is a user-defined, alpha-numeric code and allows you to "group" Smart Codes. Note that you could have different category codes for the standard smart codes and the overrides for that smart code. When you use F3 to search, you can enter that code at the top of the screen. Only those Smart Codes will be displayed.

    There is a set up option for the category codes. You must set up the code before you can apply it to a Smart Code. To do this, go to the search screen, and use F9, Category search. This will allow you to view, add and edit new category codes.

  • Change owner based on first open account - This is an existing option that allows you to change the owner based on the first open account (Y) or based on the primary (P). There is a new option T which allows you to change all of the links to the owner on the account the smart code was applied to. The Smart Code does NOT have to be duplicated. This feature has many applications, but use it wth caution, because it changes all of the linked accounts, even accounts that are with a legal collector!

  • Displaying a user-defined window, Tab-Q or Tab-* after a Smart Code is entered - On the first back screen, there is a field "Show UDW (or Q,*)" You can enter a user-defined window code, Q or *. After the smart code has been entered, the user will be taken to the specified UDW (if it exists), the Tab-Q or Tab-* screen.

  • Displaying a screen through a Smart Code - On the first back screen, there is a field "Screen code / Condition". The screen code points to an account-related screen. When applicable, you can use the condition to say "Show the screen if the screen does NOT exist" - N, "Show the screen if the screen DOES exist" - Y or "Always show the screen" - blank. The condition code is ignored for the bankruptcy or Tab+ options.

    The screen codes are -

    03 - F9/F14 DIRECT CHECKS
    04 - TabQ/4 CREDIT CARDS
    05 - TabQ/8 BANKRUPTCY
    06 - F4 SKIP TRACING
    07 - TAB+
    09 - F6 LEGAL
    10 - F17-LEGAL
    11 - TabQ/10 SETTLEMENTS
    14 - F2 -ATTORNEY

    The above options are displayed on the following screen.

  • Codes for additional Smart Codes - Presently you can have additional Smart Codes applied when a smart code gets processes This is done through the option "Code for additional Smart Codes". You can set up a code which points to up to 10 additional Smart Codes that can be applied. That set up option for that additional Smart Codes was displayed at the end of the Smart Codes option - when you used F7 to exit. That has been changed. The set up is now from the same screen that you enter the code. F22 will now take you to the system control file for "Codes for additional Smart Codes".


  • Account Audit - We have added new options to enhance the functionality. Some examples are payment amount within a date range. In addition, we have added a search option for client (number and search name) and collector codes. Simply move your cursor to these fields and press F3 to activate the search. Here is an example.

  • Viewing work maps - Those who are not classified as collectors can now look at another user's work map. This will be useful in environments where you may have a legal department and have several different users working a specific queue.

  • Payment graphs by collector - The full 4 character collector code was not showing! This has been addressed.

  • Resuming a contact series - Suppose you have a 3 letter series. The debtor makes a payment after the first letter and you stop the series. You do not get another payment and you want the contact series to continue, but from sequence 2, because letter 1 was already sent. *R in the option to start a contact series, will look at prior letters sent and resume the series, setting the next sequence to a value that will generate the next letter. If the next sequence will now be scheduled for a date that does not meet the interval required between the last completed sequence and this one, the date for the next action will be delayed to allow for the required time. If the last letter (ANY letter) was generated within 30 days (on that account), the next sequence will be scheduled for 30 days from the system date. We realize that that this may be a problem, depending on when the last sequence took place or the conditions (e.g. mail was returned), but we feel that it is safer than risking the consequences of sending a letter too quickly. We have the system set up to also mark a letter as not being "sent" (e.g. when mail is returned) but this will be activated in the future when we find a way to tell the system exactly which letter was returned.

    The codes you can presently enter in the Contact Series field within a Smart Code are therefore.
    • Any valid contact series code
    • *S to start the present series from the first sequence
    • X* where X is a Contact Series by client code - This will start a contact series based on the code X.

    For the above, the account must be open for the action to take place.

  • Requesting first letter - As you know, you do NOT have to send a first letter (validation notice) until you have had a contact! You may well identify accounts that may not need a letter. These could be low scoring accounts. You may want to call and play a message. If you have a bad number, the chances are the address is bad too. So why waste the postage? But if you ever contact the debtor (or even think you may have, because you played a message to an answering machine), you may want to make sure you send the first letter. How do you make sure this happens?

    In the letter codes system controls, there is a new option. When you end the program a new option called "Letter request options" is displayed. It allows you to tell the system to send a letter or apply a Smart Code if at least one of 5 specified letters has not been sent. This logic is triggered when a Smart Code is applied. The Smart Code must get processed. The logic is automatically executed. You can indicate whether the letter should be generated for an attempt, contact or any other action. You must indicate what letter should be sent, if none of the letters have been sent. There is an option to apply a Smart Code if the conditions are met. The Smart Code could be used in the case where you have to use logic to determine what letter has to be generated (e.g. based on the client). This feature has great potential for managing your costs! Of course, if you never send a letter, you can not credit report the account! This must be considered. The decision could come down to, "Is it worth spending $.45 to send a letter and credit report an account that is very unlikely to pay?"

    Here is a sample screen.

  • Payment arrangement reminders - We have made the following changes.

    • Letters were not being stopped if it was less that 3 days before the due date. This has been corrected.
    • There is a separate option to print letters if there is a credit card set up for the payment arrangement. Since you can specify different letters for those with a credit card, you can do different things with letters. You can print reminders for all payment arrangements, those with only credit cards, or, have different letters printed for credit card and regular arrangements!

    This in an example of the new screen.

  • Activity dashboard - There were some inconsistencies in the numbers displayed within the option that displayed real time payment and promise information for collectors. These have been addressed. We have also made some interesting changes to the main "On-line Collector Productivity" inquiry (from within the the menu options called by keying in EX from any menu).

    • We used to show only collector activity. We now show anyone who has had activity. There is an option to select only collectors (if no promises exist). If promises exist, the user is always displayed.

    • When you select the option, you can say "Select only collectors for accounts worked (Y)". This will only include collectors as far as users who had activity (if there were promises, you can not omit them).

    • A problem with the promises sometimes showing very high numbers has been addressed.

    • Presently, we show promise numbers. This can be expanded to show the number for each category (single promises to pay, direct checks, payment arrangement etc.). We also give you a total of the dollars for all of the categories. This will include the only the first payment for payment arrangements and all direct checks, but all of those, regardless of the due dates. But, there is a difference between a credit card payment and a single promise to pay, without an associated check. One is money, the other may become money! From the expanded promises display, F10 will show you "the money"! We show the total of checks, credit card payment arrangements, PAP's and single credit card payments, as long as they are dated for the current month (calendar month). This will only be available on a go forward basis and not for prior days.

    Here are some sample screens. This is the present screen for expanded promises, with the new function key.

    And here is the new screen showing the "money".

    • The existing option used to allow you to go back up to 30 days. We have removed this limitation. You can now go back as long as data has been tracked. All of the new data will only start to be tracked after you install the new update.

    • The new "money" option has great potential. You should find that there is a relationship between the total promised and the "money" that is immediately generated (direct checks and credit cards). It should be a good indication of the health of your operation and a predictor for your revenues. Some of you probably use these numbers to measure a collector's productivity. Of course it is possible that a check may not go through or that a credit card charge may not be authorized. But you will agree that this new option has great potential. As you start to use it, you will doubtless be faced with the question"How did they come up with $2435 for User JM25"? Option 9 (Print 'Money' details on activity dashboard for today) on the dashboard options will print a report by User ID, showing all of the accounts that make up the money totals on the display for the current date. This will backup the numbers on the screen. It can not be run for prior dates at this time.

    • The "Money" option looks at all direct checks set up and postdated checks that have been entered. For credit cards, we look at single credit card payments as well as the down payment and first installment for a regular payment arrangement. We also consider the first installment for non-linear arrangements. Most companies are also interested in "What is coming in this month"? From the "Money screen, you can use F10 (not shown on sample screen above) to display the money for the balance of the month only! This will be separated out by credit cards and check, along with the total of the two. This will look at the same information but omit check or credit card payments for anything other than the current month (based on the system date.)

      And how would you get a list of the accounts that made up the "money for the balance of the month"? There are two options. On the client comparison report options (from the Periodic Reports menu), option 9 is "Payment arrangement, credit card and check analysis". This will show you information by client, and the numbers should match up to the totals on the "money" option. From the Activity Dashboard options, option 11 is a new report that will also list all of the transactions that make up the "money for the balance of the month". This report is sorted by type of payment, and will show the case number as well as the owner and split for each account. If you are trying to find the transactions for a specific worker, you could run this option, hold the spool file, view it and use the "Find" option to locate a specific worker's payments. Presently, there is no option that lists the transactions for a specific user.

    • We have no report to back up the payments posted for a day (by User ID). Option 10 from with the Activity Dashboard options, will produce this list.

    • With the goal of being able to compare results over longer periods of time, we have also added an option that allows you to run the analysis for a range of dates. This is option 2 from the menu. The date range selected will be displayed on the heading line of the screen.

      As a part of the installation process, all prior data will be deleted and we will start tracking historical information from the date of the install.

  • Direct checks - We have some interesting changes.

    • There will be an option at the company level (company information) to stop direct checks from being set up by a collector if there are any NSF's on the debtor (all links considered).
    • We will show the total balance on the line that displays the title for the screen. Since some users will not be able to view the full account number and routing number, we will always show the last 4 characters of the account number and routing number under the account number field.
    • If you try to enter any check more than a year in the future, you will be warned. F12 will allow the transaction to be processed.
    • We will not allow duplicates to be entered (more than one transaction with the same date).

    Here is a sample screen.

  • Collector codes - changing accounts based on User ID - Presently, you are allowed to set up different collector codes and make them all point to one User ID. When you want to change an owner based on the person (User ID) who worked the account, which collector code do we use when we have several to choose from? We will allow you to say "Do not use for collector changes (N)" in collector update. So if you have 5 collector codes all pointing to one user ID, you can put N's on all but the one you want to use for collector changes! We will also omit collector codes that have a delete code set up.

  • Queue consolidations - We have added the following.
    • Score range (external) and an indicator to select the specific score (1-3)
    • A last transaction date range - specified in a number of days (based on the system date)
    • Balance range (amount eligible to be worked) for the consolidations by user
    • For the consolidation by client, placement date can be specified in a number of days (based on the system date). For example, 1 - 40 would mean placements within the last 40 days.
    • The phone option has been enhanced to allow you to specify home, work or cell phone.
    • It is possible for different consolidations to pick up the same account, and you could have many consolidations that run during nightly processing. You may get the wrong results based on which consolidation was first processed in the case of the nightly processing options. What is the solution? There is an option called "First pass - Y". Put a Y in this field if you want this consolidation to be processed before those that do not have a Y in the option.

    Here is a sample screen from the client option.

    • (May 2008) For consolidations by client, it is no longer necessary to enter a client code if only one User ID is specified. A bug with placement dates entered in a "number of days" format was corrected.

  • Company information - We have added the following options at the company level. (1st screen of company information)

    • Only allow smart codes to be entered on the primary account (by collectors). An "N" on the company screen will do this for all clients. You can use a "C" to tell the system to check the client master. An "N" on the client (last screen) will stop Smart Codes from being entered on anything but the primary.
    • Option to stop collectors from setting up a direct check if there are NSF's for the debtor
    • Do not create an account in the queues if any of the debtor's accounts is in a contact series

  • Linking - (June 2008) For automatic linking and points for client account number - The system will only assign points for accounts belonging to the same client.


  • Credit card payments - As the volume of credit card transactions increase, we need more tools to increase productivity. We have enhanced the option that prints credit card information and then deletes that information. (Daily payment report options from the Payments Menu) When you select the option, you will be warned that transactions will be deleted after processing. When you choose to continue, you will be notified that "The selected transactions will be loaded into a payment batch." There is an option to indicate that you do not want a batch to be created. If you select the option for a batch to be created, you will be prompted for a batch number. The batch is created in a format that distributes the payments across all of the linked accounts, based on balance types. After the batch is created, you can go into the payment edit option. After the transactions have been checked, they should be posted.


  • Purge by client - We have finally added a purge by client group! On the purge options menu, option 9 will display the new options - a preliminary report and the purge option. You can run the report as many times as required. The selections are similar to the standard purge, with the addition of a client group option. You can run the actual purge for different client group and keep adding to the "purge files". You can backup and delete the purge files after you have completed all of the required purges.

  • New client reports - We have some new client reports.
    • On the client comparison reports option, option 7 is "Historical analysis and trends". This option allows you to look at several clients and understand trends (12 months) for commissions, collections, placements, active amounts and commission rates! You have a rich range of selection options and this report should be very useful in analyzing your clients. Here is a sample from these reports. The column headings show trends in columns that compare prior months to the current month (e.g. Current month minus 1, or current month minus 5 to 8, which would be a combined 4 month period. Prior months 1 to 3 are separately displayed. Other months for the 12-months past are summarized in groups of 4 months.

    • Option 9 on the client comparison options is an analysis of payment arrangements by client and monies projected to be paid in a date range. Do take into account that if you link across client, the information may not be accurate. The report also identifies money due from credit cards tied to the payment arrangements.

  • Changes to cell phone legislation - There is news that you will be able to call cell phones through ana automated dialer provided the number was supplied to you at the time of placement. We have moved quickly to help you use this new information. Our thinking is that you must be able to differentiate from a cell number provided at time of placement, and one that may have be obtained later, through other sources. Because it will continue to be difficult to know what is definitely a land or cell number, the challenge is that what someone may say is a cell number (e.g. a skip-tracing service) may really be a land line and you may be able to call the number to to make that determination. Our decision at this time is to allow you to load cell numbers into he cell number field at time of placement. This can be done through electronic loads or manual account entry. As an audit trail, we will add a note if the account has a cell phone at time of placement, along with the number. If you get a possible cell number though other sources, we suggest that you ONLY load those numbers into the Tab+ window. This gives you a clear indication as to what number was obtained at placement. Of course it will be up to you to manage these numbers and you will have to decide how they will be attempted. e.g. With I-Tel, you can move cell numbers into a dialer campaign. In addition, to these changes please make a note of the following.

    • We have new logic to stop duplicate numbers from getting into the home, work and cell numbers. These changes will apply at the time of loading accounts. If the cell phone number is the same as the home or work number, the cell number is not loaded. If the home and work phone are the same, we clear the work phone number.
    • We have added original creditor and account number to manual account entry
    • If you use Quantrax's manual skip-tracing service, we have changed the upload process to NOT load possible cell phones into the cell phone field. They will only be loaded into the Tab+ screen.
    • In I-Tel, you have the ability (Other phone number options) to have a cell phone number (from Tab+) moved into the phone fields in Intelec's queues. You would put a C in the phone code selection, for this. You can now enter a 1 for the system to select only a cell number from the account detail screen. A phone code of 2 will only select a cell number from the Tab+ screen (from numbers with a code of C) if it does not match the number on the account detail screen. A phone code of 3 or C will select ANY phone from the Tab+ screen, with a code of C.
    • On account inquiry, we will notate the account whenever a cell number is changed or added, regardless of the option on the System Parameters to log changes to information. This will ensure that all changes to cell numbers are audited.

  • Status report - (May 2008) The secondary close code will be used in obtaining the description of the close code.


  • Reports - We have done a great deal of report clean-up. Please review the reports. If you still encounter issues, please contact support.

  • I-Tel menu - We have reorganized the menu. We have grouped the options into sub-menu items when it made sense to to that. You should have no problems and should find it much easier to get around the options.

  • Archiving data - We used to archive data for 30 days for the reporting. We have removed that restriction. Data will be archived and not deleted. This means, that on a go forward basis, you will be able to go back and pull data for any period, after this new version was installed. The log and data files may be quite large, and you will be responsible for deleting old data. The archived file will have the format SCITxxxxxx and SCCDxxxxxx, where xxxxxx is the work date for the information being archived. To delete old data, there is an option 20 on the management options from within the I-Tel menu. We will be expanding the reports to allow you to select data ranges.


You will first need to determine what version of Intelec you presently are on. The current release is displayed when you sign into Intelec and get to the Main Menu.

IF YOU ARE ON RELEASE 7.2 OR RELEASE 7.4, please go to the documentation for Release 8.0 and follow those instructions which will get you to to Version 8.2. You will then need to update to 8.25 by running option 4 and 6 from the 8.25 installation instructions below (within INSTALLATION OF THE NEW VERSION IF YOU ARE ON VERSION 8.2)


You will need to follow the instructions for upgrading to 8.1 only. This will automatically install you through versions 8.1, 8.2 and 8.25.


You will need to follow the instructions for upgrading to 8.2 only. This will automatically install you through versions 8.2 and 8.25.


You can install this update as long as no users are on the system. You can install the update at any time - at the end of a day (before nightly processing) or at the beginning of a day (after nightly processing has completed). You should have a backup from the last nightly processing that was run. There are no major file changes and a full backup is not necessary. The complete install should take less than 30 minutes, but may vary depending on your data volumes and processor.

You will receive 2 CD's - on titled BASE and another titled MODS. Please make sure you have both CD's before you start the installation.

You will first need the CD called MODS. We will need a dedicated system (No Intelec jobs running).

You should make sure that all users are signed off Intelec.

  • Cancel the Smart Code processing program.
  • If you have a dialer other than Intelec, cancel those programs.
  • If you are using I-Tel, end the dialer server.

For the following instructions, please remember to use "opt01" if you are using a CD and are prompted for the device name.

  1. Sign on with an Intelec User ID that gives you access to the command line (anything other than INTELOPR), load the CD titled MODS in the optical drive and get to a command line.

    Key in CALL INSTALLMOD and press ENTER. This job will take about 5 minutes. You will be signed off and will be asked to sign on at the end of the job. Sign on as QSECOFR.

  2. Now remove the CD titled MODS and replace it with the CD called BASE.

    Key in ADDLIBLE SCLIB from a command line and press ENTER
    Then key in ADDLIBLE SCMOD and press ENTER

    Key in CALL INSTALLNEW, press ENTER and follow the instructions. The device name should be opt01.

    This option will take about 5 - 10 minutes. At one point in the installation, the system will check that the library SCLIB is not in use and if it is, it will display any jobs that will need to be canceled. At the end of this step, you will be asked to have all users signed off the system.

  3. After Step 2 is complete sign off and sign back on with the User ID QSECOFR

    Place the CD titled MODS in the optical drive and key.

    Key in ADDLIBLE SCLIB from a command line and press ENTER.


    This step will take a few minutes.

  4. After Step 3 is complete sign off and sign back on with the User ID QSECOFR.

    Do not attempt to sign on with an Intelec User ID.

    At this stage, do not allow users to sign on. The rest of the installation process could take about an hour. We will be creating some new logical files over the account and payment files.

    Key in ADDLIBLE SCLIB from a command line.
    Key in ADDLIBLE SCFIX from a command line.
    Key in ADDLIBLE SCMOD from a command line.

  5. Place the CD titled BASE in the optical drive and key in CALL INSTALLSYS. This step will take a very short time to complete.

  6. Key in CALL INSTALR825. Press ENTER and follow instructions. The job is submitted and will run in batch. This step could run for a few hours.

    Check that the install program is running by using WRKACTJOB. Once the job has started, you should wait about 5 minutes and can leave if there are no messages.

    This time taken for this step will depend on the amount of data on your system, and your processor speed. An estimate of the time taken is under 30 minutes.

    When this step is over, the installation of the new release is complete. You should check the job to make sure it has completed (WRKMSG QSECOFR) and use the WRKACTJOB command to make sure there are no messages.

    The completion message "'Intelec Release 8.25 has been installed" will be sent to INTELOPR.

  7. After Step 6 has completed, you should run nightly processing if you installed the code at the end of the day. Otherwise, continue with your regular work.

  8. Please make sure that you send an e-mail to support@quantrax.com indicating that you have updated to the new version. This is very important.


The following were a part of the Version 8.1 upgrade. If you did not run these options, consider running them now.

As we discussed earlier, we have started to track right party contacts, has debtor called us? etc. We have a program you should run after you have set up your Smart Codes. Remember, we will be looking at the base Smart Code for our analysis. For ongoing work, it is important to set up all overrides in the same way as the base Smart Code, with regard to some of these new option. Recognizing the need to be able to easily move information across Smart Codes, we have a new program that will copy information from the base Smart Code to the overrides. In addition, you can set up some options across all Smart Codes too. From the Smart Code duplication options (3rd System Control Menu) you will see the following when you select "Smart Codes".

You can leave the copy options blank and have the system duplicate the selected options from the base smart codes to all of the overrides. This is a good time to remind you that Smart Codes and their overrides must have the same basic meaning. E.g. You should never have the base Smart Code defined as attempt and the overrides for that Smart Codes defined as contacts.

If you use ACat codes, and you want the ACat code to be used for Smart Code overrides, you need to tell they system to do that at the client level (because ACat Codes may mean different things for different clients). The above option allows you to put a Y in all of the clients for the "Use ACat for Smart Codes" option.

It is our recommendation that you update the Smart Codes as soon as possible after the new version is installed.

To update the account master based for RPC's, attempts etc. based on on prior activity, we have created a special program that can be run after the Smart Codes have been set up. The job will run for a long time (a guess is 1 - 2 hours) depending on the number of the accounts in the system. The job can be run when users are on the system, but we suggest that you run it during a period of low system activity.

To run the program key in the following from a command line.

sbmjob cmd(call qgetacci)

The job will run from the job queue.

You may want to consider setting up the following sometime soon

  • Option to stop audit notes being added for maintenance Smart Codes
  • Changing some worker codes to not have the account go into queues.


  © Quantrax Corporation, Inc.