Support for the apps you ship, with the merchant’s data on screen.
Merchbox puts a chat window inside your Shopify app’s admin, shows the merchant’s plan, quota and recent events next to their question, and follows up by email when they step away.
Open · 4
embed.off · yesterday 18:42 · theme “Dawn” publishedMerchant
Recent events
What merchants get
They never leave your app. The chat opens where they are, remembers who they are, and finds the article before they finish typing.
Chat inside the admin
One script tag in your app. The merchant is signed in already, so the thread knows their shop, name and email without a form.
help.yourapp.com/a/getting-startedGetting startedSetting up takes four steps, and the setup guide on the app’s home page tracks them for you…A Help Center on your domain
Write articles in Merchbox or let an agent write them. They open inside the chat window, on your own domain, and the widget suggests them as the merchant types.
Email when they step away
A reply nobody read in the widget goes out by email a few minutes later, and their answer by email lands back in the same thread.
What your team sees
The merchant’s own app data sits beside the message: plan, quota, embed state, the last events. Most questions answer themselves.
Who is in the app right now
Live contacts show every merchant with your app open, the page they are on, and a button to write first.
Flows on app events
Your app pushes events; Merchbox sends the email that fits: welcome, nudge, win-back, digest. Templates with a visual editor, stats per send.
Hours, team, AI drafts
Business hours set what the widget promises. Invite teammates by email. The AI draft cites your own Help Center articles, never invents.
For developers
Two lines in the admin layout and a signed identity token. Everything else is an API you already know.
// your app's admin layout <script src="https://merchbox.io/sdk.js" data-key="pk_…" data-identity="{signed shop + email}"></script> // push what the merchant's profile should show POST /v1/customers {shop, plan, quota, …} POST /v1/events {shop, kind: "embed.off"}
- Identity is signed server-side with your project secret; the browser can’t forge a merchant.
- Profiles and events arrive over REST, show up next to the thread, and drive flows.
- MCP server so your coding agent can read the inbox, write Help Center articles and change settings.
- One account, many apps. Each app is a project with its own key, widget, Help Center domain and email sender.
Open the inbox
Sign in with your work email. A link arrives, no password.