Product
Agents and automations
Agents created from a task description handle repetitive work in the company's apps — on demand or on a schedule, under human control.
An agent in Slimaco is a specialized task executor that the Slimaco assistant creates from a plain-language description. The agent gets tools in connected apps, a scope of company knowledge and a way of running — on demand or on a schedule — and works within the permissions and approval rules set by the organization.
How an automation is created
- Describing the task — what the agent should do, where to get data, who gets the result and when it runs. No coding and no drawing flows.
- Creating the agent — Slimaco picks the apps, the scope of company knowledge and the schedule.
- Setting approval — you decide whether to approve every run, or approve the action for a set period after the first run.
- Work and record — the agent runs, every run is recorded, and the result goes to the chosen people or systems.
Ways to run an agent
| Mode | When the agent runs | Example |
|---|---|---|
| On demand | An employee asks for the task in a conversation with the Slimaco assistant | "Prepare a reply to this inquiry using the current price list" |
| On a schedule | Daily, weekly, hourly or on a chosen day of the month | "Every Monday at 8:00, collect open complaints and summarize them for shift managers" |
Action approval
Reading data and preparing a draft don't change anything in external systems. Write actions, such as sending a message, creating an event or changing a CRM record, go through human consent. Approval can be set in two ways: on every run of the agent, or on the first run with the action approved for a set period. Consent is tied to the tool, user, account and scope. Details are on the Integrations and actions page.
What agents work on
- Company knowledge — approved procedures, price lists, terms and agreements. When a new version of a procedure is approved, agents work by it right away.
- Company apps — Microsoft 365 and Google Workspace plus 1,000+ other apps, including CRMs, messaging and project tools. Full list: Integrations list.
- The web — research in open sources when the task needs it, e.g. market monitoring.
Automation examples by department
| Department | Automation | Runs | Control |
|---|---|---|---|
| Sales | Reply to a quote request: identify the client in the CRM, apply the price list, draft the quote | Hourly, sales inbox | A salesperson approves the quote before sending |
| Sales | Pre-meeting brief: contact history from the CRM, recent emails, client company news | Daily at 7:30 | The brief goes only to the salesperson |
| Sales | Deals with no contact for 14 days, with a suggested next step | Fridays at 14:00 | Client messages only as drafts |
| Customer service | Complaints by the current procedure: completeness, deadline, CRM ticket, reply draft | Hourly, complaints inbox | An agent approves the reply |
| Customer service | Weekly report of open complaints with cases at risk of missing the deadline | Mondays at 8:00 | The first send waits for approval |
| Finance | Overdue payment reminders matched to the client's contact history | Daily at 9:00 | Accounting approves every message |
| Finance | A spreadsheet of cost invoices from a dedicated inbox | Mondays at 7:00 | Items to clarify go to accounting |
| HR | A new hire's first-week plan based on the onboarding procedure | On demand | HR approves the plan and invitations |
| HR | Expiring trainings and certifications with reminders for the employee and manager | Mondays at 8:00 | Reminders only to company employees |
| Operations | Morning order status from project tools and changes reported by suppliers | Daily at 8:00 | Summary only for the team |
| Operations | Answers to a client's audit questionnaire based on procedures and certificates | On demand | The quality manager approves everything |
| Management | Morning brief: pending decisions, new knowledge-mining findings, sales status | Daily at 7:00 | The brief goes only to management |
| Management | Market and competitor monitoring with web research | Mondays at 7:00 | Summary only for management |
These are examples that can be built with the available features. Each automation is described in your own words and tailored to the company. More scenarios: Use cases.
Control and security
- An agent sees only the knowledge and tools within its assigned scope — no more than the user it acts for.
- Every agent run is recorded.
- Write actions go through human approval according to the chosen mode.
- Agents don't have full autonomy — how independently they act is set by policies, permissions and approvals.
- Data is processed the same way as across the platform — see Security and governance.
Status
| Area | Status | Scope |
|---|---|---|
| Agents created from a task description | Available | Slimaco creates specialized agents, gives them tools and knowledge, and coordinates their work. |
| Scheduled actions | Available | Running agents on a schedule. |
| Action approval | Available | On every run, or on the first run with approval for a set period. |
| Integrations | Available | Microsoft 365, Google Workspace and 1,000+ other apps. |