Fixed-price system

E-commerce Order, Returns & Product Support Assistant

Every order-status question and return request eats a support ticket, and by the time someone answers, the customer is already frustrated, or has filed a chargeback.

$1,800 setup, then $700 a month. Fixed price, US dollars. Live in 12 business days from a signed scope and the deposit.

Free audit, no accounts, we change nothing.

Or ask a person: aimarketing@gonzo.co.in +91 7390990227 WhatsApp

E-commerce Order, Returns & Product Support Assistant is one of Gonzo Digital's nine fixed-price systems. It costs $1,800 to set up and $700 a month, in US dollars, and goes live 12 business days after a signed scope and the deposit. It is for E-commerce and D2C brands drowning in repetitive order-status, return, and spec tickets. Anything it sends on its own says it is from an AI.

What you get

  • Order-status lookup, answered instantly from your own order data
  • Return eligibility checked against your stated policy, with the exact rule cited every time, never a black-box yes/no
  • Technical spec Q&A that answers only from your product data on file, and says so the moment a question isn't covered
  • Escalation to a human customer executive the instant something isn't a confident, rule-based answer, never a guess dressed up as one
  • Weekly report: what got escalated, and why, so the rule set improves

Who it is for

E-commerce and D2C brands drowning in repetitive order-status, return, and spec tickets.

How it behaves

  • Anything this system sends to a person on its own says it is an AI. There is no setting to turn that off.
  • Fixed scope. The deliverables above are the scope, and the price does not move with the hours.

What this page does not show

Client results. This page describes what the system can do, not what it has done for someone. We will publish a result only when a real client has earned it and agreed to be named.

More detail

How it runs

  1. Looks the order up in your own order data.
  2. Checks a return against your stated policy and quotes the exact rule. A spec question is answered only from your product sheets.
  3. A refund request, a complaint, or anything it cannot answer from your data goes to a person. A weekly report says what was escalated and why.

Where it connects

Each row says what exists today and what has to be true before it runs for you. "Tested in the sandbox" means tested against simulated services.

ConnectionStatus todayWhat going live needs
Your storefront (orders)Built against a sandbox shop. It can read orders and write a return intake. It has no refund function.An adapter for your shop. We write one per platform.
Your return policy, product sheets and item categoriesSupplied by you.Without a policy on file, a return question is escalated. Without a spec sheet, a spec question is escalated.
Email, WhatsApp and web chatBuilt, tested in the sandbox.Each inbound channel wired to the agent. SMTP is not configured on our side yet, and WhatsApp needs a provider account and an approved template.
Your CRMRead only: the contact's name, for the greeting.A read adapter, checked per CRM before you sign.
A language model, for wording onlyBuilt. It sees the finished draft and nothing else.A model key. The model never gets the customer's message or their name, and its text is dropped if it loses an order or rule number.

What this does not do

  • It cannot refund anything. The storefront connection has no refund method, and no function in the code is named for one. A refund question gets an intake, a holding line and a person.
  • It does not guess. A spec question that your sheets do not cover is escalated, and it says so.
  • A complaint, legal language, a STOP or an erasure request ends the conversation after at most one neutral line, and you are told.
  • A return intake carries the customer's own words (the first 500 characters) to your store. Those words are not sent to the model and are not copied into the audit log, which holds hashes and ids only.
  • It matches an inbound sender to a customer by the channel's contact id. Getting that match right is the adapter's job, and we test it per shop.
  • It cannot promise a share of tickets it will resolve. The weekly report shows what it did on your tickets.

Doubts people raise about this one

Can a person take over a conversation?

Yes. The lead, reception, outreach and support systems each hand over to a person: the Lead Response Engine the moment a lead asks something it cannot answer, the AI Receptionist for anything outside its script, the Outreach Engine the moment a lead replies, and the E-commerce Support Assistant the instant something is not a confident, rule-based answer.

What if I want a refund, or want to cancel?

Refund, cancellation, notice-period and minimum-term terms are not on file, so we will not invent them here. A person will give them to you in writing before you sign.

One thing we can say: the automated systems never decide or send a refund. A refund, chargeback or credit-note request is written down and passed to a person.

What do I need to provide to get started?

It depends on the product, and the build names what it reads:

  • AI Receptionist and Lead Response Engine: your knowledge base and business hours.
  • Dormant List Revival: your customer list, with consent records for who may be contacted.
  • E-commerce Support Assistant: your order data, your return policy and your product data.
  • Connected Operations Layer: you connect each account through its own sign-in, and can revoke it.

The exact checklist for your system is agreed when scope is signed. The full list is not on file, so a person will give it to you.

