Want to learn more about Citizen Services technology? Access our eBook “Transforming Citizen Services Through IT Modernization“
From day one, Citizen Services was designed to support all our customers. Whether that’s a small town with 5,000 residents and relatively simple needs, or a major city with a need for more sophisticated features.
In terms of the Service Request workflow, the way we accomplished this historically was by implementing a basic, built-in workflow that would meet most requirements. For customers with a need for a more flexible workflow, we would integrate with a popular resource management system such as Dynamics 365 for Field Service or Cityworks.
Well, our customers have spoken, and we’ve listened. In this release, we’re introducing more configurable and flexible workflows that are built right into the system.
To begin with, customers can enable or disable the Dispatcher and/or Service Owner portions of the workflow. For example, this would allow a workflow where Service Requests could go directly from the Reporter to a Service Engineer (without involving call centers or managers).
In prior releases, Service Requests were routed to the appropriate department or Engineers based on configurations made at design time. For example, if a reporter clicked on “Potholes”, it was pre-determined where this request would be routed based on the configuration we performed at the time of creation.
What we’ve enabled in this release is the ability to route Service Request dynamically, based on what the user inputs on the request form when making the request.
For illustration, below is a Service Request Type called “Road Feature”. On the form for this Service Request Type there is a required field called “Street Feature Type” where the reporter must narrow down the nature of their request.
In Citizen Services, not only can we change the form based on which value the user selects (as described in the 1.3.1 Release Update), but we can also route the service request to the appropriate group or engineer based on user input.
In the custom workflow configuration below, you can see how we add conditions to define how the service request type will be routed.
Notice in the screenshot above, not only is the routing defined based on user selection, but we can also have choices about how to assign the work to a specific engineer. We can manually select the engineer, assign based on which Engineer has the fewest open assignments or by round-robin logic.
These tools and options provide a tremendous amount of flexibility for defining custom and dynamic workflows that can be catered to almost any requirement.
Another way in which we’ve increased the flexibility of the platform is by adding additional Role and Permission Options.
Since its launch, Citizen Services has included a Dispatcher role, which is responsible for request management such as triaging, editing, assigning and closing new service requests. This role might be granted to a city’s call center resources, for example. What we’ve heard from some of our customers, though, is that their call center resources don’t always need all the permissions and capabilities associated with the Dispatcher role. Instead, they want a scaled-down role that can add new service requests on behalf of constituents, and viewing or tracking the requests they’ve submitted (but not able to edit or assign the service requests).
Introducing the “Reporter” role, which does just that.
This role allows organizations to assign permissions with just enough capabilities, but not too much.
Clone Service Request Types
One thing our customers love about Citizen Services is how easy it is to create new Service Request Types—even if the person creating it has no technical background. Well, now we’ve made it even easier.
When creating a new Service Request Type, you can create one from scratch, or clone an existing Service Request Type and then edit it as needed. This saves customers a lot of time when setting up or making changes to their portals.
Assign Service Requests to Multiple Engineers
Sometimes tasks are too big for one person to do on their own. For that reason, we’ve added the ability to assign multiple engineers to the same service request.
This feature allows better tracking of resources and reflects the reality of how work gets done. In subsequent updates, we will be adding sub-tasks so specific parts of the job can be assigned to each resource.
Portuguese Language Support
Last but not least, we’re always getting requests for more language support. So we’ve added Portuguese to support our friends in Brazil, Portugal and other Portuguese-speaking regions.
Stay tuned! We’ll be posting more updates here very soon!