Our Design Philosophy

Three decisions we made that most AI tools don't

There are dozens of AI customer service tools. Most of them make the same bet: that a large language model, given enough context, will make the right call every time. We don't believe that's true enough to bet your refund budget on it.

Key Design Decisions

01

Rules first. AI second.

Most AI CS tools let the LLM decide what to do and then suggest an action. giiHelpdeskAgent does the opposite: your rules run first, and the LLM only drafts the reply - it never decides the action.

Here's why this matters: an LLM can be confident and wrong. It has no memory of your last 50 refund decisions. It doesn't know that you never approve refunds on orders that have already shipped. It doesn't know that a certain SKU has a known issue and should always be escalated to your supplier team.

Your rules do know all of this. So we encode them in code, where they can't be misremembered, overridden by a tired agent, or hallucinated away.

What this means for you: Zero off-policy refunds. If an order doesn't match a rule, no action is presented. The agent can still write a manual reply, but the system won't suggest an action it can't verify.
02

We will never store your customer's emails.

This is an architectural decision, not just a policy. We designed the system so that storing email content is technically impossible - not just prohibited.

Every time a Gmail thread is analyzed, the content is processed in memory, used to generate the analysis and draft, and then discarded. Nothing is written to our database. Our audit logs record hashed identifiers (thread ID hash, order ID) - never the email text itself.

Why did we build it this way when storing emails would give us more training data and better features? Because your customers' emails are not yours to give us. And because any system that stores sensitive communications is a system waiting to have a data breach.

What this means for you: Your customers' complaints, disputes, and personal information never leave the Google + Shopify system boundary that already governs your business. We are a processing layer, not a storage layer.
03

Human-in-the-loop on every action. Always.

giiHelpdeskAgent never cancels an order, processes a refund, or sends an email without a human explicitly clicking "Confirm." Not on simple cases. Not on high-confidence matches. Always a human in the loop.

We built several prototypes of "fully automatic" flows. They worked most of the time. "Most of the time" is not good enough when the downside is a cancelled order that shouldn't have been cancelled, or a refund that's now been issued and can't be reversed.

The speed we deliver - 90 seconds from email open to action complete - comes from eliminating the manual research and decision steps, not from removing the human. Your agent still makes the call. They just make it with full information, in 6 seconds instead of 8 minutes.

What this means for you: Your team is still responsible for every CS decision. giiHelpdeskAgent removes the research burden and the policy memory burden - not the accountability.

What giiHelpdeskAgent deliberately does not do

Focus is a product decision. These are things we've chosen not to build, and why we think that's the right call for our target customers.

Fully autonomous refund processing

AI confidence scores don't map to refund risk tolerances. Until they reliably do, a human confirm step is non-negotiable.

Abandoned cart recovery / marketing messages

That's a separate use case with separate tools. We focus exclusively on inbound complaints and service requests.

Customer history profiles

Storing historical customer data conflicts with our zero-storage architecture. Shopify already has this data - we look it up per-session when needed.

Omnichannel (Instagram, WhatsApp, phone)

We work inside Gmail. That's the primary CS channel for Shopify DTC teams at the 2–20 person stage. Other channels may come later.

What we do focus on

Refund requests · Order cancellations · Escalation risk detection · SOP rule matching · Draft reply generation · Shopify write actions · Per-action audit logging. That's it.

How this started

In 2025, we were helping a small Shopify brand (15 people, ~$800k/yr revenue) diagnose why their refund rate was climbing. What we found wasn't an AI problem - it was a consistency problem.

Three different CS agents were handling refund requests. Each one had read the same refund policy document. But faced with an angry email at 7pm on a Friday, each agent made a different call. The policy document wasn't in the system - it was in their head, competing with their desire to end the shift.

We didn't need smarter AI. We needed a way to put the rules where the decision happens: in the tool the agent is already using, at the moment the complaint arrives.

That's giiHelpdeskAgent. It's a narrow tool. It solves a specific problem. And we think that's exactly what makes it worth using.

Questions? Talk directly to the team:

We respond to every email. Usually within a few hours during business hours (GMT+8).

If this design philosophy makes sense to you, you're our customer.