CallScaler Product Changelog and Release Notes

Opening Filters on the call log no longer zooms the page in when you tap a search or text input, every input on mobile is now sized so Safari leaves the viewport alone. The Filters sheet also opens with the already-applied Date range collapsed (with a "Last 4 weeks" summary on top), so you can jump straight to "+ Add another filter" without scrolling past the date picker. New filters added from the picker still open expanded and ready to edit.

When you generated a deposit link from the Buyers tab and shared it with a buyer, Stripe redirected the buyer back to a page they couldn't reach, so paid deposits silently never credited the buyer's balance and no card was saved for auto top-up. Deposit links now return to a buyer-accessible confirmation page that credits the balance and saves the card the moment payment completes. Buyer-initiated Add Funds from inside the app was unaffected.

When you added a buyer or publisher using an email that was already registered on CallScaler, the contact was quietly linked to that existing account and could land on the wrong dashboard. Adding a buyer or publisher now checks the email first and tells you if it already belongs to a CallScaler account, so you can use a different one instead of creating a mismatched login.

Unqualifying a call already zeroes the publisher payout and reverses the affiliate credit, but the Payout column was still rendering the buyer's original webhook-reported call value (e.g. $152.10 in green) because the green-amount branch was checked before the Unqualified branch. The column now reads Unqualified first, then the publisher payout, then the buyer-reported call value, then a dash, so the call log matches the actual ledger state, on both desktop and mobile.

When a buyer's payout-sync webhook arrived at the same moment a call was finishing, the call-completion handler could overwrite the webhook's confirmed payout with $0 on the call row. Your affiliate balance was still credited correctly, but the per-call payout on the publisher's call log and dashboard read $0, so lifetime and monthly totals understated what was actually owed. Both writers now coordinate on the call row so whichever runs first wins, and the other preserves it. Eight affected calls across four publishers have been corrected.

Every accepted ping/post response, and the API spec popup you hand to publishers, now returns min_duration_seconds, so a publisher's bidding system can see exactly how long a call must stay connected to qualify for the quoted bid. The response already told them the routing window (ttl_seconds); now the qualifying duration is included too. The value is the minimum set on the campaign, falling back to the offer's default, and is 0 when there's no minimum. It's the same threshold used to qualify the call for payout, and it's returned for both fixed-rate and auction campaigns.

When a call flow is built as a chain of "Forward" steps that fail over to the next number, for example, ring office, then ring answering service, then voicemail, the call log was always showing the first number in the chain as the destination, even when the call was picked up by the second or later number. The destination now updates to whichever forward number actually answered, and shows blank when the call rolled all the way to voicemail. Historical calls for affected accounts have been corrected the same way using carrier data.

The Add Buyer and Add Publisher dialogs now include a "Send welcome email" checkbox, on by default. Uncheck it to create the buyer or publisher in your network without auto-emailing them login credentials, useful when you want to set up real-time-bidding specs, numbers, or payouts for them first and invite them later. The default still sends the email, so nothing changes for the way you add people today.