Numbers, carriers and porting
Number inventory, service and billing records, PSTN and SIP services, new orders, diversions and porting coordination.
BUSINESS PHONE SYSTEMS
Business calling designed around your numbers, call flows and the way your teams work.
MiCiS sets up and supports hosted business phone systems and Microsoft Teams Calling. We coordinate number transfers and the internet connectivity your calls depend on. One team coordinates porting, call flows, IVR and queues, handsets, softphones and mobile users—then retains the service context for continuity, change and support.
Australian-based coordination, one escalation point and a documented voice
service path across carriers, platforms, networks and endpoints.
Carrier
Numbers + porting
PSTN and SIP services, number records and porting dependencies coordinated.
Platform
PBX or Teams Calling
Hosted voice aligned to users, sites, licences and collaboration workflows.
Call experience
IVR + queues mapped
Business hours, routing, menus, voicemail and overflow documented.
Continuity
Support path defined
Failover options and responsibilities across carrier, platform, network and endpoints.
WHAT WE MANAGE
The numbers, platforms, call flows and endpoints behind dependable business calling.
Business telephony is a connected service path, not a single handset or licence. MiCiS coordinates number records and porting, PSTN and SIP services, hosted PBX or Microsoft Teams Calling, call routing, user devices, mobility, reporting and continuity so responsibility remains clear from the carrier network to the person answering.
Porting and cutover depend on verified records
Portability, lead times and migration options depend on the number type,
current carrier and service records, authorised customer details,
selected platform, site and network readiness, and carrier acceptance.
Dates are confirmed only after the required records and dependencies
have been validated.
Business phone system coverage
Hosted PBX and Teams Calling
Platform design, licences, users, policies, tenant or service configuration and calling enablement.
Call flows, IVR, queues and voicemail
Business hours, greetings, menus, hunt groups, queue logic, overflow, after-hours routing and voicemail.
Handsets, headsets, softphones and mobility
Device selection, provisioning, desktop and mobile apps, user profiles, hot desking and remote-work requirements.
Recording, reporting and integrations
Call reporting, recording requirements where applicable, retention and access responsibilities, and CRM or contact-centre integrations.
Continuity, support and lifecycle
Alternate routing, failover options, monitoring, escalation, controlled change and platform or endpoint lifecycle.
CALLING CONTINUITY BUILT IN
A phone platform is only reliable when the full call path is understood.
Business calling depends on more than the cloud platform. Number routing, carrier and SIP services, internet and firewall behaviour, local power, call-flow configuration and user endpoints can each change whether a call reaches the right person. MiCiS documents those dependencies, designs the available continuity paths and tests the agreed behaviour before and after change.
- Number and routing records kept current Authorised-customer details, service records, caller ID, porting state, business-hours routing and available diversion options are documented before change.
- Failure behaviour designed before cutover Carrier, internet, power and platform failure modes are mapped to the available overflow, alternate-destination and user-response options.
- Calls tested from caller to answer point Inbound, outbound, IVR, queue, transfer, voicemail, handset, softphone and mobile paths are validated to the agreed scope.
Voice continuity control path
Failure behaviour across the full call path
Numbers and routing records
Authorised-customer details, service records, caller ID,
emergency-location data where applicable, diversions and porting state
Documented
Carrier, PSTN and SIP services
Upstream service path, number routing, handoff details and carrier
escalation responsibilities
Coordinated
Internet, firewall, QoS and power
Bandwidth, voice VLANs, firewall rules, QoS, failover behaviour and
local power dependencies
Prepared
Hosted PBX or Teams call flows
Business hours, IVR, queues, overflow, voicemail and alternate
destinations
Tested
Handsets, softphones and mobile users
User profiles, device readiness, remote work and alternate answering
methods
Enabled
HOW THE SERVICE IS DELIVERED
A controlled path from number records and call-flow design to tested, supported calling.
Phone-system delivery crosses carriers, number-porting records, platform configuration, internet and firewall readiness, devices, user change and cutover timing. MiCiS maps those dependencies, confirms the number and call-flow baseline, coordinates orders and porting, configures and tests the service, and retains the records needed for support and controlled change.
Business phone delivery path
From existing numbers and call flows to an operational, documented phone system
-
Discover and baseline
Inventory numbers, current carriers, service records, sites, users, licences, call flows, devices, integrations and continuity requirements.
Output Number + call-flow baseline -
Design, order and port
Select hosted PBX or Teams Calling, design routing and continuity, prepare carrier orders, validate authorisations and plan the porting window.
Output Approved design + order plan -
Configure, test and enable
Configure users, policies, IVR, queues, voicemail and endpoints; test inbound, outbound, transfer and continuity paths; complete the agreed cutover and enable users.
Output Tested service + cutover record -
Operate, support and improve
Retain number, call-flow and configuration records; manage incidents and changes; review reporting, licences, continuity and lifecycle priorities.
Output Support context + roadmap
END-TO-END CALL PATH
A successful call depends on every layer between the number and the answer point.
Inbound and outbound calls cross number routing and carrier services, site internet and network infrastructure, hosted PBX or Microsoft Teams Calling, call-flow configuration, user endpoints and sometimes CRM, contact-centre, recording or reporting services. MiCiS maps that chain so migrations, faults and changes can be tested against the actual business path rather than one provider's service boundary.
- Trace the call from number to answer point Carrier routing, IVR, queues, overflow, transfers, voicemail and the final user destination are considered as one path.
- Separate routing, quality and endpoint faults Number routing, carrier service, internet, firewall, QoS, Wi-Fi, platform configuration and user-device behaviour are tested at the appropriate layer.
- Keep integrations and responsibilities visible CRM, contact-centre, recording, reporting, workflow and third-party support dependencies are documented before a migration or change.
BUSINESS CALL PATH
From caller and carrier to the person or workflow receiving the call
CORE CALLING SERVICE
Operational business calling
Numbers, routing, call flows, user endpoints, integrations,
continuity and support.
Documented
Numbers, carrier, PSTN and SIP
Public numbers, porting state, caller ID, carrier routing,
service records, trunks and upstream handoff
Routed
Internet, firewall, QoS and failover
Site connectivity, voice VLANs, firewall behaviour, bandwidth,
quality, local power and alternate paths
Prepared
Hosted PBX or Teams tenant
Users, licences, trunks, policies, dial plans, IVR, queues,
voicemail and alternate routing
Configured
Handsets, softphones and mobile users
Desk phones, headsets, desktop and mobile apps, profiles,
remote work and alternate answering methods
Enabled
CRM, contact centre, recording and workflows
Supported integrations, reporting, recording configuration,
workflow triggers and data-handling dependencies
Integrated
MiCiS can trace a fault or plan a change across number and carrier records, site network, calling platform, call flow, user endpoints and connected workflows while retaining one documented escalation context.
FREQUENTLY ASKED QUESTIONS
Questions to settle before ordering, porting or changing a business phone system.
A phone-system proposal should make number control, porting dependencies, platform choice, call quality, continuity, recording, licences, charges, integrations and support boundaries clear before change begins. These are the questions that most often affect scope, cost, risk and cutover timing.
Records, responsibilities and cutover assumptions documented
Numbers to port, current-provider and account details, caller ID,
emergency-calling location information where applicable, recording and
retention decisions, billing, support boundaries and cutover contacts
are confirmed before change.
Business Phone Systems FAQ
Answers before numbers or call flows change
How long does porting take, and how is our right to use the numbers verified?
Timing depends on the number type, current carrier, accurate account and authorised-customer details, the existing service state, carrier acceptance, any rejection or rework, and the available cutover window. Keep the existing service active until the port is confirmed. MiCiS can inventory the numbers, prepare the records and coordinate the order, but the date is not final until the carrier accepts it.
Should we choose hosted PBX or Microsoft Teams Calling?
Teams Calling can suit organisations that already use Microsoft 365 and Teams as the daily communications workspace. A dedicated hosted PBX may suit environments that need broader handset choice, a clearer separation between telephony and collaboration, or particular carrier, contact-centre or call-flow features. MiCiS compares users, call flows, licences, devices, integrations, support and continuity rather than selecting the platform from one feature alone.
How dependent is cloud calling on our internet and local network?
Hosted calling normally depends on IP connectivity between the user and the calling service. Quality can be affected by bandwidth, latency, packet loss, jitter, Wi-Fi, LAN design, firewall behaviour, QoS, local power and the endpoint itself. MiCiS checks the complete path. Carrier-side diversions, mobile users or alternate connectivity may provide continuity, but only where those options are part of the documented design.
What failover and continuity options are available?
Options may include carrier-side diversion, IVR or queue overflow, alternate destinations, softphone or mobile operation, secondary internet, redundant network or power arrangements, and multi-site answering. Each option protects against different failure modes. Triggers, limitations, testing and recovery responsibilities should be documented. Emergency-calling behaviour and location information are assessed separately where applicable and should not be assumed to follow ordinary diversion rules.
Can calls be recorded, and who is responsible for retention and access?
Recording availability depends on the selected platform, licences and call path. The organisation must determine its lawful basis, notification or consent requirements, permitted access, retention, security and deletion rules under applicable obligations and policy. MiCiS can configure the agreed technical feature and document system responsibilities, but legal and compliance decisions remain with the organisation and its advisers.
What carrier charges, licences and equipment costs should we expect?
Depending on the solution, costs may include number rental, carrier access or SIP services, call usage, inbound-number services, porting or project charges, platform and user licences, Microsoft or third-party calling licences, handsets, headsets, recording, contact-centre features and ongoing support. The proposal should separate one-off, recurring, usage-based and third-party charges.
Can the phone system integrate with CRM, contact centre or business workflows?
Often, subject to the selected platforms, supported APIs or connectors, licences and data-handling requirements. Integration may include click-to-dial, contact matching, screen presentation, queue or contact-centre functions, reporting, recording references and workflow triggers. MiCiS confirms the required behaviour and third-party responsibilities before treating an integration as part of the production scope.
Who supports a fault across the carrier, platform, network and endpoints?
Where the related services are within the MiCiS scope, MiCiS can provide one escalation point, retain the technical context and coordinate evidence across the carrier, internet and network, calling platform, call flow and user endpoint. Underlying carriers, platform vendors and other suppliers may still retain their own service responsibilities and restoration processes. Support windows, boundaries and escalation paths are documented for the engagement.
Ready for a business phone system built around how your calls should actually flow?
Start with a practical review of your numbers, current carrier services, users, sites, call flows, platform, devices, integrations and continuity requirements. MiCiS will identify porting and network dependencies, clarify responsibility, and recommend the right next step for hosted PBX or Microsoft Teams Calling.