CallScaler Product Changelog and Release Notes

A publisher who had a campaign suspended and was later approved again on the same offer had every call to their tracking number turned away as suspended. Only the campaign the number actually belongs to is checked now, so an older suspended campaign on the same offer no longer blocks a live one.

When an offer uses a custom vertical, the offer editor now has a Category picker (Home Services, Insurance, Legal, Financial, Healthcare, Auto). The vertical then sits in that category on the Minimum Bids tab, in the RTB vertical group picker, and on your marketplace's buyer catalog and signup page instead of under Custom or Other.

Bidders in an RTB step can sit at Priority 1, 2 or 3 (add groups as you need them; Remove priorities lets you pick which to drop and moves their bidders up). Priority 1 bidders are pinged first and take the call when their best bid clears the floor you set on the group (never below your min bid). If nothing clears, Priority 2 bidders are pinged and the best bid above the min bid wins, including any Priority 1 bid that missed the floor. A Priority 1 bidder whose ping failed (timeout, rate limit, capacity check) is pinged again in that second round. Move any bidder or vertical group between priorities with the arrow on its card, and when adding a vertical group choose all buyers or only the Priority 1 or Priority 2 buyers. Each buyer profile has a default priority that new entries and vertical groups follow, plus an Apply to all call flows button to push it into every flow where the buyer was added by hand. The call's Ping Details tab shows each bidder's priority and round. The auction stays a single pool until you click Add Priority 2; Min bid and Max bid duration now sit under Additional settings, and live auctions resolve within 6 seconds instead of 12. Each priority keeps most of the time for itself and holds back a short slice for the groups after it, so a slow Priority 1 bidder still gets its answer in, and a bidder whose accept step failed is not pinged again in the next round. The editor also stops you saving a later priority that clears at a higher price than the one before it.

On a publisher's page, select several campaigns and click Edit to change them together: campaign type, API spec visibility, payout, min duration, AI gate and RTB max wait. Each setting has a Keep option, so you only change what you tick and everything else stays as it was on each campaign.

Set up from API specs is out of beta. Paste a buyer's API documentation and the endpoint, request format, fields and response paths are filled in for you, on both the RTB bidder card and the buyer campaign editor. The bidder card now shows the endpoint and a Test ping button up front, with Ping request details and Customize test ping folded into one row.

• •Re-qualify: Re-qualifying a call the system had disqualified (a $0 or failed postback) returned an error instead of restoring the payout. It now restores the stamped payout, or clears the disqualified state on a $0 call.
• •Bulk edit: Bulk edits on buyer campaigns only apply the bid duration setting to ping/post campaigns and reject a blank cap or duration; publisher bulk edits ignore RTB max wait when no RTB campaign is selected, and a partial failure keeps the failed rows selected and shows the error.
• •Hold music interrupt: Callers on numbers that use your own SignalWire project kept listening to the whole hold clip after the auction finished. The call now connects as soon as a winner is picked, and the Caller Check hangup uses the right project too.
• •Ping details: Each bidder's response time now shows in the call's Ping Details tab.

Multi-step Gravity Forms could store a blank for a field filled on an earlier page, and forms that reuse a field name kept only one value. Every step's values are kept, repeated names are stored together, and builder plumbing fields are dropped.

On the Offers and Buyers pages, category chips that ran past the edge of the row could only be reached with a trackpad swipe or on touch. Arrows now appear at the edge of the row whenever more chips are out of view, and the mouse wheel scrolls the row too.

When a buyer signs up on your marketplace, an Advanced section lets them choose the call sources they accept (paid search, Facebook Marketplace, call centers and so on). Every source is accepted unless they remove some. The list is saved on the buyer profile, where both the buyer and you can edit it, and it shows on the buyer sheet so you can see at a glance what each buyer takes. The signup question also now reads "Which verticals do you need calls for?"

The vertical picker on buyer signup and the traffic source picker on publisher applications no longer grow taller as you select more. The box stays one line and shows "+3 more" past the first couple of picks. Both now have Select all and Clear, including per industry (for example all of Home Services in one click), and publishers can list as many traffic sources as they use instead of three.

The publisher Offers page on your branded marketplace now groups offers by vertical, the same way the buyer catalog does, so offers without a category no longer pile into Other. Category chips sit in a single scrolling row with a count in each chip, and the offer window shows the same category as the page. On the buyer catalog, cards now say "Set your hours & call volume" and the hero chip reads "Flexible payment terms".

• •Late payouts: Ringba records that settle hours after the call are picked up on later syncs; each run now rescans the last 48 hours instead of the last 30 minutes.
• •Missed records on busy accounts: Ringba call logs are pulled in 4-hour windows and deduplicated, so a single large page no longer drops calls.
• •Postbacks with no duration: A postback that reports a payout but no call length now matches the caller's most recently ended call instead of an unrelated live one.
• •$0 then paid: A call marked unqualified by a $0 postback is requalified, and the buyer is charged again, when a paid postback for the same call follows.

