Procedures

Here are procedures to be followed by Support Staff in respect to various technical matters in day to day operations of client issues.

Handling Clients with Overdue Invoice

In order to maintain good payment speed by clients NEOSYS needs to restrict support to clients that dont pay their bills on time, however the degree of restriction needs to depend on an intimate knowledge of the client which cannot be expected from all NEOSYS support staff. Therefore we will use a simple escalation policy as follows:

Overdue Support List

NEOSYS SUPPORT MANAGERS WILL maintain an overdue list on a whiteboard visible to all support staff. Generally clients will go on the list immediately when their invoice is overdue and come off only after satisfactory commitment to pay have been obtained.

For the first week of each quarter of the year, normal support should be provided for server failures and backup failures (including hung processes as it could eventually lead to backup failures). NEOSYS Support Staff must respond to any other support requests from overdue clients, with the following letter (where XYZ is the overdue client):

Dear ABC,
There is an issue with your company's account. We have requested our Accounts team for approval in order to provide support to you and other XYZ users. 

Support staff must then provide the required support to the overdue client only after 4 working hours. Support Staff need not actually contact the Accounts team for approval, although that is what is mentioned in the letter. This delay in support is to encourage clients to settle their payments on time.

After the first week of each quarter of the year, NEOSYS Support Staff must respond to any support requests from overdue clients with the above letter but MUST NOT PROVIDE SUPPORT even after 4 working hours. Instead NEOSYS Support Staff must refer the support request to NEOSYS Support Manager.

Managers may well instruct support to provide support on a case by case basis even if clients are on the overdue list. Being on the overdue list does not necessarily indicate a major issue with accounts.

Handling Frozen NEOSYS Installations and Databases

Some clients retain fully operational NEOSYS installations or just particular databases even after they stop using them for some reason, either because they move to some other software, or because they terminate an operational division, or other reasons, and this can either be on NEOSYS or their own servers.

In this case, various NEOSYS upgrade and maintenance processes may be suspended, downgraded or completely skipped especially if instant access to the server is no longer available. This does not mean that it should never be done, and pros and cons need to be assessed and documented in support emails on a case by case basis.

• Upgrading NEOSYS version
• Upgrading/standardising NEOSYS database configuration and other files for consistency, security or other issues
• Patching Windows/IIS configuration for consistency, security or other issues

Handling Links and Email Attachments

DO NOT TRUST ANY LINK OR ATTACHMENT IN ANY EMAIL EVEN FROM HIGHLY TRUSTED PEOPLE OR ORGANISATIONS

These days you can no longer trust links or attachments in emails from anybody - even emails from highly trusted people like your bank.

If a personal computer or intermediate email server is hacked then even genuine emails sent out from it can be infected and modified in a hidden way that can result in the recipient being infected if they click or open anything in the email.

Therefore you should know and understand how to avoid, as far as possible, getting tricked and infected via emails.

Malware authors generally rely on the fact that most people devote no time at all to security precautions so a moderate cautious approach, slowing down a little to spending some time on security, even where it is apparently not required, is enough to defeat most attacks.

Links

The links in an email, even from someone you know and trust, can LIE to you about what website they will open and you may be taken to infected web sites that will attempt to infect your computer.

WHAT LINK/WEBSITE WILL BE OPENED MAY NOT BE WHAT IS SAYS IN THE BODY OF YOUR EMAIL!

Therefore, to use a link in any and all emails, first hover your cursor over it and check the bottom of the screen where you can usually see exactly what website will be opened, or, to be more sure exactly what web site you are opening do not click links in emails at all. COPY/PASTE THE LINK TO YOUR BROWSER

Make sure you know and trust the web site being opened.

1. Carefully inspect the spelling of the domain name to avoid tricky look-alike fraudulent links eg hcsb.com instead of hsbc.com
2. If you do not personally know the website then get independent confirmation from the sender. Reply to the email so that the sender can check the link you received has not been tampered with.

Attachments

There is no way to determine if an attachment, even from someone you know, has not been infected and is therefore dangerous. The only protection is to rely on anti-virus/anti-malware software in your computer.

You can check the names and file types/extensions of attached files to spot any obviously strange or unexpected attachments but this is not very effective.

Be careful that if there are a lot of attached files not to assume that all are safe because the majority are unsafe.

Avoid burdening email servers with excessive graphics

Where possible, try to reduce the burden on NEOSYS and NEOSYS client's email servers by removing graphics like screenshots when replying. It is quickly done by clicking and pressing delete on each graphic.

This is especially important on long conversations about subjects that include many screenshots, since for just a simple one line reply, the email can consume many MB of space.

To be able to refer back to graphics in previous emails, add the SIZE column to your email program so that you can locate large emails with graphics rapidly without searching back one by one.

Client Communications and Meeting Report Policy

After every Client meeting online or otherwise Support MUST send a Follow Up email to the Client which is open and fully informative and not brief, stating the events during the meet and any action required by either or both parties. The email to the client must not shrink from discussing contentious issues due to a false sense of politeness or timidity to address issues face on. Obviously one should not be rude but it is not rude to address issues openly.(cc Client managers and NEOSYS Managers)

In addition to above email if there is some information that needs to be shared internally and cannot be said in public to the client then send a Client Meeting report to Support.

For Support issues, Support staff must inform clients of the progress of the issue if it is not resolved the same day but only if they contact sometime before office closing. This can be 1 or 2 hours before office closing.

