Quick question about the BYOC trunk integration. 403 Forbidden errors are hitting the registration endpoint whenever we push the Chicago team’s updated schedule. The WFM API returns 200 OK, but the telephony layer rejects the config update immediately after publication. Any ideas on the timing mismatch?
If I remember correctly, this usually stems from a permissions gap in the BYOC configuration rather than a timing issue. The WFM publish succeeds, but the telephony service lacks the specific scope to apply the schedule change to the trunk. Verify the following:
- BYOC admin role assignments
- Trunk status in Telephony settings
- API scope for schedule updates
Have you tried explicitly verifying the OAuth token scopes attached to the service account used for the trunk update?
"permissions": ["telephony:trunk:write", "wfm:schedule:publish"]
The 403 often indicates a missing scope rather than a timing issue.