Callroute Roadmap

We believe in transparency and collaboration with our customers. Together we drive value and passion for everything we make. If you would like to see a feature that would solve your problem then please submit your idea to us and we will consider it for future development.

  • Sort by

Date added

Microsoft Teams User Status

In Development
Due Date
Apr 2024

Microsoft Teams User Status

In Development

We will be making changes to the user status within the Teams service to make it easier to understand and more in keeping with terminology that Microsoft use.

At the moment you’ll notice statuses like “Callroute Voice”, “Inactive Standard”, and “Other Voice”.

These will be changing to be more intuitive to the admin. More details on what these will change to will be provided closer to the time of release.

Callroute
Date added

Number Management Reports

In Development
Due Date
Apr 2024

Number Management Reports

In Development

We will be introducing a number of new reports to the Callroute portal on number management. Admins will be able to view their number consumption and availability across multiple ranges making it easier to understand and head off bottlenecks.

Admins will also receive an email from the platform when a range has been 95% allocated so they may take appropriate action before available numbers run out.

Callroute
Date added

Enhanced CDR Reports

In Development
Due Date
Apr 2024

Enhanced CDR Reports

In Development

Improvements to the CDR reports for phone calls. Reports will include the name of the service user called / calling, call directions will be clearer, and also introducing final call closing codes for better clarity between successful and unsuccessful calls.

Callroute
Date added

Access Control Lists

Planned
Due Date
Jun 2024

Access Control Lists

Planned

Building on top of our roles based access control, Access Control Lists (ACLs) will provide the next level of granularity to customer admin controls.

When released, admins will be able to create custom roles within Callroute and associate them with an ACL that will provide them access to controlled resources.

This feature will be useful for multi-organizational teams where there are several support towers, each responsible for managing a subset of Teams users.

Orto
Date added

Multi-tenanted Teams

Planned
Due Date
May 2024

Multi-tenanted Teams

Planned

At present a customer can only connect 1 Teams tenant to their Callroute platform. We will be enabling multi-tenanted Teams connections to Callroute so that you can connect more than 1 Teams tenant to the same Callroute tenant.

When connected, you’ll be able to share your Sipsynergy and BYOC connections between connected Teams tenants and also provide a single pane of glass for Teams user management with Orto.

Callroute
Date added

Microsoft Single Sign-on

Released
Due Date
Feb 2024

Microsoft Single Sign-on

Released

Customers will be able to integrate their Microsoft 365 identity with the Callroute portal for sign-in. Instead of relying on Callroute’s internal identity service for authenticating logins to the portal, administrators will be able to sign in using their Microsoft identity.

This has added benefits for our enterprise customers

  • Ability to disable access to Callroute directly from their own Entra ID directory by disabling accounts. Without this feature, admins need to disable accounts in Callroute as well.
  • Ability to use Microsoft multi-factor authentication and other security principles within the Entra ID security framework and apply them to Callroute.
  • Easier for the admin to sign in and remember 1 credential rather than 2.

You will still be able to login to Callroute using its own local identity and multi-factor authentication if needed. This will be useful for break glass type admin accounts in the event of single sign on failure.

Callroute
Date added

Combined Sync Function

Released
Due Date
Feb 2024

Combined Sync Function

Released

At the moment admins must sync numbers, users, licenses, policies, teams, and queues separately. Whilst the majority of these synchronizations are only needed periodically there are cases where they all need to be refreshed at once.

The combined sync button will process all syncs in one tasks eliminating the need for admins to press multiple buttons. This will also be included in our initial Teams deploy routine for new customers so that the onboarding experience for fully licensed customers is improved.

Callroute
Date added

Target Provisioning Users By Entra ID Group

Released
Due Date
Feb 2024

Target Provisioning Users By Entra ID Group

Released

In addition to being able to target users for provisioning using their Entra ID attributes, admins will be able to specify which security groups a user must be a member of to trigger the provisioning rule.

This feature is useful for customers who cannot build a provisioning ruleset using user based attributes alone.

Orto
Date added

Number Range Locations

Released
Due Date
Jan 2024

Number Range Locations

Released

Allow administrators to sub-divide their number ranges into specific locations. This will allow for admins to create locations that are more meaningful to their operational team e.g. ‘Southwark Office’ and ‘Westminster Office’ and then associate numbers from ranges to those locations.

You’ll then be able to select numbers from these locations when editing a user or applying an automated provisioning policy.

Callroute
Date added

Number Quarantine

Released
Due Date
Jan 2024

Number Quarantine

Released

When numbers are unassigned from a user or service they are instantly available for reallocation to other users and phones.

Sometimes this is not desirable and there may be times where the number needs to be reassigned to old user. A common use case is when staff leave and return within a short period of time.

Number quarantine is a setting that admins will be able to enable where they can set the number of days a number is placed into quarantine before it is added back into the general number pool for allocation.

When set, numbers that are unassigned from a user will be placed into quarantine and frozen until the quarantine period has expired. This can be overridden at any time manually in the portal.

Callroute
Date added

Provisioning API

Released
Due Date
Jan 2024

Provisioning API

Released

The provisioning API will allow customers to integrate Orto with their ITSM service desk or other orchestration platforms to deliver Teams user configuration to the user based on a rules-based deployment model.

This will be useful for approval based provisioning requests and also direct integration with automated processes that lack the features to complete the entire Teams provisioning journey for a user.

Admins will be able to supply data within the API request to help target specific rules where AzureAD cannot be used as a reliable data source and also explicit numbers. This makes the API very powerful and has the ability to also help you migrate users from PBX to Teams voice in bulk with almost no scripting required.

Orto

Feature Request

We are constantly developing our product to offer the maximum value to our customers. If you have identified an opportunity for improvement, we would welcome your idea. Please complete the short form to submit your feature request.

Intermittent Microsoft Teams calling issues reported globally. This issue appears to be affecting all Microsoft customers worldwide. Microsoft are currently investigating the issue. All Callroute systems are fully operational. More information will be provided as soon as possible.