NEOSYS contracts, in the few cases where we have a written contract with the client, specifies that maximum response time is one business day generally and one business hour for complete stoppages of the system. Obviously we have to do far better than this in practice.

If issues become contentious then voice, phone call or chat is REQUIRED. Emails are NOT sufficient. If not possible to contact for any reason then an email MUST be sent stating so and suggesting or requesting a time to connect.

Every significant voice, phone or chat conversation MUST be followed up with an email confirming at least the jist of the communication.

cc Client managers (AND/OR BCC NEOSYS Managers) MAY be done if thought to be useful and/or appropriate.

Deciding to wait on issues is fine ( Also Refer to: Response to standard messages). But at least support must spend up to 5 minutes on issues to see if they CAN be handled quickly

For routine requests for service where there is a reasonable expectation of delay by the client then no need to send rapid reply.

Handling errors discovered by support staff

1. Replicate the error on all browsers after ensuring that the browsers have script error notifications enabled.
2. Check in all the wikis for a solution.
3. If there is no immediate fix for the error, try to find and provide a temporary workaround, which the client can use until the error is fixed.
4. If the error is new, do a thorough investigation (eg. check NEOSYS logs) and try to find a solution for the error.
5. If you still cannot find a fix for the error, then escalate the issue to your manager with an explanation of the issue.
6. Support MUST always provide full screenshots of all the steps required to replicate the error, as this will help identify the cause of the error much quicker.
7. When sending screenshots of the issue to your manager, the top-left of the browser MUST be visible so that it is clear which browser, URL and database is used.
8. Ensure that script errors (if any) are included in the screenshots. Include every detail available regarding the script error, for example: script name, line number etc.
9. Support MUST report the error to support team by email to keep a record of all errors in NEOSYS. Support team looks good when errors are spotted and fixed pro actively. Do not ignore the error for any reason.
10. When requesting the programmer to fix the issue, explain WHAT has to be fixed and HOW it has to be fixed. Refer to Handling request to create a new feature or modifying existing features
11. The most important step when solving any problem is Future Prevention. eg. add the solution to wiki, so that support spends lesser time fixing the problem in future.

Handling Cheques from Clients

NEOSYS staff are not to accept deliveries from clients that might be cheques without prior instructions to accept the same. They can ask courier to wait a few minutes until NEOSYS accounts or management agrees but they may not be available and probably will not agree anyway. NEOSYS payment terms do not accept cheques although clients are free to deposit cheques by themselves.

Client Password Policy

All client user passwords, including their initial one, are to be obtained via the user's email address using the password reminder/reset button on the login screen. (NEOSYS password policy)

NEOSYS staff should never know users passwords therefore NEOSYS will not obtain and grant user passwords. The reason for this is that in the event that users lose their passwords to other people who then login unauthorised then suspicion could fall on the NEOSYS staff who know their password.

All parties concerned, including client management, client users and NEOSYS support staff, benefit greatly from trusting that if something in a NEOSYS database is registered as having been done by a particular user then it was not in fact somehow done by NEOSYS support staff. Nothing should be done that would break such fundamental trust. To achieve this, NEOSYS support staff must never log in as particular users, never ask for users passwords and generally enforce the idea that all work logged as being done by users IS done by users.

Very limited amounts of work by NEOSYS support staff either in person or remotely using teamviewer is acceptable while a user is logged as long as the user login was performed by the user themselves, the user is present and the user specifically agrees with the work being done.

Support requests from ordinary client users

Any support requests concerning inability to obtain passwords will be forwarded to known skilled users on the client staff since this is the most efficient (not fastest) way to handle such issues.

Support requests from senior client management

Any support requests concerning inability to obtain passwords by senior client management users shall be handled directly by NEOSYS support staff in any way convenient to resolve the issue in the quickest possible time rather than the most efficient.

Bearing in mind that NEOSYS staff should never know user's passwords this will probably involve NEOSYS staff using the Password Reminder/Reset button to send a new password to the user.

User Defined Passwords

NEOSYS will provide user defined passwords in very special cases which must be pre-approved case by case by NEOSYS management. NEOSYS will not approve this due to the reasons mentioned here.

If the user login gets blocked due to multiple login failures and the user requests support team to reset the password to the user defined password again, support MUST delay the response to this request by at least 1 hour in order to force the user to be more careful when typing the password.

Currently permission for user defined password has only been granted to one NEOSYS client with several hundreds of databases.

Handling client issues and requests

All support issues must be dealt with through phone/email/chat. Support Staff can schedule client visits for User Training but should not schedule client visits solely for providing support for petty issues.

ALL Support staff should check the all the previous day's inbound emails for reply flags once in the morning. All Support staff will therefore be held responsible for any unreplied inbound email.

Support staff should NOT waste time and delay support by investigating issues WITHOUT having sufficient information.

Support staff should look for similar issues when solving a particular problem to avoid similar issues in future. This saves the time and energy of Support as well as the Client.

When sending screenshots to clients, support team should economise on space by minimising to the minimum that will show the problem clearly. This is because not every user will be viewing their emails on large wide screens like NEOSYS support team. Browser windows reformat their contents to suit the width available so this is particularly effective in most NEOSYS screens.

Support team MUST be cautious while sending screenshots so that no private/unnecessary information is sent to Client. If you cant avoid taking the screenshot without unnecessary information then you should hide it in the screenshot.

Handling new emails in Support inbox

