How to optimize an online store. Part 1. Automatic calling to incoming leads
a week after the release previous article where I talked about the build bot for Telegram to me for advice asked the online store of wrist watches, who has already built some of the processes for their needs. With the growth of business they are faced with the problem of processing large amounts of incoming requests, and quick reaction to a request depends buy people the product or not.
Here I will describe their case study of process optimization of the online store with Corezoid.com and the ladies in the open access link to the process template, as described below.
What you need to do:
1) Add a lead in CRM (in this case, Bitrix24) c by filling all the required additional fields.
2) to Notify sellers about the Lida or error.
3) Notify the client about the successfully accepted order, and to tell you about the additional shares (to try to warm up the customer, increase the average check).
input:
1) Name and telephone number of the customer who interested in our product.
2) Defined by the ip client.
3) Timson client.
4) partner ID (Ref-link in cookies), from which came the request.
The solution was a bunch of API services through multiple Corezoid.com, namely Bitrix24 (CRM-system) + VoxImplant (service for the implementation of callback) + Telegram (messenger).
To send the lead to the processing in Corezoid need to make API request with a php script that retrieves data from a web form on the website. In their example it looks like this:
the
Object $data is formed of data that needs to be supplied in Corezoid.
Object $ops includes the ref parameter (referense) – the unique id under which the application will be fixed in Corezoid. If the application is already in the process of working with the same ref, then the second will not be added. In this example, they are used as ref ip address of the client.
The conv_id parameter responsible for the formation of a task in a specific process (Process ID).
URL to which we send data and conv_id process take from properties in the admin:

application process
The first thing the application gets to the start node. It differs from all the green. You can view this application and see the data that was on the input.

Since the store is actively using the affiliate sales, the first thing you need to determine from which partner the order came.
Bitrix24 through the API get ID and data of this partner.
For authorization to the API in the value of the parameter "auth" inline design, which allows you to dynamically get the value of the "access_token" from the process of its generation and updates. a Detailed description of this process documentation Corezoid.com
In this example, the data on the label of the partner is stored in the object "cookies" in the parameter "utm_source", which the company monitors after clicking on an affiliate link. Pass the value of this parameter in the API.

The next step for logic CODE in which the store handles the phone. The treatment consists in AutoCorrect the first number 8 on 7, and if the client to enter only 10 digits and the first starts at 9, then add 7 to the beginning, to the phone correctly processed by the script dialler.

Next step they send the application in a separate RPC-is the process "Create new lead [RPC]". It creates a lead in CRM, and returns the ID of Lida. The documentation Corezoid a a detailed description of this process.

In case of successful creation of Lida id back into a variable lead_id.
The next step, the application is copied in a process that will reach the customer. After you copy immediately goes to the next step without waiting for the return of any value from the process VoxImplant Call Robot. This is in contrast to RPC request, when the expected return data from another process.
Dialer logic first adds a variable with the length of the phone through the logic CODE. If the phone is longer than 11 digits, it goes to the final node because the phone is too long.
The following block obtains the current time in GMT in the variable timenow.

This is necessary in order to see if the lead came in the night or early in the morning, the store did not bother customer ring the bell, and just sent SMS about the successfully accepted order and the message will call back during working hours.
After the logic CODE in the same block checks the time of day and the fact of sending an SMS to the customer. If the message has not been sent and time is not working, then the request goes to the block "Send Night SMS". Then the store sends an SMS to the client through the logic of the API and get the response in a variable description. Then go to "sleep" in a timeout for 2 hours.

Application hanging in a timeout looks like this:

If time is working, then you need to call the customer and inform about the successfully accepted order, well, to tell you about any additional shares.
This task was implemented using the logic API, which launches the script on the service VoxImplant.

VoxImplant provides a call to a client and loses he prepared the entry about the successfully accepted order. Additionally, the code is embedded detection machine.
{the script code}
Next, the application goes to the logic in Corezoid Callback, which expects a response from VoxImplant with the results of the call. If we don't wait for an answer, something went wrong and the application crashes in manual handling. If everything is OK, and VoxImplant sent the results included in the allocation process results.
If the number is incorrect, the application goes to the final node, to call and send SMS on this number makes no sense. If the client did not pick up or now his phone is off, then our application goes to the status "Medozon" and takes the time out in half an hour.

If to the client successfully reached, then optionally notify via SMS that his order is successfully accepted, and close the application. In determining VoxImplant'Ohm answering the store also sends an SMS to the client, but then don't call, as it is unknown when the client takes up, and the store will spend money on every call. Additionally, logic can be embedded limit on the number of calls, and updating Lida in CRM with call status.

