Which system should I start with?

Start where it hurts most: no traffic → social media ops; no storefront of your own → the site system; street sales running on legs and memory → field lead-gen; messages piling up unanswered → AI support; old customers going quiet → private-domain ops. Not sure? Book a demo — one conversation makes it clear.

Can I buy just one system?

Yes. Start with the single system that fixes your most painful stage, then add along the growth chain as you go.

Is it a subscription or a one-time purchase?

Most systems run as a monthly subscription; some, like the storefront, start as a project. We'll scope the right model for your case during the demo.

Are the listed prices final quotes?

They're starting anchors, not final totals. Category, market and what you already have in place differ for every business; the exact scope and quote come after the demo.

What does working together look like?

Three steps: book a demo and pin down your most painful stage; run a small pilot on that one stage and watch real results; once it works, sign and go live.

How soon can we go live?

It depends on the system and what you already have in place. We'll give you a timeline for your specific situation at the demo — no blanket promises.

What does "proven on our own brands first" actually mean?

Our own brands run these five systems on real business every day. What you see in a demo isn't a product page — it's a live system and the real content and conversations it produces. If it doesn't work, we don't sell it.

Is the chat bubble in the corner one of your systems?

Yes. The reception you're getting right now is System No. 4 — the AI Customer Service System — running for real. Buy it, and this is exactly what your customers get.

Do you guarantee results?

We don't promise blanket numbers — categories and starting points differ too much, and anyone guaranteeing you a uniform figure deserves suspicion. Our way: see the live systems at the demo, judge the pilot on your own data, then decide.

I'm not technical — can I run this?

Yes. We handle deployment and integration; you and your team make the business calls. During handover we onboard your people — what you need to know is your customers, not code.

We already have a team, or use other tools. Does that clash?

No. The systems enter one stage at a time, so one can take over a single stage and run side-by-side with what you do today. Same team — much bigger throughput.

Why systems instead of hiring more people?

Hiring adds hands; systems add scale. Publishing, reception and follow-up run around the clock, while people handle only the calls that need judgment. The usual pattern is your existing team running the systems for bigger output — not either-or.

Do you offer done-for-you management?

No. We sell systems, not outsourced labor — the system goes to you or your team and lets the same people produce far more. If you need managed services, that's not our business.

Which languages and markets do you support?

Traditional Chinese, English and Vietnamese out of the box, with multilingual reception and content, so one setup serves domestic and overseas customers at once. We'll confirm coverage for your target market at the demo.

Which channels and platforms can you plug into?

The customer service system handles website live chat, WhatsApp, Messenger, Instagram, LINE and Zalo in one place; the social media system turns one asset into native posts for up to nine platforms. We'll map it to your channel mix at the demo.

Where is my data stored?

Your data is encrypted and stays yours; we'll walk you through exactly where it lives and who can access it when we onboard you.

What happens after I submit the form?

Your details get briefed to a teammate so you never have to repeat yourself; we'll reach you through the contact you left to set a demo time.

Can I put a discount code in the package to bring buyers to my own site?

Not safely. A discount code or a direct 'order cheaper here' message is exactly the diversion language marketplaces flag fastest — it references price and asks for a repeat order in the same breath, which reads as an attempt to route the buyer around the platform's commission.

Is it safe to ask for a phone number in the on-platform order chat?

Ask for a reason tied to service — sizing, a defect, a how-to question — not as a general ask. On-platform chat is usually the most closely monitored channel a seller has, so anything that reads as a sales pitch there is the riskiest place to send it.

What's the safest single move to start building an owned list from marketplace orders?

A package insert framed as warranty registration, with a QR code to your own channel. It gives buyers a real reason to hand over a contact, and it never references price or a repeat purchase — the line marketplaces actually enforce.

How soon after delivery should I message a buyer who scanned the warranty card?

A day or two, tied to something useful — a setup tip, a care instruction — not a sales offer. The first message after opt-in sets the tone for whether they stay on the list or unsubscribe immediately.

How to Move Marketplace Buyers Onto Your Own Customer List

The marketplace's incentive is to keep the buyer, not hand them to you

On any marketplace, the platform is closer to a landlord than an ally when it comes to the next order. Order data, in-platform messaging, and repeat-purchase intent all stay inside the platform's own reach, feeding its own ad inventory and its own recommendation engine — not yours.

Every marketplace's seller terms treat direct diversion — pushing a buyer to contact you off-platform, quoting a lower price elsewhere, or routing a repeat order around the platform — as a policy violation, not a gray area. Get caught doing it inside checkout or on-platform chat, and the usual consequence is an account warning or a suspension, not a shrug.

None of that makes the relationship unreachable. It means the channels that are actually safe are narrower than most sellers assume, and they only hold up when treated as service touchpoints, not sales pitches.

The package insert: framed as service, it survives; framed as a pitch, it doesn't

A card inside the box is the one touchpoint a marketplace genuinely can't inspect before it ships — but that isn't a free pass. A card offering a discount code for your own site, or telling the buyer to 'order direct next time,' is exactly the diversion language that gets accounts flagged once a spot-check or a competitor's complaint catches it.

What tends to survive: a card built entirely around after-sales service — a warranty-registration QR code, a setup guide, a support contact for defect claims. None of it references price, none of it asks for a repeat order, and all of it gives you a legitimate reason to collect a phone number or a channel handle.

The QR code has to land somewhere that matches the card's framing. A 'register your warranty' code that opens a promotional sign-up page breaks the story the moment the buyer scans it, and hands the platform an easy screenshot if anyone ever complains.

Warranty registration, not a discount code
A support contact, not a repeat-order pitch
The landing page has to match the card's framing

The after-sales conversation is where most sellers actually get caught

Once an order ships, some sellers treat the in-platform chat thread as an opening to pitch a repeat purchase or drop an external link. That's backwards — on-platform messaging is usually the most closely policed channel a seller has, not the least, because it's the one channel the platform can scan automatically for exactly this pattern.

The safer version of this conversation happens after delivery, is triggered by a real service need — a sizing question, a defect report, a how-to-use message — and only asks for permission to keep helping, not to sell again. 'Want the setup video sent over?' earns a yes far more often, and far more safely, than a store link.

The line to hold: everything inside on-platform chat should read like customer service, because it's being read by the platform the same way.

The delivery moment is your best shot at a real opt-in

The moment a buyer opens the box is the highest-trust point in the whole relationship — the product just arrived, it matches what they expected, and they haven't had time to get annoyed by anything yet. That's when the warranty card, or a follow-up message a day or two after delivery, actually gets read instead of ignored.

This is also where the opt-in has to be explicit, not implied. Scanning a QR code to register a warranty is not the same as agreeing to promotional messages, and treating it as one invites both a policy complaint and an annoyed unsubscribe. Ask separately, and make the second ask — hearing about restocks and new arrivals — a clear yes or no, not a default.

Once that separate yes exists, the contact has genuinely left the marketplace's reach and landed on a list you operate, message, and own — which is the entire point of the exercise.

What actually triggers account-level trouble

The common thread across marketplace enforcement isn't that a seller built an owned list — it's that they used marketplace-owned surfaces, like checkout notes, on-platform chat, or packaging, to sell around the platform instead of after it. Price comparisons, links to 'buy again cheaper,' and coupon codes tied to a competing storefront are the patterns that get flagged fastest, because they're also the ones that cost the platform its commission directly.

Everything in this piece works precisely because it avoids that pattern — it asks for permission to serve, not permission to sell, and it waits until after delivery to do it. Per the seller terms most marketplaces publish, that's the difference between a warranty card and a policy violation carrying the same QR code.