Telephony data into the CRM without tripping the rate limit

The Challenge

Several jobs needed the same telephony data — analytics, backfills, reports. Each one calling the API directly meant the limit could be exhausted by whichever job happened to run first, and the block lands on the address, not the script.

The Solution

• A single API client that every job imports, with request pacing built into it rather than repeated in each caller
• A documented rule against direct calls, so a new script cannot quietly reintroduce the problem
• Call duration normalised on the way in — the platform reports milliseconds, which is a reliable source of silent arithmetic errors

The Result

Telephony data flows into the CRM as a dependable input to reporting, and the rate limit is one component's concern instead of a hazard spread across every script that needs a call log.