Support MUST spend up to 5 minutes on new emails and send a quick reply to the client, to acknowledge the request or give a quick solution in case its a petty issue or has a documented solution in wiki. This should probably be done on priority, interrupting existing work and not wait for one hour and be dealt with quickly.

For routine service requests where there is a reasonable expectation of delay by the client, Support does not need to send a rapid reply.

Handling login failure issues

Users often get login failure issues due to typing wrong password and they simply won't read and act according to the error message they get. In this case, Support must ask the users to contact their NEOSYS-registered local support person which could be their TA, IT or manager etc. This will reduce the endless mails sent back and forth to solve petty issues which could easily be solved by the client's local support.

Local support users have the LS key using which they can see the User Details page of all users. Hence, the local support person should either help the user to reset password or check the information (usercode, registered email address, last login attempts etc) in the User Details Page to find out what the real issue could be.

Support staff can keep a note of all the local support users.

Handling requests or demands for "URGENT" or "PRIORITY" support

Any request for prioritised action *without giving any reason for the prioritisation* should be disregarded and the request handled with normal priority. If a reason is given then you may at your discretion prioritise a response but there is no obligation to do so.

Handling users who login with other people's NEOSYS usercodes

This can cause a lot of confusion in both the client and NEOSYS support. It may also indicate that the correct NEOSYS monthly licensing fee is not being paid. There is no valid reason for anonymous logins or sharing logins between multiple users.

Therefore if NEOSYS support team get requests for support about using NEOSYS from users who are not registered properly in NEOSYS with an personally identifiable user code, name and email then the following email should be sent cc admin@neosys.com.

No exception should be granted to clients without NEOSYS management approval.

Dear NEOSYSUSER,

Please note that in order to receive support from NEOSYS you must personally have an identifiable user code, name and email address registered
in NEOSYS.

We can create new user account for you with your management approval. This may or may not have an impact on the NEOSYS monthly licensing fee 
depending on the agreement in force.

Please let us know what you would like us to do.

Best Regards,
NEOSYS Support

Handling emails with unrelated subject line

At times, clients forward old emails, with new issues or do not bother putting the correct subject line for new issues. In such situations, support should fix their email by deleting the irrelevant content and changing the subject and add a comment like "PS Please don't forward old emails for new issues, either start a new email or delete previous content and put a new subject."

Handling emails with poor screenshots

Sometimes Thunderbird shows full sized screenshots in a compact format that is not easy to read. These can be resized to make them more legible. To do this, make the email editable by hitting the "Reply" button, then click and drag to resize the screenshot as desired.

If the screenshot sent by the user is genuinely small and hard to read, reply to the mail and request for a full size, clear screenshot.

Handling support-request emails sent to anywhere than support@neosys.com

Client emails anywhere than support@neosys.com MUST be ignored. This is because ALL support must be recorded in support inbox without exception so that the whole support team is aware of the issue and action taken. If client complains about the delay in support then they can be told this is because they used the wrong email address.

Handling users who do not act upon standard messages

When users do not bother to read and act on standard NEOSYS-generated messages and instead ask for help, Support staff MUST delay response time and thereafter send them an email which is the same as the message so they get the point that in future they should read the messages and handle issues themselves.

Handling Requests to do Client work

NEOSYS Support staff must not agree or offer to do work on behalf of the client.

This is because doing client work while logged in as NEOSYS breaks security rules. Support uses the NEOSYS username which has unrestricted access, so when a user requests Support to do some work which they don’t have access to, and if Support agrees to do the work, the client has successfully defeated the security rules by accessing features that they are unauthorized to access.

Requests for colour and font changes

Support should not be spending lots of time on colour and font changes. Clients can make as many changes as they want until they are happy with a selection. Clients MUST send screenshot of their required color/font settings (not sample screen/reports) for Support to copy and setup for all users. If Support sees them doing something bad or poor then give comments or better suggestions.

Handling Requests that require Approval from Higher Authority

The following is a list of user requests that must be handled by NEOSYS support staff only if they are approved by or come from a higher authority (manager/admin). The LIST is NOT a complete list so there may be other things which might require approval so use good judgement and/or ASK if in doubt.

• Opening new financial year
• Adding new company/dataset
• Editing alert/backup email receiver addresses
• Customising Authorisation File
  • Adding or removing accesses for existing users in Authorisation file
  • Adding new user(s) to Authorisation file
  • Expiring a user
  • Allowing HTTPS/outside office access from any IP number

If an unauthorized user sends one of these requests to support staff, support staff must immediately instruct the user to get the request approved by the higher authority.

Handling User Requests to add an IP or range of IPs to access NEOSYS

Support staff must identify if the IP or range of IPs is for http or https access.

For HTTP access

Support staff can add local IP or range of local IPs when requested by the client. Top management approval is not needed to add local IP numbers. Listed below are the IP address ranges reserved for local network.

10.0.0.0 – 10.255.255.255

172.16.0.0 – 172.31.255.255

192.168.0.0 – 192.168.255.255

For HTTPS access

Any request for https access with no IP restrictions, or in other words any use of an asterisk in the IP restrictions (eg. 123.456.* or just *), MUST have TOP management i.e. the company's decision makers approval. The Staff and their Managers are not the best decision makers in this affair because they usually ignore the risks and it is not really their decision. Security threats like access of data by unauthorized persons or ex-employees, malicious hacking attempts etc can be triggered if access from any IP is enabled. It is completely pointless to inform the staff who want the access about these risks because only their top managers could really decide that this is NOT going to be allowed. Hence the Top Management MUST be asked for approvals and at the same time WARN them about the security risks/threats behind the no IP restrictions.

