Adoption turns the usage intelligence gathered across your connected AI systems into action. Where Usage shows who is using AI and which use cases are saving time, Adoption helps you bring idle license holders on board, spread proven use cases to the teammates who would benefit, and validate how much time is really being saved.
It does this through three kinds of outbound email program — nudges, campaigns, and surveys — each built from the use-case clusters detected in Usage. Every program is composed in a guided builder with a live email preview, a controlled sending cadence, and built-in opt-out handling, so outreach stays helpful rather than noisy.
Purpose
Adoption helps organizations:
- bring idle license holders onto systems they already pay for, through nudges
- spread proven, time-saving use cases to teammates who have not tried them, through campaigns
- validate estimated time-saved with the people actually doing the work, through surveys
- target the right recipients automatically, based on who has and has not adopted each use case
- control how often and how long people are contacted, with automatic stop conditions
- respect people who have opted out, through a tenant-wide quiet list
Adoption is where measurement becomes movement. It acts on what Usage discovers and closes the loop by sending validated time-saved figures back into Usage’s ROI.
Overview of Page Sections
Suggested opportunities
The top of the page surfaces recommended actions drawn from current usage. A use case with strong activity but only an estimated time-saved figure is flagged as worth validating, with a prompt to send a survey; a use case that is a proven win is flagged for a campaign to active teammates who have not tried it yet. Each suggestion can be acted on or skipped.
Active campaigns
A live view of every program in flight, filterable by type. Each row shows the program, its audience, progress toward activation or response, and its schedule, including when the next send is due. Selecting a program opens its results, where surveys show response rates and the distribution of answers, and nudges show how many recipients have activated.
Systems · nudge candidates
A list of AI systems that have idle license holders — people who hold a seat but are barely using it — so you can nudge them to start. When every licensed system is fully adopted, this section simply confirms there are no idle seats to nudge.
Use cases
Every detected use case, with how its adoption compares to peers and how mature its time-saved figure is. A figure may be a raw AI estimate, an early figure backed by the first survey responses, or a completed, validated number. Each use case offers a direct path to launch a campaign or a survey, and a separate page lists them all, grouped by category.
Adoption inbox
Drafts you have started but not sent, programs that have finished, and an archive all live in the Adoption inbox, so unfinished and completed outreach is easy to pick back up or review.
Quiet list
People who have silenced RexCommand’s adoption emails appear on the quiet list. They are automatically excluded from every recipient list, so opting out is always respected.
The three programs
Adoption offers three program types. They are deliberately distinct, and choosing the right one matters. A survey is usually worth running before a campaign, so that the time-saved figure you spread is real rather than estimated.
Nudges
A nudge works at the system level. Its job is to get idle license holders to start using a system they already have, not to promote one specific task. You define the rule for who counts as idle — for example, anyone who has used the system fewer than three times in the last thirty days — and the recipient list is built automatically from people who match. The email shows a few examples of what peers do with the system, which you can swap or add to from the library. You control how often emails go out and for how long, and by default a person drops off the list the moment their usage crosses the threshold.
Campaigns
A campaign works at the use-case level. It spreads one proven use case to teammates who have not tried it yet, typically within the same department. The email explains how peers use the system for that task, with step-by-step instructions condensed from how the team actually works, and the time it tends to save. Recipients default to the people who have not been seen using the use case, and you can add more. As with nudges, you set the cadence and run length, and by default a person drops off once they try the use case.
Surveys
A survey works at the use-case level too, but its purpose is to validate rather than to spread. It goes to the power users who have used a use case enough to give a real answer, and asks two questions: whether they would recommend it to others in their department, and how much time it saves them each time. The time-saved answers feed straight back into ROI — once enough consistent replies arrive, the validated figure replaces the AI estimate used in Usage. You can set a reminder cadence, and by default reminders stop for anyone who has already responded.
How this supports Usage
Adoption depends on Usage and feeds back into it. The use cases, idle-license signals, and time-saved estimates that drive every nudge, campaign, and survey all come from Usage’s classification of prompt activity. In return, the answers surveys collect about real time saved flow back into Usage, where they replace estimates in the Net ROI calculation. The result is a continuous loop: Usage measures, Adoption acts, and the response makes the next measurement more accurate.
Notes
- The three program types are not interchangeable. A nudge is system-level and targets idle license holders; a campaign spreads one use case; a survey validates one use case.
- Avoid calling use-case non-users “idle.” “Idle” refers to system-level non-use; for a single use case the correct framing is that someone has not tried it yet.
- Run a survey before a campaign where you can, so the time-saved figure you promote is validated rather than estimated.
- By default, people drop out of a program once they act — crossing the usage bar, trying the use case, or completing the survey — so no one is contacted unnecessarily. This can be overridden to run the full sequence.
- Opt-outs are always honored. Anyone on the quiet list is removed from every recipient list automatically.