A 90-day pilot, measured on your own tickets
Glassleaf runs on your manuals and your product pages for 90 days. We agree the baseline first, then count the result in your own help desk’s tickets, against products left without it, not on industry averages. The usual start for larger catalogs (Industrial, 25+ products); smaller teams can start free.
$2,500, credited to your first year when you continue.
- Tickets per 1,000 units
- before → during
- Pilot products
- 21.0 → 19.0
- Comparison products
- 20.6 → 19.8
- Fewer tickets than the comparison
- 6%
- “Did this solve it?” said yes
- 71% of 1,980
With the range and every count behind it, for your finance team.
How it runs
Three steps, and a number your finance team can check against your help desk.
- 1We agree the baseline firstThree months of tickets from your help desk, per 1,000 units sold, for the pilot products and for comparison products left without Glassleaf.
- 2We run it for 90 daysGlassleaf answers on the pilot products’ pages. Each month you send the same ticket and unit counts; we add the widget’s answers, “Did this solve it?” replies and handoffs.
- 3You get the measured resultThe change in tickets per 1,000 units on the pilot products, against the comparison products, with a range and every count behind it.
What you bring
Most teams have all of it already.
Your manuals
The PDFs you already have, for the products in the pilot.
Ticket and unit counts
Monthly tickets per product from your help desk, and units sold (or product-page visits) for the same months. No customer data.
A page to put it on
Your product or support pages, with one line of code.
Someone to approve
FAQs, guides and safety notices go live when a person on your team approves them.
See it on your own manuals.
Tell us which products you would start with. We reply by email.