This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
Copyright: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact firstname.lastname@example.org
Support Request is a kind of Ticket which the incoming Events (email, phone call, fax, etc.) of your customers are assigned to, and which is a very important
Ticket in ERP5 CRM because it allows you to manage all the interactions between your customer, your company and your supplier effectively, which helps
consolidating the customer relations of your company.
From last tutorial we have learned the standard process of managing incoming Events. In this tutorial, we will specially introduce the process of how to manage the Ticket "Support Request", following the standard process of managing incoming Events explained in last tutorial.
As you have learned from last tutorial, the second part of this illustration shows the standard process of Incoming Events: Declare as Received
Define the Event's Recipient
Create a Follow Up Ticket
Now we will explain in detail how to practice this process in managing Support Requests.
This tutorial is based on a scenario that will help you understand how to manage Support Requests and the role of this kind of Ticket.
Z Company is an electricity supplier, one of VIFIB clients who are using the ERP5 instance. John Scott Doh is the marketing manager of Z Company. From this year, as the other departments of Z Company, he starts to implement the ERP5 to manage his marketing department, and specially the ERP5 CRM for his business with his clients. In the very beginning of using this new instance, he met some difficulties in the configuration of the ERP5 instance, so he wrote to the ERP5 support team asking for help. When the ERP5 support team receives the email from this client, someone in the team will create a new incoming Event in ERP5 in order to ask for someone who is capable to answer to the request of John Doh.
Now please follow this scenario, combine with the standard incoming Events process you have learned, to see what's the steps to take in ERP5 to manage the support requests from your clients.
In ERP5 CRM, in order to better manage the customer relations, once we receive an incoming email, phonecall or fax from our clients, we will have to create a new incoming Event from the support request sender's document
in order to tell our team that we receive a message from our client. In this way, all the support requests from our clients will be recorded immediately, and be assigned to personnel to handle them later.
In our example, we will first create an incoming Event to inform our ERP5 support team that we have received an email from John Doh who is asking for help. As it is John Doh who sent this email, we will create the incoming Event directly from John Doh's Person Document, in order for the Event to be linked easily to John Doh in ERP5.
In order to create an incoming Event from the request sender John Doh's document
will be to
reach John Doh's person document
in ERP5. To do so,
click on the “Browse” tab
of your instance Homepage, and
click on “Persons”.
Then we will reach list of Persons stored in your ERP5 instance, click on John Doh's line
in order to reach his Person Document.
Now that you have reached John Doh's Person Document, the second step
in order to create an incoming Event from the support request sender's document is to
reach the Event list of John Doh
Click on the Event Tab
in John Doh's document.
As you can see, the Events list of John Doh is still empty because until now, there is no Event related to John Doh, i.e., VIFIB hasn't had any interaction with him so far.
Since we have received the mail message from our client John Doh asking for help, we will now create a new Event related to John Doh to record this message. To do so, open the “Action” item list and choose “Create New Event”
As you have learned in the previous tutorial “How to Prepare Outgoing Events”, when the new Event is created, you can first set the basic information such as Event title, type and direction
, etc. The only difference here is to
set the Event Direction to “In”
this time, because you want to create an Incoming Event, indicating that you have received an email in this case, and then you will enter this email in your ERP5 for someone of your team to process it.
Now you can copy and paste the email you have received from your client John Doh into "Message" area, or you can also do it later in the Event edit page.
In order to follow this tutorial, check Keep in draft state
option in order to create an Event on "Draft" State. Afterwards, we are going to learn how to learn how to declare it as received manually.
When you are done, click the “Create New Event”
As you can see in the red area of the picture, a new Event has been created, which is on the “Draft” state
. The blue area shows the
Sender and Recipient fields
which have already been filled automatically, following this
: The Sender is John Doh, because the incoming Event has been created from his person document. This act tells the ERP5 team that we have received an email from our client John Doh somewhere. The Recipient here is Jingjing XU, because this is the name of the
who created this incoming Event. However,
this information can be changed later
, if we need to assign this incoming Event to someone else in our team to take care of it.
Now, copy and paste the email you have received from your client John Doh into the red area: Text Format
. This area aims at showing the email you have received to all the persons of your team, which is the content of this new incoming Event. If you have done it in the previous step, you can just review and edit it as you want. And finally, don't forget to
your data changes.
Now that you have drafted
all the necessary fields of this incoming Event, it is time to conform to the ERP5 that you have
this email from your client, the move will lead to the change of the Event's state as Received.
To do so, open the Action Item List and choose “Declare as Received”
As you can see on the screenshot, after we declared that the Event is received, the state of the newly created Event is now changed from "Draft" to "Received", which is the first state of an incoming Event, as you can witness on the workflow of incoming Events in ERP5, shown on the left of the picture.
Now it is time to define who should process this Event - the person in the ERP5 support team who will have to provide John Doh with an answer.
We will ask our team member “Yingjie XU” to take care of this Event.
To be able to proceed with this step you must have already created the Person and user account for Yingjie XU by following the tutorial How to create new User.
To assign the Event to “Yingjie XU”, first change the person name in the “Recipient” field from "Jingjing XU" (the default Recipient) to "Yingjie XU". Second, as usual, don't forget to "Save".
This step aims at indicating that “Yingjie XU” should receive this email from the client, and has to take care of it. So after the step that we "Receive" the Event, this Event will appear on Yingjie's worklist as "Received Events to Deliver", which we will show you later. In this way, Yingjie will know that he is responsible to handling a new incoming Event.
Now the incoming Event has been "Received"
has been defined, the
Follow Up Ticket
has been created, so it is time for the "Replier" - the Recipient to offer support to the client. And all the following interactions between the Replier and the Client will be recorded under the Support Request Ticket we just created.
In this section, we will switch users in order to understand how users can be aware that they have Events to handle.
by opening the “My favourites” item list, and choose
. After being logged out, we have
logge in as user “yingjie.xu”
in order to help you understand how incoming Events are displayed in the
of this user.
“Yingjie” is now logged in, and while opening his Worklist, we see that there are 1 "Received Events to Deliver”
to be treated. Let's click on this line.
This is the list of "Received Events to Deliver", reached through the Worklist. All the Events declared as "Received" and have assigned to a "Recipient" will displayed on this list. In order to know who has to take care of them,
each user has to search for his person name in the Recipients field, and then he will
click now on this Event with the his name as the Recipeint order to process it. ERP5 can be also configured to only display the received events of the user who is currently logged in, but the standard ERP5 configuration for SMBs is to display all received events.
Now we have reached the List through Yingjie's Worklist, we can see that there is 1 received Event to deliver (Normally there could be more Events on the list with different Recipients). So user "Yingjie” only has his name in one Event, which means that this is the only Event he is entitled to take care of. So click on this line in order to process it.
According to the standard process of incoming Events, if the Event can be handled in a simple way, we can Create Response directly
from the Received Event's Action item list, as the option shown in the blue frame. But if the incoming Event needs to be handled in a complicated way, which needs a Ticket to contain many following Events, as in our case the support request from our client, we will then need to
Create Follow Up Ticket
from the Received Event's Action item list, as the option shown in the red frame.
So the next step will be to assign this Event to a Ticket. If you remember correctly, a Ticket can be a campaign, a sale opportunity, a support request, a meeting, etc...In this case, the client has asked for help in his email, so this is clearly a Support Request that has to be created. In order to create this Support Request Ticket, open the Action Item List and choose the action “Create Follow Up Ticket”
Now you will choose the type of Ticket you want to assign this Event to. In the first field, you can enter a Ticket Title
. This title will be displayed in the field Follow-Up of this Event. After this, you can choose the
. In our example, we will choose "Support Request" as Ticket type, which means that later we will be able to find this support request Ticket in the Support Request module of ERP5. After created, this Ticket can receive many different Events afterwards, such as the reply from ERP5 support team member, and the further questions from the client John Doh. When you are done,
click the “Create Follow Up Ticket” button
As you can see stated in the left upside of the screenshot, the Follow Up Ticket of this incoming Event has been created. You can see the Ticket is displayed in the "Follow Up"
field in the Event's page.
The Follow Up Ticket is created in order to contain all the following Events happened between the client and ERP5 team which are related to the original Event. We can easily access to it by clicking the plane icon
in the right side of this field.
Now we can access to the Follow Up Ticket of the incoming Event - the Support Request Ticket we just created. In the page of the Ticket, as circled in red, you can now define the Manager, the Supervisor and the Operators, so they will know through their worklist that they are responsible to process the Ticket.
As circled in blue, you can already see the Event from which we created the Support Request Ticket has been contained in the Events List of this Ticket. From now on, every interactions happen later between the operators and the client will be recorded in this Ticket, and clearly listed in the Events List.
Now we can return to the event and we will now explain how to provide client John Doe with an answer to his question.
Now it is time to reply to the client. If you remember, we have created a Follow Up Ticket for this Event in order to record all the following interactions related to the original Event. But the same as those Events which can be handled in a simple way so not need to be assigned to a Follow Up Ticket, we will use the Action item List in the Event page to create responses to our clients. The only difference is, all the Events of replies or other interactions created from this Event will be related to it by "Event Origin" and be recorded in the Follow Up Ticket we created.
Now we will click on "Create Response" in the Action item List
in the Event page to reply to client John Doh.
Now we reached the Reponse editing page. We will first edit the reply in the "Message" field, then check the other information in this page such as Title, Date, etd. When you are sure everything is correctly edited, click on "Create Response", then the response will be sent to the client and be created automatically as an outgoing Event with a state of "Sent"
You should be very careful before click on "Create Response"
, because after this action, your message to clients will be sent to them and cannot be modified any more.
Here we are back to the original Event Mail Message from client John Doh. As you can see on this page, it is stated "Response Created"
, which means this Information Request has been replied.
You can still access to the Response Event you have sent to clients to see the details, just have to click on the "Related Events" tab
Now we are lead to the Related Events tab
of the original incoming Event from John Doh, which we "Declare as Received", "Deliver" and "Create Response".
As we just created one response to the original Event from John Doh, there is only one Event listed in the tab which is the Response mail we want to check. Click on this Event to open it
Now we have accessed to the new Event created automatically
when we "Create Response" from the original incoming Event. The Event state is now
, this means that the email containing the answer has been sent to the client John's email address!
We will need to find all the related Events after we have communicated with the client, so we will go back to the Follow Up Ticket of the original Event, which we created to recorded all the related Events to the original Event from our clients.
The red line is the line of the Support Request Ticket we created when we assigned the incoming Event.Click on this line
in order to open this support Request Ticket.
We can see first that not much information has been edited, but you can do it now. Indeed, we have just created this ticket but not edited it yet. You can find some help in the tutorial “How to Create a Marketing Campaign”
in order to understand which field is used for what (the Campaign and Support Request Tickets look exactly the same indeed).
The red area displays all the related Events stored in this ticket
. As you can see there are three Events listed: the first one is the original Event which is the incoming Event we created to notice our team of John's question. This Event is on the Delivered state, because user “Yingjie” acknowledged it. The second and third ones are the answers that we created for John Doh. These Events are on the “Sent” state, because the email was sent to the client!
From now on, this Support Request can be used if in the future, client John Doh sends new emails about configuration problems
. The only thing you will have to do in order to add Events to this Support Requests, is to open the “Action” item list and select “Create new Event”. Then the new Event will be created and associated automatically to the Ticket, as described in the
“How to Prepare Outgoing Events”