Screens, queues and feedback: one platform or three separate tools?

Three jobs, often three owners

Many service networks run three related jobs at every location. Screens tell customers what is on offer and where to go. A queue system decides who is served next and at which counter. Feedback tools ask customers how the visit went, while it is still fresh.

In many organisations, each job sits with a different team. Marketing or communications runs the screens, operations runs the queue, and a customer experience or quality team runs feedback. Each team has its own budget and its own idea of a good tool.

Nexus Cloud consists of three products: Nexus Signage, Nexus Queue and Nexus Surveys. With Nexus Signage, teams design, schedule and publish content to screens across every location, and see what each screen is playing. Nexus Queue organises how customers arrive, wait and are served, from the first ticket to the service counter. Nexus Surveys captures feedback at the moment of service, by kiosk or QR code, and measures the experience location by location.

The case for separate tools

Separate tools let each team choose the product that fits its own work, on its own timetable. A team can replace its tool later without reopening the decisions of the other two. Ownership stays simple, because each contract maps to one department and one budget line.

Separate tools also spread supplier risk. If one vendor changes direction, the other two jobs carry on as before. If you already run a tool you are happy with for one of the jobs, keeping it can be the sensible choice.

What separate tools add

Each extra vendor brings another contract to negotiate and another procurement and security review. It also brings another set of administrator accounts, another support route and another renewal date to track. Staff who work across two or three of the jobs keep a separate sign-in for each.

IT carries most of this. Every system has to be listed, reviewed, updated and removed from people's access when they leave. None of it appears on a feature comparison, but it lands on the same few people in IT and procurement.

What "one platform" should mean

A single vendor does not remove that overhead by itself. It also moves risk the other way: more depends on one supplier, and a weak product in the set is harder to swap out.

The phrase "one platform" is used loosely. Vendors use the term for different things, and each needs its own evidence.

At Nexus Cloud, the three products share one console and one sign-in. Ask any vendor, including us, to show each shared element in a demo, and leave anything it cannot show out of the decision.

Deployment and the IT review

The CIO's questions apply to every product in the set: where it runs, who operates it and how it fits your IT rules. Ask for the answers in writing, product by product.

Nexus Signage, Nexus Queue and Nexus Surveys each run in the cloud or on premises, according to your requirements. We confirm the deployment design for each product with your IT team.

Start with one job

Not every organisation needs to solve all three jobs at once. Start with the job that has the most pressing problem and a clear owner. Then decide whether the other two should come from the same vendor or stay with their current tools.

Each Nexus product works on its own. You can add the other Nexus products later, in the same console and sign-in.

Before you decide: a short checklist

• Name the owner of screens, queues and feedback in your organisation.
• Decide which job needs a solution first, and which can follow later.
• List the contracts, reviews, sign-ins and administrator accounts each option adds.
• Ask every vendor what its products share, and see each shared element in a demo.
• Confirm cloud or on-premises deployment for each product with IT.
• Check that each product can be used on its own if plans change.