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

05 — How it works

From an uncovered function to a record of the work.

Ten steps, in the order you would actually take them. The workspace beside them changes as each step becomes current.

  1. Step 1

    Select an employee role

    You start from the work, not from the technology. Pick the role that matches the function nobody is covering.

    Interactive product walkthroughRoster
    • AE-01 Customer Support
    • AE-02 Sales Development
    • AE-03 Marketing
    See every role
  2. Step 2

    Configure its remit

    What this employee is for, in your words. Just as importantly: what falls outside it, so it knows where to stop.

    Interactive product walkthroughRemit
    • Handles inbound questions in the connected inbox
    • Outside: billing decisions, refunds, delivery dates
  3. Step 3

    Provide business context

    Your policies, your tone, what counts as an escalation. This is what it retains across assignments so you are not briefing it again each time.

    Interactive product walkthroughContext
    • Documented policies
    • Tone guidance
    • Escalation rules
  4. Step 4

    Connect permitted tools

    Choose what it may reach and at what level. Read access is separate from the ability to act, and scope narrows both.

    Interactive product walkthroughPermissions
    • Inbox — read + act, support address only
    • Helpdesk — read
    • Billing — none
  5. Step 5

    Define approval boundaries

    Name the actions that must wait for a person. This is the decision the rest of the product is built around.

    Interactive product walkthroughBoundaries
    • First reply in a new thread — waits
    • Anything touching billing — waits
    • Committing to a date — waits
  6. Step 6

    Assign the first work

    Through a structured task, a chat message, or your voice. Whichever route you use, it becomes the same object.

    Interactive product walkthroughT-2288
    Assigned
    • Assigned via voice · 08:41
  7. Step 7

    Monitor progress

    The work carries on after you close the laptop. The queue shows where every item has got to, without you asking.

    Interactive product walkthroughT-2288
    In progress
    • Read the thread and the delivery policy · 08:44
    • Reply drafted · 09:20
  8. Step 8

    Answer a question, or approve an action

    At a boundary it stops and asks, naming which boundary it hit. You approve, request changes, or stop the work.

    Interactive product walkthroughT-2288
    Needs approval
    • Stopped at a boundary and asked for approval · 09:22

    Waiting for you

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

    ApproveRequest changes
    Read how control works
  9. Step 9

    Receive the deliverable

    Named and typed in text, with the role and task reference that produced it. Never a fake file preview.

    Interactive product walkthroughT-2288
    Delivered
    • Approved replying for the first time · 09:36
    • Delivered Draft reply · 09:41
  10. Step 10

    Keep the record

    Append-only, and permanent. A rejected action stays in it exactly like an approved one — that is what makes it a record rather than a feed.

    Interactive product walkthroughRecord
    Delivered
    • T-2288 · Draft reply · 09:41
    • T-2274 · Unresolved issues, week 21 · Fri 17:48
    See the whole workspace

That is the whole path. Start at step one.