Routing and Queues
Menus, queues, skills, schedules, holiday rules and overflow. Routing is where a contact center's history lives, and it is the part most often rebuilt by hand during a migration.
Alaska
Contact Center Systems in Alaska
We assess, design, migrate and support contact centers for organizations in Alaska, with routing, recording and reporting that work the same for agents in every location.
What We Do
Trybus Solutions assesses, designs, migrates and supports contact centers and call center systems for organizations in Alaska. That covers routing and queues, agent and skill design, the systems agents work in, call recording, reporting, and the phone system and network the contact center depends on.
Most of our work starts for one of a few reasons. A platform is coming up on end of support. A contact center that began as a hunt group now answers callers from across the state. Agents are working from home or from more than one office. Or the reports cannot answer the questions leadership is asking.
End of support is close for some platforms. Cisco's contact center applications at versions 12.5 and 12.6, including Unified Contact Center Express, reach end of software maintenance and end of new service attachment on December 31, 2026, with a last date of support of December 31, 2027. Our guide to the two UCCX end-of-life bulletins explains which date applies to which license.
A contact center is usually the hardest part of a communications project, and the part with revenue or patient access attached, so we scope it on its own and price it separately. We work nationwide from Chattanooga, Tennessee. The wider scope of our collaboration, unified communications and contact center work is set out on its own page.
Why Alaska Organizations Bring Us In
- We are not tied to one platform.
We carry a range of technology partners, so what we recommend comes from your routing, your integrations and your reporting needs. If the platform you have still fits, we will say so. - We start with how callers are routed today.
Menus, queues, schedules, holiday rules and overflow have usually grown for years without documentation. We take them from the live system before anyone chooses what comes next, because routing logic nobody wrote down does not migrate. - We plan for agents in more than one place.
Agents in Anchorage, agents in a regional office and agents working from home need the same queues, the same recording and the same reporting. We design for the link at each location, so call quality does not depend on where an agent sits. - We set it up in Alaska time.
Most of Alaska is four hours behind Eastern time. Opening hours, holiday routing, reporting periods and support hours all need to be set in local time, and that is easy to get wrong on a platform configured from somewhere else. - We scope recording and retention up front.
Which calls are recorded, how long recordings are kept, who can listen to them and when they are deleted are decided before the build, because health, financial and public records rules answer those questions differently. - We are still there after go-live.
Support is available as a separate agreement, with coverage hours agreed in Alaska time and matched to the hours your contact center is open.
What You Get
Scope varies. A single queue for a front desk does not need the documentation a contact center with agents in several locations does. Below is what we produce on a typical mid-size project, and we agree which of it you need during scoping.
Everything we produce is yours. If you take the design elsewhere to be built, it will be complete enough for somebody else to build it.
- Routing and queue inventory:
Every number, menu, queue, schedule and overflow rule, taken from the live system. - Integration inventory:
The systems agents work in, such as a CRM, a health record or a ticketing system, and how each one connects today. - Requirements document:
Call volumes, service levels, recording and retention rules, reporting needs, and the budget and timeline the project has to fit. - Recommendation and options:
What we suggest, what else was considered, and the reasoning, written so it can go to leadership without an engineer to translate it. - Design documentation:
Routing, agent and skill design, integrations, recording and reporting, at the level of detail the build needs. - Migration plan and test plan:
Stages, cutover windows, number porting, and the test calls that have to pass before each stage is signed off. - As-built documentation and supervisor training:
What was built, how it is configured, and how supervisors change schedules and queues without calling us.
The Systems We Work On
Six areas. Most contact center projects touch all of them.
Agents and Supervisors
Agent desktops, skills, wrap-up codes, and the supervisor tools for watching queues and changing them during the day. We design them with the people who use them.
Integrations
Screen pop, click to dial, and records written back to the system agents work in. Integrations past the documented connectors are custom work, scoped and tested on their own.
Recording and Quality
Call and screen recording, retention, access control, and the quality review process built on top. Retention rules are set by your sector, and we design to them.
Reporting
Real-time dashboards, historical reports and the definitions behind them. A report leadership trusts starts with agreed definitions of an abandoned call and a service level.
Resilience
What callers hear when a site loses its link, when an agent's home connection fails, or when the platform itself has a problem. Each case is planned and tested before go-live.
How a Project Runs in Alaska
Broadly the same shape whether it is one queue or a contact center with agents across the state. Timescales depend on integrations, carrier lead times and how much of your team is available.
- Scoping and kickoff:
Agree what is in scope, the deliverables, who decides what, and any procurement rules or funding deadlines that set the calendar. - Discovery:
Routing, integrations and reporting taken from the live system, plus sessions with supervisors and agents. When discovery changes the scope, we price it and you decide before we carry on. - Design and review:
Routing, integrations, recording and reporting documented, then walked through with your team and your supervisors. - Build and test:
Platform configured, integrations built, and test calls run against the acceptance criteria agreed at the start. - Pilot:
One queue or one team goes first, with a way back, while everyone else keeps working on the old platform. - Migration:
Queue by queue or site by site, with number porting scheduled around carrier dates. - Handover:
Closer support while the snags come out, then documentation and training for supervisors and administrators.
What Is Quoted Separately
Most of what is below is work we do. It is not part of a contact center project by default, because each piece carries its own scope, its own schedule and its own cost. If you want any of it included, say so at scoping and we will quote it in. The last one is different: it is work we do not do at all.
- Custom development and integration.
Integrations past the documented connectors get their own scope and their own testing, so they do not sit hidden inside a migration estimate. - The phone system and the network.
The phone system around the contact center, and the network underneath it, are their own projects when they need work. We will tell you during discovery. - Structured cabling and pathways.
We do not pull cable ourselves. We survey the building, write the specification and coordinate the cabling partners who install against it, then check the results before the switching goes on top. - Ongoing operation and support.
Managed services is a separate agreement with its own service levels. Some clients run the contact center themselves after handover and some hand it to us. - Carrier service and calling plans.
We design and configure the connection to the telephone network, but we do not become your carrier. Numbers, minutes and the bill for them stay with your provider.
Who We Work With in Alaska
Contact centers differ by sector less in technology than in what callers need and what the rules require.
Tribal Health and Tribal Government →
Appointment and advice lines for patients across a region, often answered from more than one clinic.
Hospitals and Clinics →
Patient access and scheduling lines, and recorded patient contact that carries privacy and retention rules.
Boroughs, Cities and State Agencies →
Public service lines, procurement rules, and records retention for recorded calls.
Alaska Native Corporations →
Customer and service lines for subsidiaries in several industries, often running on several platforms.
Technology We Work With
We hold partner relationships across the contact center and communications industry, and our engineers also work in platforms we do not sell. A migration starts on whatever you are running now, whoever supplied it.
We do not publish comparisons between manufacturers. Which platform suits an organization is something an assessment works out, not something a website should decide.
Talk to Us About a Contact Center in Alaska
Tell us what platform you run, how many agents and queues it has, and what date is driving the change. We will tell you what we think needs doing and what does not, and put a scope and a number against it.