bland-cli 0.1.9 → 0.2.0

package/dist/index.js

@@ -25,7 +25,7 @@ const program = new Command();
 program
     .name("bland")
     .description("The official Bland AI command-line interface")
-    .version("0.1.9");
+    .version("0.2.0");
 // Register all command groups
 registerAuthCommand(program);
 registerCallCommand(program);

package/dist/types/pathway.d.ts

@@ -6,7 +6,7 @@ export interface PathwayFile {
     global?: {
         prompt?: string;
         voice?: string;
-        model?: "base" | "turbo";
+        model?: "base" | "turbo" | "smart";
         tools?: string[];
         first_sentence?: string;
         language?: string;
@@ -25,7 +25,7 @@ export interface PathwayFileNode {
     knowledge_base_id?: string;
     tools?: PathwayFileTool[];
     extract_variables?: PathwayFileVariable[];
-    model_options?: Record<string, unknown>;
+    model_options?: PathwayModelOptions;
     edges?: PathwayFileEdge[];
 }
 export interface PathwayFileEdge {
@@ -35,14 +35,52 @@ export interface PathwayFileEdge {
     /** @deprecated Use label instead. Kept for backwards compatibility on read. */
     condition?: string;
 }
+/**
+ * Tool attached to a pathway node.
+ *
+ * Tools are triggered inline during conversation when the LLM decides to call them.
+ * Use tools for information lookups (inventory, availability, pricing).
+ * Use webhook nodes for operational workflows (booking, payment).
+ *
+ * The LLM triggers a tool by outputting <function_name=TOOL_NAME>.
+ */
 export interface PathwayFileTool {
     name: string;
     description?: string;
+    type?: "webhook" | "custom_tool";
+    /** What to say (TTS) before executing the tool */
+    speech?: string;
+    /** How to handle the result:
+     *  - "feed_context": inject result into LLM context, continue dialogue
+     *  - "feed_context_and_route": inject result AND evaluate response_pathways to potentially offramp
+     */
+    behavior?: "feed_context" | "feed_context_and_route";
     url?: string;
     method?: "GET" | "POST" | "PUT" | "DELETE" | "PATCH";
     headers?: Record<string, string>;
     body?: Record<string, unknown>;
+    /** JSONPath response mapping — extract fields from webhook response */
+    response_data?: Array<{
+        name: string;
+        data: string;
+        context?: string;
+    }>;
+    timeout?: number;
+    max_retries?: number;
     input_schema?: Record<string, unknown>;
+    tool_id?: string;
+    response_pathways?: Array<{
+        variable: string;
+        condition: string;
+        value: string;
+        target_id: string;
+        target_name: string;
+    }>;
+    extract_vars?: Array<{
+        name: string;
+        type: string;
+        description: string;
+    }>;
 }
 export interface PathwayFileVariable {
     name: string;
@@ -50,6 +88,12 @@ export interface PathwayFileVariable {
     description: string;
     spelling_precision?: boolean;
 }
+export interface PathwayModelOptions {
+    model_type?: "base" | "turbo" | "smart";
+    temperature?: number;
+    skip_user_response?: boolean;
+    block_interruptions?: boolean;
+}
 export interface PathwayTestCase {
     name: string;
     scenario: string;

package/dist/types/pathway.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"pathway.d.ts","sourceRoot":"","sources":["../../src/types/pathway.ts"],"names":[],"mappings":"AAAA,4CAA4C;AAC5C,MAAM,WAAW,WAAW;IAC1B,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,OAAO,CAAC,EAAE,OAAO,GAAG,YAAY,GAAG,MAAM,CAAC;IAE1C,MAAM,CAAC,EAAE;QACP,MAAM,CAAC,EAAE,MAAM,CAAC;QAChB,KAAK,CAAC,EAAE,MAAM,CAAC;QACf,KAAK,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC;QACzB,KAAK,CAAC,EAAE,MAAM,EAAE,CAAC;QACjB,cAAc,CAAC,EAAE,MAAM,CAAC;QACxB,QAAQ,CAAC,EAAE,MAAM,CAAC;KACnB,CAAC;IAEF,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,eAAe,CAAC,CAAC;IAEvC,KAAK,CAAC,EAAE,eAAe,EAAE,CAAC;CAC3B;AAED,MAAM,WAAW,eAAe;IAC9B,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,YAAY,CAAC,EAAE,MAAM,CAAC;IAGtB,MAAM,CAAC,EAAE,MAAM,CAAC;IAGhB,IAAI,CAAC,EAAE,MAAM,CAAC;IAGd,iBAAiB,CAAC,EAAE,MAAM,CAAC;IAG3B,KAAK,CAAC,EAAE,eAAe,EAAE,CAAC;IAG1B,iBAAiB,CAAC,EAAE,mBAAmB,EAAE,CAAC;IAG1C,aAAa,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IAGxC,KAAK,CAAC,EAAE,eAAe,EAAE,CAAC;CAC3B;AAED,MAAM,WAAW,eAAe;IAC9B,MAAM,EAAE,MAAM,CAAC;IACf,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,+EAA+E;IAC/E,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED,MAAM,WAAW,eAAe;IAC9B,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,MAAM,CAAC,EAAE,KAAK,GAAG,MAAM,GAAG,KAAK,GAAG,QAAQ,GAAG,OAAO,CAAC;IACrD,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IACjC,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IAC/B,YAAY,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CACxC;AAED,MAAM,WAAW,mBAAmB;IAClC,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,QAAQ,GAAG,SAAS,GAAG,SAAS,CAAC;IACvC,WAAW,EAAE,MAAM,CAAC;IACpB,kBAAkB,CAAC,EAAE,OAAO,CAAC;CAC9B;AAED,MAAM,WAAW,eAAe;IAC9B,IAAI,EAAE,MAAM,CAAC;IACb,QAAQ,EAAE,MAAM,CAAC;IACjB,aAAa,CAAC,EAAE,MAAM,EAAE,CAAC;IACzB,kBAAkB,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IAC7C,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB"}
+{"version":3,"file":"pathway.d.ts","sourceRoot":"","sources":["../../src/types/pathway.ts"],"names":[],"mappings":"AAAA,4CAA4C;AAC5C,MAAM,WAAW,WAAW;IAC1B,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,OAAO,CAAC,EAAE,OAAO,GAAG,YAAY,GAAG,MAAM,CAAC;IAE1C,MAAM,CAAC,EAAE;QACP,MAAM,CAAC,EAAE,MAAM,CAAC;QAChB,KAAK,CAAC,EAAE,MAAM,CAAC;QACf,KAAK,CAAC,EAAE,MAAM,GAAG,OAAO,GAAG,OAAO,CAAC;QACnC,KAAK,CAAC,EAAE,MAAM,EAAE,CAAC;QACjB,cAAc,CAAC,EAAE,MAAM,CAAC;QACxB,QAAQ,CAAC,EAAE,MAAM,CAAC;KACnB,CAAC;IAEF,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,eAAe,CAAC,CAAC;IAEvC,KAAK,CAAC,EAAE,eAAe,EAAE,CAAC;CAC3B;AAED,MAAM,WAAW,eAAe;IAC9B,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,YAAY,CAAC,EAAE,MAAM,CAAC;IAGtB,MAAM,CAAC,EAAE,MAAM,CAAC;IAGhB,IAAI,CAAC,EAAE,MAAM,CAAC;IAGd,iBAAiB,CAAC,EAAE,MAAM,CAAC;IAG3B,KAAK,CAAC,EAAE,eAAe,EAAE,CAAC;IAG1B,iBAAiB,CAAC,EAAE,mBAAmB,EAAE,CAAC;IAG1C,aAAa,CAAC,EAAE,mBAAmB,CAAC;IAGpC,KAAK,CAAC,EAAE,eAAe,EAAE,CAAC;CAC3B;AAED,MAAM,WAAW,eAAe;IAC9B,MAAM,EAAE,MAAM,CAAC;IACf,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,+EAA+E;IAC/E,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED;;;;;;;;GAQG;AACH,MAAM,WAAW,eAAe;IAC9B,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,IAAI,CAAC,EAAE,SAAS,GAAG,aAAa,CAAC;IACjC,kDAAkD;IAClD,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB;;;OAGG;IACH,QAAQ,CAAC,EAAE,cAAc,GAAG,wBAAwB,CAAC;IAGrD,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,MAAM,CAAC,EAAE,KAAK,GAAG,MAAM,GAAG,KAAK,GAAG,QAAQ,GAAG,OAAO,CAAC;IACrD,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IACjC,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IAC/B,uEAAuE;IACvE,aAAa,CAAC,EAAE,KAAK,CAAC;QACpB,IAAI,EAAE,MAAM,CAAC;QACb,IAAI,EAAE,MAAM,CAAC;QACb,OAAO,CAAC,EAAE,MAAM,CAAC;KAClB,CAAC,CAAC;IACH,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,WAAW,CAAC,EAAE,MAAM,CAAC;IAGrB,YAAY,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IACvC,OAAO,CAAC,EAAE,MAAM,CAAC;IAGjB,iBAAiB,CAAC,EAAE,KAAK,CAAC;QACxB,QAAQ,EAAE,MAAM,CAAC;QACjB,SAAS,EAAE,MAAM,CAAC;QAClB,KAAK,EAAE,MAAM,CAAC;QACd,SAAS,EAAE,MAAM,CAAC;QAClB,WAAW,EAAE,MAAM,CAAC;KACrB,CAAC,CAAC;IAGH,YAAY,CAAC,EAAE,KAAK,CAAC;QACnB,IAAI,EAAE,MAAM,CAAC;QACb,IAAI,EAAE,MAAM,CAAC;QACb,WAAW,EAAE,MAAM,CAAC;KACrB,CAAC,CAAC;CACJ;AAED,MAAM,WAAW,mBAAmB;IAClC,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,QAAQ,GAAG,SAAS,GAAG,SAAS,CAAC;IACvC,WAAW,EAAE,MAAM,CAAC;IACpB,kBAAkB,CAAC,EAAE,OAAO,CAAC;CAC9B;AAED,MAAM,WAAW,mBAAmB;IAClC,UAAU,CAAC,EAAE,MAAM,GAAG,OAAO,GAAG,OAAO,CAAC;IACxC,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,kBAAkB,CAAC,EAAE,OAAO,CAAC;IAC7B,mBAAmB,CAAC,EAAE,OAAO,CAAC;CAC/B;AAED,MAAM,WAAW,eAAe;IAC9B,IAAI,EAAE,MAAM,CAAC;IACb,QAAQ,EAAE,MAAM,CAAC;IACjB,aAAa,CAAC,EAAE,MAAM,EAAE,CAAC;IACzB,kBAAkB,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IAC7C,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bland-cli",
-  "version": "0.1.9",
+  "version": "0.2.0",
   "description": "The official Bland AI command-line interface",
   "type": "module",
   "main": "dist/index.js",

package/templates/PATHWAY_GUIDE.md

@@ -0,0 +1,159 @@
+# Bland Pathway Design Guide
+
+## Phone Tone Best Practices
+
+Pathways power phone calls. Every prompt should be written for spoken conversation:
+
+- **Keep responses short.** 1-3 sentences per turn. Nobody wants a monologue.
+- **Use natural speech patterns.** Backchannels ("mhmm", "gotcha", "yep"), brief acknowledgments ("perfect", "great"), casual transitions.
+- **Don't read lists.** Weave questions into conversation, one or two at a time.
+- **Show emotion.** "Oh no, I'm sorry to hear that" or "That's awesome!" — not "I understand your concern."
+- **Be warm but efficient.** Friendly doesn't mean slow. Respect the caller's time.
+- **Avoid robotic phrasing.** No "I will now proceed to..." or "Please provide your..."
+- **Mirror the caller.** If they're casual, be casual. If they're formal, match it.
+
+## Node Design: Dense Context
+
+Each node should be self-contained with rich context. The LLM only sees the current node's prompt, so pack in everything it needs:
+
+```yaml
+Check Availability:
+  type: Default
+  prompt: >-
+    Ask what type of appointment they need and when they'd prefer to come in.
+    We're open Monday-Friday 8am-6pm, Saturday 9am-1pm.
+
+    Use the check_availability tool to look up slots. Share 2-3 options.
+    If nothing works for their preferred time, suggest nearby alternatives.
+
+    Keep it helpful: "Let me check what we've got for you."
+  condition: >-
+    Met when the caller has selected a specific appointment slot.
+  extract_variables:
+    - name: visit_type
+      type: string
+      description: Type of visit
+    - name: preferred_date
+      type: string
+      description: Preferred date
+```
+
+## Tools on Nodes vs Webhook Nodes
+
+**Prefer tools on nodes** over standalone webhook nodes:
+
+| Use Tools On Nodes | Use Webhook Nodes |
+|---|---|
+| API lookups during conversation | Standalone operations that block flow |
+| Inventory/availability checks | Payment processing |
+| CRM data retrieval | Form submissions |
+| Multiple tools on one node | Single critical API call |
+
+### Tool Structure
+
+```yaml
+tools:
+  - name: check_inventory        # LLM triggers via <function_name=check_inventory>
+    description: Look up product stock
+    type: webhook
+    behavior: feed_context        # or "feed_context_and_route" for conditional routing
+    speech: "Let me check that."  # Said before execution (optional)
+    url: "https://api.example.com/stock"
+    method: POST
+    body:
+      sku: "{{product_sku}}"      # {{var}} placeholders replaced at runtime
+    response_data:
+      - name: in_stock
+        data: "$.available"       # JSONPath extraction
+    timeout: 5000
+    max_retries: 2
+```
+
+### Response-Based Routing
+
+Route to different nodes based on API response:
+
+```yaml
+tools:
+  - name: book_appointment
+    type: webhook
+    behavior: feed_context_and_route
+    url: "https://api.example.com/book"
+    method: POST
+    body:
+      patient: "{{patient_name}}"
+      date: "{{date}}"
+    response_data:
+      - name: status
+        data: "$.booking_status"
+    response_pathways:
+      - variable: status
+        condition: "=="
+        value: "confirmed"
+        target_name: Booking Confirmed
+      - variable: status
+        condition: "=="
+        value: "unavailable"
+        target_name: Try Another Time
+```
+
+## Edge Design
+
+Edges control conversation flow. Each edge needs:
+
+- **label**: Short text shown on the edge (what triggers this transition)
+- **description**: Detailed condition for the LLM to evaluate
+
+```yaml
+edges:
+  - target: New Patient Info
+    label: New patient
+    description: Caller says they are new and haven't visited before.
+  - target: Returning Patient
+    label: Returning patient
+    description: Caller says they've been here before or have an existing record.
+```
+
+## Node Conditions
+
+The `condition` field tells the LLM when to transition away from this node:
+
+```yaml
+Collect Info:
+  prompt: "Collect their name, phone, and email..."
+  condition: >-
+    Met when the caller has provided their full name, phone number,
+    and email address.
+```
+
+## Variable Extraction
+
+Extract structured data from conversation:
+
+```yaml
+extract_variables:
+  - name: patient_name
+    type: string
+    description: The caller's full name
+  - name: appointment_date
+    type: string
+    description: The selected appointment date and time
+  - name: is_urgent
+    type: boolean
+    description: Whether the caller described an urgent medical need
+```
+
+## Model Options
+
+Control LLM behavior per node:
+
+```yaml
+model_options:
+  model_type: smart        # base, turbo, or smart
+  temperature: 0.3         # Lower = more deterministic
+  block_interruptions: true # Don't let caller interrupt during this node
+```
+
+## Complete Example
+
+See `templates/complex-pathway.yaml` for a full appointment booking pathway with tools, conditions, and routing.

package/templates/complex-pathway.yaml

@@ -0,0 +1,248 @@
+# Complex Pathway Template — Appointment Booking with API Integration
+#
+# This template demonstrates best practices for pathway design:
+# - Dense, conversational prompts with phone-tone guidance
+# - Tools on nodes for real-time API lookups
+# - Extract variables for structured data capture
+# - Node conditions for clear transition logic
+# - Edge labels/descriptions for deterministic routing
+#
+# Usage: bland pathway init --template complex
+
+name: Appointment Booking Agent
+description: AI receptionist that schedules appointments via API integration
+
+global:
+  voice: nat
+  model: smart
+  first_sentence: "Hey there, thanks for calling! How can I help you today?"
+  language: en
+
+nodes:
+  Greeting:
+    type: Default
+    prompt: >-
+      You are a warm, professional receptionist at a medical practice. This is a
+      phone call — keep responses short and conversational. Use natural speech
+      patterns: occasional backchannels like "mhmm" or "gotcha", brief
+      acknowledgments, and friendly transitions. Never sound robotic or read
+      from a script.
+
+      Greet the caller and ask what brings them in today. If they want to
+      schedule an appointment, find out if they're a new or returning patient.
+    condition: >-
+      The condition is met when the caller indicates whether they want to
+      schedule an appointment (and if so, whether they are new or returning).
+    edges:
+      - target: Collect Patient Info
+        label: Wants appointment
+        description: Caller wants to schedule an appointment.
+      - target: General Inquiry
+        label: General question
+        description: Caller has a general question not related to scheduling.
+
+  Collect Patient Info:
+    type: Default
+    prompt: >-
+      Collect the caller's information conversationally — DO NOT read a
+      checklist. Weave questions into natural dialogue, one or two at a time.
+
+      Needed: full name, date of birth, phone number.
+
+      For returning patients, just confirm their name and DOB. For new patients,
+      also get their insurance provider.
+
+      Keep it warm — say things like "perfect" or "got it" as they share info.
+      If they volunteer information unprompted, roll with it.
+    condition: >-
+      The condition is met when you have the caller's full name, date of birth,
+      and phone number. For new patients, also their insurance provider.
+    extract_variables:
+      - name: patient_name
+        type: string
+        description: The caller's full name
+      - name: date_of_birth
+        type: string
+        description: The caller's date of birth
+      - name: phone_number
+        type: string
+        description: The caller's phone number
+      - name: insurance
+        type: string
+        description: Insurance provider (new patients only)
+    edges:
+      - target: Check Availability
+        label: Info collected
+        description: All required patient information has been collected.
+
+  Check Availability:
+    type: Default
+    prompt: >-
+      Ask the caller what type of appointment they need (wellness check,
+      sick visit, follow-up, etc.) and their preferred day/time.
+
+      Once you have their preference, use the check_availability tool to look
+      up open slots. Share 2-3 available options and let them pick.
+
+      If nothing works, offer to check a different day. Keep it helpful and
+      flexible — "Let me see what we've got for you."
+    condition: >-
+      The condition is met when the caller has selected a specific appointment
+      slot from the available options.
+    extract_variables:
+      - name: visit_type
+        type: string
+        description: Type of appointment — wellness, sick visit, follow-up, etc.
+      - name: preferred_date
+        type: string
+        description: The caller's preferred appointment date
+      - name: preferred_time
+        type: string
+        description: The caller's preferred appointment time
+    tools:
+      - name: check_availability
+        description: Check available appointment slots for a given date
+        type: webhook
+        behavior: feed_context
+        url: "https://api.example.com/appointments/available"
+        method: POST
+        headers:
+          Content-Type: application/json
+          Authorization: "Bearer {{API_KEY}}"
+        body:
+          date: "{{preferred_date}}"
+          visit_type: "{{visit_type}}"
+        response_data:
+          - name: available_slots
+            data: "$.slots"
+            context: "Available time slots"
+        timeout: 5000
+        max_retries: 2
+    edges:
+      - target: Confirm Booking
+        label: Slot selected
+        description: Caller has chosen an available time slot.
+
+  Confirm Booking:
+    type: Default
+    prompt: >-
+      Recap the appointment details: {{patient_name}}'s {{visit_type}} on
+      {{preferred_date}} at {{preferred_time}}. Ask the caller to confirm.
+
+      If they want to change something, go back and adjust. If confirmed, use
+      the book_appointment tool to finalize the booking.
+
+      After booking, give them a confirmation number and any prep instructions.
+    condition: >-
+      The condition is met when the appointment has been booked successfully
+      or the caller wants to change the details.
+    tools:
+      - name: book_appointment
+        description: Book the confirmed appointment
+        type: webhook
+        behavior: feed_context_and_route
+        speech: "Let me get that booked for you right now."
+        url: "https://api.example.com/appointments/book"
+        method: POST
+        body:
+          patient_name: "{{patient_name}}"
+          date_of_birth: "{{date_of_birth}}"
+          phone: "{{phone_number}}"
+          date: "{{preferred_date}}"
+          time: "{{preferred_time}}"
+          visit_type: "{{visit_type}}"
+        response_data:
+          - name: confirmation_number
+            data: "$.confirmation_id"
+          - name: booking_status
+            data: "$.status"
+        response_pathways:
+          - variable: booking_status
+            condition: "=="
+            value: "confirmed"
+            target_id: booking_confirmed
+            target_name: Booking Confirmed
+          - variable: booking_status
+            condition: "=="
+            value: "failed"
+            target_id: booking_failed
+            target_name: Booking Failed
+    edges:
+      - target: Check Availability
+        label: Wants to change
+        description: Caller wants to change the appointment details.
+      - target: Booking Confirmed
+        label: Booking successful
+        description: Appointment was booked successfully.
+      - target: Booking Failed
+        label: Booking failed
+        description: Appointment booking failed due to a system error.
+
+  Booking Confirmed:
+    type: Default
+    prompt: >-
+      Great news — the appointment is confirmed! Share the confirmation number
+      {{confirmation_number}} with the caller.
+
+      Remind them to arrive 15 minutes early, bring their insurance card, and
+      a photo ID. Ask if there's anything else you can help with.
+    condition: The condition is met when you have shared the confirmation details and asked if they need anything else.
+    edges:
+      - target: Anything Else
+        label: Confirmation shared
+        description: Caller has received their confirmation details.
+
+  Booking Failed:
+    type: Default
+    prompt: >-
+      Apologize sincerely — something went wrong with the booking system.
+      Offer to try again or take their information and have someone call them
+      back to confirm. Keep it reassuring — "Don't worry, we'll get this
+      sorted out for you."
+    condition: The condition is met when you have offered an alternative.
+    edges:
+      - target: Check Availability
+        label: Try again
+        description: Caller wants to try booking again.
+      - target: End Call
+        label: Will call back
+        description: Staff will call back to confirm the booking.
+
+  General Inquiry:
+    type: Default
+    prompt: >-
+      Answer the caller's general question helpfully. Common questions include
+      office hours (Mon-Fri 8am-6pm, Sat 9am-1pm), location, insurance
+      accepted, and services offered.
+
+      If you don't know the answer, offer to transfer them or have someone
+      call back. Don't make up information.
+    condition: The condition is met when the caller's question has been addressed.
+    edges:
+      - target: Greeting
+        label: Wants to schedule
+        description: After getting their question answered, caller now wants to schedule.
+      - target: Anything Else
+        label: Question answered
+        description: Caller's question has been fully answered.
+
+  Anything Else:
+    type: Default
+    prompt: >-
+      Ask if there's anything else you can help with. If they're all set,
+      thank them warmly and wish them a great day. Keep it brief and genuine.
+    condition: The condition is met when the caller says they're all set or asks for something else.
+    edges:
+      - target: Greeting
+        label: Has another question
+        description: Caller has another question or wants to schedule.
+      - target: End Call
+        label: All done
+        description: Caller has no more questions and is ready to hang up.
+
+  End Call:
+    type: Default
+    prompt: >-
+      Thank them for calling and wish them well. If they have an appointment,
+      remind them of the date. Keep the goodbye warm but brief — don't drag
+      it out.