Shopify support + sales app

More sales, fewer tickets, one live inbox.

AI support for Shopify stores that recommends products, answers delivery questions, tracks orders, and hands over to your human team without losing context.

24/7 AI first replies when your team is offline
1 inbox Support, sales, order questions, and team handover
ROI-led Track chats influenced, conversions, and saved support time
Live product example Three believable flows: handover, draft approval, and sales assist.
AI + team online
Emily Parker - VIP customer Order NS-1042 - Cart GBP 148 - charcoal accessories
Live handover
Customer
My laptop stand order still says dispatched. Do you have a matching sleeve?
AI draft
Your parcel is due tomorrow before 6pm. The best match is the Reply Panda felt sleeve in charcoal.
Reply composer Human is editing the final answer
Order context, customer value, and product match already loaded.
Shopify-first install
AI sales copilot
Order status assistant
Human takeover
PWA inbox
Why merchants keep it

Built for daily use, not one-off automation.

The product has to feel useful every day. That means chat resolution, order context, product guidance, and team workflows all living in one place instead of another disposable widget.

Sales assistance

Recommend products inside the conversation.

Bundle suggestions, comparisons, accessories, size help, and cart-saving nudges without sending shoppers away.

Support reduction

Answer repeat questions before a human ever opens the thread.

Shipping times, returns, warranties, installation help, and help-centre answers come from your store logic and docs.

Operational control

Pull agents in only when the moment matters.

Keep internal notes, reassign chats, flag VIP customers, and give the team a mobile inbox they actually check.

Merchant inbox example

See high-intent conversations before they disappear.

Merchants should open the app and instantly see who needs help, who is about to convert, and where AI already handled the easy work.

Live inbox snapshot
Need help tracking order #NS-1042 Emily Parker - VIP - GBP 1,180 lifetime
Agent takeover
Can I return the bag if the size is wrong? Sophie Turner - Approval needed - AI draft ready
Approve draft
Which backpack should I choose for a 16-inch laptop? Daniel Shaw - Sales assist - Product recommendation
AI suggestion
What we market hard

Security and trust are part of the product, not a footer page.

Shopify OAuth, role permissions, audit logs, token protection, webhook verification, and private operational controls are part of the platform story from the start.

Shopify OAuth only

No fragile password flows for stores.

Audit-friendly ops

Track admin actions, impersonation, and suspicious behaviour.

Rate limits + bot defence

Keep the chat useful without turning it into spam intake.

Simple launch pricing

Price it around value, not around tokens.

Merchants buy more orders, fewer support tickets, and faster customer replies. The plans should reflect operational value, not raw model trivia.

Starter

For small stores getting first daily value.

GBP 19 / month
  • 1 agent seat
  • 300 chats
  • Standard AI routing
  • Basic widget styling
Pro

For stores turning support into a growth channel.

GBP 99 / month
  • 10 agents
  • Premium model routing
  • Custom widget experiences
  • PWA team mode + deeper reporting
Questions merchants will ask

Handle the practical objections on the page, not in a sales call.

The faster the product feels concrete, the easier it is to convert. These are the questions a merchant usually needs answered before trying a support + sales platform on their store.

Is this only a chatbot, or can my team actually work inside it?
It is built as an operational inbox, not just a widget. AI handles first replies, order questions, and product suggestions, then your team can step in, edit drafts, add notes, and keep the full thread history.
Can it help with both support and sales at the same time?
Yes. The same thread can answer delivery questions, recommend accessories, compare products, and escalate to a human when the moment becomes high intent or sensitive.
What makes this sticky enough for merchants to keep paying?
Daily inbox usage, saved team workflows, chat history, AI-trained answers, order context, product recommendations, and revenue reporting make it hard to replace with a simple bot.
Can we start simple and upgrade the AI later?
That is the intended path. Launch with shared routing, then move specific stores or plans to stronger models, deeper automations, and more advanced reporting without rebuilding the product surface.
What the merchant buys

Not “AI chat”. More sales, fewer tickets, faster replies.

The message has to stay outcome-led. Merchants care about conversions saved, complaints reduced, and whether their team gets a cleaner workflow than email plus random plugins.

Sales influenced Show what the inbox actually helped convert.
Tickets avoided Let AI absorb the repeat operational questions.
Team speed Keep context, notes, approvals, and replies in one place.
Install + contact

Give stores a clear next step.

Public landing pages should make the next action obvious. A merchant either wants to install, see the app preview, or talk about rollout, pricing, and support requirements.

Install path

Try the product flow, then move into the merchant app.

Keep the public site focused on trust and conversion. Keep the operational dashboard behind it. That separation is what makes the product feel structured and scalable.

Contact options

Useful for founders, agencies, and larger stores.

Sales / onboarding Use this for plan fit, migrations, and rollout questions.
Security / procurement For stores that need security answers before installing.
Agency / white-label interest For partners who want to manage multiple Shopify stores.
Build direction

Public site in front. Product app behind it.

That split is the right architecture. The root domain sells the product. The merchant app handles operations. The super admin panel stays private. Three clear layers, one product story.

Next natural step:

Now that the public layer is in place, the next build should be auth + roles for the merchant app so `/app` stops feeling like a public preview and becomes a real product area.