Contact person: Business Client

Phone:Show

Email:Show

Location: Castelnuovo, Italy

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Project Proposal – WhatsApp Centralized Lead Management System

I am looking for a technical partner, developer, or automation expert to design and implement a centralized WhatsApp ecosystem for a multi-client medical marketing operation.

Context

I manage digital marketing for multiple medical clinics.
Each clinic:

Has its own Meta Business Manager

Has its own CRM sub-account (GoHighLevel)

Clinics are fully independent from each other in terms of ads, Business Managers, and data.

Goal

Create a system where:

All leads coming from different clinics and different GoHighLevel sub-accounts

Are automatically contacted on WhatsApp

Using one single WhatsApp number

Managed by one centralized secretary

Branded generically as “Secretary” or “Medical Secretary” (not as a specific clinic)

Constraints (Very Important)

The same WhatsApp number cannot be connected to multiple GoHighLevel sub-accounts

Business Managers cannot be shared

WhatsApp must not be managed natively inside GoHighLevel

Clinics must remain technically and legally separated

Required System Architecture

The solution should:

Use WhatsApp Business API or an equivalent solution

Use one centralized WhatsApp inbox external to GoHighLevel

Receive lead data from multiple GoHighLevel sub-accounts

Identify the clinic of origin for each lead

Support tags or labels per clinic

Support custom fields such as clinic name, service, and source

Be usable by a single operator (secretary)

Be scalable for 15 or more clinics

Lead Flow Example

A lead submits a form (Clinic A, Business Manager A, GoHighLevel A)

GoHighLevel triggers a webhook or automation

Lead data is sent to the centralized WhatsApp system

A WhatsApp message is sent from the same number

The secretary sees the lead name, phone number, and clinic name

The conversation is handled manually by the secretary

Technology Preferences (Open)

WhatsApp Business API (Cloud API or BSP)

External inbox platforms such as [login to view URL], Callbell, Trengo, WATI, or custom solutions

Webhooks, Make, or Zapier

No-code or low-code solutions preferred, but custom development is acceptable

Expected Deliverables

System architecture proposal

Tool stack recommendation

Cost estimation (setup and monthly)

Implementation timeline

Documentation for future scaling

Who Should Apply

Automation specialists

CRM and WhatsApp API developers

No-code experts (Make, Zapier)

Agencies with experience in multi-tenant systems

If you have built similar centralized communication systems or have strong experience with WhatsApp Business API and CRM integrations, I would like to review your proposal." (client-provided description)