Support MUST also mention that installation of VPN by the Company is the industry standard way of providing access to mobile staff (i.e those on dynamic IP numbers from home or travelling) to corporate software assets like NEOSYS IN A SECURE MANNER. Installation of VPN is to be done by their own IT support.

Sample Email:

 Dear XXX,
 
 I do not recommend allowing access from all IPs because security threats like access of data by unauthorized persons or ex-employees,   malicious hacking attempts etc can be triggered if access from any IP is enabled.

 I strongly recommend that you keep IP restrictions for XYZ dataset.
  
 If you want to provide access to mobile staff (i.e those on dynamic IP numbers from home or traveling) to corporate software assets like NEOSYS IN A SECURE MANNER, then installation of VPN is the industry standard of achieving this. Installation of VPN is to be done by your own IT support. 
 
 If you still wish to allow access from all IPs, kindly confirm that you acknowledge the security threats of doing so. 
  

Handling requests to create a new feature or modifying existing features

Many issues are small and not important but can still be considered for development because they may be easy and neatly added to NEOSYS. The aim here is to avoid development on hard issues for little benefit, or little issues that make NEOSYS more complex for little benefit.

Any request to create a new feature or modify an existing feature MUST be discussed with other clients before forwarding it to the programmer because the other clients might not be comfortable with the change as it may not be in accordance with their workflow. If other clients agree to the proposed change then support should go ahead and request the programmer to implement it.

A workaround must be given to the user, which is either a permanent solution, for example if the issue is a rare case and not commonly faced by other clients (and the workaround is acceptable to the client), or a temporary solution until some better solution is discovered or can be developed.

Therefore before escalating a request to the programmer to modify a feature in NEOSYS, the approval for the same from other clients must be taken into account.

Updating Clients about unresolved issues

Support should proactively inform clients if an issue is not solved within the same day it was raised, after judging the urgency of the issue and the time it was raised. An email to the client who raised the issue, before the end of each day, is a best practice that keeps the client updated and other support staff too. This email should be sent regardless of the degree to which the issue has been resolved or if the issue is unresolved. If the issue is unresolved, the email should explain why and also explain the cause of delay.

Handling new USER creation

Support staff should create new USERS for clients ONLY when requested by an authorised person.

If the request comes from an unauthorised person, then support MUST reply to the same person informing them that this request must come from an authorised person. Support MUST NOT directly contact the authorised person asking for approval/confirmation because that is client work.

Clients should not be discouraged to create new users. Clients are billed as per user usage which is reviewed periodically. Over time old USERS are replaced with new USERS.

The USER code is the first name of a user.

Support team MUST NOT discuss billings with clients unless authorised to do so.

Support team MUST NOT proceed with creating new users until the following details have been clearly provided by the client, otherwise the user may end up with more than the required authorisation, which can lead to problems in future.

New user requirements :-

• Full name
• Email address
• Group level / User with similar authorisation

Handling letterhead change requests

Support staff should reject any requests that requires the letterhead to be setup on the TESTING dataset before it is setup in the MAIN dataset.This is to reduce double work for support staff and to ensure that clients have a clear understanding of their requirements and also send the correct logo image. The MAIN dataset can be copied to the TEST dataset for any kind of testing.

See How to change letterhead

Handling error messages

Important: Before Attempting to resolve client issues, please ensure that we have secure access to the NEOSYS server.

1. The very first step is understanding client problem. Ask questions to the client until you CLEARLY understand the problem.
2. If the error is familiar and does not require a screenshot, resolve the problem immediately.
3. If the error is unfamiliar and/or requires a screenshot and the user has not sent a screenshot, IMMEDIATELY ask the user to send a screenshot of the problem, along with the options used (basically you need to know HOW to replicate the error and the screenshot MUST show WHAT the error is).
4. If the user says "nothing happens, so no screenshot of the error", then IMMEDIATELY request for screenshots again with the exact steps to reproduce the problem using mouse and keyboard.
5. Upon receipt of the error and steps to reproduce the error, follow the steps and reproduce the error.
6. If the issue is unknown or you don’t understand it clearly, with the users acknowledgement use remote support to gain access to the users desktop to view how to replicate the error.
7. Replicate the error on all browsers after ensuring that the browsers have script error notifications enabled.
8. Check in all the wikis for a solution.
9. If there is no immediate fix for the error, try to find and provide a temporary workaround, which the client can use until the error is fixed.
10. If the error is new, do a thorough investigation (eg. check NEOSYS logs) and try to find a solution for the error.
11. If you still cannot find a fix for the error, then escalate the issue to your manager with an explanation of the issue.
12. Support MUST always provide full screenshots of all the steps required to replicate the error, as this will help identify the cause of the error much quicker.
13. When sending screenshots of the issue to your manager, the top-left of the browser MUST be visible so that it is clear which browser, URL and database is used.
14. Ensure that script errors (if any) are included in the screenshots. Include every detail available regarding the script error, for example: script name, line number etc.
15. Support MUST report the error to support team by email to keep a record of all errors in NEOSYS. Support team looks good when errors are spotted and fixed pro actively. Do not ignore the error for any reason.
16. When requesting the programmer to fix the issue, explain WHAT has to be fixed and HOW it has to be fixed. Refer to Handling request to create a new feature or modifying existing features
17. The most important step when solving any problem is Future Prevention. eg. add the solution to wiki, so that support spends lesser time fixing the problem in future.

