Philippines staffing blog ·
Review two support queues after a merger
A practical order for comparing tools, request types, and ownership when two support teams become one.

Direct answer
Operational guidance
Start with the customer-facing surface
A merger is visible to customers through a changed domain, a new support address, or a different portal. Before comparing internal queues, list every place a customer can ask for help and who currently answers it. Include the help center, the contact form, the chat widget, and the address printed on invoices. Two teams can merge on paper while customers still reach the old channel for months.
Test each entry point from outside the company. Send a test request and note where it lands, how long an acknowledgement takes, and whether the reply names the right brand. These small observations reveal routing that no org chart shows. Fix the entry points before merging the queues, because a merged queue fed by a broken form will only spread the confusion.
Compare request types before comparing volumes
Raw ticket counts rarely compare cleanly across two companies. One team may log every password reset separately, while the other groups them under account access. Build a shared list of request types and map each queue to it. Volume differences often shrink or reverse once the categories align, so the first comparison should be treated as a draft rather than a finding.
Look for request types that exist in only one queue. They may reflect a product the other team does not support, or a habit that will disappear after the merger. Ask the agents which categories are real work and which are artefacts of an old tool. A taxonomy that nobody trusts will produce a merger plan built on the wrong demand.
Find the duplicate tools and duplicate owners
List the tools each team uses for tickets, knowledge, chat, and reporting. Mark the ones that overlap and the ones that hold unique history. Do not assume the larger team's tool should win, because the deciding factor is which system preserves the evidence customers and auditors need. A cheap migration can be expensive if it loses the record of past commitments.
Duplicate ownership is harder to see than duplicate software. The same customer may have an account manager, a billing contact, and a technical owner in each company. Map those roles before routing changes, or the new queue will send requests to people who no longer hold the relationship. Ownership records should be confirmed by the people named in them.
Read a sample from each queue
Take a sample of closed and open tickets from both teams and read them with the same questions. Was the request understood, was the answer correct, and did the customer know what happened next? Compare the notes for evidence and tone as well as the outcomes. A queue with tidy metrics can still hold vague notes that will not survive a merger.
Include the oldest open tickets in the sample. They show which commitments were made before the merger and which ones have no current owner. A customer who was promised a fix last quarter does not care which team inherited the promise. The review should produce a named owner for every old commitment, not just a count, and the owner should confirm the next contact date.
Set one routing rule at a time
Resist the urge to redesign the whole support model in the first month. Pick one request type, write the routing rule, and run it for a defined period. Compare the result with the old path using the same measure. A small change that holds is more useful than a broad redesign that nobody can evaluate, because the team can repeat a small change and learn from it.
Announce each rule with the customer message, the agent instruction, and the fallback when the rule does not fit. Agents need a safe way to route an unusual case without breaking the new structure. If the fallback is a person's personal inbox, the rule is not finished. The fallback should be a monitored queue with a named owner.
Keep both histories accessible
Decide how long the retiring system stays readable and who can search it. A read-only archive is enough for most historical tickets, but active cases need a live path. Record the cutover date and the location of the archive in the new knowledge base. Future agents will need the old record when a customer references a years-old promise.
Check that search finds the old records by customer name and by the old ticket number. A migration that only preserves the new identifier creates a dead end for anyone holding an old email. Test the search with a real example and document the result. Access to history is part of service continuity, not an archive project, and it should be tested before the old system is switched off.
Report what changed and what did not
After the first month, report the shared request types, the routing rules in force, the old commitments closed, and the entry points still pointing at the old brand. Include the items that did not change, because they explain why some customers still see the old experience. Give each open item a named owner and a date. A merger report that only shows progress hides the work that remains, and the hidden work is usually what customers notice first.
Set a review date for the next stage and name the person who owns it. The goal is not a single perfect queue but a sequence of changes that customers can follow. Each stage should leave the record clearer than the one before. That standard is easier to defend than a launch date chosen before the teams met.
Authoritative sources
- NIST SP 800-53 Rev. 5 security and privacy controls
- ISO 18295-1:2017 customer contact centres
- GAO Assessing Data Reliability
- GSA customer experience guidance