> ## Documentation Index
> Fetch the complete documentation index at: https://docs.salesfinity.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Companion

> What the AI Companion is, what it can do across Salesfinity and your connected platforms, and how it plans, acts, and asks for approval.

The AI Companion is a sales assistant that lives inside Salesfinity. You talk to it in plain
language and it answers from your real data: call history, analytics, follow-ups, contact lists,
and every platform your team has connected. It can also act, from drafting a follow-up to
enrolling a contact in a sequence, and it asks before it changes anything.

<Note>
  The companion is available to members of a team with an active plan. Open it from the
  companion panel anywhere in the dashboard.
</Note>

## What you can ask it to do

<CardGroup cols={2}>
  <Card title="Analyze performance" icon="chart-line">
    Connect rate by time of day, list performance, SDR leaderboards, call scoring trends. Answers
    come back as charts and metric cards, not paragraphs.
  </Card>

  <Card title="Work your pipeline" icon="list-check">
    Review today's activity, find calls with a given disposition, create and complete follow-up
    tasks, build a call list from call history.
  </Card>

  <Card title="Ask your CRM" icon="database">
    Look up a contact, account, or deal in HubSpot, Salesforce, Outreach, Salesloft, Apollo,
    Amplemarket, SmartLead, or Gong, and update records with your approval.
  </Card>

  <Card title="Build and enrich lists" icon="table">
    Source new accounts and people onto a table, load CRM records by stage or owner, check which
    rows already exist in your CRM, and enrich the rest.
  </Card>

  <Card title="Draft and send" icon="envelope">
    Write follow-up emails from a call, send on-brand HTML email, post to Slack, and book
    meetings through connected apps.
  </Card>

  <Card title="Brief you before a call" icon="user">
    Pull together the CRM record, call history, logged emails, open deals, and battle cards for a
    person or company into one briefing.
  </Card>
</CardGroup>

## How it works

A conversation with the companion runs as a loop: it reads your message, decides which tools it
needs, calls them, reads the results, and either calls more tools or writes its reply. A single
request can involve many tool calls. Several things shape that loop.

### It plans first

For anything that takes more than a couple of steps, the companion writes a short, visible plan
and ticks items off as it works. If a step reveals new work, it updates the plan rather than
silently drifting.

### It loads tools on demand

The companion has well over a hundred tools, so it keeps only a few in view and loads the rest
by name or category when a task needs them. You do not have to name a tool. Ask for the outcome
and it finds the capability.

### It dispatches specialists for connected platforms

Each connected platform has its own specialist. When you mention HubSpot, the companion hands
the lookup to the HubSpot specialist, which knows that platform's objects and query language and
returns a clean result. Specialists run in parallel when a question spans platforms, for example
checking the same person in HubSpot and Salesforce at once.

Specialists **read**. Writes come back to the companion, which performs them itself so every
change passes through approval.

### It uses external apps through connected accounts

Beyond the platforms with specialists, the companion can reach apps your team has connected for
it, such as Gmail, Google Calendar, Slack, Notion, Calendly, Cal, Pipedrive, and ActiveCampaign.
If an app is not connected, the companion tells you and gives you a link to connect it.

### Every write is approval-gated

Any tool that changes something outside Salesfinity's own scratch space, whether it is a CRM
update, an email send, a sequence enrollment, or a paid enrichment, pauses the conversation and
shows an **Approve / Decline** card with the exact input. Nothing runs until you approve. A
declined or ignored card resolves as declined after ten minutes, and the companion asks what you
would prefer instead of retrying.

Paid enrichment has one more rule: the companion never enriches phones or emails on its own
initiative. It only does so when you ask, and it states the row count before the card appears.

### It answers with visuals

The companion renders results as rich blocks: metric cards, charts, tables, single-record cards,
org charts, and clickable suggestions. Every call, list, or score it mentions links to the
matching page in Salesfinity.

## What makes it yours

<Card title="Tutorials: list building with the companion" icon="graduation-cap" href="/tutorials/overview">
  Eight step-by-step tutorials with prompts to paste: build accounts, use signals, score, check the
  CRM, re-engage closed-lost, track job changes, find contacts, and build look-alikes.
</Card>

<CardGroup cols={2}>
  <Card title="Skills" icon="wand-magic-sparkles" href="/ai-companion/skills">
    Saved workflows the companion follows when a request matches. Author them, generate them from
    a conversation, or import them.
  </Card>

  <Card title="Memory" icon="brain" href="/ai-companion/memory">
    Durable facts about you and your work that the companion carries across conversations.
  </Card>

  <Card title="Routines" icon="clock">
    Companion workflows that run on a schedule or when a call is logged, with their own approval
    policy and an inbox for results.
  </Card>

  <Card title="Scratchpad" icon="note-sticky">
    Per-conversation working files the companion uses for multi-step research, so long tasks do
    not lose intermediate results.
  </Card>
</CardGroup>

## Routines

A routine is a saved companion task with a trigger. It runs hourly, daily, weekly, monthly, on a
custom cron schedule in your timezone, or when a call is logged that matches a filter, and it can
also be run manually or test-run before you save it. Each routine has a write policy:
**read-only** strips every mutating tool before the run, **require approval** pauses the run and
sends each write to your approvals inbox, and **auto-approve** lets the run execute writes on its
own. Runs, their results, and any questions the routine needs answered land in the routine inbox.

## Companion and the REST API or MCP server

The companion is the assistant inside Salesfinity. If you want to bring Salesfinity data into a
different assistant, such as Claude, use the [MCP server](/mcp/overview). If you want to build
your own automation, use the [REST API](/api-reference/introduction). All three read the same
data.