Launching today
NINA
Guide users step by step inside your product.
293 followers
Guide users step by step inside your product.
293 followers
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.
Free Options
Launch Team / Built With
NINA
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.
@varun1jan 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!
NINA
@orkhan_ilyas thanks
@varun1jan Which product flows tend to benefit most from this kind of guided in-app assistant?
Also congrats with the launch)
@varun1jan 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?
NINA
@martin_herran 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...
The part I would ask about is the handoff. When NINA cannot finish something, whoever picks it up next needs the transcript and the steps already tried, otherwise the person types it all again and the deflection becomes a tax on the customer.
The other half is which questions guidance can reach at all. How do I is a UI question and you can walk someone through it. Why did this happen to my order is a record question, and pointing at the screen does not answer it. Deflection rate looks great on the first kind and never touches the second.
When NINA gives up, what does support receive?
NINA
@jernej_jan_kocica That is exactly the problem we are trying to avoid.
When NINA cannot complete the request, support receives the full transcript along with the steps NINA already tried. The user should not have to repeat the problem from the beginning.
You are also right about the boundary. “How do I complete this workflow?” is a product-guidance question, and NINA can walk the user through it. “Why did this happen to my order?” requires access to the customer’s actual records and business data.
Without that integration, NINA should not pretend it can answer. It should hand the case to support with the full context. With the right API or system integration, we can extend it to those record-specific questions as well.
So for us, the goal is not just deflection. It is either resolving the issue or making the handoff much better.
Swytchcode
How do you get the context for the app? Do you feed some initial data and also monitor for changes?
Does your Agent hallucinate?
NINA
@chilarai @sasha_buratynskyi 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.
NINA
@chilarai 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.
NINA
@chilarai 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..
NINA
@chilarai 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?
NINA
@ashis04 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.
Adomate
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?
NINA
@ozan_gungor 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.
Congrats on the launch! Does the assistant mostly work in a chat-like manner, guiding you through, or can it act as a fallback to a more interactive onboarding?
NINA
@mateuszkonik This is real time walk-through , like GPS , it shows you UI in real time...think like someone if giving you real time demo or showing how to work ,rather than just 20 steps like product manual
NINA
@mateuszkonik Not chat, this is like any Human expert is giving you training and walk through.....Like GPS
Congratulations on the launch! I wanted to know what languages does NINA support?
NINA
@sakshi_shrivastava7 Great question, we have customer using English for now.. What language do you think is second most imp after English ?
NINA
@sakshi_shrivastava7 English - we have deployed so far.....