NINA
Guide users step by step inside your product.
Start new thread

NINA - Guide users step by step inside your product.

by
•
NINA lives inside your product and helps users exactly where they get stuck. They ask “How do I…?” by voice or text, and NINA guides them step by step on the live interface before they open a ticket, search documentation, or message support. It is not a scripted tour, chatbot, or FAQ. NINA is built for B2B SaaS teams still relying on onboarding calls, product videos, Slack channels, and repeated support answers.

Add a comment

Replies

Best
Maker
📌

I used to work as a Product Manager. Half my week went to the same questions: "How do I do this?" "Where is that?"

We did what every SaaS team does - videos, documentation, a help center, Chatbot. Users still asked. Videos cannot answer back and show them in real time.

NINA is the fix we wanted. It lives inside your product and answers users where they get stuck, by voice or text, guiding them step by step on the your product UI in real time.

And when you update your product, NINA keeps its guidance current. No re-recording walkthroughs after every release.

Setup is honest, not magic:

  • Install the SDK and match NINA to your brand (about 10 minutes),

  • Upload your docs (answers start immediately),

  • Record your top workflows

The difference from your Looms: a video cannot answer back. NINA can.

Built for B2B SaaS teams running onboarding calls, supporting users in Slack or Discord, and maintaining tutorials nobody watches twice.

NINA is built by our team at AgenQ. Ask me anything I'll be here all day.

 Congrats on the launch! 🚀 I really like the idea. Keeping product guides up to date after every release is a real challenge, so this solves a very practical problem. Wishing you lots of success!

Maker

 Which product flows tend to benefit most from this kind of guided in-app assistant?
Also congrats with the launch)

Maker

 Enterprize B2B apps where UI is bit complex

   Dmitrii, "complex enterprise UI" is true but it is not the sharpest cut. The better predictor is how often the flow is done by the same person.

Guided walkthroughs pay off hardest on flows that are high stakes and rare. Setting up billing, configuring permissions, running a quarterly export. Nobody does those often enough to remember them, so everyone relearns from zero every time, and that relearning is what generates the ticket.

Flows people touch daily need the opposite treatment. They do not want guidance, they want the click count to go down. Putting an assistant on top of those is friction wearing a helpful hat.

So the rule I would use is not complexity, it is frequency. Rare and consequential is where this earns its keep. Daily and routine is where it annoys people.

 Congrats! We lose real hours to "how do I" questions that are already answered in the docs, so I get the pitch. What does NINA do when someone asks for something the product just can't do? Say so, or hand off to support?

Maker

 She is very honest, If she does not know something, she does not make up..She ask user - what he wants next, leave a note or talk to human support...

   Martín, the answer you got is the right one, and there is a second version of your question that usually matters more.

"Say so or hand off" covers the case where the product genuinely cannot do the thing. The harder case is where it can, but the user is asking for it in words that do not match anything in your docs. That does not read as an unanswerable question to the system. It reads as a miss, and the user hears no when the answer was yes.

Those two failures look identical in a deflection metric and need opposite fixes. One needs a better handoff. The other needs your docs to learn the words your users actually use.

If you run this, the thing worth logging is not just what NINA could not answer. It is what people asked in the week before they gave up and opened a ticket anyway. That list is usually the most honest product feedback you will get all quarter.

 With that shift, from resolving 'how do I...?' through a ticket or a call, to resolving it in seconds without leaving the flow, what real impact are you already seeing in activation and in your customers' support team workload?

Maker

 less chrun, Onboarding team is less stressed, Less no. of simple tickets,

 you mentioned nina reads the live interface via the SDK to handle ui updates. how exactly does it anchor to elements if we ship a major frontend redesign? css selectors break so often. btw I found Agenq really great idea

   Mohsin, on the redesign question, there is a cheap test you can run before you commit to anything here.

Take the flows you would want NINA to walk people through, and check whether each target element has a stable accessible name today. Open the browser inspector, look at the accessibility tree rather than the DOM. If the button reads as "Save changes" there, that survives almost any restyle. If it reads as blank, or "button", or the label lives in a sibling div, that element is going to be fragile no matter how good the anchoring logic is.

That check takes about twenty minutes and tells you which parts of your product are safe to automate against and which are not. It is also useful independent of this tool, because the same gaps are what make your product hard for screen reader users.

If a lot of them come back blank, the honest answer is that you fix the labels first and adopt anything selector-driven second.

How do you get the context for the app? Do you feed some initial data and also monitor for changes?
Does your Agent hallucinate?

