Discovering constraints before a telephony migration

An aging telephony replacement often begins with a request for certainty about downtime. An account executive should resist answering with a cutover promise. The more valuable move is to find the support lines, integrations, and change windows that make a migration safe enough to evaluate.

Ask the technology manager to draw the current call path in plain language. Find out which lines handle urgent escalations, which carrier or application sits outside the main environment, and when the customer enters a change freeze. Then ask who validates compatibility. This creates a fact base for the technical team instead of treating every connection as already known.

Jordan told Lena, “Our leadership wants assurance that critical support will stay available.” Lena said, “I cannot confirm a migration plan before the architecture is reviewed. Which lines must receive special attention during a change?” Jordan explained that emergency escalations use a separate carrier and that a freeze begins next month. Lena answered, “Let us schedule a workshop with the carrier contact, your architecture lead, and operations. We can map those dependencies and agree what evidence the team needs before choosing a timing path.”

Prepare for the workshop by listing every system named by the customer and placing an owner beside each one. Include the change freeze date and the definition of a successful validation. In roleplay, practice the sentence that acknowledges urgency while moving toward evidence. A call review should confirm that the executive asked about the architecture before discussing a date.