Camp Run · Open Innovation

Suki Pulse

Every complaint at Suki Mart is a symptom. Suki Pulse lets Hermes find the operational cause behind it (a late rider, a supplier, a missing purchase order, a broken points ledger) and fix both sides.

Root causes of open complaints

Fewermore Top cause for the branch A complaint can carry several causes. Jev scores each one on its own.

How Hermes runs it

  1. 1

    Desktop plugin

    A Suki Pulse pane in Hermes Desktop. Pick a branch, then run a pulse check, fix the top cause, or recover the riskiest customer. Results come back as native cards in the chat.

  2. 2

    Skill suki-pulse

    Triage, then root cause, then a plan that covers operations and customers. It asks before it writes, then shows the before and after.

  3. 3

    MCP server suki

    Ten domain tools. Triage, rollup, scorecard and customer story read. Resolve, reply, reconcile points, draft POs and flag a rider write.

  4. 4

    TypeSafe Jev

    One call per complaint returns six yes or no cause checks, a churn score and urgency. Cached, fractions of a cent, with a keyword fallback.

Why both tracks. Customer experience sees angry tickets. Operations sees late purchase orders. Nobody joins them. Suki Pulse ranks a branch's complaints by cause, then shows the record behind each one: riders' lateness across every branch they serve, perishables near expiry, items under reorder point with no purchase order, and points ledgers that do not add up.

Why Jev and Hermes. Jev is the fast classifier. It read every open complaint above in about a minute for under two cents. Hermes is the slow thinker. It reads the evidence, decides the fixes, asks you, then acts through the MCP tools.