The in-app support channel requirement: what reviewers check and how to build a support process

What changed, and when

On July 14, 2026 Zid published a changelog post titled "Add a Working In-App Support Channel". It states that every app must include a visible, working support channel inside the app, so merchants can reach your support team without leaving the app or hunting through your website.

• The channel had to be added before July 17, 2026.
• Starting July 17, 2026, any app in review without one is rejected.
• A dead link or an unattended inbox does not qualify.

Zid's stated reason: merchants need a reliable way to reach app developers while using the app, and a working support channel reduces unresolved issues and builds trust. The item is now part of the App Review Requirements Checklist in the help centre.

What counts as an in-app support channel

Any one of the following is accepted:

• A live chat widget.
• An in-app contact or support form.
• A direct link to a ticketing system.

Per the announcement and the review checklist, the support contact (email, chat or ticketing link) must be actively monitored, and you should disclose an expected response time where possible. The in-app channel is separate from your App Market listing contact info: merchants must be able to reach it from inside the app itself, at the point where they need help.

Listing support: what's still required

The new channel doesn't replace the Support your customers requirements. The App Market doesn't provide merchant support for third-party apps, and developers are required to support merchants in a timely manner:

• Maintainer E-mail: a required field and the basic support method. It must be an active, valid address.
• Support portal URL: optional, such as a forum or ticketing system. You can mention it in your app description.
• Phone number: required for shipping apps only.
• Where to set it: in the Partner Dashboard, click the edit icon on your app, then enter the technical support email (and mobile number for shipping apps) under General Data.

When merchants hit a problem they can click Report Application, choose an issue type, describe it and attach files. The App Market team evaluates the report and loops you in; you provide the needed help and bug fixes. A monitoring mechanism checks that response times follow the agreed ticket resolution SLA.

Build the channel into your app

If your app is embedded, it runs inside the merchant dashboard in an iframe, so put the support link in the app's own interface, not on your external website. A simple header that shows the link on every screen:

<header class="app-header">
  <h1>Shipping rules</h1>
  <!-- visible on every screen, opens your chat, form or ticketing page -->
  <a class="support-link" href="/support/new?screen=shipping-rules">
    Contact support
  </a>
  <small>Typical reply: within [your committed time]</small>
</header>

• A good practice is to attach the screen, app version and store from your server-side session to each request, so the merchant doesn't retype what you already know.
• Never ask for access tokens, API keys or Zid passwords in your support form; the activation policy prohibits collecting them from merchants.
• Test the channel yourself on a development store: submit a real request and confirm it reaches the right team.

Response times and your support process

Zid asks you to disclose an expected response time where possible, and the theme manual article recommends including support contact details and response hours. The process itself is up to you; these are general practices that help you keep what you promise:

1. Define priority levels, for example: service down, a bug affecting orders, a how-to question.
2. Commit to a first-response time per level that you can actually meet, and show it next to the support link.
3. Route every channel (chat, form, maintainer email, reports forwarded by Zid) into one queue with a daily owner.
4. Give reports coming through Report Application clear priority, since Zid monitors them.
5. Turn repeated questions into FAQs and in-app guidance, and review the numbers monthly.

Zid notes that exceptional support increases merchant satisfaction and leads to better reviews and higher sales.

Before you submit: what to check

• The support link or widget is visible inside the app on the screens where merchants need help, not only on your website.
• The channel works: the form submits, the link opens, and chat is answered by a person or a monitored system.
• An expected response time is shown next to the channel where possible.
• The Maintainer E-mail in the Partner Dashboard is active and monitored, and a phone number is added if yours is a shipping app.
• Your support portal is mentioned in the app description, if you have one.