Merchant support

How support cases from merchants reach your organization, and every way to answer them.

Merchants who use your listed apps and themes open support cases with you through Tringify. A case belongs to your developer organization, carries a snapshot of what the merchant agreed to share, and is answered by your team in the Developer Portal, the CLI, the developer MCP or your own help desk. Tringify steps in when a merchant asks after 3 business days without a reply.

Where cases start#

Entry point

entry_point

Notes

Get help in Store Admin

store_admin

On your app’s or theme’s page. Always on.

Help Center Contact support

help_center

Store tab, topic Apps or Themes. Always on.

Inside your app

app_bridge

support.open() from App Bridge. Can be turned off.

App Store or Theme Store listing

app_store, theme_store

Shown to merchants who have it installed.

Merchant AI assistant

mcp

Store MCP tool create_support_case. Can be turned off.

Your app’s backend

app_api

Store API support cases.

Every app with Marketplace distribution, every private app built by a developer organization, and every Theme Store theme takes cases. Themes a merchant uploaded themselves have no developer, so those questions go to Tringify.

What a case contains#

  • display_number such as C-20418, subject, the merchant’s messages and attachments.

  • about: the app (apps.id) or theme (Theme Store listing id) and its version when the case was opened.

  • store: id, name, plan and region. The requester is shown by first name only; you never see a merchant’s email address, and merchants never see your team’s.

  • shared: the snapshot the merchant saw before sending: store, install date and plan, and optionally up to 20 groups of app errors and failed webhooks (or theme editor errors) from the last 7 days. Never customer data, payloads or email addresses.

Statuses#

display_status

Stored status

Meaning

needs_reply

new, open

The merchant is waiting for you.

waiting_for_merchant

waiting_on_customer

You replied. Closes after 7 days without an answer.

with_tringify

any open status

The merchant escalated; Tringify support answers too. You can still reply.

solved

solved

The merchant can reopen it within 7 days by replying.

closed

closed

Final. New messages are refused.

Escalation#

When a merchant message has waited 72 business hours (Monday 00:00 to Friday 24:00 UTC) without a developer reply, the merchant may ask Tringify to step in, once per case. You get support.case.escalated and an email. A member can also hand a case to Tringify with Send to Tringify (POST /cases/{id}/handoff), which opens a linked Tringify ticket.

Listing signals#

Listings show the median time to your first reply and the share of good ratings once an app or theme has 10 answered cases in 90 days (satisfaction also needs 5 ratings), plus your own response target from support settings. They come from daily rollups, so a change shows within a day.

Answering#

Tool

Signs in with

Docs

Developer Portal › Support

your account

Help Center

tringify support …

your account (tringify login)

CLI

Developer MCP

your account (OAuth)

list_dev_support_cases and related tools

Your help desk

a Developer API token (tdv_…)

Support API, webhooks