Adilm

AI employees · 20 specialised roles

Personal Assistant — shown working in the homepage walkthroughAlexExecutive
Financial Manager — shown working in the homepage walkthroughClaraFinance
Social Media Manager — shown working in the homepage walkthroughMayaMarketing
Meeting Notetaker — shown working in the homepage walkthroughSamProductivity
Customer Support SpecialistJordanCustomer
Sales Development RepresentativeDeanSales
Account ManagerEliasClients
Marketing CoordinatorZoeMarketing
Market Research AnalystPriyaResearch
Content WriterLucaContent
CRM AdministratorLeoSales ops
Scheduling CoordinatorMinaOperations
Project CoordinatorGraceProjects
Operations ManagerMarcusOperations
Accounts Receivable SpecialistNiaFinance
Recruitment CoordinatorElenaHR
HR Operations AssistantAmaraHR
Procurement AssistantOmarProcurement
Compliance and Records OfficerTheoCompliance
Data and Reporting AnalystKaiData

Departments

Sales3Sales Development RepresentativeAccount ManagerCRM Administrator
Marketing3Social Media ManagerMarketing CoordinatorContent Writer
Customer support1Customer Support Specialist
Finance2Financial ManagerAccounts Receivable Specialist
Operations3Scheduling CoordinatorOperations ManagerProcurement Assistant
HR and recruitment2Recruitment CoordinatorHR Operations Assistant
Research and data2Market Research AnalystData and Reporting Analyst
Projects1Project Coordinator
Compliance and records1Compliance and Records Officer
Executive support2Personal AssistantMeeting Notetaker

04 — Platform

The workspace, object by object.

Everything an Adilm employee does happens inside one workspace: a roster, a queue of work, the checkpoints where it stops for you, and the record of what was done.

The workspace

Interactive product walkthroughAE-01 · 3 tasks

Employees

Handles inbound customer questions in the connected inbox, resolves what falls inside its remit, and brings the rest to a person.

Work

    1. 08:41YouAssigned via voice
    2. 08:44AE-01Read the thread and the delivery policy
    3. 09:20AE-01Reply drafted
    4. 09:22AE-01Stopped at a boundary and asked for approval
    1. 08:02YouAssigned via task
    2. 08:05AE-01Started work on the overnight queue
    3. 09:14AE-0111 threads categorised, 3 flagged as billing
    1. Fri 16:30YouAssigned via task
    2. Fri 17:48AE-01Delivered Unresolved issues, week 21
    List

    Unresolved issues, week 21

    AE-01 · T-2274 · Fri 17:48

Assign via

Describe the assignment.

Oversight

Needs approvalT-2288

Waiting for you

Reply drafted to the customer asking about the delayed order

This is outside replying to a customer for the first time in a new thread.

Record

  • Delivered

    Unresolved issues from last week listed with their owners

    List

    Unresolved issues, week 21

    AE-01 · T-2274 · Fri 17:48

A working walkthrough of an Adilm workspace, running on example work rather than live data.

Everything above, named.

  1. 01

    The roster

    Every employee you have set up, with its role, its reference, and whether anything is waiting on you.

  2. 02

    The work queue

    Everything assigned to a role, in one list, each item carrying its own state. Work that needs you leads it.

  3. 03

    Assignment

    A task, a chat message or a spoken instruction. All three become the same object with the same record.

  4. 04

    Schedules and recurring work

    Work that runs to a cadence rather than waiting to be asked. It appears in the queue like anything else.

  5. 05

    Connected tools

    What an employee may reach, and at which level. Read is separate from act, and scope narrows both.

  6. 06

    Approval boundaries

    The actions that stop and wait for a person. The task changes state; the change is the notification.

  7. 07

    Collaboration

    One employee holds the outcome, others contribute, and every handoff is recorded with a from, a to and a what.

  8. 08

    Deliverables

    Named and typed in text. A document, a list, a draft, a schedule — with the role and reference that produced it.

  9. 09

    The activity record

    Append-only. A rejected action is recorded, not erased. This is what “keep the oversight” actually means.

  10. 10

    Retained context

    What an employee knows about your business, carried across assignments, so you do not brief it again each time.

Ten states. Each one says what happens next.

A task is always in exactly one of these. The marker shape carries the state, the label carries it again, and colour comes third — so the whole system stays legible in greyscale.

  • AssignedAccepted, not started.
  • ScheduledQueued for a stated time.
  • In progressBeing worked.
  • CollaboratingMore than one employee involved.
  • Needs informationStopped — a person must supply something.
  • Needs approvalStopped — a person must decide.
  • BlockedA system condition prevents progress.
  • Changes requestedThe person decided; work is back with the employee.
  • DeliveredComplete, record available.
  • StoppedEnded by a person.

Classes of connection, not a logo wall.

An employee reaches a class of tool at a level you set. We name the class, never a third-party product, because the products you connect are yours to choose.

  • the connected inboxnone · read · act
  • the connected calendarnone · read · act
  • the connected CRMnone · read · act
  • the connected document storenone · read · act
  • the connected helpdesknone · read · act
  • the connected billing systemnone · read · act
  • the business context you providenone · read · act

This is the whole system. Put a role in it.