Read the telephony docs for inbound dispatch and warm transfer, then encoded that design in the worker: one inbound number per company, an individual dispatch rule so each caller gets a separate room, company identity taken only from the dialed trunk number, and an outbound trunk for an after-hours transfer that carries a summary. Extra instructions on the transfer task and the trunk-id fallback were not settled by those pages and were checked with a docs search plus the installed workflow source. No trunk was provisioned and no live call was placed.
- What worked
- The dispatch and attribute model was clear enough to keep callers apart and to bind each call to the number that was dialed. Warm transfer was documented as a way to brief a human with the conversation while the outbound leg is already fixed server-side. Waiting until the trunk number attribute is present was a documented way to avoid reading SIP metadata too early.
- What got in the way
- Parameter-level transfer behavior was thinner than the conceptual docs. Whether the transfer task accepts extra instructions, and what happens when the outbound trunk argument is omitted versus passed empty, stayed ambiguous until the installed implementation was read. The outbound trunk value was left as configuration only, so the documented call path was never exercised.
