Phonexa Updates: Granular Callback Data & Fewer Blind Spots

A few things have been updated across Phonexa — some at the suite level, others specific to Call Logic and LMS Sync. The concept is pretty simple: better visibility, fewer surprises, and less manual work to figure out what’s actually happening.

Here’s what changed.

Callback Enhancements (Call Logic)

Granular Control into Every Callback Event

What’s New: Callback campaigns now track each stage of the callback lifecycle as its own event:

• Callback Initiated: request is created and dialling begins
• Callback Failed: callback can’t be completed due to routing or configuration issues
• Callback Answered: call connects and is answered successfully
• Callback Failed With Busy: all retry attempts come back with a Busy status
• Callback Failed With No Answer: all retry attempts complete with no answer

Purpose: No more squinting at callback data trying to piece together what happened. Each stage now has its own event, so you can see exactly where a call connected, where it didn’t, and what needs attention.

How Teams Use It: Inside event-based rules, specific Callback events are now available directly from the Trigger dropdown. Your workflows stop treating every callback the same — they respond to what actually happened.

Learn More: Event Tracking Type → Ping URL

Tracking (LMS Sync & Call Logic)

Early Warnings for Tracking Rule Issues

What’s New: There’s a new Warning Notifications block inside Tracking rules. Set a threshold — a number of no-responses or bad requests within a given window — and the system emails you when things start heading in the wrong direction.

It runs in the background, covers all levels, and gives the rule creator a heads-up if someone tries to delete a rule that still has active notifications. There’s a $0.0001 fee attached to this feature.

Purpose: By the time most integration issues become obvious, they’ve usually been quietly building for a while. This catches them earlier — when there’s still time to do something about it before performance takes a hit.

How Teams Use It: When you’re in a tracking rule — creating or editing — Warning Notifications show up as an optional toggle. Flip it on, set your conditions, and leave it. The rule itself works exactly the same; this just sits on top of it and watches.

Learn More

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

Lead Stash

A Clearer View of Lead Stash API Usage

What’s New: Lead Stash now has an API Access Summary report that pulls together API activity across products and keys in one view.

Purpose: When you’re working across multiple products, API usage gets hard to follow fast. This makes it visible without having to chase it down.

How Teams Use It: Open the Lead Stash reporting page and find the API Access Summarytab. Usage broken down by product and API key, in one place — no log-diving required.

Learn More

• Lead Stash Data → API Access Summary

Final Thoughts

Some industry problems are loud. These updates are aimed at the quiet ones — the kind you only notice once they’ve already cost you something. 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.