Call Transfer Not Working
Your agent attempts to transfer calls but the transfer fails or doesn’t complete to the intended recipient.
Symptoms
- Agent initiates a transfer but the call drops
- Transfer completes but goes to the wrong number or voicemail
- No error message, but the call simply disconnects
- Caller hears silence or is returned to the agent instead of the transferred party
- Transfer works in testing but fails in production
Common Causes
- Testing transfers on web calls — Web widget calls don’t support phone-to-phone transfers; transfers only work with real phone calls
- Using Workflow Transfer node — The Workflow Transfer method has a known persistent bug and should not be used
- Incorrect phone number format — Destination numbers missing country code prefix (e.g., missing +1 for US numbers)
- Model incompatibility — Older LLM models may not reliably initiate transfers
Quick Fix:
Use the Function Call Transfer method instead of the Workflow Transfer node.
- Go to Agent Configuration → Function Calls
- Enable the “Transfer Call” function
- Set up parameters: destination number, caller ID (optional), reason (optional)
- Update your workflow to call this function instead of using the Transfer node
- Save and test with a real phone call
How to Fix
Step 1: Use Real Phone Calls, Not Web Calls
- Do not test transfers using the web widget in your dashboard
- Instead, test with a real phone call to your agent’s phone number
- Have the agent transfer you to a real destination number
- Web calls have a different architecture that doesn’t support phone-to-phone transfers
Step 2: Switch from Workflow Transfer to Function Call Transfer
- Open your Agent Workflow
- Find any “Transfer Call” nodes that use the Workflow Transfer method
- Delete these nodes and replace them with Function Call Transfer:
- Go to Agent Configuration → Function Calls
- Enable the “Transfer Call” function
- Set up parameters: destination number, caller ID (optional), reason (optional)
- Update your workflow to call this function instead of using the Transfer node
- Save and test with a real phone call
Step 3: Verify Phone Number Format
- When specifying a transfer destination number, ensure:
- US numbers: Use format
+1XXXXXXXXXX(e.g.,+12125551234) - International: Always include the country code with
+prefix (e.g.,+447911123456for UK) - No hyphens, spaces, or parentheses - only digits and the
+prefix
- US numbers: Use format
- Double-check the destination number is:
- A real, active phone number
- Not a landline that doesn’t accept inbound calls
- Not a number that requires special dialing codes
- Update your workflow with the correctly formatted number
Step 4: Ensure Model Compatibility
- Go to Agent Settings → Model Configuration
- Verify you’re using GPT 4.1 or GPT 4.1-mini
- If using an older model, upgrade to one of the recommended models
- Save changes and re-test the transfer flow
Step 5: Test the Full Transfer Flow
- Call your agent’s phone number from a real phone
- Request a transfer through your agent’s conversation
- Verify that:
- The destination phone rings
- The transfer completes without dropping the call
- You’re connected to the intended recipient
- If transfer still fails, check your Dialora billing and phone number status
Prevention Tips:
- Always test transfers with real phone calls, never the web widget
- Use Function Call Transfer method only — avoid Workflow Transfer nodes
- Create a standardized phone number format for all transfers (with country codes)
- Maintain a list of valid transfer destinations and validate them regularly
- Test transfer functionality weekly to catch issues early
- Use GPT 4.1 or 4.1-mini for all production agents handling transfers