Granular Callback Data, & Fewer Blind Spots: Phonexa Product Updates

These updates span the Phonexa platform, including suite-level improvements and updates across Call Logic and LMS Sync. The focus is on reliability, visibility, and making everyday workflows easier to manage.

Here’s what’s new and how teams are using it.

Callback Enhancements (Call Logic)

Granular Control into Every Callback Event

What’s New: New tracking events have been added for Callback campaigns, covering each stage of the callback lifecycle:

• Callback Initiated: Callback request is created and dialing begins
• Callback Failed: Callback cannot be completed (e.g., routing or configuration issues)
• Callback Answered: Callback is successfully connected and answered
• Callback Failed With Busy: All retry attempts complete with a Busy status
• Callback Failed With No Answer: All retry attempts complete with a No Answer status

Purpose: These events exist to make callback outcomes explicit and measurable. They provide a clearer view of where callbacks connect, fail, or require follow-up.

How Teams Use It: When creating event-based rules, you can select specific Callback events directly from the Trigger dropdown. This allows workflows and integrations to respond to precise callback outcomes instead of treating all callbacks the same.

Learn More: Event Tracking Type → Ping URL

 

 

 

 

 

 

 

 

Tracking (LMS Sync & Call Logic)

Early Warnings for Tracking Rule Issues

What’s New: A new Warning Notifications block is now available in Tracking rules. Users can configure email alerts when integrations reach a defined number of no-responses or bad requests within a selected timeframe.

The system monitors this automatically in the background, applies it at all levels, includes a $0.0001 fee, and notifies the rule creator if a publisher attempts to delete a rule with active notifications.

Purpose: This update helps teams catch integration issues early. Instead of discovering problems after performance is affected, alerts surface potential failures as they begin to accumulate.

How Teams Use It: When creating or editing an event-based tracking rule, you can enable Warning Notifications as an additional setting. This feature lets you set alert conditions but does not create a new rule or change how the rule itself works.

Learn More:

• Product Settings → Tracking
• Campaign Configuration → Tracking
• Publisher Configuration → Tracking

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Lead Stash

A Clearer View of Lead Stash API Usage

What’s New: A new API Access Summary Report is now available for Lead Stash. It provides visibility into how the Lead Stash API is being accessed across products and API keys.

Purpose: The report helps teams understand usage patterns and identify potential issues or inefficiencies as they happen.

How Teams Use It: Within the Lead Stash reporting page, an added API Access Summary tab provides visibility into API activity across products and API keys, making it easier to review usage and spot anomalies.

Learn More: Lead Stash Data → API Access Summary

Final Thoughts

These updates focus on practical improvements that support how teams work inside Phonexa every day. By bringing clearer insight into callbacks and tracking rules, along with deeper visibility into API usage, each change is designed to improve control and transparency without adding operational overhead.

If you’re already using these features or want to explore them further, reach out to your Account Manager to see how they fit into your current setup.