Callbacks and number pools
A number pool is a set of your workspace’s phone numbers that rep calls go out from. It decides two things: which number a call shows to the prospect, and what happens when the prospect calls that number back.
How a number is picked
Unless a call names its own from, Rydhm picks one from the pool:
Each number makes at most dailyCapPerNumber calls a day (default 80, 1 to 1,000, counted in UTC). A number at its cap is skipped; when every number is, the call is refused with 429 pool_exhausted (add numbers, or raise the cap). Spreading calls keeps each number’s reputation healthy, so carriers are less likely to label it spam.
Where callbacks ring
When someone calls a pool number back, the pool’s callback routing rings, in order:
Each step rings for ringSeconds (5 to 60, default 20) before the next. The default order is rep_browser, rep_mobile, voicemail. When the rep declines in the browser, routing moves on at once. At the expert step the call becomes that expert’s AI call from then on.
Callers no rep has called (a new lead calling in, someone calling from another phone) follow the pool’s unmatched setting:
The rep sees the callback as incoming in the softphone; your server sees call.incoming on the rep’s event stream, and as a webhook. Its externalRef is the call they’re calling back about, when Rydhm knows it.
Set it up
TypeScript
Python
Numbers themselves are bought or imported as usual: see Phone, Bring your own Twilio and Bring your own Telnyx.
Pools themselves can be managed with a key (calls:write, from a key that isn’t limited to some experts). Moving a number into a pool and setting its inboundMode stay in the app (Sales calls → Numbers) or a signed-in admin session, like every phone-number route: an API key gets 403 not_available_to_api_keys from PATCH /v1/phone-numbers/{id}.