Most software vendors solve customer education the same way: a help center over here, a knowledge base over there, a few recorded webinars somewhere no one can find. The training exists, but it lives outside the product. Customers have to go looking for it, and most of them don't.
The iorad widget flips that model. Instead of asking your customers to leave their workflow to find documentation, you bring the documentation to them, right inside the app they're already using.
What the widget actually is
The iorad widget is a button, typically a small question mark icon, that you embed directly into any web application you have codebase access to. When a customer clicks it, a panel opens inside the app showing a fully searchable, categorized library of your iorad tutorials. They can search by keyword, browse by category, and launch any tutorial right there without ever leaving the product.
The technical lift is minimal. Once you activate the widget inside iorad's integrations settings, you get a short JavaScript snippet. Paste it into your app's codebase and the button appears. That's the entire implementation.
How it works in practice
The widget connects to your iorad library, which you configure and organize inside your iorad account. You control which tutorials appear, how they're categorized, and who can see them. If you have tutorials that are specific to one customer or one product configuration, you can make those available only to the right audience by using embed or invite-only access settings on the library.
The search inside the widget is full-text, so customers don't have to know the exact name of a tutorial to find it. They type what they're trying to do and the widget surfaces the closest matches across your entire content library.
Because the widget reads from your existing iorad content, there's no separate publishing step. If you're already building tutorials in iorad and sharing them as links, those same tutorials can feed the widget. You don't have to rebuild anything.
Here's an interactive tutorial
Who this is built for
The widget is most useful for customer education teams at software companies with two things in common: a product customers log into every day, and training content that lives outside it.
If you're running live onboarding sessions and sending follow-up links afterward, the widget gives those links a permanent, searchable home inside the product itself. If you're managing a library of step-by-step tutorials for different customer roles, the widget surfaces them exactly where customers need them, at the moment they need them. If you're dealing with high user turnover at customer accounts, where the person you trained six months ago has left and a new employee just logged in for the first time, the widget turns your tutorials into on-demand, always-available support that doesn't require you to run another session.
The case for in-app learning
The standard alternative to the widget is a shared link or a help center embed. Both work, but both require customers to know they need help before they go looking. Most don't realize they're stuck until they're already stuck, and by then the friction of leaving the product, navigating to documentation, and finding the right article is often enough for them to either guess their way through or submit a support ticket instead.
When the tutorials are inside the product, that friction disappears. A customer sees the question mark button, clicks it, searches for what they need, and starts the tutorial right there. The training is self-paced, repeatable, and always current, because when you update the underlying tutorial in iorad, every instance of the widget pulls the latest version automatically.
For teams serving customers who work odd hours, across time zones, or in organizations that can't commit to live training sessions, on-demand in-app tutorials are the only training format that actually scales.
Getting started
Activation happens inside iorad under the integrations tab. Toggle the widget on, copy the script, and hand it to whoever manages your product's codebase. The script needs to be added to the app you want the widget to appear in, which requires access to that application's front-end code. For your own proprietary software, that's typically a quick change. For third-party SaaS tools, it depends on whether that platform gives you codebase or script injection access.
A practical way to start is to pilot it with one customer on one product area, especially one with high support volume or a known onboarding gap. Once the widget is live, customers will find it. The feedback you get from that first pilot will tell you exactly how to expand it.
What to build before you launch the widget
The widget delivers your content, but the content still has to be good. Before adding the button to your product, it's worth spending time on a few things:
Name your tutorials consistently. Use a format like "How to [do X] as a [role]" so customers can search by task and find what they're looking for quickly.
Organize tutorials into categories that match how your customers think, not how your internal team organizes features. Customer-facing categories by workflow or role will make the library easier to navigate than categories by product module.
Keep tutorials short. The smallest self-contained unit of a process is the right scope for a single tutorial. A library of 10 focused tutorials is more useful than one long tutorial that tries to cover everything.
Once those are in place, the widget does the rest.
One platform for all your tutorial needs.
Capture, edit, and deliver your training content across multiple formats with iorad.