Addressing Technical support emails

In the case of technical support issues, address emails to the IT person and cc the complete group of recipients of backup emails and other NEOSYS alert emails. This allows both NEOSYS and client IT staff to take credit for resolving issues that NEOSYS raises instead of working in the background unacknowledged.

Technical support issues include backup failure, server failure, missing alert email, server connectivity issues and port forwarding issues and many other issues.

For technical issues like browser configuration, clear cache, etc. support must send the user a link to the appropriate wiki article to help the user fix the problem. In some cases the user may be helpless and unable to follow the steps to fix the problem. In such cases, support MUST NOT waste time trying to help the user fix the problem, instead support MUST ask the user to get help from the IT person.

Acceptable report format when handling issues in NEOSYS reports

NEOSYS Support must only resolve issues in NEOSYS output first. This is because only NEOSYS outputs can be trusted and user versions in Excel or PDF could be copied wrongly or edited by the user.

In case users send reports in excel or other formats, get them to send the original NEOSYS HTML report as an attachment or copy-pasted in email.

Handling issues with totals on reports

If a client has a problem with any total output by NEOSYS software then NEOSYS support will advise them which other NEOSYS report or reports provide a complete breakdown of the total (if necessary, to individual transactions) and ask the client to locate any offending transactions themselves.

NEOSYS support staff will handle any issues where the total on the breakdown report does not add up to the total on the summary report.

Reconciling totals can be hard if there are many transactions involved. Regardless of how hard it may be, reconciliation is an operational task for users not for support staff since NEOSYS support staff will not get involved in understanding client transactions or data.

Trial Balance and Financial Statements

NEOSYS support staff do not have to prove or trace any figures in NEOSYS Trial Balance Reports or any financial reports. If a figure is stated to be wrong by the user, then NEOSYS support staff should ask for proof or say NEOSYS is confident that the figures are correct unless proved otherwise.

NEOSYS support staff should point out reports in NEOSYS which will support the figures in question but not actually run the reports. Support staff can suggest the users to refer to detailed ledger accounts to prove balances.

Handling issues with Office PBX phones

Support should check their respective Office PBX phones every morning to find out if the phone is up and working. In case Support finds any issue with their phone, immediately fix it so that clients do not lose contact with the Support team via phone. Next send an email to Support inbox mentioning the fault, cause and solution for records/future prevention.

Configuring Browsers to show Javascript errors in NEOSYS

NEOSYS Support MUST ensure the following Settings for browsers because if NEOSYS generates any javascript error message, the same would appear in the bottom left corner of a window, which in turn helps the programmer to fix the error. This must be done after every Factory Reset.

Internet Explorer

Tools > Internet Options > Advanced > Browsing - the items Disable script debugging (Internet Explorer) and Disable script debugging (Other) are UNTICKED.

Chrome

Chrome Menu > More Tools > Extensions > Get More Extensions, search for Javascript Errors Notifier. Add the extension to Chrome.

Firefox

Firebug add-on is used to NOTIFY about script errors because we have no other method to get any warning on screen but you should use the main firefox developer tools to investigate any errors as firebug is essentially replaced by built in developer tools.

For developer tools, go to Tools > Web Console

For enabling notifications of script errors, download the add-on Firebug from here. When a Javascript error is encountered, the firebug icon will report the number of errors.

Handling Browser related issues in NEOSYS

See NEOSYS browser requirements

Clients frequently ask Why NEOSYS doesn't support other browsers

To avoid browser errors, all new users must follow the steps given in Getting started with NEOSYS before logging in to NEOSYS for the first time.

To troubleshoot browser related errors see Troubleshooting Web Browsers

Users must clear browser cache after every NEOSYS Upgrade to avoid errors. See Sample email to clients who face issues due to failure in clearing browser cache

Pop-up blockers and any 3rd party toolbars must be deactivated/switched off or else certain pages and alert messages while using NEOSYS do not appear as a result of blocking from either the pop-up blocker or toolbars with built-in pop-up blockers.

NEOSYS support must ask users to Reset browser (See Reset browser) if they notice any user browsers which have pop-up blockers or 3rd party toolbars installed.

Handling NEOSYS Upgrade

See Upgrading NEOSYS

Using Support Tools

Website Live Support

www.neosys.com is equipped with a Live Support software and clients can visit the website, click on this link and chat with any of our support staff, without the need for any installation. The client has to fill in their name and enter their questions to connect to an available support personnel. During non-working hours, the Live Support icon on the website automatically displays "offline".

NEOSYS Support personnel who are authorised to provide such support, need to login to Live helper chat in Firefox using the link given below:

http://neosys.com/lhc/lhc_web/index.php/site_admin

Support personnel should enter the account details as provided by their Manager.

Enable notifications for Live helper chat so that whenever there is a visitor trying to contact Support team, the Support personnel will get the notifications on his screen. Set the Live helper chat login page as your home page in firefox.

Use the link below to enable notifications:

http://neosys.com/lhc/lhc_web/index.php/site_admin/chat/listchatconfig

After setting up Live helper chat if you sign in to a new profile in firefox, you might have to re enable the notifications after your firefox is synced to the new profile.

Teamviewer

Since Teamviewer allows no restriction on access once a fixed pass is installed, Support must not install fixed pass on teamviewer however convenient it might be.

