Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Schedule

Support LevelDaysIsrael (GMT+2|3)US Eastern (GMT-5)UK (GMT)
RegularMon - Thu9 am - 5 pm2 am - 10 am11 am 7am - 7 3 pm
ExtendedSun9 am - 5 pm2 am - 10 am11 am 7am - 7 3 pm
ExtendedMon-Thu5 pm - 9 pm10 am - 2 pm7 3 pm - 11 7 pm
ExtendedFri10 am - 4 pm3 am - 9 am12 pm 8 am - 6 2 pm
Emergency24X7All Other Times
                                                          Daylight Savings Time applies to all times listed aboveWhen clocks adjust for Daylight Savings Time, the above table may not be accurate until all countries are aligned.

Regular support is available to all customers of Agat products.

For regular and extended support email support@agatsoftware.com

...

Critical

Customer's business has significant loss of or degradation of services

More than 3 end users are affected

UC product (Teams, Webex, etc) is down due to Sphereshield

High

Outage or performance degradation affects several users at a site

Critical product functionality does not work

Medium

Customer's business is substantially functioning with minor or no impediments of service

Affects a single user

Does not prevent user from performing their job

Non-critical product functionality does not work

Low

Training

Product information and questions

Planning a scheduled deployment or upgrade

...

Customer Guidelines for Receiving Support

All electronic communications with Customer Support must be via email to support@agtsoftware.comThis will create a ticket in our Zoho ticketing system and will auto-reply with the ticket number in the Subject line. Messages to individual technicians or via other communication methods may not receive a reply in a timely fashion or at all.

Report every independent issue in a separate ticket.  Avoid mixing several unrelated issues in the same ticket .

Subject -The subject of the email should include a short description of the issue or question

In the email message body include :

  1. Description - more detailed description of the issue or question.   Include screenshots or copies of any relevant information.
  2. Priority - objective priority of the issue, ie high, medium, low, etc.    
  3. Scope - number of users or systems are effected by the issue.   If specific users, provide details.
  4. Time - the date and time of the incident or issue.  Specify your time zone.
  5. Users - the full username(s) used to sign in that experienced the issue (the "display name" is insufficient). If more then one user is affected, specify as many users as possible
  6. Reproduce - Steps to replicate the issue, as precise and detailed as possible.   Example: Create a meeting from the meet now button in the Teams calendar tab. Add an external user. Try sharing your desktop.

If you use the Sphereshield proxy include:

See Also: