SenseOS 2.0 Functions
SenseOS gives an organisation AI employees with a face and a voice. They join meetings, take video calls and work together in Rooms. Between conversations they keep working at their own desk: they handle email, tasks, the CRM, phone calls and background jobs, and ask you in the Inbox when they need a decision.
185 functions in 17 areas
- Newadded since the 30 Oct edition, live today
- Liveon benita.one
- In developmentbeing built, not usable yet
- Partialpresent but limited
How SenseOS works
From setting up an employee to the finished work, in five steps. An employee works in two ways: live, while you talk with it, and at its desk, on its own between conversations.
1
Set up
An Owner or Admin prepares the organisation and its employees.Details- Organisation profile, people and org chart
- Employee: role, persona, avatar, voice
- AI models and Claude agent
- Mailbox, CRM role, phone permission
- Desk on, autonomy level and limits
2
Give work
Work reaches an employee from anywhere you are.Details- Speak to it in a meeting, call or Room
- Ask in a Room: it becomes a task
- Chat or give a task on its page
- An email arrives in its mailbox
- A CRM follow-up falls due
3
The employee works
It answers live, or its desk wakes it for a work turn.Details- Reads the task, mail and history
- Uses the CRM, email and contacts
- Places phone calls
- Starts background jobs: research, images, decks, prospect lists
- Hands steps to other employees
4
It checks with you
What its autonomy level doesn't allow waits in your Inbox.Details- Approve or reject, with a note
- Answer its questions, attach files
- Its supervisor decides
- Limits and budget stop runaway work
5
It delivers
Results come back where you'll see them, and nothing is forgotten.Details- Links and files in the chat
- Task moves to Done in its Work tab
- Every turn recorded in its Log
- Meeting summaries and memory
- Cost charged to credits
The loop. Your answer in the Inbox, a finished background job, a reply email or a task another employee finished wakes the employee again. It picks up where it left off until the task is done, failed or removed.
Live: meetings, video calls and Rooms
The employee talks and listens in real time with its avatar, uses tools during the conversation and hands longer work to background jobs. It knows its open tasks and recent desk work.
At the desk: always on
Between conversations the desk waits at no cost. When something arrives it wakes the employee for one work turn, then the employee writes down what it did and goes back to waiting.
AI Employees
Create and manage the organisation's AI employees. Each employee's page is grouped into coloured, foldable sections, with its chat always open beside every tab.
Create an employeeLive
Name, description, role, persona, instructions and key guidelines.
Choose avatar and voiceLive
Pick a live video avatar and a natural voice.
Custom avatar requestLive
Request a custom avatar and follow the request's status.
Employee pageNew
Overview, Work, Meetings, Knowledge & files, Memory, Log and Settings tabs. Every tab uses the same sections: a coloured header, one line of description and a fold for the details.
Chat with an employeeNew
A chat panel that stays open beside every tab. Messages go to its desk, with documents and photos attached if you like.
Brain shown per employeeNew
Each employee's Settings tab shows the organisation's Brain, backup brain and Voice it thinks with; the Owner changes them for everyone in Organisation › Brain.
Own Claude agentNew
Give an employee its own Claude agent, environment and vaults (for example one with Apollo). Blank fields use the organisation's default. A Check button looks the agent up first.
Desk settingsNew
Desk on or off, autonomy level, daily budget, background jobs per day, emails per day and turns per hour, all in the Settings tab.
Phone call permissionNew
Off, Ask me each time, or Allowed, set by Owners and Admins, with a calls-per-day limit.
Own mailboxLive
Connect a Microsoft 365 mailbox. The employee reads incoming mail, writes drafts and sends from its own address.
Employee directoryLive
Each employee knows the others: names, titles, capabilities, responsibilities, contact details and reporting line.
Memory across meetingsLive
Remembers earlier meetings and picks up follow-ups the next time.
Memory tabNew
The summaries of meetings, video calls and Rooms the employee brings into later conversations, newest first, with filters by kind. Owners, Admins and its supervisor can delete one; the Log says who.
CRM role per employeeLive
None, Read, Write or Admin access to the built-in CRM.
Edit, list and archiveLive
Change the profile, language, memory and tools; see every employee; retire one without losing its history.
Cost breakdownLive
What each employee has cost, broken down by provider.
Video call buttonLive
Start a face-to-face video call with the employee from its page.
The DeskNew
Employees keep working between meetings. The desk costs nothing while there is nothing to do, and wakes an employee within seconds when there is.
Turn the desk onNew
Every desk starts off. An Owner or Admin turns it on per employee, and can pause and resume it.
What wakes an employeeNew
A new email in its mailbox, a message or task from you, a request in a Room, a CRM follow-up falling due, your answer in the Inbox, a finished background job or phone call, a playbook, or one of its duties.
One-step playbooksNew
When something happens, a role's employee gets a task by itself: when a lead is saved, a call ends or is missed, an email, WhatsApp or Teams message arrives, a task or mission changes, a deal moves stage, an approval is decided, on the hour, or with Run now. An optional condition narrows it, for example only leads from a customer-care line, picked in plain words. Owners and Admins write one with New playbook on the Playbooks page: its name, what starts it, who does what. It costs one task and one turn of the employee, and shows as one line in the Activity log with its cost. More steps are added later in the same editor, one at a time.
RolesNew
Sales, Customer care, Manager, Owner or any role you add, held by employees and people. A playbook gives work to the role: the first employee holding it who is at work takes it, or the one with the fewest open tasks; a disabled employee or a desk that is off gets nothing.
DutiesNew
Any number of recurring lines per employee, each with days, a time on the organisation's clock and what to do in plain words, on the employee's Settings tab. The daily review is one of them.
Playbooks stay safeNew
A playbook gives no new powers: the employee's instructions, autonomy and Approvals still decide. A customer's words stay outside text. Each playbook runs at most 20 times a day and spends at most 20 credits a run and 100 a day unless you change it, a playbook never starts on its own work, and a chain of playbooks stops after three.
GoalsNew
The organisation's goals in plain words with a number and a period, for example 10 new qualified leads a month, with how far each is and who changed the number last. Owners and Admins set them on the Playbooks page; the manager can update the number.
Morning planNew
Whoever holds the Manager role reads the goals, each employee's open and stuck work and yesterday's results at 08:00 on working days, and gives the day's tasks down the org chart.
Evening reportNew
At 18:00 on working days: what was done, what is stuck, what needs you and the credits spent, per employee, counted exactly, with the manager's own words. It goes to the Owner (or whoever you pick) by WhatsApp, email or only in SenseOS, and the latest one is on Home.
Nothing falls throughNew
A failed task, desk work that failed every try, a playbook step nobody could take, or a message to an employee who is disabled or whose desk is off becomes one task for the manager, at most 10 a day.
PlaybooksNew
Work in several steps, handed from role to role. The Playbooks page has four tabs: My playbooks, Templates, Runs and Roles; a gear opens Setup (outside apps, goals and report, approvals). Each playbook is one row: a round icon for its job function, its name, the flow as chips (when, then who does what), one line on how it is doing, an On/Off switch, and icons with tooltips for Edit, Try it, Run now, See its runs and More (copy, delete). A playbook that cannot run says why on its row in red, with a link to fix it. A playbook starts when something happens, or by hand. Saving a changed step makes a new version; a run keeps the version it started on.
Playbook stepsNew
Do (an employee holding the role does it as an ordinary desk task and can write notes down), Wait (a time, or until something happens to the same record), Ask for a yes (a person holding the role says yes or no in Approvals), Check (tests one of the notes and picks the next step, no AI, no cost) and Tell someone (a short message to members only). Each kind has its own square icon and colour everywhere: starts violet, Do blue, Wait amber, Check cyan, Ask for a yes pink, Tell someone teal. Where a role does something, the photo of the first AI employee holding that role stands next to the step, with a tooltip such as Sales: Michael.
Notes and the runNew
Each run carries notes: what started it and what each step found out, with whose words each entry is. Customers' words stay outside text through every step. The run shows the steps one under the other, the notes and the credits used. A run is saved step by step, so a restart never loses it.
Try itNew
Tries a playbook with sample facts: employees really work the steps, but nothing is sent outside the organisation and nothing in the CRM changes; what they would have sent is shown on the run. Requests for a yes and messages go only to you, marked TEST, and waits are cut to a minute. A trial shows on the Runs tab with a grey Trial mark.
Side by sideNew
A Side by side step sends work down two to four branches at the same time, each a short list of steps. The playbook goes on when all branches have finished, or when the first one has (the others are stopped). What each branch found out comes back into the notes.
Start another playbookNew
A step that starts another playbook (for example Escalation) with a copy of the notes and waits for it; what it found out comes back. A playbook switched off can still be started this way. A playbook never starts itself, at most three start each other in a row, and one another playbook starts cannot be deleted.
Runs: every run in one listNew
The Runs tab lists every run of every playbook, newest first, each marked Needs you, Working, Finished, Went wrong or Trial, with what started it and where it stands now. Filters show all, the ones waiting for you, working, finished or gone wrong; See its runs on a playbook shows that playbook's only. A run opens in place: what happened step by step, and the notes so far. Pause and Stop are icons on the run: Pause holds it with its branches and the playbooks it started (nothing new starts, a task an employee already has may finish), Go on carries on, Stop ends it for good, cancelling its open task and withdrawing its open request for a yes.
TemplatesNew
The Templates tab is a library of ready-to-use playbooks grouped by job function, each with its own round icon, colour and count: Customer Service, Marketing, Sales, Operations, Accounting, Human Resources, Project Management and General. Look at the steps shows what a playbook does in plain words and who in your team would do each step, before you add it. Add to my playbooks adds it switched off; Try it first adds it switched off and opens a trial that sends nothing. It names roles, not people (Owner, Manager, Sales, Customer care, Operations), and the screen says which roles nobody holds yet. A playbook written for one kind of business (property, clinics, shops, professional services, hotels and restaurants, trades) carries that as a small label. The clinics' playbooks never give medical advice.
Lead fit scoreNew
A lead can have a fit score from 0 to 100, on the lead, in the list (sortable) and on its pipeline card; its stars follow it. Prospecting runs in four steps (find in Apollo, save the new leads, score and qualify by an editable SCORING with a bar of 70, tell the Owner), each passing on what the next needs.
Web search for every BrainNew
Employees search the web in tasks, background jobs and playbooks with any Brain: Claude Opus and Sonnet with their own search, ChatGPT, Gemini, Fable and Haiku through SenseOS's Google search, charged as Web search (At the desk and in playbooks). Up to 5 searches a turn, 30 a background job.
Start nowNew
On the Runs tab, a run that was not started (a daily limit was reached, say) has a Start now button: it starts that run once, from what started it, past the daily limits this once, and says who started it.
A caller's lead sourceNew
A lead saved for a caller (customer-care line or the website's call button) takes its source from the call: Website or An incoming call. SenseOS sets it, during the call or in a playbook step about the call, and the employee can't change it later. "When a call ends" can check where it came in: the phone or the website.
Incoming call follow-upNew
A Customer Service template that starts when someone from the public calls (the customer-care line or the website's call button): Customer care makes sure the caller is a CRM lead, Sales emails them after a person's OK in Approvals, and the Owner is told. It is the only thing that acts on such a call: employees are not woken after an incoming call, don't pass work from outside on to each other, and Marketing leaves callers' leads alone. "When a call ends" can check who called: the public or a member.
Notes a step writes downNew
A Do step can write notes down for the steps after it: a word, a number, or a whole list or report. The employee can write them in any turn it works on the step, also after a background job comes back, and the step cannot be finished before they are written. If a step is closed without them, the run shows Went wrong with the reason and no message goes out. A Tell someone step that includes a note sends the note itself: a short one on its line, a list or a report under its own heading, with the link to the run last. The message comes from the employee who did the work, from its own mailbox. What the employee wrote after reading outside material goes to your own people with a line saying so; words that came in from outside as they are, and anything to an outside app, stay out as before.
Playbooks by job functionNew
My playbooks has one tab per job a playbook does: Customer Service, Marketing, Sales, Operations, Accounting, Human Resources, Project Management, and General for anything else, each with its icon and how many it holds; one job function shows at a time, so the list stays short, and a last tab, All, shows every function under its own heading. Templates has the same tabs, and the one you pick is kept when you move between the two. A playbook added from Templates takes its template's job function. You choose it when you write a new playbook, and change it in the editor under Category, saved on its own.
Templates for every job functionNew
Every job function has at least ten templates to start from, except Marketing with seven. Fifty are new, ten each: Operations (morning check, a task that could not be done, ordering from a supplier, chasing a late delivery, Friday review, setting up a new customer, stock check, renewals, when something went wrong, cover for someone away), Accounting (send an invoice, unpaid invoice reminder, a bill arrives, expense claim, month-end close, weekly cash check, deposit, refund, costs review, papers for the accountant), Human Resources (new starter, job application, after an interview, time off, off sick, three-month review, birthdays and anniversaries, someone leaving, a question about the rules, monthly team check-in), Project Management (kick-off, weekly status, customer update, deadline near, overdue tasks, change request, meeting notes to tasks, hand over, project at risk, what we learned) and General (morning briefing, end-of-day wrap-up, email or WhatsApp from someone new, finished work, meeting preparation and follow-up, asking for a document, weekly summary, a decision is needed). In each one a person says yes before anything is sent outside the organisation or money moves, no employee ever pays, refunds or orders by itself, and it ends by telling a person how it went. They name the positions Finance, HR and Project manager next to the ones you know.
ProspectingNew
A template under Sales: every morning at 9 the employee in the Sales position starts a background job that searches Apollo for people who fit your ideal customer, which you write once at the top of its step (industry, company size, job titles, countries). It leaves out anyone already in the CRM, by email address or by name and company, and anyone without an email address Apollo marks as verified. It adds ten new leads a day to the CRM with name, job title, company, email, phone, website, city and country, the LinkedIn address, industry and company size, marked campaign Prospecting and medium Apollo. It looks up at most 30 people a day in Apollo and starts at most two jobs; if it ends with fewer than ten it says how many and why. It writes to nobody. The Owner is told the count and the names with a link to the run. Apollo must be connected to the organisation's background jobs, and each look-up that reveals an email address uses your Apollo credits.
Sales playbooksNew
Under Sales in the library, ten templates: Inbound lead qualification, Lead to meeting, Cold outbound sequence, Website lead: answer at once, Follow-up after no reply, Discovery call: prepare and recap, Proposal follow-up, Win back a lost deal, After a meeting: next steps and CRM, and Ask for an introduction. They name the roles Sales, Owner and Manager, arrive switched off, and each ends by telling a person how it went. What is a judgement (how far to look into a lead, how good is good enough, whether a lost deal is worth a second try) is left to the employee's own instructions: the playbook only says when to judge. Writing to someone outside still goes through Approvals as always.
Messages that say what they are aboutNew
A message a playbook sends to a person (a Tell someone step) now says what the run is about, for example the lead or the call that started it, and ends with a link that opens that run on the Runs tab. Words that came from outside the organisation are still never sent: then only the record is named.
Social media playbooksNew
Under Marketing in the library, seven playbooks for social media: Weekly content plan (Monday 8:00), Idea to post, Trend watch (every morning; ends quietly when nothing fits), One idea, three networks (an Instagram carousel, a Facebook post and a LinkedIn document post at the same time), Post went out, Post not posted yet, and Monthly account check (the first Monday of the month). They name the roles Owner and Marketing. The employee holding Marketing writes each post into Marketing with its picture and time; every such post waits in Approvals for a person's yes whatever the autonomy setting, and no employee can publish. A playbook can now start when a post goes out, could not be posted, or is approved but still not posted, and on a day or week of the month. Facebook is a third network next to LinkedIn and Instagram: SenseOS posts on your Page once it is connected, and says plainly when it is not; LinkedIn is copy by hand until its company page is connected.
Social media: comments, messages and numbersNew
After a post is out, SenseOS reads what comes back. LinkedIn can be connected to the company page, so SenseOS posts approved LinkedIn posts itself; LinkedIn's sign-in lasts 60 days and Marketing says so before it runs out. For Instagram, Facebook and LinkedIn, Marketing shows Comments, Messages and Numbers each as Connected or Not connected with the network's own reason; LinkedIn does not offer a page's messages to other apps. The employee in the Marketing position reads comments and messages, writes replies, and reads the numbers per network (reach, likes, comments, shares or sends, saves, followers), this week against last week. A reply waits in Approvals for a person's yes; the organisation can let short simple replies (no link, contact detail, price or figure, at most 280 characters) go out by themselves. What people outside write is always marked as such and can never make an employee do anything but answer it. A playbook can start when a comment or a message arrives. Five more playbooks under Marketing in the library: Weekly social report (Friday 16:00), Winner follow-up (Monday 9:00), Comments and messages, Lead from social (Instagram and Facebook; LinkedIn does not allow it) and Complaint in public (a holding reply, the Owner told, Escalation run). LinkedIn comments are removed after 48 hours, as LinkedIn requires. Comments, messages and numbers need each network's permission for SenseOS's app; until it is granted they say Not connected.
X as a marketing channelNew
X (Twitter) is a fourth network next to LinkedIn, Instagram and Facebook. An Owner or Admin connects the organisation's X account in Marketing › Settings. The employee who does the marketing writes X posts of up to 280 characters, posts with up to four pictures, or threads of two to ten posts; each waits in the Inbox for a yes, with its words and pictures exactly as they go out, and SenseOS posts it at its time. A thread that was cut off goes on from the next post, never posting one twice. X charges for each post, so SenseOS takes at most 10 X posts a day. Not connected, you post them yourself.
SenseOS proposes playbooksNew
When the same kind of work reaches the manager three times in two weeks because no playbook covers it (messages to an employee who is away, tasks or desk work that keep failing), the manager drafts a playbook for it. The task is written from the organisation's records only, never from what customers wrote; the draft uses only Do, Check, Wait, Ask for a yes and Tell someone steps, existing roles, no links, email addresses or phone numbers, and no words copied from the messages. It waits in Approvals for an Owner: only an Owner's yes adds it, switched off and tagged "Proposed by". Refused or unanswered in 7 days, nothing is made, and the same kind is not proposed again for 30 days. At most one a day and three waiting; a switch on Playbooks → Setup (the gear) → Goals & report turns it off.
Notices with answersNew
A Tell someone step can include answers from the notes, such as the Monday pack. Answers holding words from outside the organisation are never sent; the message says to read them on the run.
Playbook editor: Steps and MapNew
One editor with two views of the same steps. Steps shows what starts the playbook and each step as a card, top to bottom, with + between them; a pencil opens that card for changing in place, and its Save and Cancel are in the card: saving saves that step only. Map shows the same playbook as boxes and arrows with their tops on one line: a pencil on a box opens its fields right under it, with Save, Cancel and Remove as icons; drag from a box's "if" to another box for a condition, drag an arrow's end to change where a step goes, + on an arrow inserts a step, and a box stays where you put it (Tidy up lays them out again). The side column says Ready to run or what is missing, lists the kinds of step you can add, and holds the limits. On a phone the Map is for looking and opening boxes; the fields show under it.
Conditions on connectionsNew
A step can have several connections out, each with a short label ("if not a fit"). Drag from a box's "if" handle onto another box, then click the connection's word: its fields open under the box, with Save and Cancel. A condition is a plain check on an answer in the notes (no AI, no cost) or, on a Do step, the judgement of the employee who did the step, who picks the connection when finishing. Conditions are checked in order; when none fits the run takes the step's "otherwise" connection, so it cannot get stuck. The Steps view shows the same conditions as "If … go to …" lines.
Ready to run, and loop protectionNew
Next to the steps the editor says Ready to run, or lists what is missing (a role nobody holds, a step with a problem), each with a link to fix it. A step with a problem cannot be saved, so a playbook can never be switched on broken. Warnings (a step nothing leads to, a circle with no Wait or Ask for a yes) do not stop a save. Loop protection is always on: a step runs at most 5 times in one run, and a run takes at most 30 steps.
Playbooks that come with SenseOSNew
Behaviour that used to be fixed in SenseOS is a playbook you can see and change on the Playbooks page, tagged Comes with SenseOS. Each starts with exactly what SenseOS did before, so nothing changes until you edit one; behaviour that did nothing before arrives switched off. It cannot be deleted: edit it, switch it off (the row then says what stops happening) or put it back as it came (under More).
Approval copy to WhatsAppNew
A playbook that comes with SenseOS, switched on: when an employee asks for approval, the person who decides also gets it on WhatsApp with Approve and Decline buttons (a question asks for a reply), only while it still waits for an answer. Change its wait, for example to 60 minutes, to send the copy only if nobody decided in the Inbox or the Office first. Switched off, requests stay in the Inbox and the Office; a playbook's own Ask for a yes steps still go to WhatsApp.
Approval reminderNew
A playbook that comes with SenseOS, switched off: after a day without an answer the decider is reminded; after two days the Owner is told. A decision ends it.
How long approvals wait, and who decidesNew
On the Playbooks page: Approvals expire after (7 days unless you change it), Marketing posts expire after (4 hours), and who decides when an employee puts a task on waiting: as before (the Room owner, else who gave the mission, else the employee's creator), the employee's supervisor, or a role. Requests now also expire on the clock. Who is allowed to decide does not change.
Wait and Tell someone steps, more choicesNew
A Wait of 0 minutes checks once whether its event already happened. When a Wait ends it writes "waited: happened" or "timed out" into the notes, so a condition on its connection can branch ("decided → finish"). A Tell someone step can go to the decider of the approval the run is about, on one fixed channel (WhatsApp, email, or the app only), or send the approval's own WhatsApp copy. A run with no Do step gives nobody a task and is not counted as work.
Outside apps send to SenseOSNew
On Playbooks → Outside apps, an app such as a web shop, a form, Zapier or Make gets its own address and a signing secret, shown once. Each signed message becomes an event (an outside app sends something), so a playbook can start on it and test its fields. Unsigned, older than 5 minutes, repeated or bigger than 64 KB messages are refused and logged; at most 60 a minute per app and 2,000 a day. What an app sends is always words from outside.
SenseOS sends to outside appsNew
Add an app's https address once and choose which employees may send to it and whether playbooks may. An employee sends to it by name with a desk tool; a Tell someone step can send to it instead of a role. It goes through Approvals like email to someone outside (always when outside text is in the work, or when the app says always ask first). Private, internal and SenseOS's own addresses are refused every time, redirects are not followed, each message is signed, at most 50 sends a day unless you change it, and a trial sends nothing. "Send a test" checks the address.
Playbook budgetsNew
Each run stops at its budget (20 credits unless you change it), counting its branches and the playbooks it started; each playbook starts at most 20 runs and spends at most 100 credits a day; a run takes at most 30 steps in all. A playbook does not start again for a record it is already working on (a customer's reply is not a new case). A run that stops because nobody could do a step goes to the manager.
Playbook and duty work in the Activity logNew
A turn a playbook or a duty started is labelled with it and shows what it cost; the Playbooks page shows each playbook's runs and credits today and what it did lately.
One work turnNew
The employee reads what happened, uses its tools and writes down what it did. Several wake-ups at once are merged into one turn.
Desk toolsNew
CRM, read and draft email and send it from its own mailbox, its task list, tasks for employees, background jobs, contacts and employees, notes and questions for its supervisor.
Autonomy levelsNew
Paused, Assistant (drafts, tasks for itself and other employees) or Teammate (CRM changes, internal email). Anything above the level becomes an Inbox request.
Working limitsNew
Daily credit budget, turns per hour, emails per day, background jobs per day and calls per day. When one is hit the employee stops and says why.
Phone calls from the deskNew
Places calls by itself or after your OK, watches each call, and is woken with the summary and transcript.
Desk and calls know each otherNew
In web calls and Rooms the employee knows its recent desk work. At the desk it sees its recent meeting summaries, so promises made in a call get done.
Outside text stays outsideNew
Email and other outside text can't pass as your instruction. A turn that read it can only propose emails and CRM changes, not do them.
Who sees a deskNew
Owners and Admins see every desk; a member sees the desks of the employees they supervise.
Safe retriesNew
A turn that failed before doing anything is retried. Once it acted, it is never repeated.
Tasks and WorkNew
One task list per employee, from any Room and from its desk, and a record of everything it did.
One personal task listNew
Every task given to an employee, from any Room's mission board or its desk, with where it came from.
Room requests become tasksNew
Ask an employee for something in a Room and it takes it as a desk task. The chat says it took it, and its desk then works on it by itself.
Give a taskNew
From the Work tab, with details and attached documents and photos. Files are checked before the employee reads them.
Work tabNew
Tasks grouped as Needs you, In progress and Finished. Each opens to its notes, result, links and the history of the work on it.
LogNew
Every desk turn, linked to its task, with the detail folded away until you open it. One combined Log for all employees.
Remove a taskNew
By hand from the Work tab, the Room board or the Inbox, with a confirm step, or by asking the employee. Only a member who may remove it can.
Tasks in callsNew
In web calls and Rooms the employee knows its list and can finish or annotate a task. Tasks it unblocks wake the employees waiting on them.
InboxNew
One place for everything an employee is waiting on you for.
One queueNew
Held desk actions (emails, CRM changes, tasks for others, phone calls), questions to the supervisor, Room tasks waiting on you and questions from background jobs.
Approve or rejectNew
Approving carries out the action with every check run again. Rejecting with a note wakes the employee so it learns why.
Answer with filesNew
Attach documents and photos to your answer for the employee.
The right person decidesNew
The employee's current supervisor, from the org chart. Approving a CRM change needs CRM Write access yourself.
Badge and Home cardNew
A count on the Inbox menu item, and decisions on Home with one-click Approve for task decisions.
In meetings and calls
What an employee can do while it's in a meeting, a video call or a Room.
Natural voice conversationLive
Listens and answers in real time with a speaking video avatar.
Knows when it's addressedLive
Responds when spoken to by name, stays quiet otherwise, and keeps track of who is speaking.
Varied greetingsNew
Employees joining together don't all say the same hello.
Camera on or offNew
Turn an employee's avatar video off to save cost; voice and everything else keep working. Only the person who started the call can switch it.
Reads and writes meeting chatLive
Reads the Teams chat and posts written answers, links and summaries.
Shares results in chatLive
Generated images, decks and files arrive in chat as titled links. Web calls show images as pictures.
Meeting rosterLive
Knows who is in the meeting, by live participant names.
Facilitator modeLive
Runs a stand-up, going round the participants in order.
Present modeLive
Presents a deck slide by slide and answers questions about the slides.
Web searchLive
Looks up current facts before answering.
Contacts and employeesLive
Looks up people and saves new contacts; knows which employee handles what.
Send email and phone callsLive
Sends email in the background and places outbound phone calls while it keeps talking.
Its desk workNew
Knows and can search its recent desk work and task list, in web calls and Rooms started by its supervisor or an Admin.
CRM toolsLive
Searches, reads, creates leads, updates records, logs activities and drafts quotations, in web calls and Rooms only, capped by the role of the person who started the session.
Background jobs and progressLive
Hands longer work to a job and keeps talking. A chip names the job, counts the time and shows Done or Failed.
Background jobs
Longer work handled by Claude Managed Agents. The employee starts the job, follows it up and brings the result back, in a conversation or at its desk.
Images, decks and web pagesLive
Generates images, builds Gamma presentations and publishes simple web pages.
ResearchLive
Investigates a question and reports back.
Prospect lists with ApolloNew
Finds decision-makers through the Apollo tools on the employee's agent, waiting for Apollo's search to finish.
Business systemsLive
Looks up records in connected systems such as Odoo.
Shared filesLive
Reads files shared in a call or attached to a task, through signed short-lived links.
Asks for an OKNew
When a job needs your input it stops and asks in the Inbox, then continues with your answer.
Budget per jobNew
Each job has a spending cap. A job that reaches it stops and says so plainly.
Live job statusNew
The employee sees its jobs as they are now, and says which tools they reach.
The organisation's own workspaceNew
Jobs run on the organisation's own Anthropic key, stored encrypted, and its default agent or the employee's own.
Meetings
Schedule employees into meetings on the major platforms.
Meeting platformsLive
Microsoft Teams, Zoom and Google Meet.
AgendaNew
Upcoming meetings as an agenda, with day, week and month calendar views.
Create, edit and cancelLive
A meeting with a link, a time, an employee and participants.
Send the employee in nowLive
Start the employee in a meeting immediately, and stop it. See which meetings have an employee in them right now.
Joins from its invitationsLive
An employee with a mailbox joins meetings it is invited to.
Summaries, transcripts and memoryLive
A summary, transcript and artifacts for each session; what was agreed carries into the next one and to the desk.
Usage and cost per sessionLive
Detailed usage and cost of every session of a meeting.
Video calls
A one-to-one browser video call with an employee, without needing Teams or Zoom.
Start and end a callLive
Call an employee from the browser with camera and microphone; a clock shows how long it has run.
Live avatar videoLive
The employee's avatar talks back in real time, or voice only with its camera off.
Type during the callLive
Write instead of speaking. The employee answers by voice.
Share photos and documentsLive
Photos, PDF, Word, Excel, CSV and text files up to 10 MB. The employee sees the photo or reads the document.
Results panelLive
Links, image previews, job progress and posts, next to the video.
Files kept with the callLive
Shared files stay with the call's meeting and are deleted with it.
Rooms
A meeting room for you and up to four AI employees at once.
Create and manage roomsLive
Name a room, choose its employees, rename it or archive it. Every room is listed on the Rooms page.
Enter, add and send outLive
Entering starts the room's employees, each on its own video tile. Bring one in or send one out during a visit.
Talk or type to one, several or allLive
Address one employee, a few or everyone, by voice or in the chat.
Brainstorm togetherLive
Employees take turns and build on each other's ideas.
Requests become desk tasksNew
What you ask an employee becomes a task on its desk, which keeps working on it after you leave.
Missions and task boardsLive
Missions for one employee or several, broken into tasks you can edit, reassign, retry, close or remove.
Share photos and documentsNew
Attach files in the room chat for the employees to see and read.
Camera on or offNew
Switch any employee's avatar video off to save cost; it keeps talking.
Chat history and visit costLive
The conversation is kept between visits; live and past visit costs are shown.
Built-in CRM
Business development from prospect to onboarded client, modelled on Odoo CRM. It belongs to the organisation, and access is set by CRM role.
Companies and peopleLive
Prospects and clients, with their details and history.
LeadsLive
Add leads with a source and an owner, filter the list, and qualify or disqualify with a reason.
PipelineLive
A compact kanban that fits all five stages on a laptop screen: drag opportunities, with open pipeline value and totals per stage.
OpportunitiesLive
Expected revenue, probability and close date. Mark won or lost with a reason, or reopen.
CurrenciesNew
A default currency for the organisation, and a currency per deal and quotation.
Activities and notesLive
A timeline of calls, meetings and notes; due follow-ups wake the employee who owns the record.
Quotations and onboardingLive
Line items and totals; accepting a quotation wins the deal, makes the customer a client and starts an onboarding checklist.
Stages and lost reasonsLive
CRM Admins configure pipeline stages and the reasons a deal can be lost for.
CRM rolesLive
None, Read, Write or Admin for every person and employee, checked on every action. An employee is capped by the role of whoever started the session or supervises it.
Presentations
Decks employees can present in meetings.
Upload PowerPointLive
Upload a PPTX file and it becomes a presentable deck.
Build and edit decksLive
Create a deck in one step or slide by slide; edit, reorder and bulk-update slides and assets.
Deck summariesLive
Each deck gets an AI summary, so an employee can pick the right one, including today's.
Organisation and people
Everything a person configures, in one Settings area grouped as You, Organisation and App.
My profile and photoNew
Name, job title, phone, timezone and language. Upload, replace or remove a profile photo, shown instead of initials.
Password and securityLive
Change or set the password you sign in with.
Organisation profileNew
Description, vision, mission, address, phone and email, used in every employee's instructions. An AI writer drafts or improves each text field, with Undo.
BrainNew
The Owner connects Google Gemini, Anthropic Claude and OpenAI ChatGPT with the organisation's own keys (or uses SenseOS's, in credits) and chooses the Brain, its effort, a backup brain and the Voice for every employee.
Claude workspaceNew
The organisation's own Anthropic key (stored encrypted, shown only by its last four characters) and its default agent, environment and vaults.
Members, roles and invitationsLive
Invite people by email, change their role (Owner, Admin, Member) and remove them.
Org chartLive
People and AI employees in one chart. An employee's manager is its supervisor for the Inbox and desk.
ContactsLive
The organisation's address book.
API keysLive
Create, list and revoke organisation API keys.
Separate data per organisationLive
Each organisation has its own database. A user can belong to more than one organisation.
Plans, credits and usage
Plans, prepaid credits and a cost record for everything employees use.
Three plansNew
SenseOS Free ($0), Basic ($19, 190 credits a month) and Pro ($49).
Change planNew
Upgrade now with the prorated difference and its credits; downgrade or cancel at the next renewal. Credits already bought are kept.
Buy creditsNew
Top up with $10 to $500 of credits.
Checkout confirmed on returnNew
A paid checkout is confirmed as soon as you come back.
Credit balance and activityLive
Credits with their USD value, and every purchase and charge with the meeting and employee behind it.
Usage by periodLive
Spent, credits used and credits remaining, from Today up to the last 12 months.
Accurate provider costsLive
Every provider priced from its own figures; desk turns at the price of the model they ran on.
Pay as you goLive
Sessions charged once with the platform margin; desk turns, desk calls and jobs charged as they happen.
Sign-up credits and adjustmentsLive
New organisations start with free credits, and SenseOS's team can add or remove credits.
Stops when out of creditsLive
Meetings, calls, Rooms and desk turns don't start without enough credits.
Home and portal
The signed-in home screen and the app around it.
HomeNew
A greeting with today's date, decisions waiting on you, today's agenda and your recent Rooms with their employees.
SidebarNew
Home, Inbox, Meetings, Team, Rooms, CRM and Settings, each with the same icon as its page heading.
Page headingsNew
Every main page opens with the same heading: an icon tile, the title and one line about the page.
InnovaSense logo and versionNew
The InnovaSense circle logo in neon at the top of the sidebar, and the live version at the bottom left at all times.
EmployeesLive
Every AI employee with its status, and a way to create a new one.
Light and dark modeLive
Switch in Settings, Appearance. Your choice is remembered.
Installable appLive
The portal can be installed as a web app.
Website and sign-in
What visitors see before they sign in.
Public landing pageLive
Features, how it works, templates, pricing (Free, Basic, Pro) and a live product preview.
Functions pageNew
This public list of SenseOS's functions at benita.one/functions.
Sign up, sign in and outLive
Create an account and organisation; email and password with sessions that refresh themselves.
Join by invitationLive
Accept an invitation link to join an organisation.
Google sign-inPartial
Not available yet: it is still a placeholder.
Billing return pagesLive
Success and cancel pages after checkout.
Platform and operations
The parts that keep it running.
Concurrent sessionsLive
Up to 4 live employee sessions at once on the current server; desk turns don't take live slots.
Desk serviceNew
The desk runs on its own, next to live sessions, and wakes within seconds when work arrives.
Session orchestration and workersLive
Starts, monitors, recovers and cancels employee sessions, with health checks on every worker.
Event busLive
Platform events with a live stream and a status page.
Health, version and metricsLive
A health check with active sessions, a public version number, and monitoring dashboards.
WebhooksLive
Billing, phone calls and mailbox notifications arrive the moment they happen.
Security hardeningNew
Per-organisation Claude keys that fail closed, file checks before reading uploads, and outside text kept apart from instructions.
One-command deployLive
Every release is rebuilt, updates each organisation's data and checks its health in one step.
VersioningLive
Major.Minor.Function.Build, shown in the portal and the API.
In development
Started, not usable yet.
WhatsApp for employeesIn development
Each employee with its own WhatsApp number: text and voice notes in and out, handled at its desk. The design is approved and the groundwork is in.
Ready to build your
First AI employee?
Create an AI employee and put it to work in minutes.