RULE: NO FIXED PASS TO BE INSTALLED ON TEAMVIEWER IN ANY NEOSYS OR NEOSYS CLIENT COMPUTER

Running teamviewer live from a web link is fine because it does not allow installation of a permanent password

For certain tasks that require temporary install of Teamviewer on the client servers (e.g. upgrading Cygwin remotely), use Teamviewer 7 on the server as well as Support staff computer. Contact NEOSYS IT for commercial license of Teamviewer 7. Teamviewer MUST be uninstalled after usage, otherwise it creates an additional unnecessary security risk.

To support client users who use the latest version of Teamviewer, support staff must also install the latest Teamviewer version available alongside Teamviewer 7.

Documenting Processes in Wiki

NEOSYS Support staff must be in continual learning mode. This is mandatory for support staff and is not an option. Support must read, learn and understand everything in the support emails and ask questions if they don't understand. This understanding must be transferred into wiki in the form of new articles and improvements to existing articles.

For all articles related to formatting and editing in Wiki, see Documenting NEOSYS systems

Avoiding duplication of text in wiki

Duplication of text in wiki is to be avoided almost at any cost. Duplication has the problem that when one copy is changed or improved in future then it is highly likely the editor will fail to update the other copy or copies and wiki will over time become an inconsistent mess.

There are several ways to avoid duplication:

1. Two or more procedures which have significant areas of duplication can be rewritten as a single procedure with alternatives in the middle of the procedure
2. Wiki Templates- Templates reproduce the same text in all places and editing one place edits all places. See How to create templates in wiki
3. Wiki links- Only put the text in one place and put links to that in all the other places that it is appropriate.
4. Place a note in all copies something to the effect that "This is similar to x, y and z". This alerts any future editor of all other places in wiki that might also have to be updated.

Future modifications in one place may or may not be appropriate to other places. The editor must decide whether to change one or all places

Highlighting information in wiki

To highlight particular instructions or info in wiki do NOT invent new styles which are not the way the rest of wiki is done. Instead, follow the USUAL STYLE or open a DISCUSSION with any recommendations you have BEFORE USING THEM.

Instead of using various kinds of highlighting styles like bolding and words like "Note:", use the following words IN CAPITALS especially the word MUST.

The use of the following words IN CAPITALS indicates that you are using them in a special way with formally defined meaning as explained below. Use of the words in lower case indicates that you are using the word in an ordinary commonsense meaning.

• MAY - means optional
• SHOULD - means recommended and you need GOOD reason (not just any weak excuse) to not follow to follow this recommendation
• MUST - mandatory

Only in the rare cases where the consequences of doing or not doing something are irreversible or take a lot of work to reverse then you can use your own additional highlighting methods, eg ALL CAPS, stars, color red etc.

Explain WHY

Any sentence which uses the word "MUST" in capitals, MUST be followed by a SPECIFIC REASON explaining exactly why is the instruction is mandatory; the reason MUST not be vague and non-specific meaning no more than "or bad things will happen".

WRONG way: You MUST also delete ads if deleting schedules.

WRONG way: You MUST also delete ads if deleting schedules otherwise it will cause problems in future.

CORRECT way: You MUST also delete ads if deleting schedules otherwise the deleted schedules' ads will still show in all media-diary like reports and screens

The Wrong way above gives a general reason "it will cause problems in future" which is vague and a reader may even go ahead and ignore "MUST" because there is no objective or proper side effect mentioned for not following the MUST statement. Basically he doesn't understand the point behind following a certain rule.

Whereas the Correct way gives a SPECIFIC reason for "deleting ads while deleting schedules", so reader will exactly know the trouble that will be caused if ads are not deleted. Therefore "SPECIFIC REASON" behind using the word MUST must be to the point and very informative.

Why explain WHY

The information contained in the WHY phrase is often extremely informative to the reader about things that you may otherwise not have considered saying.

The most valuable information is usually contained in the "WHY" of something. There is an apocryphal story of a company where managers could be fired if they gave instructions to their staff without providing explanation. In almost all cases it is better for the efficiency of a team of people that any instructions they follow contain the "WHY" of something. Only in few cases should staff be expected to follow instructions without being well or fully informed.

Use of personal email addresses by NEOSYS support staff

NEOSYS support staff MUST NOT use any personal email addresses for NEOSYS business.

The xxxx.neosys@gmail.com addresses that are created by support staff for themselves on joining are also considered personal email addresses and must not be used for NEOSYS business. These email addresses might be linked to NEOSYS wiki accounts but that doesn't matter because wiki is not confidential.

Accessing NEOSYS accounts on personal devices

NEOSYS staff MUST NOT install NEOSYS accounts on skype/dropbox/gmail (or any other external tool) on their personal devices without written permission from NEOSYS management

Support Staff work-in-progress documents/files

Support Staff must not save working files hidden on their computer. Work that is not visible is not work . Support work should not be done privately and should be shared to all.

ALL personal working files however trivial MUST be stored in Dropbox and MUST NOT be stored anywhere in personal computer (My Documents/Desktop etc.)

The personal encrypted pass file MUST be stored somewhere in personal folder under SB NEOSYS staff in Dropbox. This is because if there is a loss of OS/Computer, it should not lead to loss of access as all the passwords saved in the file will be lost.

Handling CLIENT/NEOSYS Servers

NEOSYS support staff must exercise extreme caution when working on CLIENT and NEOSYS servers. Do not risk making changes without due care and attention to the fact that the consequences of errors can be serious on working production servers.

