NOAN is highly praised for its ability to enhance business operations through AI-driven collaboration. Users appreciate its effectiveness in content generation, ideation, and maintaining brand consistency. Many reviews highlight its potential to unify and centralize company documents, policies, and messaging, making it a valuable asset for businesses. The platform's user interface and innovative features receive commendations, with users noting its capacity to elevate professionalism and streamline workflows. Overall, NOAN is seen as a powerful tool for business growth and efficiency.
How granular is the versioning? For example can a team update only one pricing rule without creating a new version of everything else?
I like the idea of separating company facts from the documents that contain them. Does NOAN keep a history of who changed each fact and why?
Is there a workflow for resolving conflicting facts before they reach an agent?
Congrats on the relaunch Neal and team! Full disclosure, we work with Noan, but the Activity feed is the bit I'd point people to - being able to trace an agent's answer back to the exact fact it read is what makes it safe to let agents near sales and client comms.
Great to see the agent pack open sourced too.
What are you launching next?
NOAN
@christine_johansen our voice agent on the homepage right now might be the give away... https://www.getnoan.com/
The business brain finally has a home instead of living in 19 Google Docs and a group chat haha. Cool idea, congrats on the launch! @neal_mann @danmonthell @imfilp
NOAN
@danmonthell @imfilp @zach_francis haha It does indeed! Thanks a lot.
Dial
the fact-level permissions and drift detection answer above is solid for async channels where someone can wait for approval. our case is voice, the agent is mid-call and has maybe 800ms to answer, so there's no time to check for a pending approval. curious whether NOAN distinguishes "verified and stable" facts from "approved but still drafty" ones at read time, so a live agent could be configured to only pull the former and fall back to "let me check on that" for the rest
NOAN
@galdayan we use voice too! Our voice agent runs on the fact layer, our investors talk straight to her for instance too. Facts are either live or draft, it's about what is live on the API. So a voice agent would be a service using the API, as a result it's what's live that matters to it. It's a different way to think about how a business is run, your facts control the company and agents. If given write permissions it can also update facts or the contacts details it is talking to as well in real time.
NOAN
@galdayan facts are approved decisions. Our agents only ever answer questions if it can find the answer in our fact base. It will say outright that it doesnt have the answer if it cant find it. At which point a human gets flagged in the task manager so we can fill in the gap for next time. Our agents will never provide an answer that is not recorded as a fact.