Skip to content

Commit 2276474

Browse files
Vadym-KharchenkoVadym-Kharchenko
committed
Add documentation for request processing and working with deals
1 parent 851207b commit 2276474

5 files changed

Lines changed: 306 additions & 4 deletions

File tree

‎docs/help/commercial-requests-management.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ and how to work effectively with the request list.
2020

2121
## **What are Commercial Requests?**
2222

23-
A request includes essential details about a customer’s inquiry — what they want to purchase,
23+
A request includes [essential details](request-processing.md) about a customer’s inquiry — what they want to purchase,
2424
who they represent, and their contact information. These records can appear in the CRM in
2525
several ways:
2626

‎docs/help/deals-management.md‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ description: Learn how to manage deals in Django CRM, including deal creation, a
88
The **deal** is the main [CRM](../index.md) object used by sales managers to
99
track commercial work with potential and current customers.
1010
It stores the full history of communication, negotiation, and decision-making —
11-
from the initial request to the successful closing (or rejection) of the deal.
11+
from the initial [request](request-processing.md) to the successful closing (or rejection) of the deal.
1212

1313
This page explains how to work with the deal list and use available tools for
1414
organizing and analyzing sales activities.
@@ -110,5 +110,6 @@ This is especially useful for data sharing or reconciliation with trading partne
110110

111111
## Related Topics
112112

113-
- [Managing Commercial Requests in Django CRM](commercial-requests-management.md)
113+
- [Working with Deals](working-with-deals.md)
114+
- [Managing Commercial Requests](commercial-requests-management.md)
114115
- [CRM Software Overview](../features/overview.md)

‎docs/help/request-processing.md‎

Lines changed: 118 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,118 @@
1+
---
2+
title: Request Processing
3+
description: Learn how to effectively process commercial requests in Django CRM, including verifying request details,
4+
enriching missing information, linking to existing CRM entities, and creating deals or cases.
5+
---
6+
7+
# **Request Processing in Django CRM**
8+
9+
Request processing ensures that every inbound client inquiry is converted into accurate, complete,
10+
and actionable CRM data. This page guides users through verifying request details, enriching missing information,
11+
linking the request to existing CRM entities, and ultimately creating a deal or closing the request as a case.
12+
Effective request processing strengthens data quality, reduces duplicates, and improves follow-up speed.
13+
14+
---
15+
16+
## **Purpose of request processing**
17+
18+
Request processing focuses on **verifying** and **enriching** client contact information before passing the inquiry to the sales pipeline.
19+
Accurate request handling ensures the verification and completeness of customer data.
20+
This serves two critical functions:
21+
22+
1. Ensuring the sales team can reach the client.
23+
2. Matching the inquiry to existing CRM records to avoid duplicate [leads](lead-management.md),
24+
[contacts](contact-management.md), or [companies](company-management.md).
25+
26+
Most client [requests](commercial-requests-management.md) are generated automatically when a visitor submits a website form or sends an email.
27+
Before the request becomes a deal, all information must be checked for accuracy and completeness.
28+
29+
Once **validated**, a deal must be created. For users with the operator role,
30+
the request owner must be reassigned to a sales manager before creating the deal.
31+
Note that deals cannot be created from requests marked as duplicates or as cases/incidents.
32+
33+
---
34+
35+
## **Request counter and assignment workflow**
36+
37+
The left-panel includes a request **counter** that helps CRM users track incoming workload.
38+
39+
- The green value shows the number of new pending requests that need processing.
40+
- The red value indicates requests older than 24 hours that are still unassigned to a sales manager.
41+
42+
A request disappears from the counter once a sales manager is assigned as the owner.
43+
44+
---
45+
46+
## **Case and incident handling**
47+
48+
If a request does not require payment or sales follow-up, it must be marked as a **case/incident**.
49+
This replaces the Create Deal button with a Close button.
50+
Cases appear green in the request list and turn gray after closing. These items are excluded from the sales workflow
51+
but remain available for support tracking.
52+
53+
---
54+
55+
## **Working with the action buttons**
56+
57+
When you open a request, a set of gray action buttons appears at the top.
58+
These actions do not modify or save request data. They allow you to:
59+
60+
- Create an email linked to the request
61+
- View all email correspondence
62+
- Import an email manually from your mailbox (emails with the request ticket are imported automatically)
63+
- Print the request
64+
- Copy the request to create a new one using the same data
65+
- View the change history
66+
67+
Hovering over any button shows a **tooltip** explaining its function.
68+
69+
---
70+
71+
## **How to correctly fill out contact name fields**
72+
To maintain record accuracy, CRM provides three separate fields for names:
73+
74+
- First name
75+
- Middle name
76+
- Last name
77+
78+
Only **one word** is allowed in the first and last name fields. If a full name contains more than three words,
79+
all additional words should be placed in the middle name field.
80+
This helps prevent data inconsistency and improves matching accuracy.
81+
82+
---
83+
84+
## **How to avoid duplicate company records**
85+
86+
Pay careful **attention** to the Company name field. Customers often provide shortened or abbreviated company names,
87+
which may cause duplicate company entries.
88+
If the company already exists in the CRM, enter abbreviations and alternate spellings in the "**Alternate Names**"
89+
field of the company profile instead of creating a new company.
90+
91+
---
92+
93+
## **Translation, remarks, and product selection**
94+
95+
- If a request arrives in a foreign language, use the Translation field to provide a translated version.
96+
- This translation will also appear in the deal.
97+
- Enter internal comments or clarifications in the Remark field.
98+
- Use the Products field to select the products or services requested.
99+
This improves CRM reporting quality and enables product-based filtering in the request list.
100+
101+
---
102+
103+
## **Relationship validation and automatic linking**
104+
105+
When creating a request, Django CRM attempts to find **matching** clients in the database.
106+
If a match is found, the system links the request to an existing lead or contact and company.
107+
These links appear in the Relationships section, accompanied by a checkbox indicating that the relationships need verification.
108+
Review and confirm these links, and then clear the checkbox once validation is complete.
109+
110+
If no match is found, the CRM will create a **new lead** or contact and company (depending on available data) during deal
111+
creation and automatically link them to the request.
112+
113+
---
114+
115+
## **Viewing email conversations**
116+
117+
The bottom of the request page displays the last four emails exchanged in the conversation.
118+
This gives users immediate context without navigating away from the request.

