Direct phone conversation
Speak directly with Rubin Chal for commercial introductions, project fit discussion, or a first-stage overview of requirements.
+60 11-5121 5688This page now works more like a decision page. It shows the available contact routes, what information is useful before you enquire, and the structured form for teams evaluating AI-ready infrastructure projects.
Different stakeholders prefer different contact channels, so the page now makes those options explicit instead of burying them inside a single contact block.
Speak directly with Rubin Chal for commercial introductions, project fit discussion, or a first-stage overview of requirements.
+60 11-5121 5688Useful when you want a quicker first message before moving into a fuller discussion or formal project briefing.
Start WhatsAppUse the office address and map link when internal review or partner verification requires a formal business location.
Open in MapsBest when the enquiry includes site context, project type, timeline considerations, or cross-team requirements.
Go to formThis summary keeps the direct business details visible while visitors complete the form or prepare internal approval to make contact.
A short checklist makes the contact page more useful for first-time visitors who need to gather information internally before reaching out.
Explain whether the discussion is for a new deployment, an expansion, a retrofit, or a broader smart city programme.
Describe the site, systems, or operational setting that the infrastructure needs to support.
Note whether facilities, IT, operations, procurement, or external partners are already involved.
Indicate whether phone, WhatsApp, or form-based response is the best next step for your team.
A public email address is not listed here, so this form is designed to capture your preferred reply details clearly while preserving the existing Netlify submission flow.
This comparison makes the page more practical for different types of visitors, especially when multiple internal stakeholders are involved.
| Contact Route | Best For | What To Prepare | Expected Use |
|---|---|---|---|
| Phone call | Immediate commercial introduction or direct project-fit discussion. | Basic project objective, timeline, and who is involved. | Fast initial conversation with minimal delay. |
| Quick first contact, short follow-up, or confirmation before a fuller discussion. | A short summary of the enquiry and the preferred next step. | Convenient early communication channel. | |
| Enquiry form | Structured project submissions where more context should be recorded clearly. | Project type, site context, contact details, and operational requirements. | More complete handover of information for follow-up. |
| Map and office reference | Internal approval, partner review, or business verification. | Office address and the reason location detail is needed. | Supports due diligence and formal business review. |
The contact page still answers the initial questions visitors are most likely to ask before starting the conversation.
It helps to share your project objective, current environment, whether the work is new-build or retrofit, and what kind of systems need to be supported or integrated.
Yes. The site is structured to support early commercial and planning discussions, not only fully defined implementation requests.
Yes. A phased approach is often more realistic for infrastructure programmes involving facility readiness, budget alignment, and multiple stakeholders.
Yes. WhatsApp is included as a direct communication option for initial enquiries and quick follow-up.
Use the form for structured project details, WhatsApp for a faster first conversation, or the phone number for direct discussion.