What Auttendo is
Auttendo organises your work into projects, each with one agent that finishes what you ask, tells you when it can't, and asks before anything irreversible.
Work in a company happens in clusters: a campaign, a client, a product. Auttendo is organised the same way. Each cluster is a project, and each project has exactly one agent.
That agent is the teammate who owns the cluster, and you talk to it where the work lives. If you’re working on Marketing, you talk to Marketing’s agent, and the work lands in Marketing’s channels and Library. Auttendo has no roster of agents to choose from, nothing that routes your request somewhere else, and no separate chat app beside the work.
Where work starts
The workspace home greets you, shows your agents, and gives you one place to start. Type what you need into the composer and send it.
A request sent from the home opens a conversation in Tendo, your own project that nobody else can see. Work that belongs to a shared project starts inside that project instead, in one of its channels. Either way the thread has two parties from the start: you and that project’s agent.
What “finished” looks like
Ask for something and you get the thing itself, not a plan or a draft or a list of steps for you to run. The document is saved, the rows are in the database, the message has gone out. The reply then tells you what changed, in a few lines.
There is also the case where the agent can’t finish. It might be missing access, an integration might not be connected, or the data might not be there. Then it tells you what is blocking it and stops. It doesn’t make up a result or describe work it didn’t do. “Gmail is not connected” tells you what to fix. A paragraph claiming the email went out would leave you with nothing to fix and a false picture of what happened.
When the agent needs a decision from you, it asks in the thread and waits for your answer.
The last yes stays human
Before the agent deletes, archives or merges anything, it stops and asks you first. Once you answer, it picks the work back up. Nothing that can’t be undone happens just because the agent decided it should.
What a project holds
A project is a shared cluster of work. It has one agent and everything the work needs around it:
- Conversations, in channels. A conversation is the thread where you and the agent work on a request and its follow-ups. Every project starts with a General channel and adds more as the work splits up.
- A Library. The documents, databases and apps the agent makes, and the files you upload, land in the Library. It is built for finding things again rather than browsing.
- Integrations. Integrations give the agent accounts to work in, within that project’s access.
- Instructions and memory. Instructions are what you write for the agent. The agent reads them and never changes them. Memory is what the agent writes down as it works, and you correct it.
- Skills. A skill is an agreed playbook the agent follows. It isn’t another agent.
- Scheduled actions. A recurring instruction the agent runs on a schedule. Each run posts what it produced into a channel as an ordinary conversation you can reply to.
You also get a project that is yours alone: Tendo. It has one member, you, and nothing in it leaks into a shared project.