Back-end Processes - Revision history

Editor at 17:25, 13 April 2021

2021-04-13T17:25:29Z

Bbaigorri: /* Quick Access */

2021-01-14T12:00:14Z

Quick Access

Bbaigorri: /* Expired Jobs */

2021-01-14T12:00:01Z

Expired Jobs

Bbaigorri: /* Back-end Processes */

2020-12-09T19:23:53Z

Back-end Processes

Bbaigorri: Created page with "=Back-end Processes= ==Notification processes== The notification process runs once a day and scans all those tasks that need follow-up. This process finds all the tasks abo..."

2020-12-09T19:22:51Z

Created page with "=Back-end Processes= ==Notification processes== The notification process runs once a day and scans all those tasks that need follow-up. This process finds all the tasks abo..."

New page

=Back-end Processes=

==Notification processes==

The notification process runs once a day and scans all those tasks that need follow-up.

This process finds all the tasks about to expire and all the tasks that have reminders, that is, the reminders that have been configured for both tasks as well as opportunities, events and invoices.

These notifications will appear on the dashboard each time the user logs in.

In addition, notifications can be of two different types:

Blocking notifications: the user must attend to all the tasks that require follow-up in order to continue using the CRM, otherwise the system will close the session preventing them from reconnecting. The objective of this type of notification is to guarantee compliance with the company's sales process. Although these types of notifications can be created by the users, in general they are generated by the system automatically as a result of said sales process.

Non-blocking: this type of notification simply seeks to remind or give notice of certain types of tasks or issues to take into account during the sales process. It is important to clarify that, unlike the previous ones, these types of notifications are generally generated by the users as a way to facilitate their work.

==PARC==

This process generates the opportunities and tasks that must be carried out as part of the PARC Agreement.

It automatically creates the opportunity, inspection task, and follow-up. The corresponding dispatch is also created, so that it can be assigned to the team that will be conducting the visits as part of the PARC.

At the same time, the system sends a summary to the account managers of all the tasks that were generated as part of a PARC agreement.

This process runs weekly and the time these processes are generated can be fully customised by users with administrator permissions.

==Batch Processes==

The following processes don’t require user interaction to work. These are automated.

===Finance process - Past Due Invoices===

This process takes all the invoices with a debt greater than zero and performs a validation of the days corresponding to the payment terms and the creation date of the voucher.

This process takes those payments owed, calculates the corresponding penalty and updates the payment records so that the corresponding user can control and monitor them.

It does not have any type of notification.

===Get contact Process===

This process creates a suppression list, that is, a list of contacts to whom no more emails should be sent.

The process reads all the contacts that have an assigned email and whose status is "rejected" and creates a list with them.

The objective is to avoid wasting time contacting potential clients who have already been contacted with no success.

===RPH Process - Nurture process===

This process begins once the state of an RPH is changed to "nurture P2".

When it is changed, the RPH automatically goes to a pool for which the dates and templates of the mails that must be sent as part of the nurture P2 process are established.

This process takes all the RPHs that are in that pool, takes the corresponding template, performs the data replacement and sets up the email that should be sent. Then look for the next template and update the record with the corresponding number of days in which a new email should be executed.

This process is repeated until all the templates that must be executed as part of the Nurture P2 process have been sent.

In the event that no response is received, the system will change the RPH status to “closed” due to inactivity.

This process runs once a day.

===Inbound/ outbound emails===

This process is for reading emails. All emails, both sent from the CRM, and sent and received through other email service providers are saved in a backlog of the system.

Through a security token the system reads the emails from the user's email account inbox.

Every time you read an email, it creates a data table within the CRM, and in turn establishes a tag for those emails sent from the CRM.

This process is responsible for keeping all the emails sent between our advertisers and the Leads, for instance.

===Bug detector===

It is a process that runs daily looking for errors. This process sends the CRM administrator a report with the system errors found.

===Expired Jobs===

