W
Loading…
Loading…
More than a corporate website: service and facility discovery, web and WhatsApp conversations, lead capture and a bridge into Akash’s operational CRM—plus dedicated presentations for the 3PL platform.
Akash presents storage, distribution, handling, packaging, fulfilment and relocation services across the Mumbai region. Prospective buyers need to understand the right service and facility; the sales team needs enough context to turn that interest into a useful conversation.
This build spans two jobs: explaining a logistics business to a prospective buyer, and making that buyer’s enquiry useful to the team. The work extends beyond page design into forms, chat, conversation history, notifications and the handover to the WMS CRM. The platform also needs distinct explanations for operators and their clients.
The website separates warehousing, logistics, handling, packaging, fulfilment and relocation offerings. Facility pages cover Bhiwandi, Kalamboli, CBD Belapur, JNPT and Mumbai; landing pages and editorial content support different entry points.
A buyer can evaluate the service and location relevant to their requirement.
The custom chat widget submits to the same backend that handles WhatsApp conversations. Identified leads and messages are persisted, and the contact-enquiry route coordinates staff notifications and email handling. The browser tracks enquiry, phone and WhatsApp actions.
The enquiry carries context beyond a single email notification.
The webhook service has an Akash-specific CRM bridge. It sends lead identity and available conversation context into the WMS importer using external-source identifiers so repeated pushes can enrich the same record.
Sales can work with the enquiry in the wider business system instead of treating the website as a separate inbox.
A separate React/Vite presentation uses scroll-driven sections, feature visualisations, image zooms and product lightboxes to explain the 3PL platform. An additional client-focused presentation explains the customer-facing side. Motion code includes reduced-motion handling.
The marketing experience explains both the logistics service and the software behind it.
The integration problem
A page visit or conversation can become an isolated enquiry unless its identity, history and next step are connected.
What we built
The implementation connects website forms and chat, shared messaging infrastructure, persistent records and a WMS CRM import path.
5
Dedicated facility pages in the website source
Web + WhatsApp
Connected enquiry channels
CRM bridge
Identified leads and context sent to the WMS
2 audiences
Operator and client platform presentations
Delivery scope is verified in the website and webhook repositories. Lead volumes, reply-time gains and conversion improvements need analytics or operational records; they are not inferred from the code.
Scope reviewed across the corporate website, its React platform presentation and the shared web/WhatsApp backend. The corporate site is a static HTML/JavaScript implementation; the 3PL product presentations use React/Vite. Lead persistence includes PostgreSQL and legacy Airtable integration paths. The operator/client presentation builds are present in source; their public routes were unavailable during this review.
A manufacturer’s equivalent is a product and capability website that passes qualified enquiry context into its sales or order system—not a brochure disconnected from the team.
Tell us what you make, who you sell to and where you want to grow. Start with a free review of your current website.