Hopelink — Matchmaking & CRM Portal
Project Overview
Hopelink is a highly scalable, production-grade matchmaking ERP and CRM platform deployed live at hopelinkrishta.com. Built for matchmaking agencies and matrimonial service providers, Hopelink resolves the administrative overhead of managing thousands of marriage profiles, client leads, and payment plans.
Unlike generic CRMs, Hopelink implements a **React-driven Single Page Application (SPA)** dashboard communicating with a lightweight **PHP REST API** backend. The database architecture is designed with custom validation parameters for marital status, family details, caste criteria, and dynamic partner match calculations, helping matchmakers easily bridge profiles with specific criteria.
Operational Architecture
The system separates the client representation layer from database tasks, securing client assets behind credential filters:
Core Feature Modules
Detailed Profile Engine
Manages profiles with biological metrics (age, height, weight), education, occupation, caste, location, family data (father's job, siblings count), and dynamic partner preferences.
Client Leads CRM
Tracks incoming lead entries, follow-up dates, lead sources, and whatsapp contact hooks. Allows administrators to assign leads to specific team agents.
RBAC Staff Credentials
Four distinct team access levels: `admin`, `matchmaker`, `lead_handler`, and `agent` with custom access clearance limits on patient client profiles.
Invoices & Payments
Tracks package payments (Free, Silver, Gold), dynamic registration fees, committed success fees, and payment status parameters with detailed audit logs.
Analytics Dashboard
Real-time visual stats on active profiles, newly acquired leads, monthly fee metrics, conversion performance, and team activity logs.
CMS Content Manager
CMS panel allowing administrators to adjust system settings, manage cities/religions matrices, and upload matching slider/gallery images.
SQL Relational Schema
Designed with rigid relational constraints to map cross-criteria searches quickly:
Technical Architecture Decisions
- Headless React Client + PHP API: Decoupling the frontend as a React compiled bundle hosted separately from the PHP backend API results in high-speed user interface transitions.
- Dynamic JSON Query Mapping: Match preferences are stored using checking JSON fields (`preferences` table) directly inside MySQL, enabling fast relational evaluations of target partners.
- Granular RBAC Protection: Every PHP API file (e.g. `api/profiles.php`, `api/analytics.php`) performs validation checks on authorization tokens, blocking unauthorized matchmakers or agents from downloading client details.