During the Oct/Nov 2025 BluePoint digital marketing review, Wade Zirkle reported that the CallRail outbound dialing feature was not working as expected. When attempting to place outbound calls through the CallRail mobile app, the call would ring back on his own phone rather than connecting to the intended recipient. The issue was diagnosed and resolved live during the meeting.
Status: Resolved
Client: [1]
Meeting Source: [2]
The behavior Wade experienced — his own phone ringing when placing a call — is by design, not a malfunction. CallRail's outbound dialing flow works as follows:
This two-step connection process is how CallRail routes calls through its tracking infrastructure while masking the agent's personal number with a campaign tracking number.
| Step | Action |
|---|---|
| 1 | Open CallRail mobile app and tap the + button (bottom right) |
| 2 | Enter the customer/recipient's phone number in the top field |
| 3 | Enter your own device's phone number in the "Your Number" field |
| 4 | Set Company to BluePoint ATM Solutions |
| 5 | Select the appropriate Tracker (e.g., Eastern Office Pool, Western Office) — this is the number the customer will see on caller ID |
| 6 | Tap Place Call |
| 7 | Answer your own phone when it rings — CallRail will then connect through to the recipient |
Mike Stebbins confirmed the call appeared in his CallRail log during the live test, verifying the fix worked correctly.
CallRail's outbound dialing requires a two-leg connection. The app calls the agent's own phone first; the agent must answer before the system bridges to the customer. This surprises most new users who expect a direct dial. When onboarding clients to CallRail, proactively walk through a live test call to prevent confusion.
See also: [3] (create if needed)