Feature
AI agents that follow a workflow
An agent in CrewX24 is not a free-roaming chat. It is a step in a crew: instructions, a model, and the tools that step is allowed to call.
Who it is for
Operators who want an assistant to triage mail, draft a reply, or check a calendar, and who also want the surrounding steps to be repeatable. The agent reasons where you put a model step. A tool step does the specific action.
Example
A support crew reads a Zendesk ticket, asks the model to draft a reply from the thread, and stops on the public reply. A person approves that send. The model does not get a private workspace dump, and the page you are reading does not expose one either.
Limits
Suggest-only autonomy can read and reason. It cannot change external systems. There is no code-execution sandbox: the product lists those languages as unavailable. Agents use the tools the crew was given, not an open computer.
Questions
Is this the same as a chatbot?
A chatbot answers in a thread. A CrewX24 agent is a step that can call a connected tool and whose result is stored on the run. The workflow around it decides what happens next.
Which model does the agent use?
Crew execution uses the provider key the workspace connects. Architect chat, which designs the crew, uses the managed model configured for that product, and it spends AI credits.