Handling Javascript Files in NEOSYS

All the files in NEOSYS installation folder with .JS and .JSE extension are the executable javascript files which startup NEOSYS processes (in a usual DOS window). Their default program is 'Microsoft Windows Based Script Host' (wscript.exe). If a JavaScript file is opened using a notepad, the default program may change to notepad resulting in all NEOSYS processes to open up in a notepad.

Hence be very CAREFUL when accessing a .JS and .JSE file and double check that the default program remains wscript.exe. Refer to Fixing NEOSYS process which opens up in a notepad instead of Microsoft Windows Based Script Host in case this issue comes up.

Handling Nagios Client Monitoring system

NEOSYS support staff on duty has to follow the below outlined procedures in case of any Nagios items showing a critical or warning message for any service. Failure to schedule appropriate downtime will lead to REDUNDANT ALERTS from NAGIOS every hour.

1. Nagios is required to be checked first thing in the morning and any critical or warning messages need to be dealt with to resolve the same at the earliest.
2. Some of the messages could be related to backup failures and the usual procedure as stated in Handling failure and warning messages on nightly backup alerts needs to be followed. In case the backup issue isn't resolved by 9:30 am, the Nagios service needs to be scheduled with downtime for a minimum of 2 hours and maximum until 1 am next day if the issue cannot be solved.
3. In case any HTTPS, SSH, PING service or Host is down, immediate action is required and the relevant IT people at the client side needs to be contacted to get this resolved. A downtime of 2 hours is required to be scheduled with further intervals of 2 hours incase this is not resolved. Support staff shouldn't schedule downtime till 1 am next day, just to get rid of the alerts for the day. Proactive follow up with the client is required to get this resolved before the business day - more so, if there is a weekend ahead.
4. In case the HTTPS, SSH, PING service or Host goes down during the day, a grace period of 20 minutes is given before the issue is reported to the client IT. This helps incase there is any temporary internet connection issue at the client or along the internet route.
5. In case of "Backup not changed" warning status which occurs if the client has not interchanged the USB before 12 noon on that day, no action is required from the support staff and a downtime until 1 am next day needs to be scheduled.
6. In case the HTTPS, SSH PING service or Host is down for more than 1 day, client IT should acknowledge the problem and give NEOSYS support staff an approximate time frame before which the issue will be resolved. Set an appropriate downtime for such events.
7. In case Host is down for more than 2 days and there is no progress with the fix from client IT, the client management should be notified about the seriousness of not having access to server and their acknowledgement is mandatory.
8. Support should check Nagios quite frequently during the day to look for any new alerts so that issues are fixed as soon as possible.

Handling lack of remote access to NEOSYS server located in client’s premises

If access to the NEOSYS server is lost then we must determine the root cause by:

1. Checking if the server is UP and running
2. If yes, please check internet connectivity on the server
3. If there is connectivity, please check the router for connectivity issues

Sample Response:

Dear XYZ,

Please note that we have currently lost access to the NEOSYS server. The server seems to be down at the moment and it seems that 
NEOSYS processes are not running on the server.
Kindly check if the server is UP and running. If yes, please check internet connectivity on the server.
Do keep us posted on the server status so we can test connectivity from our side as well.

Best Regards,

New Router (Port Forwarding)

If you have changed your router then you may notice that external access to NEOSYS is unavailable.

Solution:

Setup a permanent access for NEOSYS by reconfiguring the Router / Firewall for Port Forwarding from Router to the NEOSYS Server as follows:

1. Port 19580 > 19580 for SSH
2. Port 4430 > 4430 for HTTPS

You can see Set Up Port Forwarding to learn how to configure your Router.

To see how to test/ troubleshoot port forwarding settings, go to Troubleshooting Port Forwarding.

Sample Response:

Dear XYZ,

You are requested to kindly setup a permanent access for NEOSYS by reconfiguring the Router / Firewall for Port Forwarding from Router to 
the NEOSYS Server,i.e.  port 19580 for SSH and port 4430 for HTTPS.

Once this is complete, kindly send me an email to confirm the same so that we could test connectivity from our end as well.

Best Regards

Creating and Handling passwords

Passwords made out of a pass phrase should be at least 10 characters since using initials results in a lot of i's and a's etc which reduces the effectiveness of the password and allows hacking via brute force guessing especially since windows doesnt slow down logins even if it sees thousands of password attempts.

Creating a password

Passwords are generated from a pass phrase and it is important to create a very difficult to guess pass phrase.

For example, a good pass phrase would be: Today is a good day and it is the best time to go for a holiday

The password for this would be Tiagdaiitbt2g4ah

The important instructions for the above are:

1. You have to take the first letter of each word and that makes your password (i.e. by using initials)
2. Wherever any word starts with a capital, then you have to take first letter as a capital (eg. For Today you will take T)
3. Replace and with &
4. Replace to with 2
5. Replace for with 4

Handling passwords

1. Never send the actual password - always send the pass phrase
2. Make sure that the password created out of the pass phrase is at least 10 characters long since using initials results in a lot of i's and a's etc which reduces the effectiveness of the password and allows hacking via brute force guessing especially since windows doesnt slow down logins even if it sees thousands of password attempts
3. Pass phrases are never to be sent by email, whatever the case maybe.
4. Pass phrases can be sent by chat - however they have to be broken down in two parts and sent separately over two different messengers or if you are using Gtalk then use the 'off the record' mode.
5. Using SMS to send pass phrases is the best known way as of now.
6. If you save the passwords on your system in an file then:
   • Ensure that you only store pass phrases in the excel file
   • Ensure that the excel file is encrypted with a master password

