Once an application appears in Pyrus, it goes through several stages.
Distribution. The application appears in Inbox at the operator. He fills in the blank fields: indicates the type of application, client data and responsible person.
First line. The application is received by the person appointed by the operator. He communicates with the client based on his request directly in Pyrus. Once the issue is resolved, the specialist closes the application.
Note: Pyrus records the time of the first response to the client. This is important for analysis - in the summary you can estimate the time of the first response, including details by employee, and the average time of the first response.
Second line(escalation). If the first line specialist cannot resolve the issue, he escalates the request to the second line. The second line specialist sees the application in his Inbox and gets started. After resolving the issue, he closes the request or sends it to the first line so that a colleague can do it (according to the regulations in some companies, the first line specialist notifies the client about the result and closes the request).
Closing the application. Pyrus remembers the time when the request is closed as the time the issue was resolved. In the summary you can see the average resolution time for all applications. Closed tickets are stored in Pyrus. They can be found using the search function or in the registry.
Note: The decision time is only taken into account when the application is open. For example, a specialist talked with a client and sent the application to the archive an hour after the request. If the client responds after a week, the application will automatically be reopened. Let’s say that the second time the specialist responded in half an hour and again sent the application to the archive. The time that the application was in the archive is not taken into account, therefore total time solutions - one and a half hours.
Clue: you can set any order for processing applications. In the route editor, you can add and delete stages of working with an application and specify who is responsible for the decision at each step. To automatically distribute requests depending on the entered data, use conditional routing.
Response to client
To respond to the client, select the tab in the comment input field Email mail, Telegram, Viber, Facebook or VK, write the text and press the button Send. The client will receive a message via the channel you choose - by email, Telegram, Viber, Facebook or VKontakte. If he responds to the message, his response will be displayed in the application, in the comments thread.
Ready-made answers are also available here - text templates that are suitable for frequently recurring situations - for example, clarifying the order number, requesting a screenshot of an error or a scan of a document. To use a canned answer, click the canned answers icon and select suitable option. .
Canned answers are grouped according to the cases for which they are suitable. Select the group on the left and the desired answer on the right.
You can edit groups and answers or add new ones on the Canned Answers page.
If the customer's issue is resolved, click Submit and complete. If you have given an interim answer but are still working on your application, click Send.
If the support specialists closed the task, and the client wrote a response letter after that, the request will automatically open again, and the person responsible will see it in their Inbox.
It happens that clients write to an old application for new topic. For example, a client contacted us because he couldn’t pay for his order, and a week later he decided to ask a question about the terms of service. It’s quite natural to find old correspondence with the support service and write a response email. But the topic is new, and for statistics it is better that it be a separate task. You can make sure that the old request is not reopened, but instead a new one is created.
In the example above, if a client writes to an old ticket within a week after it is closed, it will be re-opened and support will continue to communicate with the client in it. If he writes a week after closing or even later, a new application will be created.
When working with an application, it is important to send an SMS message to the client. For example, notify that the bank has approved a loan application or inform that you have issued a refund and it will soon be credited to the client’s card. You can send SMS directly from Pyrus, in the form Client request. Simply select a prepared answer, change the wording if necessary, and click the send button.
To make the appropriate settings and send SMS messages, please.
Internal discussion
You can work with a request as with a regular Pyrus task: invite colleagues and discuss details in the comments on the tab Internal correspondence. The client will not see these actions.
When processing a client's request, a support specialist will need the history of his requests. Perhaps the client constantly has the same problem, or perhaps support specialists ignored his first messages.
The request history is located in the panel on the right, in the section Similar tasks:
You can open any task from the list and read how colleagues helped the client before. Tasks are defined as similar if they contain the same email address or customer phone number.
Escalation
It happens that a first-line specialist cannot resolve the issue on his own: for example, he lacks knowledge or authority. In this case, he can do his part and pass the request to the next level. To do this, just open the application, on the tab Internal correspondence press the button 2nd line and press Send.
As usual, you can invite a colleague to solve a problem: start typing his name on the keyboard, select him from the list and add explanatory text.
Application statuses
At one stage the application may be in different states. To track them, it is convenient to use statuses. Let’s say a specialist receives an application and transfers it to the “In progress” status. If you need to clarify information, asks the client a question and changes the status to “Request for information.” And when the problem is solved, it sets the status to “Evaluation”.
Available statuses can be set on the tab Settings in the form template.
Statuses reflect the stages of application processing; seeing the status of the application, you immediately understand what state it is in.
The system provides four main statuses for applications: new, in processing, processed and postponed. As soon as an application enters the system, it is automatically assigned the New status, then employees can see received visitor applications in the CRM - Applications tab.
To display current data on application statuses, processing times, etc. use the Update button. This button will help you get last changes according to requests without overloading the page and without leaving this tab.
Possible application statuses:
- new: the application has just entered the system and employees have not yet processed it. The title and status of the application New are in bold;
- in processing: the employee whose full name is indicated in the employee’s full name column is currently processing the application, i.e. he has an application processing window open;
- processed: the application was processed by the employee whose full name is indicated in the employee’s full name column;
- postponed: the application was postponed by the contractor for a certain period (the reason may be a lack of calls or unavailability of the subscriber).
Let's take a closer look at each of the application statuses.
Status New
New applications are considered to be unreviewed applications that came from the contact capture form into the system, as well as those applications for which an employee with the Manager role set the New status manually (the reason may be incorrect processing of the application or inaccurate information received as a result of communication with the client).
You can return the application to the New status from the CRM - Applications page, using the button.
An application is considered new until an employee begins processing it.
If an employee closes the application processing window without processing it and without identifying the client, the application returns to the New status.
When a new application enters the system, all users receive a notification in the site header about the receipt of a new application. Clicking on this icon opens the application processing form.
Status In processing
The Processing status is assigned to an application if an employee has opened the application processing window. While this window is open, the application is in the Processing status.
The table with the list of applications records the status of the application, the full name of the employee processing the application, as well as the date and time when processing the application began.
Status Processed
An application is considered processed only if the employee in the application processing window selected the Application processed option and clicked the Save button.
The application table records the full name of the employee who processed the application, the time of completion of processing, as well as the duration of processing the application.
Status Postponed
An employee accepting a request for work can postpone its completion for any period of time.
The reason may be the client’s request to call back or a missed call.
In this case, in the application processing window, the employee selects the Application postponed option, indicates the time and saves.
Registration of applications
Okdesk, as a system for recording customer requests, offers several ways to register requests:
The application registration method is determined automatically and displayed on the application card:
To register applications by the dispatcher in the system interface, you must click on the “+ New application” button at the top of the screen:
After clicking on the “+ New Application” button, a window will open in which you need to fill in the “Subject” (required field) and “Description” fields.
Also on the form you can indicate the connection of the application with (the contact person of the application can be an employee), , , and select for the application.
On the application creation form, Okdesk automatically calculates the planned date and time for resolving the application according to the standards (see more details). If necessary, the planned decision date can be set manually by clicking on the “Specify manually” button.
An application is created by clicking on the “Create” button on the application creation form.
Newly created tickets and tickets where last comment was left by a contact person, are highlighted in bold.
Application Processing Standards (SLA)
One of the key criteria for the quality of services is the service company’s compliance with standards at the time of resolving applications. These standards are set out in the service agreement and may depend on various parameters: the importance of the client, the priority of the application, etc. Often fixed standards that determine the quality of services are called the term SLA (Service Level Agreement, or Service Level Agreement).
The “Request Processing Standards (SLA)” module of the Okdesk system allows you to take into account SLA to control the time for resolving requests, response time to requests and service schedules in relation to specific clients, types and priorities of requests, as well as the time of registration of requests.
As a standard for processing applications, Okdesk uses the standard for resolving an application - the time within which the service company must meet to resolve the application (taking into account the client’s service schedule). For more transparent work and meeting customer requirements, Okdesk has another parameter - response time. The reaction time is the time before which a new application must be accepted for processing. From Okdesk’s point of view, the fact that an application is accepted for work is either a change in the status of the application, or the employee adding the first response - the first public comment.
Planned resolution time and planned response time for tickets are superimposed on the service schedule and are calculated automatically in Okdesk when tickets are registered. If necessary, the planned decision time can be set manually on the application registration form.
The service schedule, planned solution time and planned response time are set in the “Application \ Application Processing Standards (SLA)” subsection of the “ ” section.
To add a new service schedule, you must click on the “+ Add service schedule” button on the “Application service schedules” tab.
When adding a service schedule, you can specify exception days for which the service schedule will not depend on the day of the week (for example, national or regional holidays, shortened days).
To add a new SLA rule, click on the “+ Add Rule” button on the “SLA Determination Rules” tab.
- Application type;
- Application priority;
- Client category;
- Client;
- Application registration time.
- Maintenance schedule;
- Standard reaction time;
- Standard decision time.
When you click on the “Create” button, the rule is added to the “Rules for calculating standards” table.
The rules from the table for calculating standards are sorted “from top to bottom” until the first included rule is found, the conditions of which are met by the application. If necessary, rules can be moved around the table and temporarily disabled.
When calculating the planned time for resolving requests, the planned response time and displaying time parameters in the interface, the company’s time zone is taken into account (see more details in the “ ” section).
Order routing
Okdesk allows you to set rules for routing requests when they are created.
The order routing table is configured in the “Orders\Order Routing” subsection of the “Settings” section. In order to add a new routing rule, you must click on the “+ Add rule” button.
In each rule, you must specify the values of the defining parameters of the application and the values of the defining parameters of the application. When you click the button, a modal window opens in which the defining parameters are highlighted with the subheading “If”, and the parameters being defined are highlighted with the subheading “Then”.
The defining parameters of the application include:
- Application type;
- Application priority;
- Registration method;
- Client category;
- Application registration time;
- Additional attributes of the request of the "Value from the list" type.
The specified application parameters include:
- Responsible;
- Observers (employees);
- Observers (groups).
When you click the “Create” button, the new rule will be added to the routing table.
The rules from the routing table are sorted from top to bottom until the first included rule is found whose conditions the application satisfies. If necessary, rules can be moved around the table and temporarily disabled.
You can also set a default Owner and default Observers for an account.
The “Default” value for the owner determination rule implies the following logic:
- If a service object is defined for an application and a responsible manager is determined for this service object, then the responsible manager of the service object is appointed responsible for the application;
- If a contact person is defined for an application and a responsible manager is determined for this contact person, then the responsible manager of the contact person is assigned as responsible for the application;
- If a company is defined for an application and a responsible manager is determined for this company, the responsible manager of the company is assigned to be responsible for the application;
- If responsible managers are not defined for the company, contact person and service object, then the person responsible for the request is assigned by default from the account settings.
The logic for defining “Default” observers is similar to defining the responsible one. But when creating an application, all observers (employees and groups) are summed up by default, specified in the settings, on the cards of companies and contact persons, being divided into two categories: “Observers (employees)” and “Observers (groups)”.
You can also read about order routing in .
Application statuses
Application statuses in Okdesk are required for display current state processing applications. By default, the system provides 4 statuses, but it is possible to expand them:
- Open;
- Postponed;
- Solved;
- Closed.
From the “Open” status, an application can be transferred to the “Postponed” and “Resolved” statuses.
From the “Pending” status, an application can be transferred to the “Open” and “Resolved” statuses.
From the “Resolved” status, an application can be transferred to the “Closed” and “Open” statuses.
The status “Closed” is final.
All new applications are created with the “Open” status.
In the status “Postponed” for the application, it is not taken into account (if the scheduled decision time was calculated automatically, then when resuming the application to recalculate the planned decision time, the time spent in the deferred state will not be taken into account).
When transferring to the “Pending” status, the user must indicate until what time the application is postponed (if the application is not manually resumed before this time, Okdesk will automatically return the application to the “Open” status).
The separation of the “Resolved” and “Closed” statuses is necessary to implement confirmation of the decision of the application by the client’s contact person. The “Resolved” status means that the application has been resolved from the customer service point of view. The status “Closed” means confirmation of the decision of the application by the client. For this purpose, contact persons have the ability to confirm the closure of applications or their renewal. Okdesk also allows you to configure a timeout to automatically close resolved tickets. The timeout is configured in the “Application \ Application Processing Standards (SLA)” subsection of the “ ” section.
Changing the application status is available from the application card:
And also on the list of applications:
If necessary, the set of statuses can be expanded in the “Application \ Application Statuses” subsection of the “Settings” section.
To add a new status to the system, click on the “Add” button above the table. In the modal window that appears, you need to fill in the fields and save.
Additional order parameters
For applications, it is possible to specify additional parameters that will be displayed on the application card.
To display an additional attribute on the list of requests, you need to include the attribute in the fields. To change the composition and order of fields on the list of applications, you need to click on the gear icon under the list display view.
For all additional attributes, you can set visibility for employees by role and customer contact persons, and also determine whether the attribute must be filled out on the application creation form:
Additional parameters are set in the “Orders\Order Attributes” subsection of the “Settings” section.
Application priorities
For requests in Okdesk, you can specify a priority that affects the order in which they are executed when planning the work of the service team.
The priority of the application can initially be set on the application creation form:
During subsequent processing of the application, the priority can be changed on the application card. In the application card, priority will be displayed as a circle with a color and name:
In the list of applications, priority is displayed as a corner (in the upper left corner of the block) with a color corresponding to the color of the priority. When you hover over the corner, an alt-tip pops up with the name of the request priority.
Priorities are set in the “Application \ Order Priorities” subsection of the “Settings” section:
To add a priority with text, click on the “Add” button. In the window that appears, fill in the fields and save.
If necessary, the “Application priority” field on the application creation form can be hidden for contact persons or allowed to be filled out. This setting is located in the subsection “Orders \ Order attributes \ System attributes of orders”:
Types of applications
For requests in Okdesk, you can specify a type that affects the planning of the service department and subsequent statistics.
When creating a new request, you can specify the type of request in the modal window:
In the future, it is possible to edit the request type parameter in the request card.
Application types are set in the “Orders\Order Types” subsection of the “Settings” section.
You can create internal tickets in Okdesk. Tickets with a type set to "Internal" are not displayed to customers in the customer portal, and client alerts are not sent for such tickets. Internal requests can be used for internal tasks for the client: issuing invoices, preparing commercial proposals, and so on (that is, for any tasks related to the client, but which he does not need to know about).
To create a new type of application, you must click on the “+ Add” button located above the table. In the window that appears, fill in the fields and save.
If necessary, the “Application Type” field on the application creation form can be hidden for contact persons or allowed to be filled out. This setting is located in the subsection “Orders \ Order attributes \ System attributes of orders”:
Responsible for applications
Okdesk allows you to specify the employees responsible for resolving requests. The person in charge is appointed from a list of employees divided into. Responsibility for an application can be assigned to either one employee or a group of employees.
The person responsible can be specified on the application creation form. During subsequent processing of the application, the person responsible can be changed on the application card:
And also on the list of applications:
All employees responsible for applications receive automatic notifications about events with applications, and during the period of work you can view statistics by responsible employees.
If the application is not a personal responsibility, but a group responsibility, then notifications on the application go to the employees specified in the “List of employees for notifications” parameter of the group. You can set up a list of employees for notifications in the “Employees\Employee Groups” section.
Observers
Observers (employees or groups) of an application are company employees who, for one reason or another, need to monitor the stages of the application.
The list of observers is displayed in the application card. There you can subscribe to monitor the application or edit the list of observers.
Observers can receive Email and SMS notifications about events with an application. Observer notification templates are configured in the “Email Alerts” and “SMS Alerts” subsections of the “Settings” section.
Commenting on applications
Company employees and customer contacts can leave comments on applications. At the same time, when adding a comment, company employees can indicate whether the comment is private or public, and also attach a file to the comment.
Public comments are visible to all users (company employees and customer contacts in ). Private comments are visible only to company employees.
If necessary, in the “General system settings” subsection of the “ ” section, you can specify the default publicity or privacy of all comments:
In the comments, you can indicate any employee or contact person of the company associated with the application. In order to mention an employee or contact person in a comment, you need to enter “@” and indicate the required person in the selection window. When mentioned, an email notification is sent with the text of the comment and a link to the application.
By default, the price list includes the service “Services with time-based payment" If necessary, it can be edited or hidden in the archive (like any other lines added later).
To add a new line, click on the “+ Add” button. In the window that appears, fill in the fields and save.
- Section - select one of the options “Service”, “Work” or “Product” (these sections are intended only for the convenience of sorting price list lines when creating an application specification);
- Set a service, work or product code - a unique identifier within the price list;
- Set a title;
- Specify the unit of measurement;
- Set standard price;
- Specify VAT.
Okdesk allows you to set a ban on editing the specifications of applications that are in the established statuses. A ban on editing specifications can also be set for certain employee roles.
The price list, if it is not necessary, can be disabled in "Settings\General system settings\Activate system functions".
Formation of application specifications
For each application, you can specify the specification of paid work, services or products, generated according to the price list. To add a new line of application specification in the “Specification” section, you must click on the “+ Add” button. In the window that appears, select a job, service or product, indicate the quantity and discount, as well as the performer. The system will automatically calculate the cost.
The generated specification can be downloaded as an invoice (in Excel format). In particular, it can be uploaded by the client’s contact person to .
Account details are set in the “General system settings” subsection of the “Settings” section.
After creating a printable form, you can generate ready documents directly from the application card or equipment card. These documents can be attached either as files to the application or equipment, or you can immediately send the document for printing.
You can read more about the functionality of printed forms in .
Labor costs according to requests
Okdesk provides the ability to keep track of employee labor costs related to customer service.
All labor costs are associated with the application. In turn, the application is associated with the client. Thus, the system provides information on all labor costs by employees, applications and clients.
The amount of labor costs associated with the application is displayed in the “Time Spent” block of the application card:
To write off labor costs for an application, you must click on the “+ Write Off” button. You can view the log of all labor costs of an application by clicking on the “show all” link button (the link is not displayed if the time written off for the application is 0).
Evaluation of applications
To control the quality of services, Okdesk allows customer contacts to rate completed requests.
In order for contact persons to be able to rate applications, it is necessary to enable the rating of applications in the subsection “Settings \ Applications \ Rating applications”:
When an employee transfers an application to the “Resolved” status, a notification is sent to the client’s contact person about the decision of the application. The client’s contact person from the “one-click” notification will be able to evaluate the application (or, if necessary, resume work on it):
When you subsequently work with the application, the assessment can be seen on the application card.
In the application card, the score will be displayed as a smiley icon:
Analytics based on customer ratings are available in the Customer Satisfaction report.
List of applications
Recurring requests
The obligations of a service company to clients often consist not only of high-quality processing incoming incidents and service requests, but also from the execution of mandatory regularly scheduled activities on the client’s infrastructure or equipment. It's about routine maintenance ah, which must be carried out starting from the date of conclusion of the contract, and with a specified frequency.
Previously, Okdesk allowed you to manually create future requests. When accepting a new client for service, the dispatcher could manually enter required quantity of the same type of routine maintenance with a given execution date. Although this mechanism made it possible to “get out of the situation,” it was not complete. But now Okdesk has implemented a module automatic creation planned work according to a given schedule.
Read more about recurring requests in .
Exchange of applications
Okdesk has implemented the “Request Exchange” module, which allows companies that use Okdesk in their work and have partnerships to transfer service requests to each other for execution.
To allow the transfer of applications between partner accounts, a connection must be established. This requires either generating a pairing key and sending it to your partner, or using a key received from your partner.
To generate a key, go to the “Exchange of applications” subsection of the “Settings” section (the “+ Generate connection to establish a connection” button). Send the generated key to the partner with whom you want to establish a connection:
To establish a connection using the key received from the partner, you need to click on the “Establish connection using the key” button in the “Exchange of applications” subsection of the “Settings” section and enter the key received from the partner:
When the connection between the accounts has already been established, you can start exchanging applications with your partner. To transfer an application to a partner, on the application card, click the “Transfer to Partner” button:
In the window that opens, enter additional information:
- Transfer information about the end client - the partner will see data about the client on the submitted application card in his account;
- Transfer files - you can select application files that will be transferred to the partner.
Please note that you can chat and exchange files with your partner:
- For a comment or file, you can check the “Transfer to partner” checkbox - the files and comments will appear in the partner’s application (as public)
- Public comments and files from the partner's application will be duplicated in the original application as private. Private comments and files in a partner's application will not be duplicated in the original application.
You can also track the execution of your partner’s request:
If necessary, you can enable SMS and Email notifications to the person in charge and observers of the application “About the decision of the partner application”.
After the partner’s application has been transferred to the “Solved” status, the “Evaluate” button for the solution of the application transferred to the partner will appear in the original application:
Integration with telephony in Okdesk is carried out using the Simple Calls service, which connects various IP-PBX systems with CRM\Helpdesk systems (including Okdesk).
To set up integration, you need to obtain access details for the service on the website and independently configure the integration of your telephony system with the “Simple Calls” service.
To set up integration with the “Simple Calls” service on the Okdesk side, you must provide connection details. This setting is carried out in the subsection “Settings / Integration with telephony / Simple calls”.
On the editing form you need to fill in the fields and save:
- server address (provided by the “Simple Calls” service);
- password (provided by the “Simple Calls” service);
- the number of last digits of the number to search (the search for a number is carried out by matching the last digits of numbers in the client database with the last digits of the identified number).
After setting up and enabling the integration, on employee cards you must indicate their internal extension telephone numbers (corresponding to the numbers configured in your PBX):
Incoming calls
After the procedure for connecting to telephony has been successful, you can begin receiving calls from clients in Okdesk and recording them.
At incoming call A pop-up window will appear at the bottom right with the caller’s data and the “New Application” button for subsequent registration and processing of the application:
A client in Okdesk is identified by the “Phone” field for Companies and the “Phone” and “ Mobile phone” for contacts and individuals.
Outgoing calls
In addition to receiving calls in Okdesk, you can make outgoing calls to customer numbers.
In order to make a call from a company/contact person’s card, click on the client’s phone number. The window that opens will indicate the number (which can be changed if necessary). Next, click on “Call”:
After this, the telephony system will make a call to the desired subscriber.
Telegram bot
Bots in the Telegram messenger are special accounts that are not assigned to people, and messages sent from or to them are processed external system(in particular, the Okdesk system). At the same time, for the user, communication with the bot looks like regular correspondence with another person.
You can create your own client bot for Telegram and connect it to Okdesk. This will allow customers to contact customer service via messenger. Thanks to the Telegram bot, customers will be able not only to create new requests, but also to add new comments, close requests and evaluate the quality of service. Read more about the settings and capabilities of the bot in .
Teamviewer integration
Teamviewer is a popular tool for remote support for PC and mobile device users. Teamviewer allows you to connect to the desktop of a supported client to help users set up information systems and programs, as well as for diagnosing and eliminating incidents. In other words, this important tool, which helps service companies reduce costs for customer service and reduces the time it takes to resolve requests.
Okdesk has integration with Teamviewer. It allows you to enhance the effect of using two tools separately. Now, to initiate a remote support session, you no longer need to go to the Teamviewer interface, and session statistics are displayed in the Okdesk interface.
Read more about settings for connecting Teamviewer to Okdesk in .
Processing applications by email
Okdesk allows you to automate the process of receiving email requests from clients and subsequent email correspondence regarding the application.
To set up automatic processing Email You must specify the connection details to the mail server. This setting is carried out in the “Processing incoming email” subsection of the section.
Registration of applications
All letters received by email from the support service will be registered in the system as requests, or will be attached as comments to existing requests (see below). All files attached to letters will be attached to applications.
Okdesk will automatically determine the linking of requests to contacts and companies by the sender’s email (if the request was sent from the email of an unknown contact person, but the domain in the sender’s address matches the domain of a company from the customer database, Okdesk will link the new request to the company found by domain).
In addition, if the “Create contacts using unknown emails” option is set in the mail processing settings, Okdesk will automatically create new contacts and associate created requests with them.
Correspondence regarding requests
When sending notifications about events with applications, Okdesk puts a special marker (id of the application in the system) in the subject of the letter, thanks to which email correspondence regarding the application is available.
The logic for processing a letter containing an application token is as follows:
- An application with this marker exists:
- The text of the letter before the separator (in sent letters, Okdesk inserts a separator to cut off the entire correspondence history) is added as a comment to an existing request.
- The author of the comment indicates the employee or contact person found by email (if neither the employee nor the contact person by email are found, the comment is added on behalf of the earliest created employee with “Administrator” rights).
- Letter files are attached to the application (except for files whose size exceeds the established limit).
- Comments added by email are marked with an envelope icon, which, when clicked, will display Additional Information about the letter.
- An application with such a token does not exist, or the application token is missing: a new application is created.
Web application registration form
Web form is an Okdesk functionality that allows you to embed a special window into the Company’s website (or individual pages of the website) through which website visitors can ask a question or contact customer service.
The web form consists of two parts. Form call shortcut:
And application forms with specified fields:
Settings color range, texts and a set of fields for a Web form is carried out in the “Setting up a Web form” subsection of the section.
To place a Web form on the site, you need to copy the script generated by clicking on the “Code to insert on page” button:
And insert it before the tag
