{icon}
}
+ {title}
+{description}
+ +
+ {children}
+
+
+ );
+};
+
+export default CapabilityCard;
diff --git a/fern/products/atoms/pages/components/FeatureHighlight.jsx b/fern/products/atoms/pages/components/FeatureHighlight.jsx
new file mode 100644
index 0000000..87d1e35
--- /dev/null
+++ b/fern/products/atoms/pages/components/FeatureHighlight.jsx
@@ -0,0 +1,79 @@
+import React from 'react';
+
+export const FeatureHighlight = ({
+ title,
+ features = [],
+ badge = null,
+ gradient = "from-teal-600 to-cyan-600"
+}) => {
+ return (
+
+
+ );
+};
+
+export default FeatureHighlight;
diff --git a/fern/products/atoms/pages/components/Hero.jsx b/fern/products/atoms/pages/components/Hero.jsx
new file mode 100644
index 0000000..6c227c4
--- /dev/null
+++ b/fern/products/atoms/pages/components/Hero.jsx
@@ -0,0 +1,94 @@
+import React from 'react';
+
+export const Hero = ({
+ title = "Atoms Documentation",
+ subtitle = "Build enterprise-grade voice AI agents in minutes",
+ badge = null
+}) => {
+ return (
+
+ {badge && {badge}}
+
+
+ {title}
+-
+ {features.map((feature, index) => (
+
- + ✓ + {feature} + + ))} +
+
+
+ );
+};
+
+export default Hero;
diff --git a/fern/products/atoms/pages/components/PathSelector.jsx b/fern/products/atoms/pages/components/PathSelector.jsx
new file mode 100644
index 0000000..ba1ef01
--- /dev/null
+++ b/fern/products/atoms/pages/components/PathSelector.jsx
@@ -0,0 +1,98 @@
+import React from 'react';
+
+export const PathSelector = ({ paths }) => {
+ return (
+
+ {badge && {badge}}
+
+
+ {title}
+{subtitle}
+
+ {paths.map((path, index) => (
+
+
+ );
+};
+
+export default PathSelector;
diff --git a/fern/products/atoms/pages/components/ProductCard.jsx b/fern/products/atoms/pages/components/ProductCard.jsx
new file mode 100644
index 0000000..73e8d35
--- /dev/null
+++ b/fern/products/atoms/pages/components/ProductCard.jsx
@@ -0,0 +1,140 @@
+import React from 'react';
+
+export const ProductCard = ({
+ title,
+ description,
+ href,
+ image = null,
+ gradient = "from-teal-500 to-cyan-500",
+ badge = null
+}) => {
+ const CardWrapper = href ? 'a' : 'div';
+
+ return (
+ {path.icon}
+
+
+ {path.title}
+{path.description}
+→
+
+ ))}
+
+
+ {image && 
}
+ {!image && (
+
+
+
+
+ )}
+ {badge && {badge}}
+
+
+
+ {title}
+{description}
+
+ {children}
+
+
+ );
+};
+
+export default ProductCard;
diff --git a/fern/products/atoms/pages/components/index.js b/fern/products/atoms/pages/components/index.js
new file mode 100644
index 0000000..6f51635
--- /dev/null
+++ b/fern/products/atoms/pages/components/index.js
@@ -0,0 +1,5 @@
+export { Hero } from './Hero';
+export { ProductCard, ProductCardGrid } from './ProductCard';
+export { CapabilityCard, CapabilityGrid } from './CapabilityCard';
+export { PathSelector } from './PathSelector';
+export { FeatureHighlight } from './FeatureHighlight';
diff --git a/fern/products/atoms/pages/custom.css b/fern/products/atoms/pages/custom.css
new file mode 100644
index 0000000..afd8040
--- /dev/null
+++ b/fern/products/atoms/pages/custom.css
@@ -0,0 +1,46 @@
+/* Custom Atoms Documentation Styles - ElevenLabs Inspired */
+
+/* Gradient utilities for product cards */
+.from-teal-500 {
+ --tw-gradient-from: #14b8a6;
+}
+
+.to-cyan-500 {
+ --tw-gradient-to: #06b6d4;
+}
+
+.to-cyan-600 {
+ --tw-gradient-to: #0891b2;
+}
+
+.from-blue-500 {
+ --tw-gradient-from: #3b82f6;
+}
+
+.to-indigo-600 {
+ --tw-gradient-to: #4f46e5;
+}
+
+.from-purple-500 {
+ --tw-gradient-from: #a855f7;
+}
+
+.to-pink-600 {
+ --tw-gradient-to: #db2777;
+}
+
+.from-teal-600 {
+ --tw-gradient-from: #0d9488;
+}
+
+.bg-gradient-to-br {
+ background: linear-gradient(to bottom right, var(--tw-gradient-from), var(--tw-gradient-to));
+}
+
+/* Typography improvements */
+h1,
+h2,
+h3,
+h4 {
+ letter-spacing: -0.025em;
+}
\ No newline at end of file
diff --git a/fern/products/atoms/pages/deep-dive/campaign/campaign.mdx b/fern/products/atoms/pages/deep-dive/campaign/campaign.mdx
index ebf0721..f443f58 100644
--- a/fern/products/atoms/pages/deep-dive/campaign/campaign.mdx
+++ b/fern/products/atoms/pages/deep-dive/campaign/campaign.mdx
@@ -40,7 +40,7 @@ After creating your campaign, you'll see it listed in the Campaigns dashboard. C
To begin making calls, click the "Start Campaign" button on the right side of the campaign details page. Your campaign will immediately begin dialing numbers from your audience list.
-The system makes multiple concurrent calls based on your subscription's rate limits. More information about limits can be found [here](https://console.smallest.ai/subscription).
+The system makes multiple concurrent calls based on your subscription's rate limits. More information about limits can be found [here](https://console.smallest.ai/subscription?utm_source=documentation&utm_medium=docs).
### Pausing and Resuming
diff --git a/fern/products/atoms/pages/deep-dive/phone-number/phone-number.mdx b/fern/products/atoms/pages/deep-dive/phone-number/phone-number.mdx
index f8b482b..a1077b7 100644
--- a/fern/products/atoms/pages/deep-dive/phone-number/phone-number.mdx
+++ b/fern/products/atoms/pages/deep-dive/phone-number/phone-number.mdx
@@ -19,7 +19,7 @@ The purchased number will appear in the [Your Numbers](https://atoms.smallest.ai
+
+ 
+
+ 
+
+
+
+
+ Click **API Keys** in the sidebar, then **Create API Key**.
+
+
+
+
+
+ Name your key and click **Create API Key**. Copy it — it starts with `sk_`.
+
+
+
+
+
+
+
+ {/* Card wrapper */}
+
+
+Atoms is a voice AI platform that turns phone calls into outcomes. Customers get instant help. Leads get qualified. Appointments get booked — all in real-time, at any scale, around the clock.
+
+We built the entire stack from scratch. Pulse transcribes speech with 64ms time-to-first-transcript. Electron processes intent and generates responses in under 500ms. Lightning synthesizes studio-quality voice at 175ms latency. End-to-end, sub-800ms turn times — indistinguishable from human conversation.
+
+### Our Models
+
+| Model | What It Does | Performance |
+|-------|--------------|-------------|
+| **[Pulse](/atoms/product-overview/capabilities/voice-and-speech)** | Speech-to-Text | 32 languages, 64ms latency, 4.5% English WER |
+| **[Electron](/atoms/product-overview/capabilities/voice-and-speech)** | Language Model | Voice-optimized SLM, sub-500ms reasoning |
+| **[Lightning v3.1](/atoms/product-overview/capabilities/voice-and-speech)** | Text-to-Speech | 44kHz studio-grade, 175ms latency, voice cloning |
+
+---
+
+## Choose Your Path
+
+
+ {/* Blur glow layer */}
+
+
+ {/* Animated gradient border layer */}
+
+
+ {/* The actual card */}
+
+
+ {/* Background gradient blob - like smallest logo */}
+
+
+
+ {/* Main title */}
+ Welcome to Atoms
+
+ {/* Description */}
+
+ Voice AI agents that sound human. Build, deploy, and scale intelligent conversations in minutes.
+
+
+
+---
+
+## Filters
+
+Narrow down your data with the filters at the top:
+
+| Filter | Options |
+|--------|---------|
+| **Date Range** | Select start and end dates |
+| **Filter by Agent** | View specific agent's calls |
+| **Filter by Campaign** | View specific campaign's calls |
+| **Filter by Call** | Filter by call type or status |
+
+Click **Refresh** to update the dashboard with your selections.
+
+---
+
+## Summary Cards
+
+Quick metrics at the top of the dashboard:
+
+| Metric | Description |
+|--------|-------------|
+| **Call Counts** | Total number of calls |
+| **Avg. Call Duration** | Average length of calls |
+| **Avg. Call Latency** | Average response time |
+| **Total Cost** | Credits spent on calls |
+
+---
+
+## Charts
+
+### Call Connected Percentage
+
+Pie chart showing the connection rate by agent—how many calls connected vs. didn't connect.
+
+### Disconnection Reason
+
+Breakdown of why calls ended:
+- **Dial No Answer** — Contact didn't pick up
+- **User Hangup** — Contact ended the call
+- **Agent Hangup** — Agent ended the call
+
+---
+
+## Most Called Agents
+
+Table showing which agents handled the most calls:
+
+| Column | Description |
+|--------|-------------|
+| Agent Name | The agent |
+| Number of calls | Total calls handled |
+| Call Minutes | Total talk time |
+| Credits Spent | Cost for this agent |
+
+---
+
+## Related
+
+
+
+
+| Node | Purpose | When to Use |
+|------|---------|-------------|
+| **Default** | Speak and listen | Greetings, questions, information delivery |
+| **API Call** | Connect to external services | Fetch data, book appointments, update CRMs |
+| **Transfer Call** | Hand off to a human | Escalations, complex issues, sales closes |
+| **End Call** | Conclude the conversation | Successful completion, dead ends |
+| **Pre-Call API** | Actions before the call | Load customer data, set variables |
+| **Post-Call API** | Actions after the call | Log outcomes, trigger follow-ups |
+
+---
+
+## Default Node
+
+The workhorse of Convo Flow. Use it for any conversational turn where your agent speaks and expects a response.
+
+
+ 
+
+
+### How to Use
+
+1. Drag **Default Node** from the left panel onto your canvas
+2. Click the node to select it
+3. In the right panel, write your prompt:
+
+```
+Hi {{customer_name}}! Thanks for calling Acme Support.
+How can I help you today?
+```
+
+The prompt is what your agent says. Variables like `{{customer_name}}` get replaced with actual data.
+
+### Setting Up Branches
+
+Branches determine what happens next based on the caller's response. Click **+ Add Branch** and configure:
+
+| Field | What It Does | Example |
+|-------|--------------|---------|
+| **Branch Name** | Internal label for the branch | "Billing Question" |
+| **Condition** | When to take this path | "User asks about billing" |
+| **Next Node** | Where to go next | → Billing Help node |
+
+Write conditions in natural language. The AI interprets them:
+- "User confirms"
+- "User says no or declines"
+- "User asks about pricing"
+- "User wants to speak to a person"
+- "Anything else" (fallback)
+
+
+
+
+### How to Use
+
+1. Drag **End Call** node to mark conversation endpoints
+2. Write a closing message:
+
+```
+Great, you're all set! Your appointment is confirmed for
+{{appointment_date}} at {{appointment_time}}.
+Have a wonderful day!
+```
+
+### Dispositions
+
+Tag the outcome for analytics:
+
+| Disposition | When to Use |
+|-------------|-------------|
+| **Successful** | Goal achieved (booking made, issue resolved) |
+| **Unsuccessful** | Goal not achieved (not interested, wrong number) |
+| **Transferred** | Handed to human |
+| **Callback Requested** | Customer asked for follow-up |
+
+Dispositions help you track how conversations end and measure agent performance.
+
+---
+
+## Pre-Call API Node
+
+Execute actions *before* your agent says hello. Perfect for loading personalized data.
+
+
+ 
+
+
+### How to Use
+
+This special node runs immediately when the call connects, before any conversation happens.
+
+### Common Use Cases
+
+| Use Case | What to Fetch |
+|----------|---------------|
+| **Personalization** | Customer name, account status, preferences |
+| **Context loading** | Open tickets, recent orders, appointment history |
+| **Routing logic** | VIP status, language preference, time zone |
+
+### Example
+
+```
+GET https://api.example.com/customers/{{caller_phone}}
+
+Response → Variables:
+{{customer_name}}
+{{account_type}}
+{{last_order_date}}
+```
+
+Now your greeting can be: *"Hi {{customer_name}}! I see you placed an order on {{last_order_date}}. How can I help?"*
+
+---
+
+## Post-Call API Node
+
+Trigger actions *after* the call ends. Great for logging and follow-ups.
+
+
+ 
+
+
+### How to Use
+
+This node runs automatically after every call, regardless of how it ended.
+
+### Common Use Cases
+
+| Use Case | What to Send |
+|----------|--------------|
+| **CRM logging** | Call summary, outcome, duration |
+| **Ticket creation** | Create tickets for unresolved issues |
+| **Follow-up triggers** | Send email confirmations, SMS receipts |
+| **Analytics** | Custom metrics, conversion tracking |
+
+### Example
+
+```
+POST https://crm.example.com/activities
+
+Body:
+{
+ "contact_phone": "{{caller_phone}}",
+ "call_duration": "{{call_duration}}",
+ "outcome": "{{disposition}}",
+ "summary": "{{call_summary}}",
+ "agent_id": "voice-bot-001"
+}
+```
+
+---
+
+## Connecting Nodes
+
+Branches are the arrows between nodes — they define your conversation's flow.
+
+### Creating Connections
+
+1. Click on a node to select it
+2. Scroll to **Branches** in the right panel
+3. Click **+ Add Branch**
+4. Set the condition and target node
+5. Drag from the branch's output handle to the target node
+
+### Branch Types
+
+| Type | How It Works |
+|------|--------------|
+| **Intent-based** | AI interprets caller's meaning — "User wants to reschedule" |
+| **Keyword-based** | Matches specific words — "User says 'yes'" |
+| **Variable-based** | Checks variable values — `{{account_type}} == 'premium'` |
+| **Default** | Catch-all fallback — "Anything else" |
+
+
+
+
+---
+
+## Step 2: Fill In Basic Details
+
+A modal appears asking for basic information:
+
+
+ 
+
+
+| Field | What to Enter |
+|-------|---------------|
+| **Agent Name** | Something descriptive — "Appointment Reminder", "Lead Qualifier", etc. |
+| **Call Type** | **Outbound** (agent makes calls) or **Inbound** (customers call in) |
+| **Voice** | Click to preview voices, pick one that matches your brand |
+| **Language** | Primary language for the conversation |
+
+---
+
+## Step 3: Select Conversational Flow
+
+Choose **Conversational flow agent** — it's labeled "For stronger guardrails".
+
+
+ 
+
+
+This gives you access to the visual workflow builder.
+
+---
+
+## Step 4: Choose a Starting Point
+
+**Start from Scratch**
+Opens a blank canvas with just a Start node. Best when you have a specific flow in mind.
+
+**Use a Template**
+Pick a pre-built flow for your industry — Healthcare, E-commerce, Real Estate, Banking, Sales. Templates come with nodes and branches already configured that you can customize.
+
+
+
+
+Take a moment to orient yourself:
+
+**Left Panel** — Node palette. This is where you drag nodes from.
+
+**Center** — Your workflow canvas. You'll see a Start node (or a template flow if you picked one).
+
+**Right Panel** — Node configuration. Click any node to see its settings here.
+
+**Top Bar** — Test Agent button, Conversation Logs, Lock Agent toggle.
+
+---
+
+## Step 7: Add Your First Node
+
+Let's build a simple greeting:
+
+1. From the left panel, drag a **Default Node** onto the canvas
+2. Click the node to select it
+3. In the right panel, find the **Prompt** field
+4. Write your greeting:
+
+```
+Hi, this is an automated call from Dr. Smith's office.
+Am I speaking with {{customer_name}}?
+```
+
+The `{{customer_name}}` is a variable that gets replaced with actual data during the call.
+
+---
+
+## Step 8: Connect the Nodes
+
+Draw a line from your Start node to your greeting node:
+
+1. Hover over the Start node's output handle (small circle on the right)
+2. Click and drag to your greeting node's input handle (circle on the left)
+3. Release to create the connection
+
+Your flow now has a path: Start → Greeting.
+
+---
+
+## Step 9: Add Branches
+
+The caller will respond to your greeting. You need to handle different responses:
+
+1. With your greeting node selected, find **Branches** in the right panel
+2. Click **+ Add Branch**
+3. Configure the first branch:
+ - **Name:** "Confirmed"
+ - **Condition:** "User confirms their identity"
+ - **Next Node:** (we'll create this next)
+
+4. Add another branch:
+ - **Name:** "Wrong Person"
+ - **Condition:** "User says it's the wrong number"
+
+5. Add a fallback:
+ - **Name:** "Unclear"
+ - **Condition:** "Anything else"
+
+---
+
+## Step 10: Build Out the Flow
+
+Now add nodes for each branch:
+
+**For "Confirmed"** — Add a Default Node with the appointment details:
+```
+Great! I'm calling to remind you about your appointment on
+{{appointment_date}} at {{appointment_time}}.
+Would you like to confirm or reschedule?
+```
+
+**For "Wrong Person"** — Add an End Call Node with an apology:
+```
+I apologize for the confusion. I must have the wrong number.
+Have a great day!
+```
+
+**For "Unclear"** — Loop back to the greeting with a clarification:
+```
+I'm sorry, I didn't quite catch that.
+Am I speaking with {{customer_name}}?
+```
+
+Connect each branch to its corresponding node.
+
+---
+
+## Step 11: Add an End Point
+
+Every path needs to end somewhere. Drag an **End Call** node and connect it to successful conversation completions:
+
+```
+Perfect! Your appointment is confirmed for {{appointment_date}}
+at {{appointment_time}}. We'll see you then. Have a wonderful day!
+```
+
+Set the **Disposition** to "Successful" so you can track outcomes.
+
+---
+
+## Step 12: Test Your Flow
+
+Click **Test Agent** in the top bar.
+
+1. Choose your testing method (web call or phone)
+2. Walk through the conversation as a customer would
+3. Try different paths — confirm identity, say wrong number, give unclear responses
+
+After testing, check **Conversation Logs** to see exactly how the AI interpreted responses and which paths it took.
+
+---
+
+## You're Live!
+
+Your Convo Flow agent is ready. From here, you can:
+
+
+
+
+---
+
+## Step 2: Fill In Basic Details
+
+A modal appears asking for basic information:
+
+
+
+
+
+| Field | What to Enter |
+|-------|---------------|
+| **Agent Name** | Something descriptive — "Customer Support Bot", "Sales Assistant", etc. |
+| **Call Type** | **Inbound** if customers call in, **Outbound** if the agent makes calls |
+| **Voice** | Click to preview voices, pick one that matches your brand |
+| **Language** | Primary language for the conversation |
+
+---
+
+## Step 3: Select Agent Type
+
+Choose **Single prompt agent** — it's marked as Recommended.
+
+
+
+
+
+The other option, Conversational Flow, is for complex step-by-step workflows. Stick with Single Prompt for natural conversations.
+
+---
+
+## Step 4: Choose a Starting Point
+
+You can start from scratch or use a template:
+
+**Start from Scratch**
+Select "Start with custom prompt" to write everything yourself. Best when you have specific requirements.
+
+**Use a Template**
+Pick a pre-built template for your industry — Healthcare, E-commerce, Banking, Sales, Real Estate. Templates give you a solid foundation that you can customize.
+
+
+
+
+Fill in each section:
+
+**Role & Objective**
+Who your agent is and what it should accomplish.
+
+```
+You are Alex, a friendly customer support agent for TechStore.
+Your goal is to help customers with orders, returns, and product questions.
+```
+
+**Conversation Flow**
+How the agent should guide conversations.
+
+```
+1. Greet warmly and ask how you can help
+2. Listen and understand their need
+3. Provide helpful information or take action
+4. Confirm they're satisfied
+5. Ask if there's anything else
+```
+
+**Dos and Don'ts**
+Behavioral guardrails.
+
+```
+DO: Be patient, confirm before making changes, offer to transfer if stuck
+DON'T: Share other customers' info, make promises you can't keep
+```
+
+**End Call Conditions**
+When to conclude the call.
+
+```
+End when: Issue resolved, customer requests it, or transferred successfully
+```
+
+For detailed guidance on writing great prompts, see [Writing Prompts](/atoms/atoms-platform/single-prompt-agents/prompt-section/writing-prompts).
+
+---
+
+## Step 8: Test Your Agent
+
+Click **Test Agent** in the top bar. Make a test call and try different scenarios:
+
+- Ask a normal question
+- Ask something unexpected
+- Interrupt mid-response
+- Try to get it to break a rule
+
+Listen for how natural it sounds. Check that it follows your guidelines.
+
+---
+
+## You're Live!
+
+Your agent is now ready. From here, you can:
+
+
+
+
+Each entry shows a complete conversation with all the details you need to understand what happened.
+
+---
+
+## What's in a Log
+
+Each conversation log contains:
+
+### Call Metadata
+
+| Field | Description |
+|-------|-------------|
+| **Call ID** | Unique identifier for this conversation |
+| **Timestamp** | When the call happened |
+| **Duration** | How long it lasted |
+| **Direction** | Inbound or outbound |
+| **Phone Number** | Caller's number (if available) |
+| **Disposition** | How the call ended (successful, unsuccessful, transferred, etc.) |
+
+### Transcript
+
+A full text record of everything said — both by the caller and your agent. Each turn is timestamped.
+
+```
+[00:02] Agent: Hi, this is Jordan from TechStore. How can I help you today?
+[00:05] Caller: Yeah, I need to return something I bought last week.
+[00:08] Agent: I'd be happy to help with that. Could you tell me what item you'd like to return?
+[00:12] Caller: The wireless headphones, they don't fit right.
+...
+```
+
+### Audio Recording
+
+The actual audio of the call (if recording is enabled). Listen to hear tone, pacing, and things the transcript might miss.
+
+### Variables
+
+All variables used in the conversation — what values they had and when they changed.
+
+### API Activity
+
+For Convo Flow agents: which API calls were made, what data was sent/received, and whether they succeeded.
+
+### Branch Decisions
+
+For Convo Flow agents: which branches were taken and why. Understand the path the conversation followed.
+
+---
+
+## Using Logs for Debugging
+
+When something goes wrong, logs tell you exactly what happened:
+
+### Common Issues to Look For
+
+**Speech Recognition Errors**
+The transcript shows what the system *thought* it heard. If it's wrong, that explains downstream problems.
+
+```
+Caller actually said: "I want to cancel my order"
+System heard: "I want to cancel my daughter"
+```
+
+**Intent Misunderstanding**
+The caller's words were transcribed correctly, but the agent misinterpreted the intent.
+
+**Wrong Branch Taken**
+In Convo Flow, check which branches fired. The AI's interpretation might differ from your expectation.
+
+**API Failures**
+Check the API activity section. Failed calls explain why data wasn't available or actions weren't taken.
+
+---
+
+## Filtering and Searching
+
+With many calls, you need to find specific conversations:
+
+### Filter Options
+
+| Filter | What It Finds |
+|--------|---------------|
+| **Date Range** | Calls within a specific period |
+| **Disposition** | Only successful, unsuccessful, or transferred calls |
+| **Duration** | Calls shorter or longer than a threshold |
+| **Phone Number** | Calls from/to a specific number |
+| **Contains Text** | Calls where specific words appear in transcript |
+
+### Useful Searches
+
+- **Short calls** — Often indicate quick hang-ups or problems
+- **Long calls** — May reveal conversations that got stuck
+- **Unsuccessful dispositions** — Learn why calls fail
+- **Calls with transfers** — Understand what AI couldn't handle
+
+---
+
+## Analyzing Patterns
+
+Look beyond individual calls to spot trends:
+
+**Frequent Fallbacks**
+If many calls trigger fallback branches, your prompts may need more specific handling.
+
+**Common Questions**
+What do callers ask most? Make sure these are handled excellently.
+
+**Transfer Reasons**
+Why are calls being transferred? Can AI handle more of these?
+
+**Drop-off Points**
+Where do unsuccessful calls fail? Early hang-ups vs. mid-conversation issues tell different stories.
+
+---
+
+## Using Logs for Improvement
+
+Turn log insights into agent improvements:
+
+1. **Review regularly** — Set aside time weekly to review a sample of calls
+2. **Categorize issues** — Group problems by type (prompt, understanding, integration)
+3. **Prioritize by impact** — Fix issues that affect the most callers first
+4. **Make targeted changes** — Adjust prompts, add branches, fix integrations
+5. **Track results** — See if the same issues recur after your changes
+
+---
+
+## Privacy and Compliance
+
+
+
+
+**Unlocked (default):** Full editing enabled. You can change anything.
+
+**Locked:** Editing disabled. Configuration is frozen.
+
+Click the toggle to switch states. Locking requires confirmation.
+
+---
+
+## What Gets Locked
+
+When you lock an agent, the following are frozen:
+
+### For All Agents
+
+| Component | Locked? |
+|-----------|---------|
+| Agent name | ✓ |
+| Voice selection | ✓ |
+| LLM model | ✓ |
+| LLM parameters (temperature, etc.) | ✓ |
+| Language settings | ✓ |
+
+### For Single Prompt Agents
+
+| Component | Locked? |
+|-----------|---------|
+| Role & Objective prompt | ✓ |
+| Conversation Flow prompt | ✓ |
+| Dos and Don'ts prompt | ✓ |
+| End Call Conditions prompt | ✓ |
+
+### For Convo Flow Agents
+
+| Component | Locked? |
+|-----------|---------|
+| All nodes and their prompts | ✓ |
+| All branch conditions | ✓ |
+| Branch connections | ✓ |
+| API configurations | ✓ |
+| Variable definitions | ✓ |
+
+### Not Locked
+
+| Component | Why Not Locked? |
+|-----------|-----------------|
+| Phone number assignment | You need to connect/disconnect numbers |
+| Conversation logs | These accumulate regardless |
+| Knowledge Base content | Content can be updated independently |
+| External API endpoints | These are managed externally |
+
+---
+
+## Attempting to Edit While Locked
+
+If you try to edit a locked agent:
+
+1. The edit UI is disabled (fields are read-only)
+2. If you somehow trigger an edit API, it returns an error
+3. A message indicates the agent is locked
+
+To make changes, you must either:
+- Unlock the agent (if you have permission)
+- Create a new version based on this one
+
+---
+
+## Locking and Phone Numbers
+
+Locked agents can be connected to live phone numbers. In fact, this is the recommended workflow:
+
+```
+Lock agent → Connect to phone number → Go live
+```
+
+The lock protects the configuration while it's handling real calls.
+
+You can disconnect a phone number from a locked agent without unlocking it.
+
+---
+
+## Unlocking
+
+To unlock an agent:
+
+1. Click the lock toggle
+2. Confirm you want to unlock
+3. Editing is now enabled
+
+
+
+
+**How it works:**
+1. Click **Test Agent**
+2. Allow microphone access when prompted
+3. Talk to your agent like a real caller would
+4. The call appears in Conversation Logs when done
+
+**Best for:** Quick iterations, checking prompt changes, initial validation.
+
+### Phone Call Testing
+
+Test with actual phone audio — more realistic than browser testing.
+
+**How it works:**
+1. Go to **Settings** → **Test Phone Number**
+2. Call the provided number from your phone
+3. Have a real conversation with your agent
+4. Review the call in Conversation Logs
+
+**Best for:** Final validation, voice quality checks, realistic testing before launch.
+
+---
+
+## What to Test
+
+Don't just test the happy path. Systematically validate every aspect of your agent:
+
+### Conversation Flow
+
+| Test | What You're Checking |
+|------|---------------------|
+| **Happy path** | Does the ideal conversation work perfectly? |
+| **Edge cases** | What happens when callers say unexpected things? |
+| **Fallbacks** | Does the agent handle confusion gracefully? |
+| **Interruptions** | What happens if you interrupt mid-sentence? |
+| **Silence** | What does the agent do when you don't respond? |
+
+### Response Quality
+
+| Test | What You're Checking |
+|------|---------------------|
+| **Accuracy** | Are answers factually correct? |
+| **Relevance** | Does the agent actually answer the question asked? |
+| **Tone** | Does it sound like your brand? |
+| **Length** | Are responses appropriately concise for voice? |
+
+### Guardrails
+
+| Test | What You're Checking |
+|------|---------------------|
+| **Off-topic requests** | Does the agent stay on task? |
+| **Manipulation attempts** | Can you trick it into breaking rules? |
+| **Sensitive topics** | Does it handle them appropriately? |
+| **Competitor mentions** | Does it follow your guidelines? |
+
+---
+
+## Testing Checklist
+
+Before going live, verify each of these:
+
+**Basic Functionality**
+- [ ] Agent greets correctly
+- [ ] Agent understands common requests
+- [ ] Agent provides accurate information
+- [ ] Agent ends calls gracefully
+
+**Edge Cases**
+- [ ] Agent handles unclear speech
+- [ ] Agent manages interruptions
+- [ ] Agent recovers from silence
+- [ ] Agent deals with unexpected topics
+
+**Integrations** (if applicable)
+- [ ] API calls work correctly
+- [ ] Data is fetched/sent properly
+- [ ] Transfer calls connect
+- [ ] Variables populate correctly
+
+**Quality**
+- [ ] Voice sounds natural
+- [ ] Response timing feels right
+- [ ] Personality matches brand
+- [ ] No awkward pauses
+
+---
+
+## Testing Tips
+
+
+
+ 
+
+
+
+ 
+
+
+The Audiences page shows all your contact lists at a glance.
+
+| Column | Description |
+|--------|-------------|
+| Name | Audience name and ID |
+| Campaigns | Campaigns using this audience |
+| Members | Number of contacts |
+| Created on | When the audience was created |
+| Last modified | Last update time |
+| Actions | Three-dot menu for options |
+
+**Sorting Options:**
+- Created on
+- Total members
+- Last modified
+
+**Filter Options:**
+- All Audiences
+- With Campaigns
+- Without Campaigns
+
+---
+
+## Creating an Audience
+
+Click **Create Audience** (green button, top right) to start a three-step process.
+
+
+
+
+ 
+
+
+ You'll see a preview of your CSV data. Select the column that contains valid phone numbers from the dropdown.
+
+ 
+
+
+ | Field | Required | Example |
+ |-------|----------|---------|
+ | Audience Name | Yes | VIP Customers List |
+ | Description | No | High-value customers for premium promotions |
+
+ Click **Create Audience** to finish.
+ 
+
+
+Here you can:
+- **Search** for specific members
+- **Select contacts** using checkboxes
+- **Delete** selected contacts with the Delete button
+- **Add new** contacts with the Add New button
+
+---
+
+## Adding Members to Existing Audiences
+
+Click **Add New** to add contacts to an existing audience. You have two options:
+
+
+
+
+ Fill in the contact details one at a time:
+ - **phoneNumber** (required) — in international format
+ - Plus any other fields defined in your audience
+
+ Click **Add Member** to save.
+ 
+
+
+ Upload another CSV file to add contacts in bulk.
+
+ - CSV headers should match your audience fields
+ - Maximum file size: 10 MB
+ - Click to upload or drag and drop
+ 
+
+
+The Campaigns page shows all your outbound calling programs.
+
+| Column | Description |
+|--------|-------------|
+| Campaign name | Name and ID |
+| Created on | When the campaign was created |
+| Last modified | Last update time |
+| Contact list | Linked audience |
+| Connected agent | Agent making the calls |
+| Status | Draft, Scheduled, Active, Paused, Completed, or Failed |
+
+**Sorting:** Created on, Last modified
+
+**Filters:** All, Draft, Scheduled, Active, Paused, Completed
+
+---
+
+## Creating a Campaign
+
+Click **Create Campaign** (green button, top right).
+
+
+ 
+
+
+| Field | Required | Description |
+|-------|----------|-------------|
+| **Campaign name** | Yes | Max 40 characters |
+| **Description** | No | Notes about this campaign's purpose |
+| **Select Audience** | Yes | Which contact list to call |
+| **Select Agent** | Yes | Which agent makes the calls |
+| **Max Retries** | No | Times to retry unanswered calls (0-10). Set to 0 to disable. |
+| **Retry Delay** | No | Wait time before retrying (1-1440 minutes) |
+| **Schedule Campaign** | No | Set timezone + date/time to start automatically. Leave empty to save as draft. |
+
+Click **Create Campaign** when done.
+
+
+
+
+ Individual call records for this campaign. Same interface as [Conversation Logs](/atoms/atoms-platform/analytics-logs/conversation-logs)—click any call to see the full transcript, events, and metrics.
+ 
+
+
+ Timeline of campaign lifecycle events.
+
+ | Column | Description |
+ |--------|-------------|
+ | Date | When the event occurred |
+ | Trigger Source | What triggered the event (system, manual) |
+ | Event Action | What happened (started, paused, completed, etc.) |
+ 
+
+
+ Execution runs and their results.
+
+ **Summary:** Total Executions, Completed, Processing, Failed
+
+ **Execution History** shows each run with:
+ - Start and completion time
+ - Progress bar
+ - Total Members, Processed, Failed, Duration
+ 
+
+
+The main view shows all your phone numbers with key details:
+
+| Field | Description |
+|-------|-------------|
+| **Number** | The phone number |
+| **Provider** | Telephony provider (e.g., Plivo) |
+| **Connected Agent** | Which agent is assigned |
+| **Agent Name** | Name of the connected agent |
+| **Rent Date** | When you acquired the number |
+| **Monthly Cost** | Recurring cost |
+| **Status** | Active or inactive |
+
+Click any number in the list to see its details and manage it.
+
+---
+
+## Adding a Number
+
+Click **Add Number** in the top right. You have two options:
+
+