Support follows the agreed service.
A marketing website enquiry, an implementation project and an operational product have different support needs. Confirm which service the request concerns and which team owns the next action.
This overview does not create a response-time, uptime or round-the-clock staffing commitment. Any applicable support hours, severity definitions and service-level targets belong in the relevant agreement.
Make a support request useful.
Describe the affected product or workflow, the time of the issue and what you expected to happen. Include a safe reference or non-sensitive example where helpful. Never send passwords, private API keys or unnecessary customer data in a general support message.
- The affected task and observed behavior.
- The impact on users or operations.
- Any safe steps that reproduce the issue.
- A contact and the appropriate existing account reference.
Separate platform and provider responsibilities.
An issue may involve application code, customer configuration, an external provider, account permissions or an upstream outage. The operating plan should identify who investigates each part and how status is communicated.
Monitoring, recovery, backups, credential rotation and third-party escalation should be scoped before release rather than assumed from the presence of a support email address.
Find the appropriate next step.
For a general ZARIS enquiry, contact [email protected] and identify the service you use or want to discuss. Existing customers should follow their agreed support process where one has been provided.
For a new implementation, include support ownership and availability requirements in the proposal discussion so they can be reviewed explicitly.
Questions? Contact [email protected].
