...
The Support Team operates to deliver customer assistance throughout the entire case lifecycle. With dedicated Support Engineers, this team plays a vital role in addressing customer inquiries, resolving issues, and contributing to the user experience.
Support Engineers: Navigating the Case Lifecycle
Our skilled Support Engineers serve as a point of contact for our valued customers when a problem arises. They have a great knowledge of the product, enabling them to provide insightful guidance and solutions.
Key responsibilities of Support Engineers include
Case Management and Customer Communication
From the moment a customer submits a query or encounters an issue, Support Engineers take care of managing the case. They maintain communication with the customers, ensuring a clear understanding of the problem at hand and keeping clients informed about the progress of their cases.
Troubleshooting Expertise
Support Engineers use their technical knowledge to diagnose and address customer-reported issues.
Bug Reproduction and Resolution
In cases involving software issues or anomalies, Support Engineers reproduce reported bugs. Additionally, they collaborate closely with the Development Team to ensure timely resolution and seamless updates.
Collaborative Approach for Complex Cases
...
If the customer was to experience any issues related to the Support Team, here is the Support Escalation Path:
Level | Title: |
1 | Customer Success Manager |
2 | COO - Chief Operating Officer |
3 | CEO - Chief Executive Officer |
Incident Category Definitions
Severity | Definition | Criteria |
Level 1 - Critical | Critical production issue affecting all users, including system unavailability and data integrity issues with no workaround available. | Functions
Data
Back End
|
Severity | Definition | Criteria |
Level 2 - Urgent | Major functionality is impacted or significant performance degradation is experienced. Issue is persistent and affects many users and/or major functionality. No reasonable workaround is available. | Function
Data
Back End
|
Severity | Definition | Criteria |
Level 3 - High | System performance issue or bug affecting some but not all users. Short-term workaround is available, but not scalable. | Function
Data
Back End
|
Severity | Definition | Criteria |
Level 4 - Medium | Inquiry regarding:
Reasonable workaround available. Resolution required as soon as reasonably practicable. | Function:
Data
Back End
|
Case Reason definitions
Reason | Definition |
Bug | An anomaly, unexpected or irregular behavior or errors. |
Question about handling | Any doubts or questions about the product, questions on the documentation, responding to questions on new ADvendio functions, support if documentation is not (yet) available, support for incomprehensible functions. |
Customization / development request | If the customer has a requirement for a customization unique to their business needs. |
Feature request | If there is a feature which could benefit the product as a whole. |
Target Initial Response TimesFor
customers without a Depending on the Premium Success Plan , we aim to contact you within 2 business days. The Target Initial Response Time varies for customers with a Premium Success plan, as this depends on the and severity of the case . See the table below for further details:
...
*our target initial response time ranges from 2 hours - 2 business days.
Target Initial Response Time for Premium Success Plans and Basic Success Plans include business hours only and excludes weekends and public holidays.
Info |
---|
Support Process Flow
...