Client-facing inbox for agency project portals

The moment it becomes real: an agency finishes a project proposal in their work management tool and then has to tell the client about it via a separate email thread, WhatsApp message, or even a phone call — because the portal only notifies via email, and clients either ignore those emails or get confused logging in. Suddenly there are two conversations happening in parallel, and neither is authoritative.

The gap persists because work management vendors are primarily selling to the agency, not the client. The client is a secondary actor — a recipient of a portal link, not a paying user. That means there's no revenue pressure on the vendor to make the client-side experience excellent. The agency complains internally but rarely switches vendors over it, so the vendor deprioritizes it for years. The complaints here are explicit: 'clients are required to access the platform via email, which confuses them' and users asking for WhatsApp, Telegram, Viber, and in-app messaging in the same breath.

What's missing isn't just another chat widget. It's a communication layer that meets clients where they already are — WhatsApp, email, SMS — and threads those conversations back into the project context so the agency isn't manually copy-pasting updates. The client never has to log into a portal. The agency sees everything in one place per project.

This is a business and not a feature because the communication problem recurs with every new client, every new project kick-off, and every revision cycle. Agencies pay for this with hours lost chasing responses and re-sending context. The cost isn't hypothetical: an agency managing 20 active clients and switching between three communication channels per client is losing a material number of billable hours per week to coordination overhead that should be automatic.

What to build

Build a lightweight add-on that connects to Agency Handy, Agiled, or similar tools via API and lets agency clients reply to project updates via WhatsApp or email, with those replies threaded directly into the project timeline visible to the agency team — no client login required.

Where to start

Start with agencies already using Agency Handy specifically, since that product has an active community of users explicitly requesting this feature and no native solution on the roadmap — making it a known, named gap with a reachable audience.

The hard part

Getting clients to actually use WhatsApp Business API requires Meta approval and per-message costs, which forces a pricing conversation before the product has proven value — and agencies will resist paying per message until they've seen the time savings firsthand.

How it makes money

Monthly subscription per agency seat, with a usage tier on top for WhatsApp message volume above a baseline threshold.