Overview
A business using Teams Phone can evaluate external-number forwarding as a way to send calls to an answering service. First identify the number and routing object involved, confirm that the tenant permits the intended destination, and agree on how the answering service will handle forwarded calls. Forwarding a voice call does not by itself connect calendars, messages, or customer records.
Start with the number that callers actually use
Write down the public number and ask the Teams administrator what receives it. This guide addresses user call-forwarding settings; do not assume that changing an individual user also changes a main line managed through a queue or auto attendant. Map that path before choosing which setting to edit.
Ask the answering-service provider for the intended destination number and confirm that its team recognizes your account on that route. Do not substitute a public sales number. Record the current route so the administrator can restore it if the test fails.
Confirm the Microsoft prerequisites
Microsoft’s administrator documentation requires a Teams Phone license for the user settings described and limits the feature to Teams Only deployment mode. It also describes calling-policy controls for forwarding and simultaneous ringing to external numbers. Have the administrator verify the applicable policy and telephone connectivity before changing the route.
The current Microsoft source is linked below. A missing setting should prompt a configuration check, not an assumption that an external answering service cannot be used. This guide does not establish compatibility with a particular AnSer account or carrier arrangement.
Choose the intended forwarding behavior
In Microsoft’s documented administrator flow, open the licensed user under Users > Manage users, then the Voice tab. Immediate forwarding and unanswered-call handling are separate choices; the unanswered settings include a waiting interval. Have the administrator select the behavior your approved coverage plan requires.
Decide whether staff should have an opportunity to answer first or whether calls should go directly to the service. Record that decision before selecting a timeout. If coverage is meant to change by schedule, confirm the supported scheduling approach for the actual routing object instead of assuming an individual forwarding setting creates an after-hours schedule.
Test from an outside phone
- Call the public number from an external phone and verify the expected greeting and receiving account.
- For unanswered forwarding, let the original destination ring without answering and observe the complete path. Record elapsed time and whether another voicemail system intercepts the call.
- Confirm what caller information the answering team receives and verify that the callback number in the resulting message is usable.
- If the answering team transfers callers back, test that destination too. It should not send the call back into the same forwarding path indefinitely.
- Restore the original route during a controlled test and verify that the rollback works before relying on it.
Resolve failures with the responsible administrator
Microsoft provides a Teams Call Forwarding diagnostic in the Microsoft 365 admin center. Its documented inputs include the affected user and the forwarding destination in E.164 format. That diagnostic can help inspect configuration; it does not replace an end-to-end test call.
Give the administrator the test time, dialed number, expected route, and observed result. Share only the information needed to diagnose the call. Separately verify the answering-service script and message destination: a successful transfer into the service is not evidence that the subsequent business handoff is correct.
