Skip to content
ZVONEXGLOBAL VOIP SOLUTIONS
Get connected
ZVONEX · Business voice

Prepare your enquiry for ZVONEX

A clear brief makes a destination and connection discussion more useful. Gather the business goal, current system and expected load without sharing passwords, customer databases or unnecessary personal information.

Sales-pilot illustration with a laptop, communications module and emerald path through sequential checkpoints
Original ZVONEX illustration: Project example: Kazakhstan calling for a sales team. Conceptual artwork, not a photograph of actual infrastructure.

Describe the intended outcome

Start with one paragraph explaining who will call whom and why. For example, a sales team may want to reach customers in Kazakhstan from an existing PBX. This is a statement of intent, not an approved configuration, and it gives the discussion a concrete starting point.

Explain whether you want to add a destination, connect teams, move an existing arrangement or assess a specific scenario. If you are still comparing options, say so. You do not need to choose every technical term before asking a useful question.

List destinations and approximate demand

List each country and distinguish inbound from outbound requirements. Add typical call duration, working hours and peak concurrent calls where known. If precise figures are unavailable, give a range and identify it as an estimate rather than presenting invented precision.

Team size and simultaneous calling load are not interchangeable. Twenty employees do not necessarily make twenty calls at once. A description of normal operation and busy periods is often a better starting point than a single unsupported capacity figure.

Explain systems and constraints

Mention the PBX, softphone, CRM or other platform currently involved, including its name and version if available. Identify behaviours that must remain unchanged: existing numbers, queue arrangements, team responsibilities or service hours. These constraints help define the assessment.

If a contractor manages the setup, describe their role and whether a technical contact is available. Avoid sharing another person’s details unnecessarily. Plain-language constraints are acceptable; server credentials and SIP passwords are not required in an initial brief.

Set useful checks and a contact route

Explain what a satisfactory result would look like: the destinations and scenarios to check, the people involved and a convenient discussion window. Distinguish a preferred launch date from an actual deadline and explain any dependency that makes timing important.

Use the current contact options on the website. Keep a copy of your outline and update it when requirements change. Do not send real call recordings, customer documents or secret configuration data without first agreeing why they are needed and how to transfer them.

Before you send an enquiry

Does a country guide guarantee live availability?

No. Confirm destination availability, service parameters and any restrictions for your particular requirement before launch.

Do I need to share passwords?

No. Start with a description of your system. Agree any necessary access separately using a secure method.

Where can I ask about another destination?

Use the website contact page and list the countries and call scenarios you need.

Next steps

Discuss the project

No technical specification yet? Start with the business goal and destination list; the remaining questions can be clarified together.

Contact ZVONEX
Message us on Telegram