Every 30 minutes the system scans the database searching for all those jobs (dispatches and tasks) with a 3 hours delay. Then it sends an alert to a designated list of users with either the owners or managers for the job.

← Older revision		Revision as of 12:00, 14 January 2021
Line 78:		Line 78:

	Every 30 minutes the system scans the database searching for all those jobs (dispatches and tasks) with a 3 hours delay. Then it sends an alert to a designated list of users with either the owners or managers for the job.		Every 30 minutes the system scans the database searching for all those jobs (dispatches and tasks) with a 3 hours delay. Then it sends an alert to a designated list of users with either the owners or managers for the job.
−
−	~~=Quick Access=~~

	=Quick Access=		=Quick Access=

← Older revision		Revision as of 12:00, 14 January 2021
Line 78:		Line 78:

	Every 30 minutes the system scans the database searching for all those jobs (dispatches and tasks) with a 3 hours delay. Then it sends an alert to a designated list of users with either the owners or managers for the job.		Every 30 minutes the system scans the database searching for all those jobs (dispatches and tasks) with a 3 hours delay. Then it sends an alert to a designated list of users with either the owners or managers for the job.
		+
		+	=Quick Access=
		+
		+	=Quick Access=
		+
		+	*[[RPH]]
		+	*[[Lead]]
		+	*[[Accounts]]
		+	*[[Contacts]]
		+	*[[Opportunity]]
		+	*[[Dispatch]]
		+	*[[Invoices and Payroll]]
		+	*[[External Portals]]

← Older revision		Revision as of 19:23, 9 December 2020
Line 1:		Line 1:
	=Back-end Processes=		=Back-end Processes=
		+
		+	Internal processes ran by the system

	==Notification processes==		==Notification processes==

@@ Line 1: / Line 1: @@
 =Back-end Processes=
-Internal processes ran by the system
+These refer to internal processes run by the system.
 ==Notification processes==
@@ Line 7: / Line 7: @@
 The notification process runs once a day and scans all those tasks that need follow-up.
-This process finds all the tasks about to expire and all the tasks that have reminders, that is, the reminders that have been configured for both tasks as well as opportunities, events and invoices.
+This process finds all the tasks about to expire and provides notifications for all the functions that have reminders configured for action, opportunities, events, and invoices. These notifications will appear on the dashboard each time the user logs in.
-These notifications will appear on the dashboard each time the user logs in.
+Notifications can be of two different types:
-In addition, notifications can be of two different types:
+Blocking notifications: This type of notification aims to guarantee compliance with the company's sales process. The user must attend to all the tasks that require follow-up to continue using the CRM. Otherwise, the system will close the session and prevent them from reconnecting. Although users can create these types of notifications, they are generated by the system automatically as a result of the said sales process.
-Blocking notifications: the user must attend to all the tasks that require follow-up in order to continue using the CRM, otherwise the system will close the session preventing them from reconnecting. The objective of this type of notification is to guarantee compliance with the company's sales process. Although these types of notifications can be created by the users, in general they are generated by the system automatically as a result of said sales process.
+Non-blocking notifications: This type of notification seeks to remind the user about specific kinds of tasks or issues to consider during the sales process. Unlike the previous ones, these types of notifications are generally user-generated to facilitate their work.
 ==PARC==
-This process generates the opportunities and tasks that must be carried out as part of the PARC Agreement.
+This process generates the opportunities and tasks to be carried out as part of the PARC Agreement.
-It automatically creates the opportunity, inspection task, and follow-up. The corresponding dispatch is also created, so that it can be assigned to the team that will be conducting the visits as part of the PARC.
+It automatically creates the opportunity, inspection task, and follow-up. The corresponding dispatch is also made and assigned to the team conducting the visits as part of the PARC.
-At the same time, the system sends a summary to the account managers of all the tasks that were generated as part of a PARC agreement.
+Simultaneously, the system sends a summary to the account managers of all the tasks generated as part of a PARC agreement.
-This process runs weekly and the time these processes are generated can be fully customised by users with administrator permissions.
+This process runs weekly, and the time these processes are generated can be fully customized by users with administrator permissions.
 ==Batch Processes==
