Qualify your requests correctly to ensure an asnwer adapted to the criticality of the situation.
When creating a ticket with SatisFactory's Support, you are asked to define the priority level of your request.
This choice is decisive because it defines the intervention delay (SLA - Service Level Agreement) that our teams commit to respecting.
Priority levels overview
To help you select the right level, here are the detailed definitions for each priority.
| Priority | Definition |
| Low |
This level concerns requests of an aesthetic or comfort nature that do not obstruct your daily work. Definition: The anomaly has a low impact on the use of the platform and can be corrected during a future update. Impact: Slight inconvenience, without major functional impact. Examples:
|
| Normal |
This is the default level for most questions or minor incidents. The platform remains usable despite the problem. Definition: The anomaly causes a minor malfunction which can be annoying but does not prevent the use of the platform. Impact: Does not affect all users or concerns a minor feature of the platform. Examples:
|
| High |
This level is reserved for problems that handicap your activity, but for which a temporary solution (workaround) exists. Definition: The anomaly has a major impact on the use of the platform, but a workaround is possible. Impact: Affects a significant share of users or concerns a major feature of the platform. Examples:
|
| Urgent |
This level is a critical alert. It means that you are totally blocked. Definition: The anomaly totally prevents the use of the platform or a critical feature. No workaround is possible. Impact: Affects all users or concerns a function essential to the activity. Examples:
|
💭 In case of doubt about the criticality of your request, prioritize the "Normal" priority level. Our teams will adjust the priority if necessary after the first analysis.
To be informed in real time of maintenance and incidents on the platform, subscribe to our Status Page.
For further assistance or to report a specific issue, please contact our Support team.
Comments
0 comments
Article is closed for comments.