Find the right service for the request
A practical routing guide for front-counter staff supporting visitors across programs and service locations.
Cedar Vale Service Centre is a fictional multi-program organization. Start with the outcome the person is seeking, then check the current approved resource for the relevant service before explaining a route.
Start with the request
These fictional service families help with initial sorting; they do not determine eligibility or replace an official resource.
Housing support
- The person is asking about a housing-related service or appointment.
- Check the approved housing resource for the relevant program and location.
Community programs
- The person is asking about joining, attending, or finding a community program.
- Check the approved program resource for current routes and local scope.
Resident records
- The person is asking about a record or a records-related service.
- Use the approved records resource to identify the correct process and responsible team.
Separate the questions before routing
A clear request may have one service match. A request spanning services needs a careful handoff.
One clear request
A visitor asks, “Where can I ask about a housing appointment?” The request points to housing support. Check the current approved housing resource, then explain only the next step it supports.
- Confirm the program or location if the official resource makes that distinction.
- Do not infer eligibility from the service-family label.
A request across programs
A visitor asks about both a housing appointment and enrolling in a community program. Keep the questions distinct, check the relevant approved resource for each, and consult a supervisor or Public Service and Program Operations if a route is unclear or the answers conflict.
- Check each request against its applicable resource.
- Do not choose a program on the visitor's behalf or promise an outcome.
Completed handoff: two different questions
Visitor’s request: “I need to ask about a housing appointment, and I also want to join a community activity.”
Front-counter note in this fictional example: “I separated the two requests. The current housing resource identifies the housing desk for appointment questions. The community-program listing describes the activity but does not explain whether enrolment is currently open. I have not promised an appointment or a place.”
Question for the supervisor: “Which approved program intake route can confirm the enrolment position for this location?” The handoff preserves what was checked and what remains unanswered without gathering unrelated personal information.
Make the handoff clear
Help the receiving role understand the question and what has already been checked.
-
1
State the request
Summarize the outcome the person is seeking, using their own terms where helpful.
-
2
Name the possible service family
Use the approved service categories as a starting point, not as a decision about eligibility.
-
3
Check the authoritative resource
Verify the route and any relevant program or location distinction in the current official resource.
-
4
Explain only what the resource supports
Give the next step only when the resource makes it clear; do not promise a decision, timing, or result.
-
5
Refer unresolved questions
When the match is uncertain, resources conflict, or the request spans programs, consult the responsible supervisor or Public Service and Program Operations.
Support access and communication
Ask what would help, then follow the approved arrangements for the service and location.
Ask what support would help
Use a respectful, open question such as, “What would make it easier for us to discuss your request?” Do not assume what support a person needs.
- Listen to the person's stated preference.
- Use the organization's approved arrangements when they apply.
Get role-based guidance when unsure
If you are unsure which approved arrangement applies, involve the designated trained role or responsible supervisor for that program and location. Do not promise a particular accommodation or outcome unless the approved process confirms it.
- Keep the handoff focused on the support question and relevant service context.
- Follow the approved process for handling information shared.
When to escalate
Pause the routing decision rather than guessing.
- No service family clearly matches the request.
- Current official resources give conflicting directions or do not cover the relevant program or location.
- The request spans programs and the responsible handoff is unclear.
- You are unsure which approved access-support arrangement applies.
Consult the responsible supervisor or Public Service and Program Operations. Share a concise request summary and the resource or scope question that needs resolution; avoid promising an outcome or turnaround time.
Example ownership and upkeep: Public Service and Program Operations owns this fictional example. Send a guide correction through the responsible supervisor, identifying the service route or official reference that conflicts with this summary.