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

# Assistants

> Understand Ringg AI assistants and how teams use them.

An **Assistant** is the Ringg AI voice agent that talks to customers. It follows your script, uses the voice you choose, and works toward the goal you define.

***

## What an Assistant Does

An assistant can:

* Call contacts from a campaign.
* Answer calls made to your number.
* Speak with website visitors through a webcall widget.
* Use uploaded documents to answer questions.
* Save call results for review in History and Analytics.

***

## Call Direction

| Direction    | What It Means                            | Common Use                                    |
| ------------ | ---------------------------------------- | --------------------------------------------- |
| **Outbound** | Ringg AI calls the contact               | Campaigns, reminders, follow-ups, collections |
| **Inbound**  | The customer calls your number           | Support, intake, routing, callbacks           |
| **Webcall**  | A website visitor starts the call online | Product pages, landing pages, onboarding      |

***

## Conversation Style

| Style             | What It Means                               | Best For                           |
| ----------------- | ------------------------------------------- | ---------------------------------- |
| **Single Prompt** | One script controls the whole call          | Simple flows with one goal         |
| **Multi Prompt**  | Multiple prompt nodes guide different paths | Complex flows with branching logic |

Start with **Single Prompt** unless the conversation clearly needs branches.

***

## Templates

Ringg AI includes industry templates for common use cases.

<CardGroup cols={3}>
  <Card title="Logistics" icon="truck" />

  <Card title="Healthcare" icon="hospital" />

  <Card title="Financial" icon="landmark" />

  <Card title="Education" icon="graduation-cap" />

  <Card title="HR & Recruitment" icon="users" />

  <Card title="eCommerce" icon="shopping-cart" />
</CardGroup>

<Tip>
  Templates are starting points. Review the prompt and edit it for your company, audience, and compliance needs.
</Tip>

***

## Main Settings

| Setting              | What You Control                                                    |
| -------------------- | ------------------------------------------------------------------- |
| **Prompt**           | Opening line, goal, tone, and rules                                 |
| **Voice**            | Language and voice character                                        |
| **Custom Variables** | Contact-specific values such as `callee_name` or `loan_amount`      |
| **Knowledge Base**   | Documents the assistant can use during calls                        |
| **Call Settings**    | Duration, timezone, voicemail behavior, retries, and audio settings |
| **Embed**            | Website widget setup for webcall assistants                         |
| **Custom Analysis**  | Post-call fields to extract from transcripts                        |

***

## Prompt Basics

A good prompt has three parts:

<Steps>
  <Step title="First message">
    The exact line the assistant says when the call connects.
  </Step>

  <Step title="Objective">
    The assistant's role, business context, and goal.
  </Step>

  <Step title="Response guidelines">
    Rules for tone, language, objections, handoff, and answer length.
  </Step>
</Steps>

Variables such as `@{{callee_name}}` let the assistant personalize each call.

***

## Agent ID

Every assistant has an `agent_id`. Developers use it for API calls, campaigns, webhooks, and webcall embeds.

<Note>
  When a business user creates or approves an assistant, include the assistant name and `agent_id` in the developer handoff.
</Note>

***

## Test Calls

Use **Test call** before launch. Test the first message, voice, language switching, knowledge base answers, custom analysis, and end-of-call behavior.