voice

Calls Directed To Me

Live calls a colleague is transferring to ME, and to nobody else.

⛔THIS REPLACES A BROADCAST. Frederick, 2026-09-19: "No, we don't take live calls. So there's no reason for a call to be broadcasted. All calls are callback tickets. However, the only time that bar should show up is on your page when someone's trying to transfer you a call... outside of that, it should not be shown to everyone because we don't answer live calls."

The desk strip used to read GET /calls?status=ringing -- inbound and not yet 'in-progress' -- and draw it for all seventeen holders of cs:voice. That was never a queue of people waiting: ON_HOLD_STATUS IS the string 'ringing', the state every answered inbound call starts in while Rooster is still connecting, so the strip alarmed on every single caller.

⛔GATED ON BEING THE TARGET, NOT ON HOLDING cs:voice. The grant is still required -- this is a phone screen -- but it decides whether the person may ask the question at all, never whose calls come back. The answer is always and only this principal's own, because the row names them; there is no parameter here that could widen it.

⛔AND ONLY THE ONES STILL NEEDING SOMEBODY TO PRESS ANSWER. A transfer delivered to a colleague's own American cell phone carries transfer_number and needs no button -- their phone is simply ringing (handoff.transfer_call_to). The browser branch leaves that column NULL, which is what the desk reads to decide whether to draw anything.

get/api/voice/calls/directed-to-me

Request

  • Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.pigeonly.com/api/voice/calls/directed-to-me
  • Auth: none declared

Query parameters

limitinteger

Response

Successful Response

object[] required

Changes

No recorded changes to this operation across all 1 revision of this API.