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

# Quickstart

> A simple path from workspace setup to your first live calls.

This guide gives you the fastest sensible path to getting value from Ramba Voice.

## Before you begin

You should have:

* a clear use case for your first agent
* one small group of teammates who will test it
* the business rules the agent must follow
* access to the systems the agent may need to reference or update

## Recommended rollout path

<Steps>
  <Step title="Create your workspace">
    Set up a workspace for the team that owns the calls. Keep the pilot small at first so feedback stays fast and clear.
  </Step>

  <Step title="Define one job for your first agent">
    Pick a narrow use case such as front-desk coverage, booking requests, or lead qualification. Avoid trying to solve every call type with the first version.
  </Step>

  <Step title="Write the agent's role in plain language">
    Describe what the agent should help callers accomplish, what information it must collect, and when it should hand off to a human.
  </Step>

  <Step title="Connect the actions the agent needs">
    Give the agent access only to the actions required for the job. Start small. You can add more capabilities once the core flow works reliably.
  </Step>

  <Step title="Set up phone coverage">
    Connect or assign the phone numbers the agent should answer from or call from. Confirm whether you want inbound, outbound, or both.
  </Step>

  <Step title="Test with real call scenarios">
    Run through the most common customer conversations, including edge cases such as missing information, unclear requests, and handoff situations.
  </Step>

  <Step title="Go live with a narrow slice">
    Start with one team, one call type, or one number. Review the early calls closely before expanding coverage.
  </Step>
</Steps>

## Good first goals

Your first rollout is usually successful when:

* callers can reach the agent on the right number
* the agent handles the main call path clearly
* the agent captures the information your team actually needs
* the connected actions work consistently
* your team can review call outcomes and improve from them

## Avoid this in the first version

* too many use cases in one agent
* broad action access without clear guardrails
* trying to automate rare edge cases before common calls work well
* rolling out to every team or number at once

## Next steps

* Read [Key concepts](/product/key-concepts)
* Read [Conversation styles](/agents/conversation-styles)
* Read [Phone numbers and routing](/calling/phone-numbers)