Not specified
5 proposals
I'm looking for a specialist with real experience in Planfix to set up a basic CRM for a company that sells and installs automotive glass.
It is necessary to build the correct structure of the CRM so that it can be easily scaled in the future, adding new integrations and automations without a complete system overhaul.
1. Building the main structure of the CRM
It is necessary to set up the basic architecture of the system.
The main workflow:
Incoming request → Glass selection → Price agreement → Glass order → Installation appointment → Completed order
⸻
2. “Incoming request” card
It is necessary to create a convenient request card.
Client data
* Full name
* Phone
* Email
* Source of inquiry
* Communication channel
Vehicle data
* VIN
* Make
* Model
* Year of manufacture
Important:
Make and model must be selected from a list.
After selecting the make, the system should only show models of that make.
For example:
BMW → X1, X3, X5
Audi → A3, A4, A6
Mercedes → C-Class, E-Class, GLC
etc.
⸻
Glass data
* Type of glass (Windshield, Rear, LPD, LZD, PPD, PZD, LZF, LZC, PZF, PZC, Panorama, LPF, PPF)
* OEM number
* Eurocode
⸻
Glass options
It is necessary to implement the ability to add multiple offers to one request.
For example:
Pilkington
* Supplier
* Purchase price
* Price to client
* Profit (for example, purchase 100 without VAT. The manager adds a markup of 50 and the program calculates the price for the client (100+50)*1.2
Sekurit
* Supplier
* Purchase price
* Price to client
* Profit
Glavista
* Supplier
* Purchase price
* Price to client
* Profit
XYG
Ukraine
Client's glass
The number of options should be unlimited.
⸻
3. Request statuses
It is necessary to set up statuses:
* Incoming request
* Price learned
* In progress
* Completed
* Canceled
⸻
4. Manual request creation
There should be a possibility to quickly create a request manually.
For example, if:
* the client comes to the workshop;
* contacts in person;
* contacts by mobile phone;
* comes by recommendation;
* any other inquiry.
After pressing the “New request” button, a card for filling out should open.
⸻
5. Google Calendar
When scheduling the client for installation, it is necessary to:
* select a date;
* select a time;
* create an entry in Google Calendar;
* automatically save the event link in the request card;
* have the ability to quickly transition from the request to the calendar event. The calendar should display information such as client phone, make, model, price, and supplier, as well as the Eurocode of the glass.
⸻
6. Email integration
It is necessary to integrate the work email.
It should be that:
* new emails coming specifically from the order site create new requests;
* repeated emails are attached to existing requests;
* the correspondence history is stored within the request.
⸻
7. Binotel integration
It is necessary to integrate Binotel telephony.
It should be that:
* when a call comes in, the client card opens;
* if the client is not present, a request can be created immediately;
* call history is saved;
* a recording of the conversation is attached (if technically possible).
⸻
8. PartsLink24 button
A button should be added to the request card:
Open PartsLink24
When pressed, the login page for PartsLink24 should open in a new browser tab.
It is also desirable to make it possible to quickly copy the VIN code for pasting into PartsLink24.
⸻
9. Client search
Before creating a new request, there should be an option to find an existing client by:
* phone number;
* VIN;
* name.
To avoid creating duplicate clients.
⸻
10. Automatic request numbering
Each request should automatically receive its own number.
For example:
Client's phone number, email address, car VIN last digits
⸻
11. Training
After the work is completed, it is necessary to show:
* how to add new fields;
* how to change statuses;
* how to add directories;
* how to independently expand the CRM.
⸻
Expected result
After the work is completed, a basic CRM should be ready, with which one can immediately start working.
In the future, integration is planned:
* WhatsApp Business API;
* Telegram;
* Google Sheets;
* AI assistant;
* automatic glass selection.
Therefore, the system should be designed in such a way that it can be easily scaled.
Behance
