CONTACT MICIS
Use the form for a new technology review, service discussion, project, integration or site requirement. Existing clients should use Client Support for active support requests so each issue is recorded and sent to the right team.
New service or technology review Outcome, people, systems, risks and ownership
Enquire → 02Project, move or fitout Site, target date, providers, work packages and handover
Plan → 03Integration, automation or AI Process, data, interfaces, controls and human review
Discover → 04Existing client support Active requests, non-urgent website chat and urgent calls
Support →CHOOSE THE RIGHT ROUTE
Choose the path closest to the immediate need. The first conversation can then identify the connected systems, providers, constraints and owners that also matter.
Use this route for recurring support or a defined service layer across IT, Microsoft 365, connectivity, phones, web or electronic security.
Use this route for a new site, relocation, refurbishment, migration, technology refresh or coordinated cutover.
Use this route when work is repeated by hand or a useful outcome depends on information moving between systems.
Use Client Support for active incidents, service requests and changes so the request remains visible and routed correctly. For non-urgent assistance, use the website chat button at the bottom-right.
NEW ENQUIRY
You do not need a complete scope. Describe what is happening, the useful outcome, affected people or sites, any target date and the providers already involved.
Outcome and impactWhat must keep working, improve or be ready by a target date.
Current systems and providersPlatforms, sites, carriers, vendors and internal owners already involved.
Known timing and constraintsDates, access, licences, budgets, operating windows and non-negotiables.
Who can decide and provide accessThe people who can confirm scope, evidence, priorities and acceptance.
WHAT HAPPENS NEXT
The route changes with the request, but the operating discipline remains the same: understand the impact, map the boundaries and make the next owner visible.
Identify the affected people, site, service, process or target date.
Confirm systems, providers, existing ownership, constraints and unknowns.
Choose the next review, discovery, survey, assessment or planning activity.
Make the decision owner, required evidence and following step visible.
CONTACT CHANNELS
New discussions, active support requests, procurement and office visits have different operating paths. Starting in the right place keeps context and ownership visible.
Use the technology enquiry form or call to discuss a new service, project, review or solution opportunity.
Open the enquiry form →Use Client Support for active incidents and service requests. For non-urgent assistance, the website chat button at the bottom-right is also available. Call where the service impact is urgent. After-hours or on-call arrangements remain agreement-specific.
View Client Support →Use the Procurement Portal for product discovery, quoting, ordering and order history under your existing account.
Open Procurement Portal ↗Suite 5, 23 Brookhollow Ave, Norwest NSW 2153. Meetings and site reviews should be arranged in advance.
View the location ↗FREQUENTLY ASKED QUESTIONS
A useful first contact should make the outcome, current context, boundaries and next decision easier to understand.
Describe the outcome or issue, the affected people or sites, current systems and providers, known timing or constraints, and the person who can confirm priorities. You do not need to prepare a complete technical scope before contacting MiCiS.
Active incidents, service requests and changes should normally use the agreed Client Support path so the request is recorded, prioritised and linked to the correct service context. The contact form is better suited to new discussions and enquiries.
Yes. Start with the operating impact or desired outcome. MiCiS can identify the most useful starting service or solution and then map the connected systems, providers and responsibilities that may also be involved.
No. A general enquiry should not contain credentials, recovery codes, private keys or unnecessary personal, contractual or security-sensitive information. MiCiS can agree an appropriate transfer method later if protected information is required.
The enquiry is reviewed and routed according to its outcome and likely service path. Further information may be needed before MiCiS can recommend a review, discovery activity, site survey, assessment, project stage or service scope.
Yes. MiCiS can work within co-managed and multi-provider environments. The relevant service, access, escalation and decision boundaries are documented so the next action does not depend on assumptions.
Existing clients should use their agreed support and escalation path and call where service impact is urgent. Support windows, priority definitions, after-hours assistance and on-call engineering depend on the applicable agreement; the general contact form does not establish those arrangements.
Call MiCiS with the outcome, affected users or sites and any target date. We will help identify a useful first route without asking you to choose the final solution in advance.
