One queue for every app
Add a project for each app, launch page or store. Work through incoming conversations together, then filter by project when you need to focus. Your browser can finally stop looking like a support control tower.
Customer support for every Shopify app you build — in one shared inbox.
Connect your merchant data with the Orka SDK. See their Shopify plan, app subscription, installation date and custom attributes beside every conversation.
One inbox for your apps ↗See the merchant context ↓A merchant asking about a booking form should not get the instructions for a bundle discount. Orka keeps the project attached to the conversation while your team stays in the same inbox.
Add a project for each app, launch page or store. Work through incoming conversations together, then filter by project when you need to focus. Your browser can finally stop looking like a support control tower.
See the relevant merchant information your app supplies. A new trial, a long-time paid customer and a first-day installation need different explanations. Start with that context instead of asking everyone to repeat it.
Reply yourself, review an Orky draft or enable automatic answers from your knowledge. Keep a human in charge of exceptions and sensitive decisions. A busy launch does not have to mean abandoning your inbox.
Give teammates access to the projects they support. Assign the conversation, leave a private note, mention the person who knows the answer and keep the handover in the thread.
Your app already knows a lot about this merchant.
Give your support team the useful part.
Can I add another team member to my booking calendar?
Absolutely. Let’s check your team settings together 👋
Fictional merchant, email and account values. Your app sends the fields you choose.
Use the Orka JavaScript SDK — available as the orka-web-sdk npm package — to send the visitor attributes your team needs: Shopify plan, app subscription, installation date, billing type, usage tier, branding status, internal admin links or onboarding progress. The example fields are just a starting point. Update them when the merchant changes plans or their setup evolves. Those details travel with the support experience instead of living in another admin tab.
Explore the SDK and custom visitor data ↗
Install the SDK in your SPA ↗
Your integration decides which attributes to send. The widget does not grant access to Shopify’s Admin API, infer a subscription or read a merchant’s private account on its own. Source account-specific values from your authenticated backend and keep them current.
Bring the booking context into the conversation. Point to the availability article, ask for the missing detail and hand it to someone who knows the setup when needed.
Use a product guide for the standard setup. Keep download access and account-specific checks with the right person rather than improvising a promise.
Help the merchant understand language-based images, then inspect their configuration when a general article does not explain the result.
Start with the customization documentation. Keep screenshots, theme context and any private handover in the same support conversation.
Example support scenarios, not quotes from customers or claims about these apps’ internal workflows.
Every plan includes the help center. Publish Markdown articles, group them into collections, use your own domain and bring existing content from tools such as GitBook, Intercom, Crisp, Gorgias or Gleap.
Merchants can search and read answers inside the widget before starting a conversation. Multilingual articles and automatic translation help you cover more languages; manual edits let you correct the details. Published knowledge also gives Orky a foundation for drafts and automatic replies.
Explore the help center ↗Keep the name, knowledge and merchant context clear. All those projects can feed the same support inbox.
Copy it from Settings → your project → Installation. Put it once in the embedded app’s shared head or equivalent script loader, and test navigation inside Shopify Admin.
Shopify’s Support API lets eligible embedded apps register a handler for the Admin Support button. Your developer can connect it to Orka’s opening action. The support-link extension must point inside your app for the handler to apply.
Check the project label, merchant attributes and reply delivery with a test merchant. Test on narrow screens too. The install is ready when the whole round trip works.
A widget in your app admin supports the merchant using your software. To support shoppers on a storefront, follow the separate Shopify store installation guide.
One person. Unlimited projects.
Up to three people.
Up to twenty people.
Help center included on every plan. AI usage is separate. Full plans and AI conversation calculator ↗
Still wondering about something?
Ask a human at Orka ↗
For a founder or small team supporting several Shopify apps, Orka is built around that exact job: all project conversations in one inbox, merchant context, a help center and optional AI. If you need a specific enterprise process or a native commerce action, compare that requirement directly. “Best” depends on what your team actually needs.
A new app becomes another project in the same inbox. You do not need a separate support browser tab for each app. Conversations retain their project context, and you can focus on one project or handle the shared queue.
Yes. An app developer helps merchants configure software, understand app billing or troubleshoot an integration. A storefront team helps shoppers choose products, track deliveries and understand returns. Orka supports both contexts, and you can keep them as separate projects.
Cowlendar, BIG Digital Downloads, EZ Product Image Translate and Rapi Bundles use Orka. The app cards above link to their own Shopify listings.
Yes. Use Orka’s visitor-context SDK to attach the relevant information your app already knows. Keep the Shopify plan and your own app plan in separate fields. Your app supplies and refreshes these values; adding the widget does not automatically fetch private Shopify data.
Yes. Relevant attributes can include installation date, app plan, store domain, app version and onboarding stage. Send only information that helps with support, from a trusted source in your app.
Add your project’s snippet once in the shared head or equivalent script-loading layer of the embedded app you control. That is different from inserting it in a merchant’s storefront theme. Test it inside Shopify Admin, including navigation and smaller screens.
Shopify provides a Support API for a custom handler when the support-link extension points within your app. Your developer can connect that handler to the Orka widget opening action. Confirm the current App Bridge setup and test it in the embedded app.
Solo is free for one person, with unlimited projects and the multilingual help center. Pod is $29 per month for up to three people and Fleet is $99 per month for up to twenty. AI usage is separate.
Yes, when the answers are covered by your published articles, website or other configured knowledge. You can choose AI drafts that a person reviews, or automatic replies. Escalate uncertain, account-specific or sensitive issues to a human.
Do not assume that. Explaining a documented billing policy and executing a billing action are different capabilities. Use a person or an explicitly configured and verified integration for account changes.
Organize support around the correct project and its knowledge. Orka’s help center supports Markdown articles, collections, custom domains, imports, multilingual content and automatic translation. Visitors can read articles through the widget’s Help tab.
Yes. Two-way chat translation keeps original and translated messages together. Help-center articles can also be translated automatically and corrected manually. On Solo, conversation translation requires your own AI provider key.
Yes. Choose project access for each teammate, then use assignments, private notes, mentions and reminders to coordinate work. A shared inbox does not mean every teammate must see every project.
Orka supports imports from providers including GitBook, Intercom, Crisp, Gorgias and Gleap. Review links, formatting, collections and billing policies before publishing imported articles.
You keep one queue, with project labels and visitor context. Use assignments and priority signals to decide what needs attention. Orky can cover documented questions, but it does not remove the need for human judgment during incidents.
There is no guaranteed rating or review outcome. Orka gives you a way to answer clearly and consistently. Product quality, resolution, expectations and the merchant’s experience still determine their reaction.
Yes. You can support Shopify apps, SaaS products, websites and shops from the same inbox. Each project has its own identity and installation snippet.
Written by Orka. Valid as of September 2026. Platform requirements can change. Corrections are welcome at [email protected].
Unlimited projects. A free help center.
A human when it matters, Orky when you need a hand.