Give every people question a clear route

One question can hide three different needs

Support questions rarely stay in one lane. “How do I record sickness?” may be a platform question, a policy question or the start of a private conversation with HR. A manager asking about a colleague may need legitimate team information, not access to everything held about that person.

When every question enters the same inbox, the first reply often creates another round of clarification. The employee repeats themselves. HR becomes a switchboard. Managers rely on remembered answers or old documents because that feels quicker than working out where to ask.

The difficulty is not simply finding information. It is matching the question to the right source, audience and next step. Good support distinguishes guidance on using a system from organisational policy and from authorised knowledge about colleagues. That distinction protects privacy, reduces contradictory answers and makes escalation clearer. It also helps people recognise when a written answer is enough and when human judgement is required.

Build clear routes, not one crowded inbox

A calmer model gives people one obvious place to begin, then separates the routes behind it. Each route should say what it can answer, what information it searches and what happens if the answer does not settle the matter. Search is useful, but only when the underlying material is current and its limits are visible.

This matters most around absence, documentation and colleague information. A policy can explain how sickness should be recorded, yet an unusual circumstance may still need HR. A manager may need information about someone in their team, but that does not justify broad access. Clear routes let ordinary questions move quickly while preserving a deliberate path for sensitive ones.

The test is not whether every enquiry gets an instant answer. It is whether the person knows what they can rely on and what to do next. Keep ownership clear: platform guidance belongs with product support, organisational interpretation with HR, and colleague-specific information within authorised boundaries.

Make the next step obvious

This is where Zizzy’s Help and Support menu becomes useful rather than merely convenient. It is available on every page and divides support into three purposeful routes. Zizzy Support answers questions about the platform by searching the available information and taking the person to a recommended answer with follow-up options. HR Support searches available documentation for organisational questions, lets the person view the relevant policy and provides routes to raise an HR ticket, review previous requests, request support or contact HR. Team Knowledge lets managers and authorised team members ask for information about specific colleagues.

The practical change is that people do not need to know the organisational map before asking for help. They still need to choose the nature of the question, which is an important safeguard, but they are not left hunting through disconnected places.

No support menu can repair unclear policy ownership or poor documentation. Those foundations still matter. Used well, however, a shared starting point shortens the distance between a question and a trustworthy answer, while keeping human support available for matters that need context, discretion or judgement.