Current Limitation
There is no native "Call Returned" status that automatically links missed inbound calls to subsequent outbound calls. The system treats every call as a unique record, making automatic linking complex.
Recommended Solution: Custom Call Outcome Field
The most effective workaround is a custom Call Outcome field that reps manually update when returning missed calls.
Setup Steps
Create a custom Call Outcome field with options like "Missed Call Returned"
Train your reps to manually select this outcome when calling back a missed call
Run reports filtered by that specific outcome to track returned call volume
Alternative: Custom Workflow Automation
For teams that need automation, custom workflows can potentially be built to handle this tracking. Be aware of the following limitations:
Complex to implement since calls are treated as distinct events
Requires sandbox testing to ensure reliable mapping without data errors
May not be 100% accurate in all scenarios
β οΈ Note: Contact Dazos Support to discuss building a tailored workflow solution for your specific use case.
Common Challenges
Manual Entry Burden: If your team is accustomed to automatic call tracking (like in CallRail), the manual process may be difficult to adopt consistently.
βData Accuracy: Success depends entirely on reps consistently updating the Call Outcome field for every returned call.
π‘ Tip: Include the Call Outcome field update as a required step in your team's callback procedure to improve adoption and reporting accuracy.
β
Best Practice: Run weekly reports filtered by the "Missed Call Returned" outcome to monitor both team compliance and callback volume.
Related Resources
For more complex automation needs or custom workflow development, contact support to discuss building a tailored solution for your specific use case.