Telegram Boot with CRM

PHP, Python — incorrectly specified categories?

Project translated automatically. Log in or register, to view the original It is necessary to develop a chatbot with a CRM web interface.The primary task is to collect applications from families of asylum seekers and to build a row of refugees.Applications are collected through an inquiry in the bot.In addition to this bot accepts payment(date) from the bank crates of all countries of the world (including the maps of Russia and Belarus)+ cryptocurrency (I consider the equating tegro.money)As in the database will be stored personal data of people, good protection is required.Processing is carried out in several stages with the release of updates at each stage.Step 11.1 The first task is the bot - an inquiry.The result of the survey should be a family profile with separate exel/pdf files for each family member.All applications are gathered in a single base: Airtable (preferably) , google exel or other simple temporary (up to the implementation of CRM) application processing solution.The main condition is family grouping.The order is built from families of different numbers.Access to the bot is possible only by referral link or code.Phase 22.1 In the second phase it is necessary to implement web administration, ready solutions are permitted except for the Russian (no amocrm and so on).The volunteer exhibits the status of new applications, from the final status forms a row of families.On request of the volunteer the system publishes a list of the given number of people in a row without dividing the family.Every family has its profile in the CRM.The volunteer can fill (or edit) the data by updating the file = files.If the application for a person is filled by an administrator, the user receives the finished file in the bot and in the mail.The volunteer can change/add text questions in the questionnaire.In CRM, moderators with different degree of admission work.All are authorized through the tg (obligatory check on the user)2.2 Bot in the second stage:At this stage communication should take place by the Bot-CRM scheme.No personal chat with volunteers.Integration of third-party messenger aggregators (not Russian) is permissible.Each user is attached to a specific volunteer with the possibility of changing the responsible.It requires the ability to set template answers.At this stage, the user appears [The Hall of Expectation] in which he sees his track number, order and so on.Here are all the family survey data.Balance: In the bot there is a balance.It is supplemented with an equin or a manual administrator.Reference system for users.New roles: "Consultant" - Communicates through the bot with his supporters.The consultant has his balance supplemented with the share of the payments of the users.The CRM shows statistics on consultants and their history of correspondence with users.The number of applications, the number of successful sales, the amount of sales.The adjusted share of the bonus in favour of each consultant separately.Statistics on the moderators in admin.The number of applications accepted, the number of closed applications.Statistics on users relative to the number of references, how many, how many successful and how many rejections.The new role:"Curator" - he can independently make infinite applications by filling in questionnaires for people, forming families.With this scheme, the curators have no access to the bot.It also supplements the balance.More details after a personal conversation.

Proposals 5 Discussions 4

Dmitro K.

25 4

Projects 26
Rating -
Rating 1 066

Budget: 24000 UAH Deadline: 18 days

Hello to you. I specialize in CRM, dashboard, databases and WEB processing, accounting and analytics services. Comfortable and modern design. The development is completely key. turn to