Laserfiche WebLink
InfoSend Response — 12/29/2006 <br />customer in the file. The sample approval process can help the client catch his or <br />her own error. <br />b.) If client sends a customer record, which contains data that would not currently fit <br />on the printed statement, then truncation will occur. Example — if the current <br />printed statement is formatted to display a 20- character or less customer first <br />name and a data file is submitted that contains a 40- character customer first <br />name then data truncation will occur. If client is adding a new field to its data <br />format or is including new data elements in existing fields, it is recommended that <br />it send InfoSend a test file to ensure that data truncation will not occur. <br />3.) Availability of websites <br />InfoSend employs the use of multiple internet connections from different Internet Service <br />Providers to maximize website uptime. The websites will be accessible by customers and CSRs <br />at all times. <br />Exceptions: <br />a.) InfoSend performs periodic system maintenance that can require temporarily <br />taking the websites offline. If this type of maintenance is required the downtime <br />generally lasts for less than 1 hour. This type of maintenance is performed after <br />hours. <br />b.) If a critical security update becomes available outside of the maintenance <br />window described above that requires a temporary website outage, InfoSend will <br />install the update if it determines that postponing the update will put the client's <br />data at risk. These types of updates are rare and can generally be applied <br />without requiring the websites system to be taken offline. If an interruption of the <br />systems is required for this type of update, the outage will generally last only a <br />few minutes. <br />C.) If the EBPP system is inaccessible by a customer due to a problem on the <br />customer's end then InfoSend will not be penalized. Examples include a <br />hardware or software problem with the customer's computer, inability to access <br />the internet because of a problem with the customer's Internet Service Provider, <br />a DNS problem with customer's computer that makes the InfoSend EBPP site <br />appear to be offline when it is not. Client will judge customer complaints of EBPP <br />outage by using the following procedures: <br />i. If a customer calls or emails client and states that the EBPP is down <br />or responding very slowly, client will attempt to access the EBPP <br />system to see if it can connect at normal speeds. If client can connect <br />to the EBPP system at that time and the site is responding then the <br />problem is most likely on the customer's end and InfoSend will not be <br />penalized. Client will advise the customer to check to ensure that their <br />computer can connect to other websites and try to connect to the <br />EBPP system again. <br />ii. If neither the customer nor the client can connect to the InfoSend <br />EBPP then the client will check to see if other websites, like <br />www.google.com and www.yahoo.com are accessible. If other <br />common websites are loading very slowly or not accessible at all then <br />the problem could be caused by a major internet backbone outage. In <br />this scenario InfoSend will not be penalized. <br />iii. If neither the customer nor the client can connect to the InfoSend <br />website but the client can connect to other common websites like <br />www.google.com and www.yahoo.com, then the client can suspect <br />36 <br />