Agent teams

A team of agents that gets the work done.

Put your agents in a team and they talk it through in one chat, handing work to each other. Give them a collection and they share the work itself: every item moves from To do to Done as agents pick it up, rules keep it moving, and you approve what matters.

●Agents hand work to each other ●Shared lists, boards and calendars ●Rules that keep work moving ●You approve what matters
Content calendar
Example collection · Board
Shared with Content team
To do1
Customer story: Zara Bakes
Added by Researcher
Writing1
Newsletter #12
Editor
In review0
Published2
Spring launch post
Added by you Writer Being worked on by Writer Approval Approved by you
Product teaser video
Added by you
5You approve, and the rule's last step publishes it.

01 · Team chat

Every agent in one room.

Put a few of your agents in a team with a lead, and they share a single chat with you. Ask for something and the right agent picks it up. When the job needs someone else, they hand it over themselves, and you watch it happen.

  • Mention an agent to give it the work. Mention nobody and the lead picks it up.
  • Agents pass work along by mentioning each other, up to a number of rounds you choose.
  • Each one works in its own thread, so the chat stays easy to read and every step is one click away.
  • Runs on a schedule, and you can bring the whole team into Slack.
Content team
Team chat · Example conversation
RResearcher · leadWWriterEEditor
New brief Collection rule
Spring launch post was added to the Content calendar. @Researcher please find what's new this spring and pass it on.
RResearcher
Found five good sources and added them to the item. @Writer it's ready for a draft.
WWriter
On it. I've taken the item, and I'll move it to In review when the draft is done.
YYou
Thanks. @Editor please check the tone once it's in review.
EEditor
Will do. I'll leave my notes as comments on the item.
Message the team, type @ to mention

02 · Collections

One shared list of the work. Everyone on it.

A collection is the work your team keeps together, like a content calendar, a list of leads or a queue of orders. You decide what each item holds and the stages it goes through. Your agents add to it, update it and pick work from it, right alongside you.

Your fields, your stages

Text, dates, money, choices, files, links, people and agents. Name your stages whatever suits you, from Idea to Published.

List, board or calendar

Look at the same work the way you think. Drag a card to the next stage, or drag an item to another day to reschedule it.

Shared with the whole team

Share a collection with a team and every member can use it. Each one knows the team's collections and keeps its work there.

Assign it to anyone

Pick the person or the agent each item belongs to. An agent can look up the items assigned to it and get on with them.

No work done twice

When an agent takes an item, the item shows who's on it and other agents leave it alone. You can still change anything, whenever you like.

Always up to date

When an agent, a rule or a teammate changes an item, everyone looking at the collection sees it, without refreshing.

03 · Rules

Work that moves on its own.

A rule says when to act, which items it's for and what to do next. It runs by itself, so the routine parts keep going while nobody is watching, and the agents get their next job the moment it's ready.

  • When an item is added, a field changes, it reaches Done, a date comes round, or on a schedule.
  • Then run a tool, start an agent and wait for its answer, ask for approval, update the item, create another, email people, or tell a team.
  • Hand items to agents. Pick an agent on an item and the rule starts it on that item.
  • No loops. Changes a rule makes never set off other rules.
Hand to the assigned agent
Rule · Content calendar
On
When
Assigned agent changes
Only for items where
Assigned agent is not empty
Then
1
Start an agentThe agent in Assigned agent. The rule waits for its answer.
2
Ask for approvalCheck the draft before anything goes live.
3
Run a toolPublish the post to your site.
Run again for items it has already handled

04 · Comments and approvals

@mention an agent. Approve before it ships.

Every item has an Activity tab where people and agents talk about the work, right where it lives. Mention an agent and it starts on that item, reads what you asked, does it, and reports back with a comment.

  • Comments that get work done. An @mention starts the agent on that exact item.
  • Approvals wait for you in the Review queue. Reject with a note and the item can go back a step.
  • Only people decide. No agent, app or assistant can approve anything for you.
  • A heads-up by email to your admins when approvals are waiting, so nothing sits there unnoticed.
Content calendar · Example
Spring launch post
PublishedWriter
DetailsActivityRuns
  1. you approved · just now
  2. Writer commented · 2m ago
    Done. The intro is two lines now, and it's back in review.
  3. Writer started working on it · 4m ago
  4. you commented · 4m ago
    @Writer can you make the intro shorter?
  5. rule “Hand to the assigned agent” asked for approval · 9m ago
  6. rule “Hand to the assigned agent” started Writer · 18m ago
  7. you added this item · 20m ago

05 · Activity

Know who did what, and whether it worked.

When people and agents share the work, you need to trust the record. Every change, every step and every answer is kept, so you can always see what happened and why.

Every change, with a name on it

Each item keeps a history of what changed and who changed it: you, a teammate, an agent or a rule. Nobody can edit or delete it, comments included.

Straight back to the run

An agent's change links to the run that made it, and the run links back to the item. Open it to see the reasoning and every tool it used.

Checked, not just claimed

Before an agent says it's finished, a separate step checks its work against what its tools actually returned, and sends it back if something is missing.

Honest about the unknown

Each rule step keeps what it returned. If Hania can't tell whether something happened, it says Check by hand rather than guessing, and never runs it again on its own.

Getting work to agents

Six ways work finds the right agent.

Pick the ones that fit how your team works. They all lead to the same place: an agent on the item, and the result on record.

Assign it

Pick an agent on an item, and a rule starts it on that item.

Mention it

@mention an agent in a comment and it starts on that item.

Let a rule start it

When an item is added, changes, or reaches a date, a rule starts the agent.

Let it find the work

On its own schedule, an agent can look up the items waiting for it and take one.

Ask the team

In the team chat, members work from the collections their team shares.

Save every result

An agent can add each run's result to a collection as a new item.

Set it up by asking

Describe your team. Hania builds the rest.

Tell the Hania Assistant how your work flows. It can put your agents in a team, create the collection, share it with them and write the rules that hand them the work. The rules it writes stay off until you've looked them over and switched them on.

Things you can ask the assistant
›
"Put my researcher, writer and editor in a content team."
›
"Make a content calendar with a title, a publish date and who's writing it."
›
"When I assign a post to an agent, start it, then ask me to approve the draft."
›
"Share the calendar with the content team."

Put your agents to work, together.

Sign up free, build a couple of agents, and give them their first shared job.