Notification Handling

If something is out of order, customers, citizens or general public can submit complaints or information to the organization. The notification is then channeled to the relevant internal handler group which deals with it and if possible gives feedback to the person who submitted the notification in the first place.

)
$
3
>
6
>
)
3
?
$
#
}
[
[
7
&
(
&
6
1
1
/
<
6
$
?
#
4
}
(
7
[
3
[
<
6
3
(
<
2
)
!
)
1
/
5
1
#
?
}
/
[
{
)
}
[
/
1
5
#
{
3
6
&
#
6
[
[
[
6
2
[
$
2
5
7
}
6
>
#
$
#
$
2
6
2
1
?
>
/
/
)
3
1
/
2
#
<
)
)
<
!
4
#
7
5
?
#
1
>
{
2
5
/
7
>
/
)
?
?
/
!
3
#
?
5
)
}
/
>
)
)
!
6
7
{
2
7
7
>
!
4
}
&
{
!
?
<
!
(
)
<
[
7
5
3
5
<
>
)
[
(
7
5
3
}
1
[
7
6
5
?
2
<
)
{
#
(
&
}
3
}
[
2
5
3
[
1
#
(
4
4
2
{
[
2
!
)
?

Efficient notification channel is key for good customer relationship. The basic notification BPM workflow is simple. If something is out of order, customers, citizens or general public can submit complaints or information to the organization. The notification is then channeled to the relevant internal handler group which deals with it and if possible gives feedback to the person who submitted the notification in the first place.

The key is simplicity and efficiency. Cloud4Proces has a responsive user interface, so notification submission (with photos) via smartphones is standard. The Notification App is available as well. It can be connected to to the same Notification handling back-end.

You can offer both anonymous and “logged-in” notification. It is really easy to specify/maintain categories and sub-categories for the notification form. Handler groups for different categories are already specified in the “Roles and users”, so implementation of the notification flow is plain.