# Support Policy

**This policy explains the support structure and processes in place for platform subscribers/accounts.**&#x20;

## Subscriber Support at a Glance

### How can I get platform support?

Get platform support in three ways:

1. [Access the Knowledge Base;](#what-is-the-knowledge-base)
2. [Use Resolve](#what-is-resolve);
3. [Get in touch with your Support Contact](#who-is-my-support-contact-person).

### What is the Knowledge Base?

**The platform Knowledge Base contains a wealth of information and answers to most questions.** Select the book icon from the backend to open docs, and use the search option to find your answers quickly.

<figure><img src="https://2246165774-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7GYZjOpsTB0hr8aA2Agi%2Fuploads%2Ft8pAmzMFP7NmGWoTcey3%2FScreenshot%202024-07-24%20at%2010.24.32.png?alt=media&#x26;token=3f0dd6c5-7f7d-413a-b5cc-acbbe31e5854" alt=""><figcaption></figcaption></figure>

### What is Resolve?

**Resolve is the built-in chat tool where you can submit tickets to get help.** Use [Resolve](https://app.gitbook.com/o/-LkZMh7HTpHtgrDm7Uox/s/T71L9kat7R1ep26NRpRO/) if you are unable to solve an issue, suspect there may be a bug, or have a question about the platform that is not available in the documentation. If you are unable to solve an  issue, you can escalate it on Resolve using **/escalate**. You may be asked to supply further details about the issue.

[Resolve](https://app.gitbook.com/o/-LkZMh7HTpHtgrDm7Uox/s/T71L9kat7R1ep26NRpRO/ "mention")

### **What is a ticket?**

**A support ticket describes the issue you are having and allows you to share and track that issue with your support provider.** Tickets are posted on the platform's [Resolve](#what-is-resolve) tool, and can be [escalated](#what-is-the-ticket-escalation-process).

### **Who submits tickets?**&#x20;

Anyone on the [Subscriber's](#support-roles) account can submit support tickets via the [Resolve](https://app.gitbook.com/o/-LkZMh7HTpHtgrDm7Uox/s/T71L9kat7R1ep26NRpRO/) tool or directly via their [Support Contact](#who-is-my-support-contact-person).&#x20;

### Who receives my tickets on Resolve?

When a ticket is submitted on Resolve it is automatically escalated to the [Platform Operator](#support-roles)'s account (as well as to anyone who has been assigned the support role). The [Platform Operator](#support-roles) and/or the assigned Support Contact will be alerted (via email and a platform notification) and will respond via the Resolve chat.

### Can the end-user /  app user submit tickets?

**App users have access to the** [**App Help**](https://app.gitbook.com/o/-LkZMh7HTpHtgrDm7Uox/s/peslwaFKE1IFFVtJvP6i/) **docs.** In the app account/profile section, app users can access a support link to get in touch with the [Subscriber](https://everyday-digital.gitbook.io/guidelines-and-policies/support-roles#platform-subscriber). End-users do not use Resolve to submit tickets, but if a [Subscriber](https://everyday-digital.gitbook.io/guidelines-and-policies/support-roles#platform-subscriber) sets up their own ticketing system, then app users can post tickets there.

### Who supports the end-users (app users)?

**Subscribers support their End-Users.** The Platform [Subscriber](#subscriber) is responsible for supporting their own end-users, but may outsource this service to their [Platform Operator](https://everyday-digital.gitbook.io/guidelines-and-policies/support-roles#platform-operator) upon such agreement. [Subscribers](https://everyday-digital.gitbook.io/guidelines-and-policies/support-roles#platform-subscriber) should aim to be familiar with the platform and equipped to handle most queries not identified as errors.&#x20;

### How long will I wait for a response to my ticket?

Responses are usually issued within 24 hours (Mon-Fri, 9am-5pm). Please refer to the [#issue-types-and-resolution-times](#issue-types-and-resolution-times "mention")

### What is the ticket escalation process?

➼ Ticket created by any platform account user ([Subscriber](https://everyday-digital.gitbook.io/guidelines-and-policies/support-roles#platform-subscriber)) ➼ submits ticket on Resolve\
➼ Ticket received by [Platform Operator](https://everyday-digital.gitbook.io/guidelines-and-policies/support-roles#platform-operator) ➼ resolves the ticket or escalates it to\
➼ [Platform Provider](#support-roles) ➼ assigns [severity level](#issue-types-and-resolution-times) and replies to Platform Operator  \
➼ [Platform Operator](https://everyday-digital.gitbook.io/guidelines-and-policies/support-roles#platform-operator) communicates with [Subscriber](https://everyday-digital.gitbook.io/guidelines-and-policies/support-roles#platform-subscriber) until the issue is resolved.

### What are the Support Hours

Escalated tickets will be typically be attended to Mondays to Fridays during the hours of 09.00 to 17.00, South African Standard Time (SAST).

### Who is my Support Contact person?

**Depending on the subscription plan or agreement, you may have access to a dedicated support person or team.** All subscribers have access to [Resolve](https://app.gitbook.com/o/-LkZMh7HTpHtgrDm7Uox/s/T71L9kat7R1ep26NRpRO/) to ask for personal assistance.

### Who provides platform training?

[Platform Operators ](#platform-operator)are responsible for providing adequate platform guidance and training to their [Subscribers](#subscriber).

## Support Roles

There are three primary [support roles:](#support-roles)

1. [**The Provider: Core Development, Maintenance & Escalation Handling**](#platform-provider)
2. [**The Operator: Subscriber Support & Escalations**](#platform-operator)
3. [**The Subscriber: Internal and End-user Support** ](#subscriber)

## Support Restrictions

### What is typically excluded from support?

**External issues.** The [Platform Provider](#support-roles) and [Operator](https://everyday-digital.gitbook.io/guidelines-and-policies/support-roles#platform-operator) do not typically support any issues that are due to: connectivity/ISP provider issues, email issues, third party software, [Subscriber](#subscriber) and/or end user incorrect app use, custom requests and/or custom scope work.

### What if I have a feature request?

**The platform is a Software-as-a-Service and is generally provided as-is.** In the interest of platform improvement, regular updates and new features are developed. Isolated features and custom development may on occasion be accommodated at an additional fee. Custom development that is worked into the platform's core technology is made available non-exclusively to the [Subscriber](#subscriber).

### How can I get integration support?

**Custom requests and consultations.** When integration and/or custom requests are made, consultation with a [Solutions Architect](#solutions-architect-consulting) may be needed.&#x20;

### How are feature and custom requests handled?

1. **Feature Request.** This can be any request submitted by the [Platform Operator](#platform-operator) to the  [Platform Provider](#support-roles) for a platform feature change or new feature development. Such a request will need to be scoped and scheduled into production at the discretion of the  [Platform Provider](#support-roles). Feature requests may include an implementation fee and/or a development cost.
2. **Custom Request.** This is a request that is related to a single [Subscriber](#subscriber)'s specific need. For example, a [Subscriber](#support-roles) needs a certain feature that will not be adopted across the platform. Any custom requests will begin with a [Solutions Architect consultation](#solutions-architect-consulting) at the expense of the Subscriber.

### What is a Solutions Architect?&#x20;

**A Solutions Architect can assist with integrations, webhooks and complex solutioning.** The Solutions Architect services may be offered by either the Platform Provider or Operator at an hourly rate (pricing made available on request).

1. **Availability.** The Solutions Architect may be available upon request and without prior notice.&#x20;
2. **The Solutions Architect role may include, but is not limited to:**
   * Implementation and Integration Solutioning
   * Technical Consulting
   * Technical Sales Guidance
   * Technical Documentation
   * Platform Security Consulting
   * Platform Infrastructure Consulting
   * Technical Policy Development&#x20;
   * Implementation Guidance
   * Integration Guidance
   * API Guidance
   * New Feature Implementation
   * Bespoke Feature Development
   * Licensee technical support and error handling
   * Innovation Investment
   * Other services/attendances which may be agreed to between the parties
