Bring the assistant to the user.
Most users won't ask for help. They stall, then they leave. A Suggestion puts the assistant in front of them at the moment that matters, in the app or from a link you send, so the right guidance arrives before they drop off.
In-app nudges and magic links.
A Suggestion is one instruction to the assistant. You write it once and deliver it two ways. Inside the product as a nudge, or from anywhere else as a link.
In-app nudges
A small prompt appears above the assistant, targeted by URL or user property. Show it on the billing page, or only to accounts that still haven't connected their data. Frigade tracks who saw it, clicked, and dismissed.
Magic links
Every Suggestion also generates a shareable link. Drop it in an onboarding email, a support reply, or a Slack message. The user lands in the right place with the assistant already running the guidance you set.
Proactive beats waiting around.
With no way to reach users in the moment, you fall back on the old playbook. Generic tours, email blasts, and a support queue that only hears from the few users who bother to ask.
Users left to figure it out.
Guidance that finds the user.
As easy as briefing a teammate.
No code, no selectors, no engineering ticket. Tell the assistant what you want in plain language, the way you'd brief a sharp teammate, and it takes care of the rest. Save once and you have a nudge and a link.
Teams already use Suggestions to activate users.
“The product activation has been incredible. It's solved over 400 queries a month that would otherwise go to our support team.”
The assistant already knows your product.
A Suggestion just tells the assistant what to do. It already knows your product, because Frigade learned it by using it, so a nudge can walk a user through a real workflow instead of pointing them at a help article.
See how the assistant learns your product