Assure has a 24×7 dedicated team to provide you with support and help you with trouble shooting. Clients can find answers to common issues (and raise support tickets) via our Support Portal.

Increff Customer Support Portal

Feature Requests and Customization

New features requests from clients, can be taking into the road-map if it improves the product as a whole and is beneficial for many other clients.

If a feature request cannot be directly incorporated into the product, then Increff can develop additional wrapper software to support specific requirements.

New Release Deployments

We take downtime permissions from customers before any new release deployments

SLA Metrics

Definitions

Acronym	Definition
P1	Software system is inaccessible or disruption of service as a result of bug, system configuration issues, data inconsistency issue
P2	Minor usability fixes or feature requests which take less than 2 weeks to implement
P3	Major usability fixes or feature requests which take 2 weeks to 4 months to implement
MAT	Mutually agreed timeline

SLA (in days)

RCA: Root cause analysis, TTR: Time to respond, TTF: Time to fix

Priority	RCA	TTR	TTF	Total
P1	System inaccessible due to networking, operating system, cloud related issues	0.5	0.5	1
P1	Minor Bug which takes less than 1 day to fix	1	1	2
P1	Major Bug which takes more than 1 day to fix	1	3	4
P1	Software scalability issues	1	7	8
P1	Data inconsistency issues (if any)	1	7	8
P2	Minor usability fixes or feature requests which take less than 2 weeks to implement	14	MAT	MAT
P3	Major usability fixes or feature requests which take 2 weeks to 2 months to implement	30	MAT	MAT

Note

P2 and P3 will be taken only if the request makes sense as part of the product (feature wise or architecturally) and can be accommodated in the road-map.

Also, in case Increff needs some data / responses from the client to fix the P1 issue, then SLA will be void.