Support Policies.
Dimdim is committed to resolving customer problems quickly and professionally.
Please contact Dimdim by raising your support request via the forums at
http://forums.dimdim.com/forum/ Your support request will be addressed by Technical Support Team members and suggest a resolution either Knowledge Base Articles or additional troubleshooting steps.
You can also search the Dimdim Knowledgebase here
http://help.dimdim.com/activekb
- The Technical Support Team assigns case priority based, in part, on the urgency that you indicate.
- After reasonable troubleshooting an unresolved case will be escalated to Engineering directly for resolution.
Note: Enhancement and bug requests also funnel in through the same ticketing process. Typical resolution for enhancements will be bugs filed with Enhancement and bug requests also funnel in through the same ticketing process. Typical resolution for enhancements will be bugs filed with Engineering who will work with the Support team to provide target release dates. You can always check enhancement and bug status at
http://support.Dimdim.com.
Response Times
Initial response times are dependent upon urgency and criticality assigned to support requests which can be either Bugs, Enhancements requests or General Tasks. Categories are as follows:
Blocker ( Highest - Showstopper): This category is defined when any of the following events happen:
The product is unusable.
No workaround available.
Major feature not working.
Install Failures - of publisher & servers.
Performance problems rendering the product unusable
Usability problem leading to a major expectation failure
System outage leading to loss of business
Critical - (Showstopper with workaround):This category is defined when any of the following events happen:.
The product is unusable but a straightforward workaround exists.
Major feature not working as expected.
Tier 2 platform (e.g MAC/Linux Presenter) specific problems.
Typos in high exposure screens.
Usability problems with major features.
Major - (Feature not working under specific conditions): This category is defined when any of the following events happen:
New Documentation needed.
Documentation Errors.
Typos in low exposure screens & error messages,
Usability problems with minor features.
Intermittently reproducible issues.
Minor – (Minor Feature not working under specific conditions): This category is defined when any of the following events happen:.
Improvements & Enhancements
Trivial – (Lowest level.): This category is defined when any of he following events happen:.
Typos in screens not normally encountered.