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

# Your First Hour with Truedy

> Follow this guided path to go from zero to a live outbound campaign

# Your First Hour with Truedy

This is a **guided mini-course** with two paths (each designed to get you to a working demo in about an hour):

* Path 1: launch a small outbound batch campaign
* Path 2: build a support line with real-time webhook updates

Each step links to a deeper guide if you want more detail.

## 1. Understand the architecture (5–10 minutes)

Read:

* [How Truedy Works](/guides/how-truedy-works)
* [Agents & Calls Overview](/guides/agents-calls-overview)

Goal: know what **agents, calls, contacts, campaigns, and numbers** are and how they fit together.

## 2. Design your first agent (10–15 minutes)

1. Open the Truedy dashboard and create a new agent.
2. Choose a voice and paste a **simple but clear** system prompt.
3. Optionally attach a small knowledge base (e.g. an FAQ PDF).

Guides:

* [Prompting & Agent Design Basics](/guides/prompting-and-agent-design-basics)
* [Creating an Agent](/guides/creating-an-agent)

Outcome: one agent ready to handle outbound calls.

## 3. Configure telephony (10 minutes)

1. Decide whether you will:
   * Purchase a Truedy-managed number, or
   * Bring your own provider (SIP / BYOC).
2. Acquire at least **one outbound number**.
3. Assign that number to your agent for outbound calls.

Guides:

* [Telephony](/api-reference/telephony)
* [Import Number (SIP / BYOC)](/api-reference/telephony#import-number)

Outcome: one outbound-capable number assigned to your agent.

## 4. Prepare a small contact list (10 minutes)

1. Create a **contact folder** for this test campaign.
2. Add a few test contacts:
   * Either manually, or
   * By importing a clean CSV (E.164 phone numbers only).

Guide:

* [Contacts & Folders](/api-reference/contacts)

Outcome: a folder with a small, known-good set of contacts.

## 5. Create and schedule your first campaign (10–15 minutes)

1. In the batch calling / campaigns section, create a new campaign:
   * Select your agent.
   * Select your contact folder.
   * Choose a descriptive name (e.g. “Demo – Q1 Trial Outreach”).
2. Set scheduling rules:
   * Timezone.
   * Working days (e.g. Mon–Fri).
   * Daily call window (e.g. 10:00–17:00).
   * Max calls per day (for this small test, keep it low).
3. Schedule the campaign.

Guides:

* [Batch Calls & Campaigns Overview](/guides/batch-calls-and-campaigns-overview)
* [Batch Calls API](/api-reference/batch-calls)

Outcome: a scheduled campaign that will automatically place calls.

## 6. Monitor, pause, resume (10 minutes)

As calls start:

1. Open the campaign details page and watch contacts move through statuses.
2. Drill into a few call records to see transcripts and recordings.
3. Try pausing and resuming the campaign to see how the scheduler behaves.

Guides:

* [Pause/Resume endpoints](/api-reference/batch-calls#pause-batch-call)
* [Analytics](/api-reference/batch-calls#get-batch-call-analytics)

Outcome: confidence that you can **control** and **inspect** campaigns safely.

## 7. Wire in your own systems (optional, 15–30 minutes)

Once you’re comfortable with the basics:

1. Set up a webhook endpoint in your app.
2. Subscribe to `call.ended` and `batch.completed`.
3. Store events in your database and build basic dashboards.

Guides:

* [Webhooks Overview](/guides/webhooks-overview)
* [Webhooks](/guides/webhooks)

## Path 2: Support line with analytics (about an hour)

This path focuses on inbound support-style calls plus a reliable webhook receiver that powers your CRM/ops workflows.

### 1. Understand the architecture (5–10 minutes)

Read:

* [How Truedy Works](/guides/how-truedy-works)
* [Agents & Calls Overview](/guides/agents-calls-overview)

### 2. Design a support agent (10–15 minutes)

Guides:

* [Prompting & Agent Design Basics](/guides/prompting-and-agent-design-basics)
* [Creating an Agent](/guides/creating-an-agent)

Outcome: an agent that can collect intent, answer (using knowledge if needed), and route/confirm next steps.

### 3. Configure inbound telephony (10 minutes)

Guides:

* [Telephony](/api-reference/telephony)
* [Assign Number (to enable inbound/outbound)](/api-reference/telephony#assign-number)

Outcome: your agent can receive inbound support calls.

### 4. Start receiving calls (10 minutes)

Try:

* Dashboard: use [Making Your First Call](/guides/making-your-first-call) as a sanity check.
* Then validate your inbound flow with your provider configuration.

Outcome: you can hear the agent respond and generate call records.

### 5. Wire webhooks for real-time updates (10–15 minutes)

Guides:

* [Available Webhooks](/guides/available-webhooks)
* [Webhooks](/guides/webhooks)
* [Webhooks Overview](/guides/webhooks-overview)

Subscribe to `call.ended` (and any relevant batch/voice events you need).

Outcome: your system receives events and can update internal state immediately.

### 6. Make webhook processing safe (idempotency + errors) (5–10 minutes)

Guides:

* [Securing Webhooks](/guides/securing-webhooks)
* [Idempotency](/guides/idempotency)
* [Webhook Error Handling & Retries](/guides/webhook-error-handling-and-retries)
* [Rate Limits](/guides/rate-limits)

Outcome: re-sent events won’t create duplicate CRM updates.

## Where to go next

* Deepen prompting and agent design: [Prompting & Agent Design Basics](/guides/prompting-and-agent-design-basics)
* Optimize performance and reliability:
  * [Rate Limits & Throttling](/guides/rate-limits)
  * [Error Handling](/guides/error-handling)