plus to this question
Maker

   Great questions.

NINA gets context from three sources: your product documentation, the workflows you train and approve, and the live product interface through our SDK.

So yes, there is some initial setup: you upload the docs and train the key workflows. After that, NINA reads the live interface, so when labels, buttons, or screens change, it can stay aligned with the current UI. For larger workflow changes, the admin can review and update the guidance.

On hallucination: no AI system is completely immune, so we do not let NINA freely guess. Answers are grounded in the company’s approved documentation and workflows. For guided actions, it only uses approved paths and the elements available on the live screen. When it does not have enough confidence, it should say it does not know rather than inventing an answer.

Maker

 NINA gets context from three sources: your product documentation, the workflows you train and approve, and the live product interface through our SDK.

So yes, there is some initial setup: you upload the docs and train the key workflows. After that, NINA reads the live interface, so when labels, buttons, or screens change, it can stay aligned with the current UI. For larger workflow changes, the admin can review and update the guidance.

On hallucination: no AI system is completely immune, so we do not let NINA freely guess. Answers are grounded in the company’s approved documentation and workflows. For guided actions, it only uses approved paths and the elements available on the live screen. When it does not have enough confidence, it should say it does not know rather than inventing an answer.

Maker

 We install SDK and upload existing product documents, and train workflow. Any future UI changes, NINA knows as she will compare the old UI. No hallucination as NINA only know about product and nothing else..

Maker

 Correct, you are absolutely right

Congratulations on the launch! One thing I'm curious about: how does NINA handle situations where the UI changes frequently, such as products that ship updates every week? Does it automatically adapt, or does the team need to retrain workflows?

Maker

 NINA is always listening to changes as it is integrated , any update, it will raise to admin with update and Admin needs to approve and NINA is good to go.

Congrats on the launch!
Guiding users inside the application is crucial for them to adopt it.

P.S:
I have built a livedemo for NINA, feel free to check it out

Maker

 Thanks, George! Really appreciate the support.

I checked out the LiveDemo. It's a nice way for people to explore NINA before trying it themselves. Thanks for putting it together and sharing it here.

Congratulations 🎊 👏 💐 🥳

Maker

 Thank you, Madalina! We really appreciate the support. 🙌

Maker

 Thanks.....

This is exactly the bottleneck most new SaaS products keep running into. Onboarding is still our biggest time sink. Docs and tutorial videos only get you so far when someone's actually stuck mid-flow and just wants an answer right there.

Congrats on the launch, looking forward to seeing how far this can take our onboarding.

Two questions:

  • Any plans for Google sign-in, or is it staying limited to Slack/Microsoft Teams for now?

  • Can we swap the narrator voice for our own, so it matches our brand instead of sounding generic?

Maker

 Thanks, Ozan, you described the problem exactly.

The hardest part is when a user is already mid-flow and needs help immediately.

NINA is not limited to Slack or Microsoft Teams. We support enterprise SSO through OAuth2 and SAML, and Google sign-in can be enabled through that setup.

And yes, the voice tone and personality and even face , can be customized to match your brand. You can configure NINA’s voice, name, and visual identity instead of using the same generic narrator for every product.

Hunter

It's an honor to hunt NINA here on PH, because I truly believe in its value proposition.

Many powerful softwares have no clear first starting points.
And NINA doesn't answer with steps. She walks users through them.

NINA guides users through real workflows inside your software, no training calls, no videos, no support tickets.

If resonates, help them by supporting their launch!!!

This is such a clever way to guide users right where they get stuck. Huge congrats on the launch! 🚀🚀

Maker

 Thanks alot.

Maker

Congratulations on the launch! I wanted to know what languages does NINA support?

Maker

 Great question, we have customer using English for now.. What language do you think is second most imp after English ?

Maker

 English - we have deployed so far.....

For B2B or internal enterprise products, this is very much needed. Often those kind of products overlook a great UX in favour of legacy integrations/systems. Congrats on the launch! Wish you the best.
Maker

 Thank you, Enrique! That's exactly the gap we saw. Enterprise products are incredibly powerful, but they're often not the easiest to learn. Our goal with NINA is to help users get things done without leaving the product or relying on docs and support. Really appreciate your kind words!

Maker

 Thanks. Yeah. I loved as PM more than 15 yrs and i found that no tool tip or youtube video help when you need, u need expert right next to you when you are stuck in software...that is why we built it..

Maker

 Thanks.. You are right... Even for big product like HUBSPOT, very complex to get job done even with such a big company product..

123
Next