Conversational setup
Say 'learn advanced SEO research' and the agent activates the right skill. Say 'always check with me before sending emails' and it creates a duty. No settings panels, no admin overhead.
Just ask. It configures itself.
Skip the settings panels. Tell your AI employee what skills to learn, what rules to follow, and what personality to use, all through natural conversation. They can even browse the skill catalog and configure themselves as work evolves.
Most AI tools force you into settings panels and dropdown menus. This one listens. Tell your employee what to do in plain language, and it configures its own skills, duties, persona, and AI model through conversation.
Skills control capabilities, duties enforce rules, personas shape personality, and model selection balances cost against performance. All are managed through chat.
Your employees can even configure themselves and the platform, adjusting their own skills and settings as work evolves.
Three layers decide how an employee behaves, and they stay separate on purpose. Skills are what it is good at, duties are the rules it never breaks, and the persona is how it sounds. Change one and the other two are untouched, so tightening a rule cannot quietly rewrite the tone, and rewriting the tone cannot drop a rule. Your employee then picks the right skill for each task on its own, which means you describe the work rather than the method.
You also decide how hard an employee thinks and how far it is allowed to go. Thinking depth runs from off through minimal, light, medium and deep, or you leave it on auto and Sistava picks the right depth per message. A separate limit sets how many actions one employee may take on a single task before it stops and reports back, anywhere from 50 up to 1,000. A research role gets room to search, read and delegate, while a simple support role stays tight, and both settings apply across the workspace with a per-employee override when one role genuinely needs something different.
Credits Saver is on by default and quietly keeps everyday chat cheap. Greetings, quick acknowledgements and small edits like make that shorter are handled by a lighter model, while anything that counts as real work still runs on the model you chose for that employee. On ordinary back and forth that often means 40 to 50 percent fewer credits with no drop in quality where it counts. It is per employee and fully in your hands, so you can switch it off whenever you want.
Nothing here is locked in. Every field on an employee's Profile tab, including name, role, team, avatar, persona, language and tone of voice, is editable in place, and the change applies from its next message onward across every channel that employee works on. A change history on the same tab records every edit, including the ones the employee made to itself, so you can always see what changed and put it back. Tell your team leader once how you want to be addressed, when you work and how you like answers written, and every employee on the team picks that up without a form to fill in.
Say 'learn advanced SEO research' and the agent activates the right skill. Say 'always check with me before sending emails' and it creates a duty. No settings panels, no admin overhead.
Duties are non-negotiable behavioral rules your AI employee follows on every interaction. They persist across all conversations and all users. A duty is the difference between a one-time request and a standing policy.
Your AI agents can browse the skill catalog, activate new capabilities, and adjust their own configuration as the job demands change. You define the boundaries, they operate within them.
You shape how your AI employees think and act by assigning skills they master, duties they always follow, and a persona that fits your brand.
Skills define what an AI agent is good at: writing, research, data analysis, customer communication, and dozens more. Duties are behavioral rules the agent follows unconditionally, things like always escalating refunds over a certain amount, never making promises about delivery dates, or always responding in a formal tone. Together, skills and duties give each agent a precise and reliable character.
You also choose the underlying AI model for each employee, matching the right capability level to the right role. A lightweight model handles routine support tickets, a more powerful one tackles complex research. Agents self-manage within their defined scope, deciding which tools to use and how to approach a task, without needing you to supervise every step.
Self-configuration has edges, and you draw them. An employee can browse the skill catalog, activate what a job needs and adjust its own settings, but the ability to operate the platform itself is a capability you hand out deliberately rather than something every employee has, and anything that touches billing always waits for a person. Every change is recorded with a timestamp and the reasoning the employee gave, so you can review it later or reverse it from the change history. You set the boundaries once, then let them work inside those boundaries.
Give your employee specific skills like negotiation, technical writing, or data analysis. Skills shape how they approach problems and what methods they apply.
Duties are non-negotiable rules: always escalate billing issues, never make promises about timelines, include a summary at the end of every report. Consistent behavior, no reminders needed.
Define their name, tone, communication style, and personality. A customer-facing employee sounds warm and professional. An internal analyst is direct and concise.
Run fast, cheap models for high-volume routine tasks and switch to more powerful models when the work demands deeper reasoning. One employee, the right model per job.
You control an AI employee's behavior with three things: skills, duties and a persona. Skills are the capabilities it brings to a job, duties are standing rules it follows on every task, and the persona sets its name, tone and communication style. In Sistava you set all three by saying what you want in ordinary conversation, and the employee configures itself to match.
No. Configuration in Sistava happens in chat. Say learn advanced SEO research and the employee finds and activates that skill; say always check with me before sending an email and it turns that into a standing rule. Every setting also has a normal screen if you would rather click through it, but most people never open one.
Use a skill when you want an employee to be good at something, such as writing case studies or qualifying leads. Use a duty when you want a rule that holds on every single task, such as always summarising at the end or never quoting a delivery date. Use the persona when you want to change how it sounds rather than what it does. The three are independent, so changing one leaves the other two exactly as they were.
Immediately. A new skill, a new duty or an edited persona applies from that employee's next message onward, on every channel it works on, with no rehire, redeploy or restart. Fields on the Profile tab save the moment you click away, so there is no separate save step to forget.
Yes. Operating the platform itself is a capability you assign deliberately, usually to a team leader, rather than something every employee has. Anything that affects billing always needs a person to approve it. Every change an employee makes is logged with a timestamp and the reasoning it gave, and you can reverse it from the change history.
Every edit lands in a change history on that employee's Profile tab, including edits the employee made to itself, so you can see exactly what changed and when. Skills can be deactivated, duties removed and persona text rewritten at any time. Nothing here is permanent and nothing needs support to reverse.
Skills and duties are set per employee, which is exactly what keeps a support role and a research role behaving differently. What you never repeat is yourself: tell your team leader once how you want to be addressed, when you work and how you like replies written, and every employee on that team picks it up. Skills are reusable too, so one custom skill assigned across the team keeps everyone consistent, and updating it updates all of them.
Yes, and there are two dials for it. Thinking depth runs from off through minimal, light, medium and deep, or auto lets Sistava choose per message. Separately, Credits Saver sends greetings and small edits to a lighter model while real work stays on the model you selected, so the easy turns cost less without touching the quality of actual output.
Giving an AI agent the right skills is only half the job. The other half is making sure it behaves the way your business requires. Duties lock in the non-negotiables: compliance requirements, communication standards, escalation triggers, and brand voice. Your agent executes autonomously inside those guardrails, not around them.
When your business needs change, you update the behavior in one place and every affected agent adjusts immediately. No retraining, no re-briefing, no hoping the agent remembers. You define the rules once and trust that they stick.
Setting duties was a game changer. My sales agent stopped overpromising on timelines the moment I added that as a rule. Zero micromanagement needed.