Service Requests & 311

Resolve more resident needs before they become staff work.

Reduce repeated explanations and give staff clearer, better-routed requests. Wayhall answers from approved information, checks the details before creating work and keeps residents connected to status and resolution in your existing service systems.

  • Resolve routine questions
  • Validate before creating work
  • Keep residents informed
Wayhall Resident ExperienceIllustrative
Missed collection24 Maple Avenue
Tuesday · 6:10 PM
Missed collection · 24 Maple Avenue
ResidentMy garbage wasn’t collected at 24 Maple Avenue. What should I do?
WayhallThe collection window for 24 Maple Avenue has ended, so you can report a missed pickup if your bin was out on time and is still full. Was it out before the required time?
ResidentYes, and it is still full.
Collection context checked · report eligibility established
Behind this step
Agent · Service intakeSkill · Check service contextKnowledge · Collection guide & schedule

Example sources: approved collection guide and configured service schedule.

Tuesday · 6:14 PM
Address, collection details and eligibility retained
WayhallI’ve retained your details and checked for an existing open report. Please confirm: missed garbage collection at 24 Maple Avenue, bin out on time. A photo is optional.
ResidentThat’s correct. Please report it.
WayhallRequest SR-1042 has been created and routed to the collection team. You can return to this conversation for updates.
SR-1042 created after confirmation · team receives the details
Behind this step
Agent · Service intakeSkill · Check existing / create requestConnector · CRM or work-management system

The configured workflow determines whether to update an existing report or create a new one.

Wednesday · 9:20 AM
SR-1042 · missed collection · original details retained
ResidentMy bin is still full. What’s happening with my report?
WayhallThe collection team reports that your bin was missed on the original round. A return pickup is scheduled for tomorrow. Please keep the bin accessible. SR-1042 remains open.
ResidentThank you. Please keep me updated.
Resident informed · return pickup scheduled · work still open
Behind this step
Skill · Retrieve service updateSystem · Open service requestHuman · Collection-team schedule

Illustrative update from the connected service record. The request closes after the team records completion.

From question to resolution

Check the context. Create the right work. Keep the resident informed.

Use approved information and connected service context to determine the next step, then continue through staff action, status and resolution.

  1. UnderstandIdentify the issue and service.
  2. CheckValidate location, timing and eligibility.
  3. Resolve or createAnswer the question or confirm the right request.
  4. CoordinateRoute work and preserve staff context.
  5. ContinueShare updates and the recorded outcome.
Example: missed collection

Check before creating a request.

Municipal rules determine when a missed-collection report is eligible. The workflow checks the collection window, known disruptions and existing reports before creating or updating work.

01

Collection still underway?

Explain the collection window and when the resident should check again.

Guidance + next step
02

Known service disruption?

Share approved information and the next available update, following the reporting rules.

Information + follow-up
03

Eligible missed collection?

Check for an existing report, confirm the details, then create or update the request.

Right work + confirmation

A guidance response can answer the resident’s question while an operational issue remains open. Completion follows the responsible team’s recorded outcome.

Agentic service orchestration

Pre-built components move the 311 journey forward.

Municipal rules stay in the workflow while agents reason, skills act and staff participate where needed.

Service Intake Agent

Understands the resident's issue, asks clarifying questions and identifies the right service journey.

Reusable Skills

Validate address, search approved knowledge, create or update the service record and retrieve status.

Configurable Workflow

Controls eligibility, branching, routing, confirmation and when operational work is created.

Human-in-the-Workflow

Bring staff into complex or exceptional situations with the full interaction and collected context.

Connected operations

Use the system that already owns the work.

Keep service ownership in your existing 311, CRM or work-management platform. Wayhall sends confirmed details in, retrieves the team’s updates and explains the next step to the resident.

  • One service record and a shared reference
  • Staff continue in the system they use today
  • Residents get updates without repeating the issue
Explore the connector framework
One request. Connected updates.Illustrative
  1. 01Wayhall workflow

    Confirm the right request

    Validate address, check existing reports and capture the resident’s confirmation.

    AgentSkillsWorkflow
  2. 02Your municipal system

    Own and assign the work

    Request
    SR-1042 · Missed collection
    Owner
    Collection team
    Status
    Open
  3. 03Collection team

    Record the next action

    “Return pickup scheduled for Thursday.”

    Staff update the existing service record.
  4. 04Wayhall → resident

    Continue the conversation

    “Your return pickup is tomorrow. Please keep the bin accessible. SR-1042 is still open.”

    Source: connected collection-team update.
Configured connector carries details, references and status between systems.
Wayhall OpCenter shows the conversation, connected actions and service reference. The municipal system retains ownership and completion.
Evaluate a 311 pilot

Better intake. Useful answers. Fewer repeat inquiries.

Use Wayhall OpCenter and available service records to examine the value at each step of the journey.

Routine questions answered

Review whether residents received a useful answer or completed a self-service task. Track unanswered questions and appropriate staff involvement separately.

Request quality

Check required information at submission and whether the report reached the right service team.

Repeat reports identified

Review correctly matched existing reports and unnecessary duplicates. Check that different issues are not mistakenly merged.

Status guidance completed

Track status questions answered from connected records and the follow-up that still needs a person.

A submitted request is not a resolved collection issue. Confirm operational completion from the responsible team’s record. Where call data is available, compare telephone demand for the same service.

Explore the visibility behind these measures