Define a real role
Shape each Video Employee around a clear mission, responsibilities, boundaries and expected outcomes.
Video Employee Creation & Operations · Early access
BE creates and operates Video Employees with defined responsibilities, approved knowledge and controlled actions—while people retain consequential authority.
In development by MAJLS LABS · Early-access roles are assessed for fit and controls.
Visible presence, defined work.
01RoleClear mission & audience
02KnowledgeApproved sources
03ActionsControlled permissions
04AuthorityHuman checkpoints
Why BE
A useful Video Employee needs a job, not just an appearance. BE begins with the role: what it should know, what it may do, when a person must decide and how the work continues after the conversation.
Shape each Video Employee around a clear mission, responsibilities, boundaries and expected outcomes.
Equip the role with approved knowledge, workflows and tools so an interaction can support durable business execution.
Set permissions, approvals and escalation paths so consequential decisions remain with the right people.
How BE operates
Set the role, audience, responsibilities, boundaries and outcomes before designing the experience.
Connect approved knowledge, conversation paths and the specific workflows the role is allowed to support.
Make permissions, human checkpoints, escalation and accountability explicit.
Run the role, review its work and improve it from real interactions without weakening its boundaries.
Early access
Join the early-access list. We will contact you when there is a suitable opportunity to explore the audience, work and controls for a Video Employee use case.
No launch-date promise and no automatic enrolment. We will use your email only for this request and relevant BE follow-up.
A Video Employee is a persistent digital role that can interact through video and support defined work using approved knowledge, workflows and tools.
No. MAJLS designs Video Employees to work alongside people. Humans retain authority over consequential decisions and the organisation defines each role’s boundaries.
A role may support approved work beyond the interaction, subject to its permissions, human checkpoints and verification. The exact capability depends on the use case and operating environment.
No. BE is being built as a standalone MAJLS product. It may also connect with ONE or suitable existing customer systems.
BE is in development and accepting early-access interest. Proposed roles will be assessed for fit, controls and operating requirements; joining the list does not promise a launch date.