Mel, your My Team AI assistant
Mel is described in the product as your My Team AI employee: handling what doesn't need you, and queuing up what does.
Where: My Team › Mel (AI) You need: KAMI AI enabled on your company, and the My Team AI Agent right
If the tab shows a padlock, one of those two is missing. It means "not enabled for you", not "coming soon".
The four things on Mel's page
Waiting on you. Work Mel has prepared for a decision — "Mel prepared these, you decide". This is the queue to check, because nothing here moves until you act.
Handled autonomously. What Mel did without asking, over the last 7 days. Every action is logged and reversible. That is the safeguard worth knowing about before you let Mel act on its own: nothing it does is invisible or permanent.
Ask Mel. A plain-language box for questions about your team, or for handing over a job — the product's own examples are "prepare the separation checklist for Paolo" and "who hasn't completed onboarding?"
Mel noticed. Observations Mel surfaces unprompted — the kind of pattern nobody had time to go looking for, such as "27 people have not changed role in 2+ years." Useful precisely because no one asked the question.
Memory
Mel keeps facts about how your company works and applies them automatically across sessions, so you are not re-explaining the same context every time.
You can add facts yourself rather than waiting for Mel to learn them, and you can make it forget any of them at any time. The counter on the page tells you how many facts are currently in play.
This is the difference between an assistant that answers questions and one that knows your company. If Mel keeps getting something wrong about how you operate, adding it as a memory is usually the fix.
Giving Mel tasks
In Mel settings, you can create a task by describing what you want in plain language — the prompt is "tell Mel what you wish someone would just do for you".
Two things govern how this behaves:
- Mel checks every brief before saving it, so a vague or impossible instruction is
caught when you write it rather than when it runs.
- Mel always asks for approval before anything is sent. Tasks prepare work; they do
not communicate on your behalf unattended.
Tasks currently run on a schedule. Event-triggered tasks — running when something happens rather than at a set time — are noted in the product as coming next.
Changes to tasks apply to everyone in your company, not just you. Mel settings is a company-level configuration, not a personal preference.
The Team Insights report
Mel also writes the Team Insights Report on the Reports page. What that report covers is not fixed: Mel follows a step-by-step brief that you can edit in Mel settings under Report instructions.
If the report is not telling you what you need, change the instructions rather than working around the output.
Getting value from it
- Start with the queue. "Waiting on you" is where Mel's work becomes useful.
- Give it the boring recurring job first. The chase-ups and checklists are where an
assistant pays for itself, and the risk is low because nothing sends without approval.
- Feed the memory. Every correction you make twice is a fact worth storing once.
- Read "Mel noticed" occasionally. It answers questions you did not think to ask.