Knowledge
Policies, courses and service flows become knowledge the assistant can cite. Private records are fetched only when authorized.
Underneath Ultra, Nexus and Ethos is one layer that knows the association, connects to its systems and decides, every time, who may see what and do what.
Your systems on one side, three products on the other, and one governed layer in between.
Policies, courses and service flows become knowledge the assistant can cite. Private records are fetched only when authorized.
Roles govern each feature, source, level of detail and action. Confidential data and consequential actions need an explicit grant.
Sending, scheduling, registering, updating a record: each action is defined, bounded and confirmed before it runs.
“How many members renewed in August?” Speak naturally and interrupt when you like. The screen shows what the voice is saying.
“renewals august by category” Type when voice isn’t right for the room. Voice and text reach the same tools and the same answers.
They hold in every product, for every user, spoken or typed.
If a source is unavailable, NASOS says so and shows the last good value, clearly labelled. It never invents one.
Before sending, paying, scheduling or changing a record, NASOS states exactly what will happen and waits for confirmation.
Membership stays in RAMCO. Payment status comes from the payment provider. No competing copies of member profiles.
When someone needs more, NASOS routes the request to the association’s approver instead of a bare refusal.
Every association’s data, configuration and permissions are kept separate. Public knowledge and private records stay apart.
Assessments and HR requests are restricted to those who should see them. NASOS never makes employment decisions.