Seven curated shared libraries, each tuned to the tier-1 questions that industry hears every day. Your tenant inherits the library on day one. Your proprietary IP layers on top.
Thermostat to refrigerant. Carrier, Trane, Lennox, Daikin, Goodman, plus EPA refrigerant compliance.
Open library →
Panels, inverters, batteries. Tesla, Enphase, SolarEdge, Sol-Ark, EG4, FranklinWH, EcoFlow.
Open library →
Help-desk tier 1: M365, VPN, RMM, backup, MFA. Fortinet, Cisco, Datto, NinjaOne, Okta, Duo.
Open library →
CPAP, insulin pumps, CGMs, mobility, oxygen. ResMed, Philips, Medtronic, Dexcom. HIPAA-deployable.
Open library →
ISPs, MNOs, fiber and 5G. Calix, Nokia, Verizon, T-Mobile, Comcast. Equipment swap, no-signal, billing handoff.
Open library →
iPhone, Pixel, Galaxy. Data transfer, Wi-Fi calling, eSIM, repair claims. Carrier + MVNO + insurance.
Open library →
Starlink, Iridium, Inmarsat, Globalstar, ACR beacons, Garmin inReach. ~800 articles in production.
Open library →
The engine is vertical-agnostic. New shared libraries take 2–3 weeks to curate, audit, and publish. Email us with the vertical and we'll evaluate.
Each industry scored 1–10 on eight axes. Sum = fit score out of 80.
| Axis | What it measures |
|---|---|
| Ticket volume | Repetitive Tier 0/1 question density |
| KB density | Are the answers in extractable documentation (manuals, SOPs, vendor docs)? |
| Self-serve tolerance | Will the buyer convert from a 7-day trial without a sales call? |
| Trust premium | Does "every answer cited" move the needle for compliance, safety, or risk? |
| Catalog complexity | Does the layered KB (Shared Library + tenant overlay) actually pay off? |
| Cost-per-ticket | Is human support time expensive enough that finance notices the savings? |
| Competitive whitespace | Is this a segment the megavendors (Sierra, Decagon) aren't fighting over? |
| Trial conversion | Can the buyer go from sign-up to first cited answer in under a day? |
Three industries where every dial points the right way. Highest deployment priority.
Buyer: Operations leader at a 5–50 person hardware reseller. Often founder-led. Technical comfort is high.
Why it fits: Vendor PDFs already exist for every SKU. Customers don't read them. Truvyo does — and cites the page number. Senior techs stop being a search engine.
Reference deployment: 16 SKUs · 272 tenant articles · 460 chunks from shared vendor PDFs · 1.4 s first-response time · ~80% Tier 0/1 deflection.
Buyer: Operations director at a 50–500-tech installer network. Often dealer or franchise organized.
Why it fits: Tier 1 traffic is internal — field techs phoning HQ for torque specs and config sequences. The Technical Companion runs on a phone in a service truck. Same engine, audience-filtered to installer-only articles.
Highest cost-per-callback in our scoring: $200+ per HQ phone call in lost tech productivity + delayed customer.
Buyer: Head of developer experience or support. Technical buyer. Self-serve tolerance: 10/10.
Why it fits: Developers verify citations themselves. They hate being lied to by a chatbot. Extensive docs already exist; customers don't read them. Trial-to-deployment cycle: under one hour.
Trial conversion: <1 hour from sign-up to embedded widget. Starter plan fits a 3–10 person devrel/support team.
The math works. Use case is real. Buyer profile needs slightly more nurturing or the trial cycle runs longer.
Camera gear, pro audio, technical apparel, automotive parts, instruments. Fitment + spec questions dominate. Returns drop when customers buy the right SKU. Catalog complexity score is high.
5K–100K subscriber range. Massive Tier 0/1 volume on connectivity diagnostics. Carrier-scale accounts owned by Sierra/Decagon; mid-market is open. Regulatory pressure values citations.
CPAP, glucose monitors, home medical equipment. Trust premium maxes at 10/10 — FDA scrutiny. Slower sales cycle (won't convert from self-serve trial); Enterprise tier with HIPAA-compliant deployment.
LMS platforms, online curriculum, tutoring marketplaces. Repeat parent + student questions on login, grading, schedules. Tier 0/1 dominates traffic. Price-sensitive — Starter plan built for this profile.
Saying yes to every market is how AI products acquire bad reputations. We don't.
| Market shape | Why we decline |
|---|---|
| Consumer apps with shallow KBs (Spotify-class) | Not enough source material to ground answers. Use a regular chatbot. |
| Pure SaaS without product complexity (Slack, Notion-class) | The product is the docs. In-app help is sufficient. We don't add much. |
| Lead-gen-first chat (Drift-style outbound) | That's sales, not support. Different category entirely. |
| Real-time customer data conversations | "Where's my order?" "What's my balance?" need live system APIs, not KB lookups. We can layer on top but aren't the primary surface. |
| Pure outbound sales bots | Truvyo only activates on inbound customer questions. We don't initiate conversations. |
| Industry | Score | Tier | Recommended plan |
|---|---|---|---|
| Hardware resellers · specialty IT | 70 / 80 | Tier S | Growth or Scale |
| Field service networks | 67 / 80 | Tier S | Growth or Scale |
| B2B SaaS · developer platforms | 64 / 80 | Tier S | Starter or Growth |
| Medical device distribution | 59 / 80 | Tier B | Enterprise |
| Specialty e-commerce | 58 / 80 | Tier A | Growth or Scale |
| Mid-market telco · ISP | 58 / 80 | Tier A | Scale or Enterprise |
| EdTech | 52 / 80 | Tier A | Starter or Growth |
| Insurance · fintech | 51 / 80 | Tier B | Enterprise |
No demo to schedule. No salesperson to qualify you. 30 seconds to a trial API key.
Start your 7-day trial