Submit Your Inquiry
Share contact information and explain the subject in language that makes sense to you. A short, accurate description is more useful than technical terminology chosen only because it sounds advanced.
Let's Start a Conversation About Your Connectivity Needs.
Whether you are considering an internet connection for a home, planning connectivity for a workplace, or comparing requirements across an enterprise network, begin with the location and the work that connection needs to support. This page helps you frame a useful inquiry without assuming that a particular service is available at your address.
Different questions call for different context. Choose the closest category to preselect it in the form, or simply scroll down and choose from the full list. A category helps describe your question; it does not determine eligibility or commit you to a particular product.
Ask a general question about ZTN, this website, or where to begin exploring connectivity information.
Start an inquiry →Describe a location and ask about fiber connectivity, building considerations, or technical availability.
Ask about fiber →Discuss an office, retail site, shared workplace, or another business connectivity requirement.
Discuss business needs →Outline dedicated access, multiple locations, private networking needs, or a more complex architecture.
Explore enterprise needs →This inquiry page is organized around the information you can share: who you are, where service would be needed, the kind of connection you are considering, and the outcome you hope to achieve. It does not publish an email address, phone number, office address, or business hours because those details have not been verified for this page. Do not rely on contact information supplied by an unrelated directory as though it were confirmed here.
For general questions, identify the page or topic you are asking about. For business inquiries, describe the workplace and its important applications. For technical questions, explain the symptom without revealing credentials. If an official business email, general-inquiries channel, business-inquiries channel, technical-support channel, business location, phone number, or business hours are later verified, those details can be added here by the site owner.
An inquiry about a particular site is easier to understand when it identifies the city, locality, and intended service location. An inquiry about capacity benefits from approximate numbers of users and devices, important applications, and any upload-heavy work. A request involving multiple branches benefits from a site list and an outline of how those sites need to communicate.
Only share information needed for the discussion. Do not include passwords, one-time codes, payment card information, or confidential network diagrams in a general inquiry. You can explore service categories first and then return with a more focused question.
Compare service categories →Use the form to explain your requirements in your own words. Required fields establish a basic point of contact and identify the location or subject of the question. Optional fields can add context, but there is no need to estimate technical specifications you do not yet know.
Submission information: In this Canva Code page, a confirmed submission is saved to a write-only Canva Sheet. It is not an email, a support ticket, an appointment, or a promise of a reply. If this HTML is exported to an independent website, the owner must connect the submission function to a real, privacy-appropriate endpoint before accepting inquiries there. An exported copy without that connection will not claim to have sent anything.
For an availability question, give the intended service location rather than only a billing address. For a business or enterprise question, explain the applications that matter most and whether one or several sites are involved. For a technical issue, give observable symptoms and the steps already taken, but never send account secrets.
Provide only information relevant to your inquiry. Never enter passwords, Wi-Fi keys, one-time passcodes, payment card details, or unnecessary sensitive personal information. Read the Privacy Policy before submitting. Consent below confirms that you have read it; this page does not make claims beyond the published policy about retention, processing, or security arrangements.
Fields marked * are required. Your entries remain in place if a field needs correction.
Fiber is a useful topic to explore when your priorities include consistent access for everyday work, communication, entertainment, or shared use. Begin with the actual service location. The city alone is rarely precise enough to establish whether infrastructure reaches a particular building; adjacent streets, individual premises, and installation routes can differ.
Describe whether the location is a house, apartment, mixed-use building, office, or another type of property. Note whether you are asking for residential or commercial use, approximately how many people will use the connection at once, and what they will do online. Several simultaneous video meetings, large cloud backups, streaming devices, and remote access can raise different questions from casual browsing.
If you know your current connectivity arrangement, explain what works and what does not. Useful installation context may include shared building access, landlord or building-management requirements, equipment placement, or known limitations in internal cabling. These details are prompts for discussion, not a checklist that proves an installation is possible. Availability depends on the specific service location and technical feasibility; a general description of fiber does not confirm that any address can be connected.
Explore Fiber Internet →You do not need to know the construction method in advance. Explain what you know and clearly distinguish an estimate from a confirmed fact.
A business internet inquiry is most productive when it describes what happens during a normal working day and what changes when the workplace is busiest. A ten-person office using cloud documents and video meetings has a different traffic profile from a venue with guest devices, point-of-sale systems, and frequent media uploads. Rather than requesting a speed in isolation, describe the work that the connection needs to sustain.
Include the business or organization name, office location, approximate employee count, and a realistic estimate of connected devices. Devices can include computers, phones, printers, meeting-room systems, Wi-Fi access points, security equipment, and other networked tools. Identify applications that are central to operations: cloud software, voice and video communication, remote desktop access, large file transfers, or hosted services. Where possible, distinguish ordinary use from peak periods.
Upload and download requirements are both worth discussing. A workplace that sends design files, maintains cloud backups, or hosts video meetings may care about upstream capacity as much as downloads. Summarize the current network setup, including whether the business has one site, a guest network, existing routing equipment, or an internal IT team. Mention any special technical considerations without placing confidential credentials in the form. Accurate requirements support a clearer discussion about suitable categories; they are not a substitute for checking availability, proposed specifications, and applicable terms.
Explore Business Internet →If your organization has several locations, identify which questions concern a single office and which concern connections between sites.
Organizations exploring dedicated internet often have a particular operational reason for doing so. That might be a need to discuss predictable capacity, substantial simultaneous traffic, public-facing systems, or business-critical applications. Start by explaining that reason rather than assuming that the word “dedicated” describes a single standard configuration. Access arrangements, speeds, address options, monitoring, and contractual commitments need to be discussed and verified individually.
Share the bandwidth you believe you may need, but identify whether it is a measured requirement, a planning estimate, or a target for future growth. Explain upload and download patterns separately. Identify critical applications, expected utilization at busy times, and whether static IP addressing is relevant to your architecture. If you are considering a secondary connection, describe the failure scenario you hope redundancy will address. Two connections do not automatically provide meaningful diversity if their underlying routes share the same dependency.
Include the precise service location and any known installation constraints. If service-level commitments matter, describe the outcomes and measurements you need to evaluate rather than assuming that an SLA, repair window, or guarantee is included. Feasibility and terms require location-specific and technical review. This page does not promise a particular feature, bandwidth, route, installation method, or service level.
Explore Dedicated Internet →An enterprise conversation is more useful when it begins with a map of business relationships rather than only a list of internet speeds. Explain how many locations are involved, which site is the head office, which sites are branches, and whether staff, applications, or data must move between them. Cities and general locations can establish initial scope; precise addresses may be needed later for location-specific assessment. Avoid placing confidential building-access information in an initial message.
Outline where your cloud infrastructure lives and which sites depend on it. If private networking is being considered, describe the communication requirement: for example, whether branches need to reach centrally managed applications, whether each site needs independent internet access, or whether teams use a cloud-first approach. Include security considerations in terms of objectives and governance, not passwords, secret network configurations, or sensitive diagrams. Mention any existing network architecture so a discussion can account for equipment, routing, and operational responsibilities already in place.
Redundancy and failover should be described as outcomes. Which site must remain connected if one path fails? Which applications can tolerate interruption, and which cannot? Are there planned new sites, changes in staffing, or capacity increases? Complex requirements may require a technical assessment at each location and a careful review of interdependencies. A request for enterprise connectivity is an invitation to investigate options, not confirmation that a particular architecture or feature is available.
Explore Enterprise Solutions →Keep the initial inquiry high-level; exchange sensitive technical material only through an appropriately verified process.
Coverage is a property of a particular service location and an applicable technical arrangement, not simply of a city name. A locality can help orient a discussion, but it cannot by itself establish whether a connection can be installed in a specific building. For the most useful inquiry, identify the city, locality, postal code if applicable, and intended service address. If you are not ready to share a complete address, provide the area you are comfortable sharing and understand that any guidance may remain preliminary.
Building type matters. A detached house, apartment complex, office tower, industrial property, and shared commercial building can present different access and permission considerations. Name the service category you want to investigate, whether that is fiber, business connectivity, dedicated access, or a more complex enterprise requirement. Mention known conditions such as a shared building entrance, site access restrictions, construction constraints, or an upcoming move. Do not assume that an existing connection elsewhere in the neighborhood proves feasibility at your site.
A general location inquiry is not confirmed coverage, installation approval, or a quotation. A meaningful conclusion may depend on address checks, infrastructure information, permissions, technical feasibility, and the specific service under discussion. Use the coverage page for broader context, then ask a location-specific question when you have enough detail to do so.
Check Coverage Areas →Keep preliminary guidance separate from a verified address-level result.
When describing a technical problem, start with what you observe. Is the connection completely unavailable, slower than expected, intermittent, or limited to a particular application? Note when the issue began and whether anything changed around that time. Distinguish one affected device from multiple affected devices; that difference can help separate a local device issue from a wider network symptom. Avoid stating a cause as fact if you have not confirmed it.
If available, include the connection type, router or optical network terminal (ONT) model, and relevant indicator-light behavior. Report the exact wording of an error message without including account secrets. Speed-test results can be useful when accompanied by context: whether the device was connected by cable or Wi-Fi, the approximate time of the test, and whether other devices were active. A single measurement does not by itself diagnose a service fault.
Describe troubleshooting steps already taken, such as checking a cable, testing another device, or observing whether the issue recurs. Follow any applicable equipment or organizational instructions before restarting managed equipment. The support page offers general resources; this contact category should not be interpreted as a verified emergency channel or a promise of a particular response time. Never share passwords, Wi-Fi keys, OTPs, or sensitive account credentials in an inquiry form.
Technical Support →Never submit passwords, Wi-Fi keys, OTPs, or sensitive account credentials.
Professional inquiries can cover a broad range of subjects, so begin by identifying the nature of the proposed conversation. A technology partnership question might concern compatibility, an integration idea, or a possible area for technical exploration. A network-related business collaboration may involve an infrastructure discussion, a shared project concept, or a question about organizational requirements. A business-development inquiry might instead focus on a market opportunity or an introduction between teams.
State your organization, your role, the broad objective, and why you believe the subject is relevant to ZTN. Include a concise description of the requested next discussion and any non-confidential context needed to understand it. If the topic involves enterprise connectivity for your own organization, the enterprise category may be more appropriate than partnership. If it is a general corporate question, select General Inquiry or Partnership Inquiry according to the subject.
Do not send proprietary proposals, confidential contracts, access credentials, or sensitive technical diagrams through an initial inquiry. Nothing on this page confirms an existing partner relationship, a commercial arrangement, or acceptance of an unsolicited proposal. The purpose of the inquiry is to establish the topic clearly enough for a potential conversation.
Send a Partnership Inquiry →Choose “Partnership Inquiry” in the form and explain the purpose of the proposed discussion in plain language.
The following five steps describe a general illustrative communication journey, not a verified ZTN operational process. They do not promise a response, response time, technical assessment, installation, or service activation. On this page, a confirmed form submission means the inquiry was saved; any subsequent handling depends on actual arrangements outside this illustration.
Share contact information and explain the subject in language that makes sense to you. A short, accurate description is more useful than technical terminology chosen only because it sounds advanced.
Include the service location and technical context where applicable. Identify what you know, what you are estimating, and what you would like to clarify.
In a general inquiry workflow, information can be reviewed to understand the nature of a request. This illustration does not establish who reviews ZTN inquiries or when review occurs.
A possible conversation could explore suitable service categories, location questions, and technical considerations. No particular option should be assumed to be available without verification.
Where an actual conversation takes place, the parties could discuss applicable availability, service details, and further requirements. The appropriate next step depends on the specific circumstances.
Relevant details help distinguish a broad interest from a location-specific requirement. They can make coverage questions more precise, reveal technical considerations earlier, and reduce confusion about what a service description does or does not establish. “Complete” does not mean sharing every piece of personal or confidential information: it means providing enough accurate context to understand your question.
“I am considering connectivity for an apartment in a particular locality. Two people work from home and often join video meetings while other devices are online. I would like to understand what service categories may be relevant and what information is needed to investigate availability.” This is more useful than asking whether fiber is available throughout an entire city. It identifies the premises type, the likely usage pattern, and the question, while leaving address-level confirmation open.
“Our office has around 25 employees. We use cloud accounting, shared documents, conferencing, and regular uploads. We are planning a move and want to discuss business connectivity at the new site.” This gives a meaningful starting point for capacity and location discussion. The business can later add measured utilization, device counts, and any internal network requirements rather than guessing at a final specification.
“We have a head office and four branches in several cities. Each branch uses cloud applications and needs access to a centrally managed system. We would like to discuss possible connectivity approaches and how to evaluate resilience.” This describes relationships between sites and critical objectives without publishing sensitive topology. The precise feasibility of any architecture remains a separate technical question.
A useful inquiry also identifies uncertainty. If you do not know your current connection type, say so. If an address is still being selected, explain that availability can only be discussed provisionally. If the employee count is likely to change, provide a range. Distinguishing facts from assumptions makes a later discussion more productive than presenting uncertain numbers as guarantees.
These answers explain how to frame an inquiry using the information available on this page. They do not establish unpublished ZTN contact channels, operating procedures, support commitments, or response times.
Use the inquiry form on this page to share the topic and the information needed to understand it. In this Canva Code version, a confirmed submission is saved to a write-only Canva Sheet; it is not an email or a support ticket. No unverified phone number, email address, or office location is published here. If you are viewing an independently exported version, its owner must connect an actual submission endpoint before it can accept inquiries.
Begin with the services overview if you want to compare categories. Then choose the most relevant inquiry type and explain where the connection would be used, approximately how many people or devices will use it, and which applications matter most. If you are unsure of the category, select General Inquiry and describe your situation without guessing at a technical product name.
Select Fiber Internet and identify the city, locality, building type, and intended service location. Explain whether the use is residential or commercial and what activities the connection should support. Include any known building-access considerations. A fiber inquiry invites a location-specific discussion; it does not establish that infrastructure reaches your premises or that installation has been approved.
Select Business Internet and provide the organization name if appropriate, the workplace location, approximate staff and device counts, and important business applications. Describe cloud tools, video meetings, uploads, or other workflows that affect requirements. A clear account of current difficulties or planned growth can help frame the question more effectively than a requested download figure alone.
Select Enterprise Solutions and outline the number of sites, their broad locations, the role of the head office, and how branches need to communicate. Mention cloud dependencies, security objectives, resilience expectations, existing architecture, and expansion plans at a non-confidential level. Complex arrangements may require technical and location-specific assessment before any possible configuration can be discussed meaningfully.
Include your name, a usable email address, the relevant country and city, the intended service area, a subject, and a clear description of the question. Add details specific to the category: building type for coverage, applications for a workplace, or observable symptoms for support. Mark estimates as estimates. Do not include passwords, payment details, identification numbers, or unrelated sensitive information.
No. The phone field is optional. An email address is required so the inquiry has a basic contact reference, but entering one does not establish that ZTN will reply within a particular period. Check that the address you enter is accurate before submitting, and avoid including a number unless it is relevant and you are comfortable providing it.
Yes. Choose Coverage and Availability and identify the city, locality, postal code where applicable, building type, desired service category, and intended location. A more precise location can support a more precise question, although you should share only information relevant to the inquiry. The coverage page provides broader context; it does not replace an address-level assessment.
No. A form submission records the information you provided; it does not check infrastructure, approve installation, establish eligibility, or reserve capacity. Availability can depend on the precise premises, technical conditions, permissions, and the service category under consideration. Treat any general location guidance as preliminary until relevant facts are verified.
Yes. Select Dedicated Internet and describe the intended site, capacity requirements, upstream and downstream usage, critical applications, and any static IP or redundancy objectives. State whether bandwidth figures are measured or estimated. Discuss SLA considerations as requirements to evaluate, not features assumed to be included. The dedicated internet page offers additional background.
Select Partnership Inquiry and introduce your organization, your role, and the broad subject of the proposed conversation. Technology collaboration, network-related business discussions, infrastructure topics, and general corporate communication can all be described without assuming an existing relationship. Avoid sending confidential proposals or sensitive documentation in an initial message.
Explain the connection type if known, the symptom, when it began, and whether it affects one device or several. A router or ONT model, visible indicator-light state, contextual speed-test result, and non-sensitive error wording may help. Explain steps already tried. Do not include passwords, Wi-Fi keys, one-time codes, or account credentials. Visit support resources for general guidance.
A complete intended service address may be useful for a location-specific availability discussion, because a city or neighborhood alone cannot confirm a building-level result. If you prefer to begin with a broader area, make clear that you are seeking preliminary guidance. Do not add unrelated personal details, building-access codes, or information that is unnecessary to frame the question.
Read the published Privacy Policy for the site's stated privacy information before submitting. This contact page does not independently promise a retention period, processing arrangement, or security certification. In this Canva Code version, confirmed form entries are saved to a write-only Canva Sheet and are not displayed to other visitors through this page. Supply only information relevant to your request.
The form allows separate submissions for different subjects. If questions concern unrelated locations or service categories, separate, clearly titled inquiries may make their context easier to distinguish. Before sending another message about the same issue, consider whether you are adding genuinely new information. This page does not describe any verified ZTN case-management or duplicate-handling procedure.
On this Canva Code page, the form confirms only whether an entry was saved successfully. The five-step journey above is an illustration of how a connectivity conversation might develop, not a statement of ZTN's internal workflow. No automated technical review, callback, appointment, or service activation should be inferred from a submission confirmation.
No response-time guarantee is stated on this page. Do not interpret the form, an illustrative journey, or a service description as a commitment to reply within a particular number of hours or days. If a contractual response commitment matters to your organization, it should be discussed and verified through applicable service documentation rather than assumed from website copy.
Yes, you can describe a multi-location requirement under Enterprise Solutions. State how many locations are involved, the cities, the function of each site, and the applications or systems that need to connect. Describe desired continuity and growth at a high level. An inquiry does not establish feasibility at every site or confirm that a particular private-network architecture is offered.
Start with the Technical Support page for general information and practical troubleshooting context. The FAQs may also help explain common connectivity terms. Neither resource should be mistaken for a verified emergency channel, a diagnosis of your particular equipment, or a statement of support hours. Follow your equipment documentation and applicable organizational procedures where relevant.
Use the services overview to navigate the categories. The fiber, business, dedicated, and enterprise pages provide more focused context, while coverage and network-infrastructure pages explain other aspects of connectivity. Read those pages as general information, then frame an inquiry around your actual location and requirements rather than assuming that a described capability applies automatically to your site.
Whether you are exploring internet connectivity for a home, business, or enterprise environment, share your requirements with ZTN and explore the available options. Describe the location and use case clearly, and keep unverified assumptions separate from confirmed facts.