2
Владимир
no recommendations
no complaints
Closed
Project title: Creating a CRM to work through VC
Type of cooperation: One-time project
Section: Web development
Prepayment: without prepayment
Payment methods: Bank transfer, Electronic money
Acceptance of requests: closed
Type of cooperation: One-time project
Section: Web development
Prepayment: without prepayment
Payment methods: Bank transfer, Electronic money
Acceptance of requests: closed
Project description:
Good day!
We are looking for a programmer to write a CRM to work through VC. We are looking at the web version.
I understand that some features require a Standalone app. But there are ways to implement without stanadlone. If you don’t know how to do this, don’t respond to the project.
The purpose of such a messenger is convenient communication with customers through VK (something like CRM for correspondence via VK). It is done for your projects, not for the mass user. So design is not important.
I briefly describe the necessary functions:
(1) a database with a set of parameters is maintained for users
- parameters that are related to the VC (ID VC, Name, status of a friend (I subscribe to him / he for me / we are friends), status of being in a given group)
- parameters not related to VC (customer status, date of contact trace, amount of payments, purchased goods, etc.)
2) the ability to filter and sort users by parameter from paragraph 1
3) the possibility of conducting full correspondence with the client through the service. Track users with unread messages. The presence of quick phrases (pre-prepared templates).
4) the ability to send a message message from one account to friends who are waiting for information, not spam
(5) Auto-add friends to a database with a self-sending message in response and a contact entered in the database
(6) Mass actions:
Add/remove from friends
- accept the application / remove from the group
Changes in client parameters (e.g. customer status)
This is a brief description of the required functionality. But it outlines all the key tasks. I suggest discussing it in more detail in person.
Please respond to the project if you really understand how to implement it, if you have real experience with the API VK. Because there are enough of its nuances, limitations, etc. And for implementation, this experience is extremely important.
When responding, write a rough assessment:
1) Your experience with the VK API (if not at all, don’t write)
(1) project cost
(2) time frame
By the cost and timing, I understand that this is an approximate estimate. It is worth discussing after a detailed discussion.
Good day!
We are looking for a programmer to write a CRM to work through VC. We are looking at the web version.
I understand that some features require a Standalone app. But there are ways to implement without stanadlone. If you don’t know how to do this, don’t respond to the project.
The purpose of such a messenger is convenient communication with customers through VK (something like CRM for correspondence via VK). It is done for your projects, not for the mass user. So design is not important.
I briefly describe the necessary functions:
(1) a database with a set of parameters is maintained for users
- parameters that are related to the VC (ID VC, Name, status of a friend (I subscribe to him / he for me / we are friends), status of being in a given group)
- parameters not related to VC (customer status, date of contact trace, amount of payments, purchased goods, etc.)
2) the ability to filter and sort users by parameter from paragraph 1
3) the possibility of conducting full correspondence with the client through the service. Track users with unread messages. The presence of quick phrases (pre-prepared templates).
4) the ability to send a message message from one account to friends who are waiting for information, not spam
(5) Auto-add friends to a database with a self-sending message in response and a contact entered in the database
(6) Mass actions:
Add/remove from friends
- accept the application / remove from the group
Changes in client parameters (e.g. customer status)
This is a brief description of the required functionality. But it outlines all the key tasks. I suggest discussing it in more detail in person.
Please respond to the project if you really understand how to implement it, if you have real experience with the API VK. Because there are enough of its nuances, limitations, etc. And for implementation, this experience is extremely important.
When responding, write a rough assessment:
1) Your experience with the VK API (if not at all, don’t write)
(1) project cost
(2) time frame
By the cost and timing, I understand that this is an approximate estimate. It is worth discussing after a detailed discussion.
Project tags:
