About

Built around the ReplyIQ way of handling the inbox.

ReplyIQ is a multi-channel-native reply and escalation layer for small and mid-sized e-commerce brands. The policy file IS the knowledge base — edit a return window, refund cap, or tone-of-voice guideline and the next reply honours it. Hard escalation triggers (refund cap, legal language, chargeback, sentiment crash) hand the conversation to a named queue with the reason attached. And it sits beside your existing stack — never in front of it.

Our origin

ReplyIQ was born watching a single laptop-stack merchant run four inboxes at once — Shopify, Amazon Seller Central, eBay, and email — and lose hours every day to the same triage loop: which of these can the AI send a polite, on-policy reply to, and which need a human before the next chargeback window opens? The product is the answer to that question, repeated across every channel a multi-channel seller actually runs.

How we build

How ReplyIQ is built

Multi-channel-native
One thread across every channel
The same conversation thread runs across Shopify, Amazon Seller Central, eBay, and email from day one — and each channel keeps its native rules. No off-platform links on Amazon, case-aware replies on eBay, return windows honoured on Shopify, threaded replies on email. ReplyIQ stays inside each channel's contract instead of flattening them into one generic inbox.
Policy-as-knowledge
The policy file IS the knowledge base
Edit a return window, a refund cap, or a tone-of-voice guideline in your merchant policy store and the very next reply honours it — there is no parallel model to retrain on the side, no deployment in between, and no lag. The policy your team already maintains is the knowledge base, read the way a trained agent would before every reply.
Hard escalation
Hard escalation triggers, named queues
Refund cap reached, legally-loaded language, a chargeback mention, a sentiment crash past a defined threshold — each escalation fires on an auditable, hard trigger and routes to a named queue with the reason attached to the ticket. Refund escalations land in one queue, chargebacks in another, so the right person is paged without anyone triaging the inbound stream first.
Sits beside your stack
Sits beside your existing stack
Marketplace seller consoles stay the source of truth for fulfilment, inventory, and shipping — we read them, we do not replace the order pipeline. Shipping and catalog tooling keep their domain; voice and SMS providers stay yours; custom CRM exports and BI pipelines keep running. ReplyIQ adds a reply-and-escalation layer on top, never in place of what already works.

Channel coverage today: Shopify, Amazon Seller Central, eBay, and email. Growth adds Chat and SMS; Scale adds Social and Voice.

Team

The team (placeholder)

Names and roles coming soon — this block is intentionally empty while we finish the brand site.

PN

Placeholder name

Role TBD

PN

Placeholder name

Role TBD

PN

Placeholder name

Role TBD

Ready when you are

See the plans. Pick the one that fits.

Three locked plans with hard monthly spend caps, no per-seat creep, no surprise overage. Start with the plan that fits the channel mix you actually run.

See the plans