How are Polyosync support tickets prioritized, and what information helps determine urgency?
Support ticket priority helps determine how an issue should be assessed and handled.
The urgency of a request is not always determined by how inconvenient it feels to an individual user.
Technical impact, operational scope, security implications, and contractual support arrangements may all be relevant.
What factors help determine priority?
1. Whether the issue prevents essential business operations.
2. Whether one user or an entire organization is affected.
3. Whether customer-facing functionality is disrupted.
4. Whether sensitive data may be exposed.
5. Whether a critical automation or business process is unavailable.
6. Whether a practical workaround exists.
7. Whether the problem is ongoing.
8. Whether the issue affects an Enterprise service covered by specific contractual support terms.
Examples of different impact levels
A cosmetic interface issue that does not affect functionality generally has a different operational impact from a complete inability to access a business workspace.
A failed non-critical workflow may have a different impact from an unavailable customer-facing process that prevents an organization from serving customers.
A credible security incident requires careful assessment regardless of whether the visible impact initially appears limited.
How can I communicate urgency?
Explain the business impact in concrete terms.
For example:
"The customer-facing AI Employee is unavailable, and customers cannot complete the affected interaction."
Or:
"An automation used for internal reporting has failed, but employees can temporarily complete the task manually."
These descriptions provide more useful context than simply writing "Urgent."
Can I choose my own ticket priority?
The ability to select priority depends on the support interface and account configuration.
The final handling of a request may depend on its assessed severity and applicable support arrangements.
Does Enterprise automatically mean every request receives the highest priority?
No such assumption should be made.
Enterprise support arrangements may include specific service levels, but these depend on the applicable agreement and account configuration.
Does priority guarantee a particular resolution time?
No.
A priority designation alone is not a guaranteed resolution deadline.
Any contractual response commitments should be interpreted according to their specific terms.
Recommended practice
Describe the operational impact accurately and distinguish between inconvenience, service disruption, and potential security incidents.