Which AI does it use, and does my data go to another AI company?

The models are Hermes and DeepSeek, and the code allows no others. Which product uses which:

  • AI Outreach & Lead Qualification Engine: our product list says it runs only on Hermes and DeepSeek.
  • E-commerce Order, Returns & Product Support Assistant and Connected Operations Layer (MCP): the stack lists Hermes and DeepSeek.
  • Every other product: a person will confirm in writing which models are used, because the product list does not say.

Rules and templates decide what is said. The model only helps with wording, and its wording is thrown away if it changes a figure or adds a claim.

Before text reaches a model, email addresses, phone numbers and money amounts are swapped for placeholders by pattern, and names are swapped where they have been supplied to the tool. An address, a name nobody supplied or an order number is not caught, so this lowers the risk and is not proof that no personal data remains.

Both model families are hosted. We have not yet settled whether hosted models may see redacted personal data, so we do not claim that your data never reaches another AI company. How personal data is handled is on the trust page. What the model providers' own terms say about training is not on file, so we do not state it. Nothing here has run live yet.

What does it connect to?

What exists today, by product. Everything below has been built and tested against simulated services only; nothing has run live for a client.

  • Lead Response Engine: the official WhatsApp Business API and email are built. The web form and web chat adapters are not built yet. Your CRM: it writes to our own CRM log, and whether it mirrors into yours is checked per CRM.
  • AI Receptionist: web chat and a calendar adapter (Google or Microsoft) are built against a sandbox calendar. The phone line and voice gateway are not built. Confirmations go by email.
  • Client Onboarding Pipeline: an e-signature webhook, an intake form, email, WhatsApp (when a template is supplied) and a calendar are built in the sandbox. The calendar tools have never run live, and the store for onboarding state is not built.
  • Dormant List Revival: email and the official WhatsApp Business API are built in the sandbox. It needs a separate sending domain and a persisted consent store.
  • AI Outreach & Lead Qualification Engine: email and official WhatsApp (opted-in contacts only) are built in the sandbox. Apollo enrichment has never run live.
  • Quote-to-Invoice Automation: an intake form, email and Stripe payment links (money in only) are built. Stripe has never been run live. Your accounting package is not connected: invoices live in the system's own book.
  • E-commerce Support Assistant: an adapter for your storefront is written per platform. Email, WhatsApp and web chat are built in the sandbox.
  • Connected Operations Layer: four Microsoft 365 read tools and two Google Drive read tools are built. Gmail or Outlook, Google Calendar, HubSpot and WhatsApp go through an integration router that has never run live, and most write connectors are not built.

Your exact version of a tool, a self-hosted system or a niche CRM is not on file. A person will check it before you sign.

Will it embarrass me in front of a customer?

We cannot promise it never gets something wrong. No system can, and we will not say so.

What it is built to do instead:

  • Answer from the data and policy you give it. The support and reception systems say so when a question is not covered, and pass it to a person.
  • Stop and tell you on a complaint, a legal threat, a request for a human, a STOP, or a data-erasure request. It sends at most one neutral acknowledgment.
  • Say it is an AI on the first message, so nobody is misled about who they are talking to.
  • Keep money questions inside limits you set. Above them, it sends a holding line and asks you.
  • Write every action to a tamper-evident log you can check afterwards.

Other systems

Managed Automation & Infrastructure Retainer

You bought the automations. Now who keeps them running, tunes them as you grow, and tells you the truth about your cloud and infrastructure bills? Doing it in-house means a hire you can't justify yet.

$2,500setup, once
$2,500per month

Live in 7 business days from a signed scope and the deposit.

See what you get →

Connected Operations Layer (MCP)

Your tools don't talk to each other. Your inbox, your CRM, your calendar, your WhatsApp, your documents: every one is its own island, and you are the integration nobody's paying for.

$5,000setup, once
$2,500per month

Live in 21 business days from a signed scope and the deposit.

See what you get →

Lead Response Engine

Inquiries sit unanswered for hours. By the time you reply, they've booked with whoever answered first.

$2,000setup, once
$600per month

Live in 10 business days from a signed scope and the deposit.

See what you get →

Next steps

Start with the free audit.

Send one web address. In about five business days you get a short written report. If a system fits, a fixed-price scope follows.

Free audit, no accounts, we change nothing.

What happens next

  1. Free auditAbout five business days. A short written report on one page. We change nothing.
  2. Fixed-price scopeIf a system fits, you get its scope and price in writing. Nothing is paid on this site.
  3. Build7 to 21 business days from a signed scope and the deposit. The written handover comes before go-live.

Or ask a person: aimarketing@gonzo.co.in +91 7390990227 WhatsApp