iPhone and iPad bookmarks and Safari tabs on a white-label domain now show your icon (or a neutral one) instead of a blank tile.

Form tracking only caught forms submitted the standard browser way. Gravity Forms, and other builders that submit forms from their own scripts, skipped that path, so those leads never appeared in Forms or were forwarded by email. They are captured now, including multi-step forms (only the final step is recorded) and forms that redirect to a thank-you page. Builder housekeeping fields such as nonces, state tokens and captcha responses are no longer stored with the lead, and a very long answer or a form with more than 50 fields is trimmed instead of being dropped.

On a white-label domain the sidebar, payment window and welcome wizard now always show your uploaded icon (or a neutral glyph if you have not uploaded one). The CallScaler mark no longer appears anywhere in the app on your domain, and /favicon.ico on your domain now serves your icon instead of a 404.

Your branded marketplace now has a buyer side at /marketplace/buyers. Visitors see every vertical you sell calls in, grouped by industry, with coverage and hours on each card. Offers that aren't tagged with a vertical still get their own card, named from the offer and filed under the right industry, so nothing hides in a catch-all list. Pricing never shows on the public page. Clicking a card goes straight to signup with that vertical selected, and buyers can pick several; each one becomes its own campaign and they land in the first one's editor. Your brand color is applied throughout, including dark and light brand colors.

If you route calls from your own numbers into a marketplace you also sell in, the earnings shown on those calls were being counted as a publisher cost on your Pay Per Call margin, so the dashboard margin chart and the Pay Per Call overview (margin card, revenue chart, buyer breakdown) dropped every time one of those calls paid out. Those earnings are no longer subtracted.

You can now give other people their own login to your publisher account. Open Team, add their email and a temporary password, and choose their access: a viewer sees everything you see (calls, campaigns, earnings, payouts) but can't change anything, and an owner has full control. Each login is tied to one network, so if you sell in several networks you decide which one a teammate can reach. You can send a password reset for any login, and removing one cuts off access immediately. On an account that sells in more than one network, payout details stay with the account holder, since one payout destination covers every network.

On a white-label domain, several places still said CallScaler instead of your brand:

• •Browser tabs and favicon: Every page inside the app now shows your brand name and icon, including after moving between pages, not just on the login screen.
• •In-app wording: Porting, number transfers, pools, tracking, the call log, offers and applications, the RTB editor, billing and payment screens, email reports and add-ons now use your brand name.
• •Not-found pages: A bad link on a white-label domain now shows a neutral branded page instead of the CallScaler one.
• •Search engines: App pages on a white-label domain are no longer indexable and no longer describe themselves as CallScaler.

Occasional tips and product emails from us now carry a working unsubscribe link, plus the one-click unsubscribe button your mail app shows at the top of a message. Unsubscribing takes effect immediately and never affects account email such as receipts, call notifications or anything you asked us to send.

Buyer campaigns that route to a ping/post endpoint now use the same Pricing card as campaigns routed through your own call flow: choose a fixed price per call or revenue share, set the percentage you pay, and see the margin you keep, with a short "How revenue share works" explainer. The percentage accepts 1 to 100, so you can bill exactly the bid your endpoint returns. Billing the full bid still needs no subscription; keeping a margin does.

RTB campaign settings now include a max wait, so you can keep a ping's wait time under your publisher's own timeout instead of relying on the 4 second default. Leave it blank to use the default.

The live offer count and category list on a white-label storefront only counted offers with a marketplace category, so storefronts with uncategorized offers showed far fewer offers than they listed. Uncategorized offers now count and appear under Other.

Calls routed through an RTB step ignored several call flow settings that worked everywhere else. All of them now apply to RTB transfers:

• •Show tracking number as caller ID: When enabled, the agent who answers an RTB transfer sees your tracking number instead of the caller's own number.
• •Whisper message: Your whisper now plays to the answering agent before an RTB transfer connects.
• •Steps after an RTB step now run: If the winning destination does not answer, or no buyer takes the call and no fallback number is set, the call continues to the next step in your flow instead of ending. You can chain a second RTB step as a retry and follow it with voicemail; each step runs with its own settings and reuses the ZIP the caller already entered.

Retrying the card step during signup could quietly create a second subscription that billed separately at the end of the trial. Retries now reuse your existing subscription, strays are canceled automatically, and a daily check cleans up anything that slips through. A failed renewal charge that fell back to your backup card also retried it repeatedly in quick succession; it now tries the backup card once. Affected accounts were reviewed and corrected.

You can now log out from any step of the trial setup wizard, and the card step shows a cleaner order summary.

Publisher applications no longer ask for the platform-wide "consumer-initiated inbound calls only" confirmation. Networks now run offers with other call sources such as warm transfers, so each network sets its own source rules on the offer instead.

Some bot crawlers fake a search engine referrer so their visits look like organic traffic. These bursts are now detected and excluded from visitor analytics automatically, so your traffic reports reflect real people.