customer-experience · workflow

Helpshelf

Name: Helpshelf
Brand: nox.markets
Price: 18000 USD

Help-center drafts from the replies that actually closed tickets

new

8 h/mo

Saved

90 min

Setup

Systems touched

Credits per run

$18,000/yr

Annual license, per product

Or included in Growth at $990/mo as the hosted build, along with everything else that tier carries.

Request the annual license Book a demo

Deployment: self-hosted
Setup: 90 min
Hours saved / month: 8
Included from: Growth
Credits per run: 0

03 — Proof

SELF-HOSTED

What is measured, and what is not.

The hours and the setup time are catalog math at a stated volume. Production telemetry is not published yet, and nothing here pretends otherwise.

Catalog math

8 article drafts/month from repeat solved tickets × 45 min to extract, write, and publish (~6h), plus ~2h finding which questions repeated

Run telemetry

04 — What it does / 5 outputs

Clusters solved tickets and drafts Notion or help-center articles from the winning replies.

Draft articles
duplicate-merge list
ticket-ID footnotes

05 — Architecture

It runs inside your perimeter.

Your data does not enter nox.markets production. We receive license telemetry only, and the product runs on your own model keys.

Solved tickets
existing help-center catalog
category allow-list
publish destination
schedule

Out

Draft articles
duplicate-merge list
ticket-ID footnotes
unpublished help-center entries
weekly gap digest

06 — How it works / 90 min setup

Three steps, then it is furniture.

01
Connect Notion and Zendesk
Scoped authorisation, revocable from your IdP or the dashboard.
02
Point it at the work
Solved tickets, existing help-center catalog.
03
It runs
Draft articles — on a trigger or a schedule, 90 minutes after you start.

07 — Features / 7 listed

What is actually in the box.

Runs against a ticket export or helpdesk API from your network; the corpus does not sit on nox.markets
Clusters by question, not by tag — tags are usually wrong
Draft article uses the winning public reply as the spine, with ticket IDs as footnotes
Writes to Notion as a draft page, or to Zendesk/Intercom as an unpublished article
Duplicate merge list so “password reset” does not become seven drafts
Will not publish; unpublished is the only output state
Does not draft legal, pricing, or security articles unless you explicitly include those categories

08 — Data

Does it fit your stack and your data?

Inputs this product consumes and outputs it produces
Input	Output
Solved tickets	Draft articles
existing help-center catalog	duplicate-merge list
category allow-list	ticket-ID footnotes
publish destination	unpublished help-center entries
schedule	weekly gap digest

09 — Integrations / 6 systems

It touches these, and nothing else.

10 — The money

Your hours, your hourly cost.

Two numbers: the hours this product removes at the catalog's stated volume, and the cost of an hour, which only you know.

Hours saved per month

Your loaded hourly cost, USD

You type this one. We do not know what an hour costs you.

Recovered per month

$400

8 h × $50 an hour, before the credits a run spends.

Where the hours come from: 8 article drafts/month from repeat solved tickets × 45 min to extract, write, and publish (~6h), plus ~2h finding which questions repeated.

11 — Pricing

USD

Licensed by the year, run on your keys.

Annual license

$18,000/yr

Runs on your infrastructure and your model keys.
Consumes no credits.

Per run

Nothing. A self-hosted product bills no credits, because the inference is yours.

See how plans and credits work

12 — Security

SELF-HOSTED

You run it, we license it.

Your data does not enter nox.markets production. We receive license telemetry only, and the product runs on your own model keys.

Run payloads are kept for your workspace retention window — 30 days by default on Starter and Growth, 90 on Scale and Enterprise, with zero retention available on Enterprise.

Read the security controls

13 — Customers

Someone like you, running this.

14 — Detail

The long version, including what it will not do.

Help centers rot in the gap between what the article says and what actually closed the ticket. Helpshelf is a workflow you run in your environment (`self-hosted`) because the corpus is a year of customer mail. Each week it clusters solved tickets that used no article, or used an article and still needed a long custom paragraph, and drafts a new or updated Notion / Zendesk / Intercom article from the winning reply — quoted, not paraphrased into mush.

A human publishes. It will not invent refund policy. The first month is a pile of near-duplicates; you merge them. One-time license; you run it on a schedule. It is a $18,000 annual license per product that runs on your own keys and consumes no credits. If you already have a dedicated knowledge manager and a clean help center, spend the $399 elsewhere. Buy it when the same workaround has been typed forty times and still is not an article.

15 — Questions / 5 answered

Before you buy.

What does it need from me before it can run?

Solved tickets; existing help-center catalog; category allow-list; publish destination; schedule. Nothing else is collected for a run.

How long does setup take?

90 minutes. You run it, we license it. You authorise Notion, Zendesk, Intercom, Freshdesk, Slack, Gorgias once.

What does it cost to own?

$18,000 per year for this product, running on your own keys, consuming no credits. The hosted build of the same product is included in the Growth plan at $990/mo.

What does it hand back?

Draft articles; duplicate-merge list; ticket-ID footnotes; unpublished help-center entries; weekly gap digest.

Where does the hours-saved number come from?

8 article drafts/month from repeat solved tickets × 45 min to extract, write, and publish (~6h), plus ~2h finding which questions repeated

16 — Related / 4 products

More on the Customer Experience shelf.

17 — Collections / 0 shelves

Where it sits on a shelf.

No curated shelf lists this product yet.

Helpshelf runs 8 hours of this a month.