> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apollospace.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Use cases
> Where agents create value — by function and by sector. The 'how' and the 'why', not just a feature list.
**The right question isn't "what does Apollo do?". It's "what stops
being your problem once a whole area has agents?"**
## How to read this section
Most tools describe themselves by **feature**: "we have a CRM, we have
email sending, we have tasks." Apollo is better described by **work that
leaves your plate**. So this section has two axes — enter through
whichever fits how you think:
What changes in **your role** or **your area** — operations,
backoffice, planning, management, commercial, finance, people. Start
here if you think "how does this help my team?".
What changes in **your market** — logistics, healthcare, credit, real
estate, agencies, retail, services, education, manufacturing,
technology. Start here if you think "does this fit my business?".
## The pattern that repeats
Almost every Apollo use case has the same shape. Worth understanding
once — after that you'll recognize it anywhere:
```mermaid theme={null}
flowchart LR
A[Trigger
message, deadline, event] --> B[Agent pulls context
from the Company Brain]
B --> C[Decides + uses tools
CRM, docs, integrations]
C --> D{Sensitive action?}
D -->|No| E[Acts and logs it]
D -->|Yes| F[Proposes + waits for a human]
E --> G[Becomes memory
improves the next one]
F --> G
```
1. **A trigger happens** — someone sends a message, a deadline hits, a
lead goes cold, a meeting ends.
2. **The agent pulls the right context** from the
[Company Brain](/en/features/brain) — who the client is, what was
agreed, what worked before.
3. **It decides and uses the tools** — moves a lead in the
[CRM](/en/features/crm), creates a [task](/en/features/boards), writes
a [document](/en/features/documentos), triggers an
[integration](/en/integrations/composio).
4. **The sensitive stuff waits for you.** Money, contracts, heavy
external communication — the agent **proposes** and waits for approval.
The rest it handles.
5. **Everything becomes memory.** Next time is better than last time.
**Why this creates value, in one sentence:** the repetitive, low-risk
work — the kind that eats hours and rarely fails expensively — starts
happening on its own, logged and within budget, while the decisions
that matter stay with people.
## By function
Triage, tracking, routines, and tasks that move between areas without
someone pushing.
Documents, records, organization, and reconciliation — the invisible
work that holds everything up.
Goals become tasks, priorities get clear, what's in flight becomes
visible.
Overviews, nudges, and the pulse of the operation — for whoever leads
and doesn't want to micromanage.
Research, prospecting, follow-up, and CRM — the whole funnel with
agents on the team.
Entries, expenses, and reading the numbers — the agent that watches
the cash.
Onboarding, support, and relationships — continuity without depending
on one person.
## By sector
Tracking, delivery status, carrier follow-up, and incident triage.
Scheduling, pre-visit intake, and clinic backoffice — with the right
care where it's clinical.
Origination, document collection, and follow-up — with the credit
decision always human.
Lead qualification, viewing scheduling, and offer follow-up.
Account management, briefs, reporting, and content production.
Support, post-sale, catalog curation, and cart recovery.
Firms and consultancies — proposals, deadlines, and client
relationships.
Enrollment, registrar work, student support, and cohort tracking.
Purchasing, suppliers, orders, and the backoffice that connects the
floor and the office.
Sales, onboarding, support, and internal operations for a team that
already thinks in product.
## Before you hunt for your scenario
Where does your team spend hours on repetitive, low-risk work? That's
where an agent hands time back first.
Money, contracts, and heavy external communication stay with people —
the agent **proposes**. Knowing that line is half the design.
One agent, one routine, one channel. As it gets things right, you
grant more autonomy. Trust is a ratchet, not a leap.
Didn't find your exact sector? The patterns transfer — enter through the
**by function** axis, which describes the work independently of the
market.