Customer Service Chained Events

Created by Migration Bot, Modified on Fri, 23 Oct at 2:29 PM by Migration Bot

Originally written by John Hardwick, last updated Oct 12, 2023, on the Swan Retail knowledge base (FRS).


This document is based on SwanFRS release version 1207

Overview

A chained event is effectively a series of linked events which are added to the service when a specific event is manually added.

Items for consideration.

  • Consider what trigger event will start the chain, is it the creation of a new service, the intention or collect goods from the supplier or a series of steps relating to the control of an allowance.

  • Break the service down into smaller manageable workflows - what is the sequence when responding to the complaint, what steps are performed when returning the item or offering an allowance.

  • Many events in SwanFRS are mini workflows in their own right and therefore do not need a chained event - ensure you’re familiar with the ‘action' buttons at the foot of the service screen before embarking on a chain event creation.

  • Keeps chained events succinct - a large chained list requires each event to be processed - smaller chained events can be added as required

  • no service is the same - chained events bring a sequence or process to the service response, making them too complex with many steps can reduce efficiency.

  • Consider a chained event to be a series of milestone events marking specific actions. Notes and comments can be added to each milestone as needed.

  • An event within the change can be dynamic - for example when returning the item - you may not decide if you are returning for repair or credit until after the inspection feedback, therefore leave ‘return’ event within the chain open for the operator to choose when this action is reached.

  • Events can time from the point of addition to the service or when the previous event closes - consider SLAs / review times to ensure premature escalations do not occur.

Configuration

The following section details how to set up chained events.

Service Events

Menu Location: Systems Admin > Customer Service > Set Up Service Events

Prior to setting up a chained event, all the individual steps in the chain should be created within this routine.

The use of ‘review days’, ‘escalations’ are important, as is the ‘affect bookings’ option.

Chained Events

Menu Location: System Admin > Customer Service > Set Up Chained Events

Chained events can be set for the entire estate or be location specific.

Choose the correct trigger point and build the linked events from that.

When creating the chain, choose whether the chain is a mandatory or optional feature.

For events within the chain, it is possible to set an event ‘placeholder’ allowing the operator to choose which variant of the event is to be set at the point of processing the specific event.

Operation

Chained events are dormant until the trigger event is selected when progressing a service complaint.

Chained events are only operational within service - if an event, when a linked chain, is selected outside the service arena, the chained event will not operate.

Optional Chains

When a trigger event is selected which is linked to an optional chain, SwanFRS presents a checkbox below the event subject.

In this instance, an ‘Action’ Event is linked to a chain and the operator is being asked if the chain is to be added to the service’s event list.

Unchecking the box adds the master event without the chain.

It is very easy to miss the checkbox, when using chained event please ensure the team are aware of this feature and to look out for it when adding actions to service calls.

If the trigger event is linked to a mandatory list of chained events, the checkbox is not accessible and the list of linked events will be automatically added to the service call upon successful addition of the master event to the service.

Chaining the chain will not alter those events already added to the service.

Editing the master event will not refresh or reload chained events. They are only added when the master event is added to the service.

Chained Events

In the example below, a ‘collection’ event added to the service has created a series of 9 chained events.

Once added to the service call, chained events become autonomous, allowing the operator to process them in the sequence of their choice.

The exception to the rule relates to With Closure chained events, in that their Review Dates only become set when the previous chained event action is closed.

SwanFRS records changes to events, listing the operator, date and time of change. This is presented as a change history to the lower right side of the page (highlighted with a red box below)

When using chained event or when viewing service calls with many events, is it recommended that the Hide Closed event check box is ticked.  This hides events where no further actions are required.

Multiple Owner Events

Any chained event where the owner is set to Multiple causes one event per ‘owner’ to be added to the service call.

In the example above, events 5 of 9, 6 of 9 and 7 of 9 may look to be repeats however they each have a different owner and as such the system has generated an event for each owner as the outcome of each owner viewing the action may be different.

Flexible Events

Flexible events offer the operator a choice when processing the event.  The event is added to the chain when the master event is added, however it is left for the operator to choose the Event Type / Subject later.

In the example above, events 2 of 9 and 4 of 9 are flexible, The operator may choose the ‘variant’ of Item Return / Item Addition once the event has been selected and edited.

When viewing a flexible event, the detail section replicates the text entered for the master event until the operator click the EDIT EVENT button, whereby the system offers the operator the ability to choose the event type and possibly subject for the chained event.

Once the variant has been selected, the event becomes fixed and no further change of Type / Subject is allowed.

Event Timing

When adding chained events to the service call the event, the system dates the chained events with either the master event date (Immediate) or will leave the event timings open (With Closure).

  • Immediate events will have a review date set using the review date set against the event being added to the system date. I.e. A fixed date by which the event should be completed. This date is not affected by the closure date of the event immediately before it in the chain.

  • With closure, events are displayed with a blank Review Date and a OPEN status indicator. When the event immediately before it in the chain is closed, the system will set the review date, adding the event's review date to the system date and therefore creating a fixed expected completion date. The status indicate will then either change to OPEN, DUE or OVERDUE dependent upon, system settings.

Cancelling Chained Events

It is not possible to cancel a chained event once added to the service unless the operator possesses the SERVICE_CANCEL_CHAINED_EVENT user privilege.

If the operator can cancel a chained event the CANCEL EVENT button is active, clicking cancels the selected chained event resulting in the cancellation of the event (in this example event 6 of 9)

Files from the Confluence page

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article