The process also provided notice in a Telegram to the seller, if the main process upon receipt of the list of partners will be an invalid token and you need to process the application manually. And notification of successfully added Lida. And in the process to dashboards, using your logic IF requests are distributed across nodes according to the criteria that define the partner or site and total amount of orders from each partner.
the following articles I will describe other cases of using Corezoid in online store and share templates:
That the most interesting, write in the comments.
The template described in the article, available the link. And own cases of combining different services into a single ecosystem, You can implement Corezoid.com.
Have questions?
Can contact me at Telegram or e-mail.
Article based on information from habrahabr.ru
Here I will describe their case study of process optimization of the online store with Corezoid.com and the ladies in the open access link to the process template, as described below.
What you need to do:
1) Add a lead in CRM (in this case, Bitrix24) c by filling all the required additional fields.
2) to Notify sellers about the Lida or error.
3) Notify the client about the successfully accepted order, and to tell you about the additional shares (to try to warm up the customer, increase the average check).
input:
1) Name and telephone number of the customer who interested in our product.
2) Defined by the ip client.
3) Timson client.
4) partner ID (Ref-link in cookies), from which came the request.
The solution was a bunch of API services through multiple Corezoid.com, namely Bitrix24 (CRM-system) + VoxImplant (service for the implementation of callback) + Telegram (messenger).
To send the lead to the processing in Corezoid need to make API request with a php script that retrieves data from a web form on the website. In their example it looks like this:
the
$data = (object) array('server'=>$_SERVER,'cookies'= > $_COOKIE,'post'=>$_POST );
$full = (object) array('ops'=> array( (object) array( 'ref'=>$ip,'type'=>'create','obj'=>'task','conv_id'=>'31754','data'=> $data)) );
$cmd = ( json_encode( $full ) );
$str = "curl 'https://www.corezoid.com/api/1/json/public/31754/e4203ff8f55f17595a46549d35dbd00d51d0879d' -H 'Accept: application/json, text/javascript, */*; q=0.01' --data '".$cmd."' --compressed";
$res = shell_exec($str);
Object $data is formed of data that needs to be supplied in Corezoid.
Object $ops includes the ref parameter (referense) – the unique id under which the application will be fixed in Corezoid. If the application is already in the process of working with the same ref, then the second will not be added. In this example, they are used as ref ip address of the client.
The conv_id parameter responsible for the formation of a task in a specific process (Process ID).
URL to which we send data and conv_id process take from properties in the admin:

application process
The first thing the application gets to the start node. It differs from all the green. You can view this application and see the data that was on the input.

Since the store is actively using the affiliate sales, the first thing you need to determine from which partner the order came.
Bitrix24 through the API get ID and data of this partner.
For authorization to the API in the value of the parameter "auth" inline design, which allows you to dynamically get the value of the "access_token" from the process of its generation and updates. a Detailed description of this process documentation Corezoid.com
In this example, the data on the label of the partner is stored in the object "cookies" in the parameter "utm_source", which the company monitors after clicking on an affiliate link. Pass the value of this parameter in the API.

The next step for logic CODE in which the store handles the phone. The treatment consists in AutoCorrect the first number 8 on 7, and if the client to enter only 10 digits and the first starts at 9, then add 7 to the beginning, to the phone correctly processed by the script dialler.

Next step they send the application in a separate RPC-is the process "Create new lead [RPC]". It creates a lead in CRM, and returns the ID of Lida. The documentation Corezoid a a detailed description of this process.

In case of successful creation of Lida id back into a variable lead_id.
The next step, the application is copied in a process that will reach the customer. After you copy immediately goes to the next step without waiting for the return of any value from the process VoxImplant Call Robot. This is in contrast to RPC request, when the expected return data from another process.
Dialer logic first adds a variable with the length of the phone through the logic CODE. If the phone is longer than 11 digits, it goes to the final node because the phone is too long.
The following block obtains the current time in GMT in the variable timenow.

This is necessary in order to see if the lead came in the night or early in the morning, the store did not bother customer ring the bell, and just sent SMS about the successfully accepted order and the message will call back during working hours.
After the logic CODE in the same block checks the time of day and the fact of sending an SMS to the customer. If the message has not been sent and time is not working, then the request goes to the block "Send Night SMS". Then the store sends an SMS to the client through the logic of the API and get the response in a variable description. Then go to "sleep" in a timeout for 2 hours.

Application hanging in a timeout looks like this:

If time is working, then you need to call the customer and inform about the successfully accepted order, well, to tell you about any additional shares.
This task was implemented using the logic API, which launches the script on the service VoxImplant.

VoxImplant provides a call to a client and loses he prepared the entry about the successfully accepted order. Additionally, the code is embedded detection machine.
{the script code}
Next, the application goes to the logic in Corezoid Callback, which expects a response from VoxImplant with the results of the call. If we don't wait for an answer, something went wrong and the application crashes in manual handling. If everything is OK, and VoxImplant sent the results included in the allocation process results.
If the number is incorrect, the application goes to the final node, to call and send SMS on this number makes no sense. If the client did not pick up or now his phone is off, then our application goes to the status "Medozon" and takes the time out in half an hour.

If to the client successfully reached, then optionally notify via SMS that his order is successfully accepted, and close the application. In determining VoxImplant'Ohm answering the store also sends an SMS to the client, but then don't call, as it is unknown when the client takes up, and the store will spend money on every call. Additionally, logic can be embedded limit on the number of calls, and updating Lida in CRM with call status.

The process also provided notice in a Telegram to the seller, if the main process upon receipt of the list of partners will be an invalid token and you need to process the application manually. And notification of successfully added Lida. And in the process to dashboards, using your logic IF requests are distributed across nodes according to the criteria that define the partner or site and total amount of orders from each partner.
the following articles I will describe other cases of using Corezoid in online store and share templates:
-
the
- organization partnership program (Bitrix24 + Corezoid + Google Sheets); the
- automation of courier (MoySklad + Corezoid + Telegram); the
- Check the status of an invoice (Cdek + Corezoid + Telegram); the
- Bot – checker the execution of business processes (Telegram + Corezoid + pic / s).
That the most interesting, write in the comments.
The template described in the article, available the link. And own cases of combining different services into a single ecosystem, You can implement Corezoid.com.
Have questions?
Can contact me at Telegram or e-mail.
Комментарии
Отправить комментарий