G-connect

The brief

A sales team that works entirely through personal Zalo accounts owned by the company — not through an official OA. The problem is not sending messages; it is doing so without losing an account, which takes years to warm up and minutes to burn.

The approach

Separate everything. G-connect runs as its own system — its own repository, database, Redis, server and its own IP range — deliberately isolated from the main platform, so a problem on one side cannot reach the other. A client and a server, with the messaging layer treated as the fragile component it is.

The engineering rules live in the repo and each one is written with the incident that produced it, because a rule without a reason gets deleted by the next person.

The harder parts

Everything here is a rate-limiting and pacing problem. The transport is an unofficial protocol binding, so it can change without notice, and every operation has to assume it may be throttled, delayed, or rejected. That means queues rather than loops, human-shaped pacing rather than bursts, and a hard rule that nothing runs at machine speed just because it can.

Built for internal use by one company's own sales team on accounts that company owns.