PHLO (Visual Workflow Builder)

​

Overview

• No XML or code required
• Drag-and-drop components
• Built-in testing
• Instant deployment

​

Access PHLO

​

Use Cases

​

Components

​

Triggers

​

Actions

​

Logic

​

Endpoints

​

Building a PHLO

​

Step 1: Create New PHLO

1. Navigate to Voice > PHLO
2. Click Create New PHLO
3. Enter a name for your workflow
4. Select trigger type (Incoming Call or HTTP Request)

​

Step 2: Design Workflow

1. Drag components from the sidebar
2. Connect components by drawing lines
3. Configure each component’s settings
4. Use branches for conditional logic

​

Step 3: Test

1. Click Test in the PHLO editor
2. Simulate incoming calls
3. Verify flow behavior
4. Debug any issues

​

Step 4: Deploy

1. Click Save to deploy changes
2. Assign phone number to PHLO
3. PHLO is live immediately

​

Assign Phone Number to PHLO

​

Method 1: From PHLO Editor

1. Open your PHLO
2. Click Assign Number
3. Select available phone number
4. Save

​

Method 2: From Phone Numbers

1. Go to Phone Numbers > Active
2. Click on the number
3. Select PHLO for Application Type
4. Choose your PHLO from dropdown
5. Update

​

Example: Simple IVR

[Incoming Call]
       ↓
[Speak: "Welcome. Press 1 for sales, 2 for support"]
       ↓
[Get Input: timeout=10, digits=1]
       ↓
[Branch]
   ├── Input=1 → [Dial: Sales Team]
   ├── Input=2 → [Dial: Support Team]
   └── No Input → [Speak: "Goodbye"] → [Hangup]

​

Example: Call Forwarding with Voicemail

[Incoming Call]
       ↓
[Dial: Primary Number, timeout=20]
       ↓
[Branch: Call Answered?]
   ├── Yes → [End]
   └── No → [Speak: "Leave a message after the beep"]
              ↓
           [Record: max_length=60]
              ↓
           [HTTP Request: Send recording URL to webhook]
              ↓
           [Hangup]

​

Triggering PHLO via API

curl -X POST \
  "https://phlorunner.plivo.com/v1/account/{auth_id}/phlo/{phlo_id}" \
  -u "{auth_id}:{auth_token}" \
  -H "Content-Type: application/json" \
  -d '{"from": "14151234567", "to": "14157654321"}'

​

Best Practices

​

Design

• Keep workflows simple and focused
• Use meaningful component names
• Document complex logic with notes
• Test all branches thoroughly

​

Performance

• Minimize HTTP request latency
• Use efficient audio files
• Handle timeouts gracefully

​

Maintenance

• Version your PHLOs (create copies before major changes)
• Monitor call logs for issues
• Update based on user feedback

​

PHLO vs XML Applications

• Building standard IVR/routing flows
• No development resources available
• Quick deployment needed

• Complex business logic required
• Integration with existing systems
• Dynamic, data-driven call flows

​

Troubleshooting

​

Common Issues

​

Debug Tools

• Use PHLO’s built-in test mode
• Check call logs in console
• Review HTTP request/response logs

​

Related Resources

• PHLO Documentation
• PHLO API Reference
• Voice API Reference
• XML Application Guide