From the presentation of Events, we have seen how the Event is used to trace every interaction between our employees and the outside world. It is really easy with events to keep track of a simple or complex interactions.
But what about parallel interactions? What if you organise a conference and you want to keep track of every interaction you have while you prepare the conference? This is not possible with only the Events. The same problem happens when you want to keep track of every discussion which occurs when you send a press release: in the same time you will start maybe one hundred or more discussions. This is why every CRM system uses what we call "Tickets".
From the presentation of Events, we have had a general idea of how to use the CRM feature "Event" to manage company's interactions with external contacts. Following the VIFIB example, in the detail page of the Event
(the left side screen shot) which is a reply email from one contact who got the original mail message from our VIFIB manager, it shows the Event "
the "Beta Developer Program" (the right side screen shot).
The Ticket records a marketing campaign to hire software developers.
VIFIB director Mr Smets plans to launch a marketing campaign aims to increasing the product awareness of SlapOS the new operation system of VIFIB by hiring software developers. The main interactions of this campaign is to send mail messages to contacts (customers) of VIFIB, and these emails would be the
. So they would be listed in the detail page of this Ticket.
Beta Developer Program
This is a typical Ticket for ERP5 CRM. Now we will explain in detail what is a Ticket and then introduce the four different kinds of Tickets.
Tickets are records in the system which gather all events and documents related to the same subject.
For example, it allows you to put all the interactions related to the same marketing campaign in a same record.
By doing so, you will have the possibility to do better reporting of the actual situation of the company,
which will allow you to allocate roles of every employee and organise the work of each one.
In our example "VIFIB Beta Developer Program", the operation manager XU Jingjing will take care of all the Events of the Ticket, including coordinating the interactions between the VIFIB manager Cédric and his contacts, organizing the communication and cooperation between different persons inside and outside VIFIB who are related to this marketing campaign, and so on.
Now that we have seen what is a ticket and why it is useful, we will see what is the ticket made of.
A ticket is representing a movement of resource
, for example, the time spend on the ticket-
the Begin Date and End Date
. Therefore the Ticket looks like an order.
The resource is the type of ticket
such as a sale opportunity, a campaign, a support request or a meeting. In the case of a sale opportunity, we move it from our company to the company of our
client, this is why we have the fields
A Ticket is the record of its related Events and Documents. In the detail page of the ticket, you can find
a list of the related Events and Documents
which follow the Ticket.
We can also evaluate the
or the "
" of the ticket . These fields will help us to do reporting. In the case of sale opportunities, if we evaluate each of the tickets, it will allow us to create a report of the expected sale in the next six months; We will also be able to compare the global amount of sale opportunities in a given period with what we have entered as sale order. In the case of a meeting, we might evaluate the cost of the ticket in time, for example, how long does it take us to prepare it.
The standard workflow of a ticket is very simple: the operators edit and prepare the Ticket, then request the approval of the campaign's supervisor. If everything is OK, the supervisor will open the submitted campaign. Then the related interactions will be recorded as Events under this Campaign. When the campaign is finished, the operators will close it.
Note that even a closed Ticket can be opened again.
Now that the concept of a ticket is well understood, we will go in deep to the four specific tickets and their workflows in ERP5, which are Campaigns, Sale opportunities, Support requests and Meetings.
1. Press Release:
Press Release is a Campaign starts from sending many different Events
to recipients (the left side illustration).
In the case of a product release campaign of SlapOS, we will prepare many different Events
in terms of contents (since we want to send personalised emails for each journalist) and methods such as phone calls and visits besides emails (since some journalists are more important than others).
Once the Campaign is ready, we will
open it and send the Events
(send mails, give phone calls or pay visits) to the VIFIB customers.
We will then
from the customers either by mail messages, phone calls, or visits,etc. So in the same time we will have many single interactions with many different customers.
Thanks to the function of Ticket, every interactions between our customers and VIFIB will be tracked in the Ticket-the product release Campaign
At the end of the Ticket, once we finished all interactions, we will be able to learn from the closed Ticket that how many replies did we get, how many interactions have ended with a "Sale opportunity", etc. These informations would be very useful for the
of this campaign and the market prospects. These kinds of informations are very important if you want to be more efficient next time.
Newsletter is another kind of Campaign. The only difference with Press Release is that Newsletter starts from
a single Event
with many recipients (the right side illustration), so everyone will receive the same Event.
In our example "VIFIB Beta Developer Program" as presented above, follow the Ticket - the marketing Campaign, we will
prepare an Event - a same outgoing email
sending the recruitment message to different VIFIB contacts.
3. Other types :
Prospection, Partner Acquisition, Public Relations, etc.
Please note that, as the other features of ERP5, the Campaign types can be modified by ERP5 configuration.
The workflow of a Campaign is the standard work-flow of a Ticket. It assumes that there are two hierarchical levels: one person (normally the operator of the campaign) drafts
the campaign, and then
the campaign to the supervisor, while the state of the campaign changes from
"Draft" to "Approval Requested" or "Submitted". Then the other person (the supervisor) approves and opens
it. The state is marked as
"Open" during the process of the campaign, when multiple interactions happen and be recorded under the campaign. After the campaign is finished, they will close
it, changing the state to
In our example "VIFIB Beta Developer Program" which is exactly a campaign, the operations manager
drafted and prepared the campaign to hire software developers, then she submitted it to the supervisor
VIFIB director Mr Smets to
approve it. When everything is sure, Mr Smets opens the Campaign, then the community manager Cédric, who is in charge of sending the Mail Message Event "SlapOS Resilient Cloud Beta Developer Program", starts his interactions with his contacts, while all the Events (eg, emails) would be recorded under the Campaign "Beta Developer Program". After the marketing campaign is finished when VIFIB find enough qualified developers, the managers will close the campaign. Then all the Events recorded under the Campaign can be easily accessed when needed.
The screenshot above displays a few campaigns in different states as well as a worklist where the number of campaigns in each state is shown. The same as the Event, the worklist gives us efficient access to the campaigns of different states and facilitates the operation and management of company's campaigns.
As you can see in the screen shot of the detail page of ticket Sale Opportunity "VIFIB Offer PC Internet", in the case of a VIFIB offer in november 2011, we sent the promotion of PC through a newsletter to our customers. Some of them are interested in buying our products and services by replying to us saying "Hello, I want more info about your products, I am interested in them." etc. From then on, we need to create a dedicate Ticket which will be a "Sale Opportunity".
A sale opportunity starts from customers' replies which express their interest in our product and service. But normally few sale opportunity will come to a result very fast. First, only few clients will maybe take decisions fast. Second, there will be many actors involved in the decision to go with in the same sale opportunity: you might negotiate with the product supplier and the bank while keep in contact with your customers.
In one word, the decision from a sale opportunity can be made very quickly but sometimes it can take more than a year. So we need to use the Ticket "Sale Opportunity" to keep track of your commercial effort-your interactions with all the contacts involved, so to organise and to qualify our sale opportunities.
The Sale Opportunity work-flow is more complex than the basic ticket workflow, it ends by a Sale or a Rejection.
In the case "VIFIB Offer PC Internet", after the operations manager sent the offer to the customers, she got replies. She then
the ticket Sale Opportunity to manage the following interactions between VIFIB, the customers, the PC supplier and the bank. She will
the Sale opportunity to the suppervisor. If Mr Smets the suppervisor verifies and approves the Sale opportunity, the operations manager and sales staff will
contact the prospect
and negotiate with the PC supplier. When sales condition is set, VIFIB will give the final
. Finally, if the customer accept the offer, the VIFIB products will be
; If not, then sale opportunity is
This example displays a few sale opportunities in different states as well as a work-list where the number of sale opportunities in each state is shown. They offer quick access to the tickets, facilitating the company's operation management.
The third kind of ticket is the Support requests. Supports requests are used for customer help and support. For example, if you sell products through the Internet, some customers might return their products since they are broken or have defauts.
When a customer calls you to let you know the product is defected, you should open a support request: Then if the customer send picture of the product, Warranty scan etc., you can attach all documents in the tickets; Once you have received the product from the customer, you might ask the manufacturer if he will replace or fix it, so you can manage all the interactions between your customer, you and your supplier in the Tickets.
Here's the support request workflow.
Just like a standard ticket workflow, it is assuming that there are two hierarchical levels: one person prepare and submit the campaign, then the other approves, opens it and closes it.
This example displays a few support requests in different states as well as a worklist where the number of support requests in each state is shown. The same as the other tickets, they offer quick access to the tickets, facilitating the company's operation management.
The last kind of tickets in ERP5 CRM is the Meeting ticket.
Meeting should not be compared to the Event “visit”. A meeting is for instance a conference. If you prepare a conference you will first contact every speaker you want to ask whether they are interested in or not. You will also have discussion with the place holder and the clients you will invite to the conference. Before the presentation, you will need to call every single one of your speaker to confirm if they are arrived in their hotel rooms, if they are ready for the presentation, etc. Once the meeting is over, you will thank all your speakers for their efforts, etc.
The workflow for the meeting is a standard ticket workflow.
This is how the meetings are displayed in ERP5. Just like for the other tickets, you can check how many meetings are in Draft, Submitted, or Open states.
Powered by Python, Zope and ERP5
(c) 2001-2011 Nexedi & ERP5 Community. All Rights Reserved.