> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/readme.md).

# Welcome to Spara

An introduction to Spara

Spara gives every buyer a fast answer, a live look at the product, and a rep who already knows what they care about. It does this with two kinds of AI:

* **Agents** talk to your buyers and customers. An admin builds them once for the whole company on Spara's no-code platform. Five channels, built and run the same way: [Chat](/build/channels/chat.md), [Email](/build/channels/email.md), [Phone](/build/channels/phone.md), [SMS](/build/channels/sms.md) and [Product Demo](/build/channels/product-demo.md). Every channel writes to one lead record, synced to [HubSpot](/integrations/crm-integrations/hubspot-crm.md), [Salesforce](/integrations/crm-integrations/salesforce.md) or [Marketo](/integrations/crm-integrations/marketo.md). Agents draw from your [Knowledge](/build/knowledge.md) and [Media](/build/channels/chat/media.md), qualify leads, book meetings through your [calendar tool](/integrations/calendar-integrations.md), and alert your team in [Slack](/integrations/communications-integrations/slack.md), [Microsoft Teams](/integrations/communications-integrations/microsoft-teams.md) or [Webex](/integrations/communications-integrations/webex.md).
* **Collaborators** work with your reps, and each rep sets up their own. **Scout** is the AI sales assistant for reps: it works in [Slack](https://docs.spara.com/scout/connections/slack) and by [SMS](https://docs.spara.com/scout/connections/text), watches accounts, inbox and CRM, and puts the next move, already drafted in the rep's voice, in the rep's own Gmail or Outlook. Nothing sends until the rep sends it. See [Connect your tools](https://docs.spara.com/scout/getting-started/connect-your-tools). **Samantha** is the AI Solutions Engineer for sales calls: she joins the rep's Zoom, Google Meet or Microsoft Teams meeting, hands the rep an answer card for every technical question, and answers out loud when called on. See [Meet Samantha](https://docs.spara.com/solutions-engineer).

<figure><img src="https://4072969777-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FreCGkFdsmuPJzGP9ZgGA%2Fuploads%2Fgit-blob-725e92989edc61f19ad0a9b6a59df55adeeeafd1%2FAgents%20vs%20Collaborators.svg?alt=media" alt="Agents talk to buyers and customers and are set up once by an admin. Collaborators, Scout and Samantha, work with one rep each and are set up by that rep."><figcaption><p>Agents are built once for the company; each rep sets up their own Collaborator.</p></figcaption></figure>

**Setting up agents for your company?** Start with [Building Your First Agent](/guides/get-started/building-an-agent.md).

**Are you a rep who wants help with your own book?** Start with [Meet Scout](https://docs.spara.com/scout).

**Want an AI Solutions Engineer on your sales calls?** Start with [Meet Samantha](https://docs.spara.com/solutions-engineer).

## How they work together

1. **Agents create and qualify pipeline.** They answer the buyer's questions, show the product and book the meeting before a rep joins.
2. **Scout works the rep's book.** What your website agents learn reaches the rep through Scout: what a buyer asked about, and whether they finished a demo without booking. Scout uses those signals to tell the rep who needs attention and why, and briefs the rep each morning.
3. **Samantha joins the call.** Once the meeting is booked, she sits in as her own participant, hands the rep an answer for each technical question as it comes up, speaks when called on, and shows the product on her screenshare. See [What the meeting sees](https://docs.spara.com/solutions-engineer/in-the-meeting/what-the-meeting-sees).
4. **Agents stay with the customer after the sale.** The same agents can onboard new customers and answer their questions. See [Product Demo Use Cases](/guides/best-practices/product-demo-use-cases.md).

<figure><img src="https://4072969777-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FreCGkFdsmuPJzGP9ZgGA%2Fuploads%2Fgit-blob-5bb11c690da88f5ab701cfe6f630aaa9b60a9604%2FHow%20Agents%20and%20Collaborators%20Work%20Together.svg?alt=media" alt="Inbound signals from your agents feed Scout. Scout drafts the next move, the rep sends the outbound, and that outbound brings buyers back, creating more inbound signals."><figcaption><p>What your agents learn from buyers feeds Scout. Scout makes the rep's outbound better, and better outbound drives more inbound.</p></figcaption></figure>

Scout also works on its own from the rep's inbox, CRM and other tools, so you can start with it before you run any agents. See the [Scout FAQ](https://docs.spara.com/scout/trust/faq).

## What you can do with agents

* **Qualify and book inbound.** Put Spara on your site with [Spara Navigator](/build/channels/chat/spara-navigator.md), after or instead of the web form. It answers questions, asks your qualification questions, and books the call with your [calendar tool](/integrations/calendar-integrations.md).
* **Answer your phone line.** A [Phone](/build/channels/phone.md) agent picks up incoming calls, qualifies the caller and routes them.
* **Follow up with leads who didn't book.** A [workflow](/build/workflows.md) sends an email, call or text when a lead leaves a chat or a form without booking, and an agent handles the reply.
* **Run AI demos for any audience.** One [Product Demo](/build/channels/product-demo.md), pointed at a different audience by changing its [AI Instructions](/build/channels/configuring/ai-instructions.md). For prospects, open it from a website button, a chat suggestion, an email link, or a private page for a deal in progress. For new customers, embed it in your product or portal. For partners, give them their own version. See [Product Demo Use Cases](/guides/best-practices/product-demo-use-cases.md).

## Where to go

**Agents.** Set up and run what your buyers talk to. The sections follow the menu in the app.

* Build: [Agents](/build/agents.md), [Channels](/build/channels.md), [Workflows](/build/workflows.md), [Knowledge](/build/knowledge.md), [Data Model](/build/data-model.md) and [Testing](/build/testing.md)
* Pipeline: [Leads](/pipeline/leads.md), [Accounts](/pipeline/accounts.md), [Owners](/pipeline/owners.md) and [Analytics](/pipeline/analytics.md). Identify anonymous visitors with [deanonymization](/pipeline/leads/deanonymization.md).
* Platform: [Ask Spara](/platform/ask-spara.md), [Todos](/platform/todos.md) and [Settings](/platform/settings.md)
* Integrations: [Calendar Integrations](/integrations/calendar-integrations.md), [Communications Integrations](/integrations/communications-integrations.md), [CRM Integrations](/integrations/crm-integrations.md), [Document Sync Integrations](/integrations/document-sync-integrations.md), [Google Analytics 4 (GA4) Integration](/integrations/google-analytics-4-ga4-integration.md) and [Signals Integrations](/integrations/signals.md). Map CRM fields into the [Data Model](/build/data-model.md) to decide who enters a workflow and what gets written back.
* Guides: [Get started](/guides/get-started.md) and [Best practices](/guides/best-practices.md)

**Collaborators.** Help for each rep.

* [Scout](https://docs.spara.com/scout): sign up, connect your tools, and see how drafts and approval work
* [Solutions Engineer](https://docs.spara.com/solutions-engineer): set up Samantha, send her to a meeting, and see what the meeting sees

**Developers.** Install Spara and connect it to your systems.

* [Developer: Spara API](https://docs.spara.com/developers/spara-api/web-api), [Developer: Webhooks](https://docs.spara.com/developers/spara-api/webhooks) and the [installation guides](https://docs.spara.com/developers/installation/installing-spara-navigator)

Security details are in [Developer: Security & Compliance](https://docs.spara.com/developers/installation/security-and-compliance) and the [Trust Center](https://trust.spara.com).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spara.com/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.