


The hardest part of the job was that every change to pacing or abandoned-call accounting affects compliance, and a wrong fix could push a campaign over the 3% limit. So we first reconciled production data against call logs without touching the live system and kept a register of the issues we found.
The audit found the core of the platform sound, including the model that sizes extra lines and the way agents are reserved for calls, so the dialer needed better measurement and control around them, not a rewrite. Pacing changes were then checked in the load simulator, and releases got a staging copy with a guarded rollback.


The rule starts the two-second clock when the person finishes their greeting, a few seconds before answering machine detection decides that the caller is a person. So the dialer counts from the greeting, as the rule defines, and not from the detection decision.
The pacer sets lines per agent from the campaign's answer rate, so a campaign with few completed calls had no estimate of its own and stayed on its starting lines.


A person who answers a call should never hear silence, so the dialer must not place a call for an agent who cannot take it. Readiness now rests on a live connection, not on a presence flag.
We built the first version of a controller that sets lines per agent from agent occupancy (the share of time agents spend on calls) and aims at a set occupancy level.


Changes can now be tested without calling real people, because we extended the platform's load simulator. It runs the real dialing engine with simulated telephony, answering machine detection and agent browsers.
The team can rehearse releases and rollbacks away from production: our scripts define a reduced two-host copy of the production deployment that places no real calls.


The browser phone re-registers with the telephony server from time to time, and manual calls now ride out these short gaps the same way auto-dial does, with a short, limited set of retries.
DialRush runs about ten services in Node.js and Python. Agents call from the browser over WebRTC, and supervisors can listen to calls in their team, whisper to the agent (speak so that only the agent hears) or barge in. Calls go out through several carriers, with routing per destination and automatic failover. Answering machine detection combines speech recognition with a text classifier. Before every dial, the platform checks internal DNC (do-not-call) lists, a litigator scrub, state calling hours and attempt limits.

The stack below is the platform's. Our changes touched the dialing engine and pacer, the answering machine detection service, agent presence, monitoring metrics and alarms, the load simulator, and the release tooling.
Under the FCC rule, a call is abandoned when a person answers and no agent joins within two seconds of the person's completed greeting, and a campaign may abandon no more than 3% of live answers over 30 days. A dialer that starts the clock at answering machine detection, a few seconds later, undercounts. In DialRush, the clock starts when the greeting ends.
Because pacing depends on the answer-rate estimate, and a campaign with few completed calls may not have one. In DialRush, a blended estimate gives every campaign a value from its first calls, using the organization's recent data while the campaign's own data is thin.
In small, reversible steps. The occupancy controller ships switched off and is enabled per campaign, and it holds its target or falls back to the starting lines if a value it needs cannot be read. Releases are rehearsed on a staging copy, and the rollback script refuses to run if a server's state has changed.
Fora Soft handed the work over after four weeks. The client deploys the alarm stack on its own and enables the occupancy controller campaign by campaign, and the load runs gave the next round of scaling work a measured starting point. The project combined telephony, real-time pacing logic, compliance metrics and load testing on a live system built by another team. We take on the same kind of work for other live call center and VoIP platforms.