NEOSYS Maintenance Window

The NEOSYS server is functional from 6am – 1am. There is a 5hr window gap for the system to perform updates & backups.

The 5hr maintenance window:-

1. At 1am – The server performs a data backup on a USB (for the respective clients) & once the backup has been completed, the system automatically generates an email addressed to the neosys staff & the respective clients.

2. At 2:45am – The main data over writes the test data on the server.

3. At 3:00am – The server by itself performs an update for Windows.

4. At 4:00am – The server performs a backup to the headquarters for clients, and then automatically generates an email addressed to the NEOSYS staff & the respective clients.

5. At 6:00am – The server starts up NEOSYS.

Using NEOSYS Terminology while communicating with Clients

NEOSYS support must communicate in correct language to clients on finance issues in order to ensure that our records exactly represent reality. Conversely NEOSYS must not use other terminology because it can cause considerable confusion and poor quality results. In case client is new and still in training, use client terminology optionally as long as

1. It is only an addition to NEOSYS standard terminology
2. Only if clear that it is client terminology by putting in brackets like this "Sales Invoices (called PI by you)", where "you" means the client you are talking to or you can put the client company name instead perhaps.

The objective is over time to avoid having the support team to have to know the terminology of the client. NEOSYS support team cannot possibly know and remember it for each client therefore the client MUST over time learn and use NEOSYS terminology. The initial period is one of relearning and translation for the client not for NEOSYS.

Many users operating NEOSYS finance module do not know proper financial procedures and may not appreciate how doing something in a wrong or unusual way now may not be correctable in the future.

NEOSYS staff must follow NEOSYS procedures only. If NEOSYS procedures need to be updated then this must be agreed in advance and not AFTER the fact.

Amending/Reposting Journal Entries

In certain exceptional cases, amending/reposting of journal entries is allowed for a brief period of time to enable clients to present reports in an alternative manner. This would be subject to NEOSYS would requiring a written LETTER OF APPROVAL duly signed and stamped by the highest management of the company.

In case the client management decides to allow editing/reposting of journal entries, the following procedure is to be followed:

1. Client must de-allocate vouchers which need to be amended
2. NEOSYS support staff must wait for a day so that de-allocated vouchers are copied into Test database
3. Authorise required users to amend and repost (without record) in Test database only
   ( While reposting, we have 2 options i.e. with record and without record. The 'with record' option causes the system to maintain a history of edits made. Hence, we want to repost without record so that there is no trace of the edit in the system)
4. Amend a substantial number of vouchers in Test and verify them.
   To verify if the edits made are reflected:
5. *Print all ledgers for the whole year
6. *Cross-check all balances
7. Once you verify the balances are correct in Test database, grant users permission to amend and repost in the Live database.
8. Ask users to amend and repost vouchers in the Live database.
9. Cross-check all balances for the current year.
10. If you successfully verify the balances, revoke permissions immediately. Else, wait for 24 hours and revoke permissions irrespectively.

Removal of unauthorized third-party software on client servers

Rule: Any third party software that is discovered by NEOSYS support staff on client servers that has been installed without the agreement of NEOSYS should be uninstalled immediately on discovery.

However purposeful a software is, NEOSYS is contractually responsible for support and there are too many opportunities for poorly installed software to cause unpredictable damage to the NEOSYS database so NEOSYS has to have a clear and safe and simple policy to ensure the integrity of client data. Installing software without prior discussion with NEOSYS by itself indicates that insufficient care and consideration as been given to possible issues.

Any software required by client IT for some purpose may only be installed after discussion and agreement from NEOSYS support staff concerning the configuration and operation of the software.

The NEOSYS Software Licence and Support agreement requires that where NEOSYS software is installed on client servers that a dedicated server is provided and dedicated implies that no other software may be installed without the agreement of NEOSYS support.

Configuring tunnelier to autologin on opening tlp files

If you have many tunnelier tlp files in a directory and connect by opening the desired tlp file the, instead of opening the file and then clicking Login you can also right click the file and select Connect.

Alternatively, you can configure tunnelier to login (connect) automatically by following the procedure mentioned below. (Even if you configure automatic login, you can still open and not login by right clicking and choosing Open)

Windows 8

Cannot be done using standard Windows UI. Some download utilities can do it. TODO put a safe one in neosys.com/support

Windows XP/Vista/7/2008

1. Go to My Computer
2. Click on Tools -> Folder Options
   
   
   
   
3. Click on File Types
   • Select TLP (Bitvise Tunnelier Profile) [Type "TLP" to find it quickly]
   • Click on Advanced
     
     
     
     
4. Click on Connect and Click on Set Default
   
   
   

International v/s Indian English

There are some words which have completely different meanings in International and Indian English. NEOSYS Staff should follow International English only. Below are the examples of few of those words:

Word: Doubt

In the English language word "doubt" means to distrust an alleged fact on the basis of a reason, depending on the strength of the reason which may be anything from factual to feeling e.g "I have no reason to doubt him". This usage is followed worldwide.

Some people especially from Indian origin use "doubt" when they are unaware about a fact. e.g "I want to clear my doubts about this procedure". This is incorrect. The word must be used when you do not agree on something on the basis of a reason and not when you do not have knowledge about it.