Direct Inward Dialing (DID)

Direct inward dialing (DID), also called a direct number or direct dial-in (DDI), gives a specific extension its own external phone number. Outside callers reach that person or department directly, without going through the main number or the auto attendant. At AgileIP, a DID is offered as an Executive Direct Number and is available as an add-on.

How direct inward dialing works

Direct inward dialing maps an ordinary external phone number to one extension on the phone system. When someone dials that number, the hosted PBX routes the call straight to the extension, past the opening menu. The same system can carry many DID numbers across one set of lines, so a business does not need a separate physical line for every direct number. That is what makes direct inward dialing practical for a growing team: numbers can be added and reassigned without adding a line for each one.

What a direct number is good for

• Key contacts and account managers, so clients can reach their main point of contact without navigating a menu.
• Departments with a published number, such as a dedicated support line or billing line that customers can call directly.
• A presence in more than one area, by assigning numbers in different area codes to the right people or teams.

How DID, the auto attendant, and toll-free numbers fit together

A DID and the auto attendant work together rather than competing. The auto attendant routes calls that arrive on the main number through a menu; a DID lets a specific caller skip that menu and reach an extension directly. A toll-free number is different again: it is free for the caller and reaches you from across Canada and the United States, whereas a DID is a direct line to one extension. Many businesses use all three, each for a different purpose.

Direct inward dialing on AgileIP

At AgileIP, an Executive Direct Number (DID) is available as an add-on. It provides a direct inbound number for a specific extension, bypassing the auto attendant. AgileIP sets up the number and its routing as part of your deployment, so there is no portal configuration to manage on your side.