‎docs/help/working-with-deals.md‎

Lines changed: 181 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,181 @@
1+
---
2+
title: Working With Deals in Django CRM
3+
description: Learn how to effectively manage deals in Django CRM, including understanding the deal page layout,
4+
using interface actions, and utilizing deal data for sales analytics and reporting.
5+
---
6+
7+
# **Working With Deals in Django CRM**
8+
9+
The Deal page in CRM is your central workspace for managing the full sales process —
10+
from initial inquiry to final payment. This page collects key client information, communication history,
11+
workflow steps, and financial data to help sales teams work efficiently and keep all deal-related information organized.
12+
13+
Below is a detailed overview of each section and function available on the Deal page.
14+
15+
---
16+
17+
## **Interface Actions and System Behavior**
18+
19+
### Gray-Button Actions
20+
21+
**(Do not save or modify deal data)**
22+
Some buttons on the Deal page are designed for creating related objects without altering the deal itself:
23+
24+
- **Office Memo** – Creates an internal memo linked to the current deal. Each memo includes a shortcut for users with access to quickly open the deal.
25+
- **Message** – Opens a chat message form.
26+
27+
- If the chat already contains messages, a *View chat* button appears.
28+
- If there are unread messages, the button turns **red**.
29+
30+
### Email Synchronization
31+
32+
CRM automatically syncs the assigned salesperson’s mailbox using deal tickets embedded in emails.
33+
At the bottom of the deal page, you’ll see the **four latest emails**.
34+
Use the **two-envelopes icon** to view the full list of email correspondence.
35+
If an incoming email did not include a deal ticket, you can attach it manually using the **Import** button.
36+
37+
### Additional Tools
38+
39+
- **Deals** – Shows the number of deals associated with the same client. Clicking opens the full list.
40+
- **Reminder (clock icon)** – Creates a reminder related to this deal. All reminders can be viewed in the **Common** section.
41+
- **History** – Displays the full audit log: who changed what, when, and how.
42+
43+
---
44+
45+
## **Section 1: Main Information**
46+
47+
Here you can manage basic deal attributes:
48+
49+
- **Deal name** – Editable at any time. By default, inherited from the originating request.
50+
- **Request information** – View key details from the request. Click **Request** to open it.
51+
- **Important flag** – Highlight the deal in the Deal Manager and enable filtering by importance.
52+
- **Closing the deal** – Select a closing reason from the drop-down list to close the deal.
53+
54+
*Related topic* - [Managing Requests](commercial-requests-management.md)
55+
56+
---
57+
58+
## **Section 2: Contact Information**
59+
60+
This section shows whom you're working with and provides quick communication tools:
61+
62+
- **Contact or Lead** – View the person involved in the deal and navigate to their profile.
63+
- **Communication shortcuts:**
64+
65+
- Send an **email**
66+
- Message via **WhatsApp**
67+
- Message via **Viber**
68+
- **Company website** – Open the customer’s website.
69+
- **Company profile** – Navigate to the customer’s company page.
70+
71+
*Related topics:*
72+
73+
- [Managing Leads](lead-management.md)
74+
- [Managing Contacts](contact-management.md)
75+
- [Managing Companies](company-management.md)
76+
77+
---
78+
79+
## **Section 3: Deal Progress and Workflow**
80+
81+
This section supports the operational management of the sales process:
82+
83+
### Stage Management
84+
85+
Select the current **deal stage** from the predefined list. These stages are used to build Sales Funnel report.
86+
87+
### **Financial Fields**
88+
89+
- **Total amount and currency** – The overall value of the deal.
90+
- After adding payments, the CRM automatically calculates:
91+
92+
- **Paid amount**
93+
- **Expected amount**
94+
95+
### Next Step Planning
96+
97+
- **Next step** – Briefly describe the upcoming action.
98+
- **Step date** – Select the deadline.
99+
- **Remind me** – Automatically creates a reminder.
100+
101+
### Workflow and History
102+
103+
- **Workflow** – Lists completed actions as the deal progresses.
104+
- **Description** – Space for internal notes.
105+
- **Stage dates** – Automatically populated list of completed stages with dates.
106+
107+
---
108+
109+
## **Section 4: Advanced Data and Linkages**
110+
111+
### Labels
112+
113+
Attach labels to categorize and filter deals more efficiently.
114+
115+
### Deal Connections
116+
117+
The deal displays its links to:
118+
119+
- Contact person and company (or lead)
120+
- Partner representative (if applicable)
121+
- Request
122+
123+
**Important:**
124+
For accurate customer analytics, always specify the **end customer** in the contact and company fields — even if the sale is made through a partner. This can be adjusted later if the end customer becomes known.
125+
Specifying a partner allows you to see all deals with this partner in the Deal manager using the partner filter.
126+
127+
### Additional Information
128+
129+
This area shows:
130+
131+
- Deal owner and co-owner (responsible sales managers)
132+
- Last modified information (who last changed the deal and when.)
133+
- Deal ticket
134+
135+
### Outputs (Products / Services)
136+
137+
Here you can describe what you're selling:
138+
139+
- Quantities and prices
140+
- Contract and actual shipment dates
141+
- Serial numbers (if applicable)
142+
- Shipment status
143+
144+
### Payments
145+
146+
Add and track payment details:
147+
148+
- Payment amount and currency
149+
- Actual or expected payment date
150+
- Payment status (received / guaranteed / high probability / low probability)
151+
- Contract and invoice numbers
152+
- Order number
153+
- Indicator for payments via representative office
154+
155+
### Files
156+
157+
Upload contracts, specifications, invoices, and other deal-related files.
158+
159+
---
160+
161+
## **Why Accurate Deal Data Matters**
162+
163+
Django CRM uses deal information to generate powerful marketing and analytical reports:
164+
165+
### Closure Reasons Report
166+
167+
Helps identify why deals fail and reveals patterns that impact sales performance.
168+
169+
### Sales Funnel Report
170+
171+
Based on the **Stage** field. Shows at which stage most deals are lost — for example, deals that never progressed beyond the price offer stage.
172+
173+
### Income Summary Report
174+
175+
Uses payment statuses to build revenue forecasts for the current and next two months.
176+
177+
### Sales Report
178+
179+
Shows which products or services were sold, when, by whom, and at what price.
180+
181+
If you need to update preset values for deal stages or closing reasons, contact your CRM administrator — these lists can be customized to match your business processes.

‎mkdocs.yml‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ nav:
8888
- Creating and assigning tasks: help/creating-assigning-tasks.md
8989
- Editing and updating tasks: help/editing-updating-tasks.md
9090
- Deleting tasks: help/deleting-tasks.md
91-
- Memos:
91+
- Memos (CRM notes):
9292
- Working with CRM notes: help/notes-crm.md
9393
- Memo creation: help/creating-crm-note.md
9494
- Editing and updating memos: help/editing-updating-crm-note.md
@@ -98,7 +98,9 @@ nav:
9898
- Creating and assigning projects: help/creating-assigning-projects.md
9999
- CRM Module:
100100
- Commercial request management: help/commercial-requests-management.md
101+
- Request processing: help/request-processing.md
101102
- Deal management: help/deals-management.md
103+
- Working with deals: help/working-with-deals.md
102104
- Lead management: help/lead-management.md
103105
- Company management: help/company-management.md
104106
- Contact management: help/contact-management.md

0 commit comments

Comments
 (0)