WhatsApp Business API gives port stevedoring firms and shipping agents in India one timestamped channel to push berth confirmations, gang deployment orders, hourly hatch tallies, IGM/EGM filing milestones and delivery order (DO) release notices to masters, terminal operators, customs brokers and cargo owners. Instead of chasing a shifting berth line-up across phone calls and a dozen personal WhatsApp groups, every milestone in the vessel call fires automatically from your operations system as a structured, auditable message tied to the vessel and voyage number.
That matters more in 2026 than it did five years ago. India's 12 major ports now move roughly 820-855 million tonnes a year, and all-India throughput including the non-major ports has crossed 1,500 million tonnes. Average vessel turnaround at major ports has compressed to about 0.9 of a day — near 22 hours. When a port call is measured in hours rather than days, a berth-shift message that reaches the stevedore supervisor twenty minutes late means idle gang cost, a missed tide, and a demurrage argument nobody can evidence three weeks later.
Why the vessel call breaks on voice calls and personal WhatsApp groups
A single port call touches an absurd number of parties: the master and owner, the charterer, the terminal operator, the port authority's marine department for pilot, tug and mooring gangs, the stevedore's shift supervisor, tally clerks at each hatch, the customs broker, the surveyor, the transporter lifting cargo out, the CFS, and the cargo owner who only wants to know when the DO drops.
Most Indian agents and stevedores coordinate all of this on personal WhatsApp groups. It works until it does not, and the failure modes are always the same four:
- No audit trail bound to the voyage. When a demurrage or idle-gang claim lands, you are scrolling a group with 400 messages a day looking for a screenshot.
- Knowledge walks out of the door. The group lives on a supervisor's personal number. He resigns; the history and the contacts go with him.
- No delivery evidence. "We informed you at 0230" is a claim. A delivered-and-read receipt against a named number is a fact.
- No system link. Nothing is triggered by your operations software, so every message depends on a tired human remembering to type it at 3 a.m.
WhatsApp Business API fixes exactly this layer. One business number for the firm, milestone messages generated by the system, delivery and read state captured against each recipient, and full history retained against the vessel record rather than an individual's handset.
The Indian regulatory spine your messaging has to respect
Port messaging is not a marketing channel. It is an operational record inside a heavily regulated chain, and the content of each alert should map to a real statutory or contractual event.
Major Port Authorities Act, 2021. This replaced the Major Port Trusts Act, 1963 across the 12 major ports and gave each Board real autonomy over its own tariffs, berthing policy and land use. The practical consequence for your notification design is that berthing priority rules, penal berth hire and idle-gang charges now differ from port to port. A generic "berth confirmed" template is not enough — the message must carry port-specific berth hire and priority implications, because Deendayal, Paradip and V.O. Chidambaranar no longer share one rulebook.
PCS 1x. The Port Community System operated by the Indian Ports Association has been the single electronic window for the port community since 2018, connecting ports, terminals, shipping lines, agents, CFSs, banks and Customs. Vessel-call and container events land there. WhatsApp does not replace PCS 1x — it is the human-readable last mile for events PCS 1x and your terminal system already hold. Read the event, push the alert.
IGM, EGM and SCMTR. The Sea Cargo Manifest and Transhipment Regulations, 2018 restructured manifest filing into arrival and departure manifests on ICEGATE. The Import General Manifest under Section 30 of the Customs Act, 1962 is filed before arrival; the Export General Manifest under Section 41 is due within seven days of the vessel's departure. A late or error-ridden EGM stalls the exporter's IGST refund and duty drawback, which is why "EGM filed" and "EGM error — action needed" are two of the highest-value automated alerts a shipping agent can send.
Licence and record-keeping status. Steamer agents act for the carrier under Section 148 of the Customs Act. Clearance work sits under a Customs Broker licence per CBLR 2018. Multimodal operators hold MTO registration granted by the Directorate General of Shipping under the Multimodal Transportation of Goods Act, 1993, renewable on a three-year cycle, and crewing arms hold DG Shipping RPSL approval. Every one of those licences carries a record-keeping obligation. A retained, timestamped message log against each voyage is one of the cheapest ways to satisfy an inspection.
India's port cohort in numbers
| Indicator | Recent published figure | Why it changes your messaging design |
|---|---|---|
| Cargo at the 12 major ports | ~820-855 million tonnes per year | High call frequency; templates must be reusable across commodities |
| All-India incl. non-major ports | Over 1,500 million tonnes per year | Non-major ports often lack terminal portals — WhatsApp is the only shared channel |
| Container throughput, all-India | Roughly 20 million TEU per year | Container calls generate per-box events; bulk calls generate per-hatch events |
| Largest container gateways | Mundra (non-major) around 7 million TEU; JNPA around 6.4 million TEU | Concentrated volume rewards deep integration at a handful of terminals |
| Largest major port by tonnage | Deendayal (Kandla), roughly 130-140 million tonnes | Dry and liquid bulk dominate — tally and draft-survey messaging, not box tracking |
| Average turnaround, major ports | About 0.9 day (~22 hours) | Alert latency budget is minutes, not hours |
| Output per ship berth day | Broadly 16,000-18,000 tonnes at major ports | Hourly progress against this benchmark is the single most requested update |
| Free period on import cargo | Commonly around three days before demurrage slabs begin | Countdown reminders have a hard, measurable money value |
Treat those as orders of magnitude published by the Ministry of Ports, Shipping and Waterways and the Indian Ports Association rather than to-the-decimal truth. The design conclusion holds either way: alerting has to be event-driven, because no human keeps pace with a 22-hour call across four hatches.
The six-stage vessel-call lifecycle on WhatsApp
Map automation to the call, not to the org chart. Six stages cover almost every dry-bulk, break-bulk and container call an Indian agent or stevedore handles.
Stage 1 — Vessel nomination and pre-arrival
Trigger: agency appointment received, or ETA update from the line. Push a nomination confirmation to the principal and a pre-arrival checklist to the terminal and stevedore: expected ETA window, cargo tonnage and stowage plan, draft, hatch count, crane availability, and the pre-arrival document set required for the arrival manifest. A single template with variables replaces the ten-email thread that usually precedes a call.
Stage 2 — Berth confirmation, pilot and tug slot
Trigger: berth allotted in the port's berthing meeting or terminal system. This is the message that most often arrives late. Send berth number, expected berthing time, pilot boarding ground timing, tug allocation and the anchorage waiting position if the berth slips. Every subsequent revision fires an amendment on the same thread, so the recipient sees the sequence rather than three contradictory forwards.
Stage 3 — Gang deployment and shift roster
Trigger: berthing confirmed for a shift boundary. Push hatch-wise gang allocation, shift timings, supervisor name and the safety brief acknowledgement request. Supervisors reply on the same thread to accept or flag short manning, which gives you a documented manning position before the shift starts rather than an argument after it.
Stage 4 — Discharge and loading progress
Trigger: hourly or per-hatch tally posted in the terminal system. Push cumulative tonnage or box count, per-hatch rate against the planned output per ship berth day, remaining quantity and revised completion estimate. Principals and charterers stop calling for updates, which alone frees several hours a day for an operations desk.
Get a 1-minute BSP audit on WhatsApp
Drop your WhatsApp number — we line-item your current invoice against Meta India rates in under 60 seconds. India-hosted, DPDP-compliant.
Stage 5 — Tally, documentation and customs milestones
Trigger: statement of facts, draft survey, mate's receipt, IGM filed, EGM filed. Push the milestone with the reference number and the document as an attachment. The EGM alert deserves its own template because of the downstream refund linkage described above.
Stage 6 — DO release, invoice and the demurrage clock
Trigger: freight and charges cleared, DO generated. Push the DO release with a countdown of remaining free days on the container or cargo, then automated reminders at the free-period boundary. Attach the e-invoice reference. This is the stage with the clearest rupee return: a consignee who is told on day two that day four starts detention behaves differently from one who discovers it on the bill.
Stages 4 and 6 are also where the chain outside the port gate begins. If you also arrange evacuation, the same event stream can drive alerts to your GTA and truck operator coordination, and clearance milestones flow naturally into the custom house agent and freight forwarder workflow.
Gang deployment and dock-labour safety communication
Stevedoring is governed on the safety side by the Dock Workers (Safety, Health and Welfare) Act, 1986 and the Regulations of 1990, which put positive duties on the employer for safe means of access, hatch cover handling, certification of lifting appliances and provision of protective equipment. Most ports run three eight-hour shifts with meal reliefs, and gang idle time is both billable and routinely disputed.
Three automations pay for themselves quickly. A roster push four hours before the shift with an explicit acknowledgement reply, so unfilled gangs surface early. A toolbox-talk and PPE checklist at shift start, acknowledgement stored against the shift record — useful the day an inspector asks. And idle-gang reason-code capture: when work stops, the supervisor replies with a code and a photograph, timestamped at the moment it happened. Reason codes recorded live are worth far more in a claim than a reconstruction written a week later.
Demurrage, detention, and what a late message actually costs
| Cost head | Charged by | Typical Indian pattern | Alert that prevents it |
|---|---|---|---|
| Port / terminal demurrage on import cargo | Port authority or terminal | Short free period, commonly around three days, then slabs that escalate with each further block of days | DO-release countdown plus reminders at each slab boundary |
| Container detention | Shipping line | Free days per the line's tariff, then per-container per-day charges that step up sharply at each slab | Empty-return reminder with nearest depot and cut-off |
| Berth hire and penal berth hire | Port authority | Levied on vessel tonnage per hour of occupancy; idle time at berth is chargeable | Real-time progress alerts so completion and unberthing are not missed |
| Idle gang / gang cancellation | Stevedore or labour supplier | Per gang, per shift, whether or not cargo was available | Roster acknowledgement plus live reason codes |
| Vessel demurrage under charter | Charterer / owner | Laytime counted per the charterparty, then a daily demurrage rate that dwarfs every shore-side charge | Statement-of-facts events pushed as they occur, not reconstructed later |
Slab values differ by port, terminal and line, so verify against the applicable tariff rather than a rule of thumb. The structural point holds regardless: every one of these clocks starts on an event your systems know about before any human does. Charges accrue because the party who could have acted was not told in time.
GST, e-invoicing and the agent's billing trail
Stevedoring, cargo handling and port and terminal handling services attract GST at 18%. Because these are performance-based services rendered at a specific place, the place of supply follows the port, so a stevedore working at Paradip charges Odisha CGST and SGST even where the principal is headquartered in Mumbai — which in practice means state-wise registration wherever you hold a stevedoring licence.
Shipping agents carry an extra complication. Agency commission earned from a foreign principal is frequently treated as an intermediary service under Section 13(8)(b) of the IGST Act, which places the supply at the supplier's location and taxes it domestically instead of treating it as an export — a dispute the trade has been living with for years. Separately, reverse-charge GST on ocean freight for CIF imports was struck down by the Supreme Court in Mohit Minerals in 2022, and e-invoicing is mandatory for B2B supplies once aggregate turnover crosses ₹5 crore, a threshold that captures most mid-size stevedores and agency houses.
The messaging angle is simple: send the invoice and its IRN reference as a utility template attachment. You get a delivery receipt on the document and payment follow-ups gain a defensible starting point. The same discipline applies across the marine services chain — see how ship chandlers and marine suppliers use the same pattern for stores delivery notes.
Templates, opt-in and what Meta will and will not allow
Two kinds of message exist on the platform. Template messages, pre-approved by Meta in marketing, utility or authentication categories, can be sent to a contact at any time. Free-form replies are allowed inside a 24-hour service window that opens each time the contact messages you.
Almost every message in the six-stage lifecycle above is a utility template — a factual operational update on an existing transaction, with variables for vessel, voyage, berth, hatch, quantity and reference numbers. Build one template per milestone rather than one clever template trying to serve six: approval is faster and quality complaints are rarer.
Two cautions worth stating plainly. Opt-in must be collected and recorded for every recipient, and consent from a cargo owner for shipment alerts is not consent for promotional broadcasts. And no provider can promise that unsolicited or bulk messaging is safe — Meta acts on recipient feedback and quality signals, and a number that generates blocks can be restricted regardless of who supplies the API. Consented, relevant, transaction-linked messaging is the only durable model. The automation and template features exist to make that easy, not to make bulk outreach survivable.
What it costs to run this
| Item | Client Pay | SaaS Pay |
|---|---|---|
| Setup fee | ₹0 | ₹0 |
| Monthly platform floor | ₹0 | ₹0 |
| Meta account | Yours — you pay Meta directly for conversations | Ours — nothing separate to settle with Meta |
| Per message | ₹0.10 flat | ₹1.20 marketing / ₹0.30 utility and authentication |
| Replies inside the 24-hour service window | Free | Free |
| Trial | 14 days with 100 free credits | |
Because port operations run almost entirely on utility templates and free-window replies, the effective cost of a fully instrumented vessel call is small next to a single hour of penal berth hire. Full details are on the usage-based pricing page, and the economics work out similarly for adjacent trades such as air freight forwarding.
One compliance note that catches new operators: the 14-day trial runs without GST registration, but going live with your own WhatsApp Business Account effectively requires GST. Business verification and the billing chain both assume a registered Indian entity, so treat GST as a production prerequisite, not an optional extra.
Getting live without disrupting a live berth
The sane rollout is narrow and fast. Pick one commodity or one terminal. Build four templates — berth confirmation, gang roster, hourly progress, DO release with a free-day countdown. Wire them to the events your terminal or agency system already emits. Run them alongside your existing groups for two or three vessel calls, compare what the log shows against what people remember, then switch off the group for that flow. Add the rest once the desk trusts the alerts.
Most agency houses and stevedoring firms are live on their first flow inside a fortnight, with business verification the long pole rather than the configuration. Start the 14-day trial with 100 free credits and instrument one vessel call end to end — the berth-hire arithmetic makes the rest of the argument by itself.