Question 1

How do Kivlet anomaly alerts work?

Accepted Answer

Kivlet compares today’s order, refund, and support activity with a seven-day UTC baseline, then surfaces a signal when the change is meaningfully above that pattern. It needs activity on at least three of those seven complete UTC days before it can establish a baseline, so a new shop may see “insufficient history” first.

Question 2

What does support automation cover?

Accepted Answer

Kivlet helps triage customer conversations, draft grounded replies, and move routine order, refund, shipping, and policy follow-ups forward. It keeps exceptions and owner decisions visible in the operations inbox instead of pretending every case should be handled automatically.

Question 3

What is included in the daily report?

Accepted Answer

The daily report brings together sales activity, support volume, unresolved issues, inventory signals, and notable order or refund changes. It is designed to give a lean retail team a clear next decision, not another dashboard to monitor all day.

Question 4

How does setup work for a retailer?

Accepted Answer

Start with Kivlet’s retailer onboarding path: share the store context and operating policies that shape your workflows, then review the first operating picture with the team. Kivlet works within the supported operations surface and keeps anything needing an owner’s judgment in view; it does not claim unsupported integrations or autonomous actions.

The questions that come up before the first morning brief.

Clear answers for the work behind the storefront.

See what Kivlet coverage could look like for your shop.