About ClickMaker Connect
We built the WhatsApp layer our own products needed.
ClickMaker IT Solutions LLP operates vertical SaaS products used by gyms, schools and transport businesses. WhatsApp became central to those products, and building Meta integration repeatedly was the wrong answer.
Why this exists
Messaging infrastructure should not be rebuilt per product.
Every product eventually needs to send a reminder, a receipt or a delivery update. Doing that directly against Meta means owning OAuth flows, token custody, template policy, webhook verification, retries, consent and tenant boundaries — inside each product.
ClickMaker Connect centralises that work as a shared platform. The products we operate use it. External CRMs, SaaS platforms and agencies can use the same infrastructure through scoped applications, without receiving a customer's Meta access token.
The product is deliberately opinionated: customer-owned WhatsApp accounts, asynchronous sending, explicit approval states, signed events and no invented delivery claims.
Company
- Legal name
- CLICKMAKER IT SOLUTIONS LLP
- Product
- ClickMaker Connect
- Category
- WhatsApp Business Platform infrastructure & CRM
- Jurisdiction
- India
- Primary domain
- connect.clickmaker.in
Registered address, CIN and tax identifiers are published only after legal confirmation. This page does not invent corporate details.
The ecosystem
Operated products and external platforms, one foundation.
ClickMaker Connect is not a side experiment. It is the communication layer behind products with real operational workflows.
Gymavio
Fitness business platform
Gyms and studios manage members, payments and communication. WhatsApp handles reminders, renewals and member conversations.
SchoolOrbit
School ERP
Schools coordinate parents, staff and operations. WhatsApp carries attendance, fee and event updates through approved templates.
Builty.in
Transport operations
Transport teams track consignments and share delivery updates with the parties who need them.
Your product
External SaaS
Any platform can connect through scoped applications and the same messaging API without building Meta infrastructure.
Principles
The rules we do not bend.
These are product constraints, not slogans. They shape schema design, API contracts and what the UI is allowed to claim.
The customer owns the account
A WhatsApp Business Account belongs to the business. ClickMaker connects and operates it; ClickMaker does not take it over. Shared sender numbers are not an acceptable shortcut.
Delivery truth over optimistic UI
A queued message is not delivered. A local template is not approved. The platform models the real state machine and reflects Meta events honestly.
Tenant boundaries are structural
Tenant isolation is not a UI filter. Every record, job and webhook resolves ownership from server-side mappings and fails closed.
Meta's role is not our role
We operate the integration and dashboard. Meta operates WhatsApp, decides eligibility and sets conversation pricing. We do not blur that line in product or marketing.
Independent technology provider
ClickMaker Connect is not owned, operated, certified or endorsed by Meta. WhatsApp and the WhatsApp Business Platform are Meta products.
Built for platforms
Applications, scopes and tenant authorization are first-class. The platform is designed to be integrated, not just logged into.
For teams, not one admin
Owners, admins, managers, agents, developers and viewers have distinct permissions and audit visibility.
ClickMaker Connect
Use the infrastructure we run our own products on.
Create a workspace, connect a number you own, and start with a real WhatsApp integration.
No shared ClickMaker sender · Customers own their assets