-The following processes don’t require user interaction to work. These are automated.
+The following processes don't require user interaction to work. These are automated.
 ===Finance process - Past Due Invoices===
-This process takes all the invoices with a debt greater than zero and performs a validation of the days corresponding to the payment terms and the creation date of the voucher.
+This process takes all the invoices with a debt greater than zero and performs a validation of the days corresponding to the payment terms and the voucher's creation date.
-This process takes those payments owed, calculates the corresponding penalty and updates the payment records so that the corresponding user can control and monitor them.
+This process takes those payments owed, calculates the corresponding penalty, and updates the payment records so that the corresponding user can control and monitor them.
-It does not have any type of notification.
+It does not have any notification.
 ===Get contact Process===
-This process creates a suppression list, that is, a list of contacts to whom no more emails should be sent.
+This process creates a suppression list- a list of contacts to whom the company should send no more emails. The process reads all the contacts with an assigned email and whose status is "rejected" and adds them to the suppression list.
-The objective is to avoid wasting time contacting potential clients who have already been contacted with no success.
+The objective is to avoid wasting time contacting clients who have already been approached with no success.
 ===RPH Process - Nurture process===
@@ Line 51: / Line 47: @@
 This process begins once the state of an RPH is changed to "nurture P2".
-When it is changed, the RPH automatically goes to a pool for which the dates and templates of the mails that must be sent as part of the nurture P2 process are established.
+When changed, the RPH automatically goes to a pool of dates and email templates to be sent as part of the nurture P2 process.
-This process takes all the RPHs that are in that pool, takes the corresponding template, performs the data replacement and sets up the email that should be sent. Then look for the next template and update the record with the corresponding number of days in which a new email should be executed.
+This process takes all the RPHs in that pool, takes the corresponding template, performs the data replacement, and sets up the email. The system looks for the next template and updates the record with the corresponding number of days when the system should send a new email.
-This process is repeated until all the templates that must be executed as part of the Nurture P2 process have been sent.
+This process is repeated until all the templates- part of the Nurture P2 process- have been emailed.
-In the event that no response is received, the system will change the RPH status to “closed” due to inactivity.
+If no response is received, the system will change the RPH status to "closed" due to inactivity.
 This process runs once a day.
@@ Line 63: / Line 59: @@
 ===Inbound/ outbound emails===
-This process is for reading emails. All emails, both sent from the CRM, and sent and received through other email service providers are saved in a backlog of the system.
+This process is for reading emails. All emails, both sent from the CRM and sent and received through other email service providers, are saved in the system's backlog.
-Through a security token the system reads the emails from the user's email account inbox.
+Through a security token, the system reads the emails from the user's email account inbox.
-Every time you read an email, it creates a data table within the CRM, and in turn establishes a tag for those emails sent from the CRM.
+Every time you read an email, it creates a data table within the CRM, and in turn, establishes a tag for those emails sent from the CRM.
-This process is responsible for keeping all the emails sent between our advertisers and the Leads, for instance.
+This process is responsible for keeping all the emails sent between our advertisers and the Leads.
 ===Bug detector===
-It is a process that runs daily looking for errors. This process sends the CRM administrator a report with the system errors found.
+It is a process that runs daily, looking for errors. This process sends the CRM administrator a report with the system errors found.
 ===Expired Jobs===
-Every 30 minutes the system scans the database searching for all those jobs (dispatches and tasks) with a 3 hours delay. Then it sends an alert to a designated list of users with either the owners or managers for the job.
+Every 30 minutes, the system scans the database, searching for all those jobs (dispatches and tasks) with a 3 hours delay. Then it sends an alert to a designated list of users with either the owners or managers for the job.
 =Quick Access=