CASE STUDY 01REAL-TIME MESSAGING

Messaging that moves from inbox to action

A multi-tenant WhatsApp CRM brings customer messages, team handoffs and workflow automation into one product.

ROLE / CONTEXTFull-Stack Developer - Advanced Resources
PERIOD / STATUSFebruary 2025 - August 2025
TOOLS / AREASNode.js · WhatsApp Business API · Webhooks · Real-time messaging

01 / CONTEXT

The problem

Customer conversations become operational work: someone needs to receive a message, understand its context, route it to a team and follow through. A shared inbox is only useful when those handoffs connect to the systems behind it.

ClusterDen brings customer messaging and automated workflows into a multi-tenant CRM. My work at Advanced Resources covered backend services, WhatsApp Business API webhooks, real-time messaging and workflow automation.

02 / PERSONAL SCOPE

My contribution

  • Built and maintained backend services and third-party integrations.
  • Developed WhatsApp Business API webhook integrations alongside real-time messaging and CRM workflow features.

03 / OUTCOME

What changed

Improved one automated workflow, reducing its execution time by approximately 75%.

~75%less execution timeONE AUTOMATED WORKFLOW

THE SYSTEM IN PRACTICE

From a message to the next action.

Follow the path from an incoming conversation to the team and workflow that act on it.

FOLLOW THE FLOW

01 / Receive

A customer starts the conversation.

An incoming WhatsApp event is the starting point for work inside the CRM.

WHATSAPP BUSINESS API

02 / Connect

The integration brings it into the product.

Webhook integrations connect incoming events to backend services and the conversation experience.

WEBHOOKS + BACKEND SERVICES

03 / Act

Teams and workflows take it forward.

Real-time messaging and automated CRM workflows help a conversation move beyond the inbox.

MESSAGING + WORKFLOW AUTOMATION

04 / Improve

Less waiting in one automated workflow.

I improved one automated workflow, reducing its execution time by approximately 75%.

~75% LESS EXECUTION TIME · ONE WORKFLOW

ENGINEERING CONSIDERATIONS

The details behind the interface.

The interface depends on the integration.

The work crossed API events, backend services and real-time product behavior. That meant treating the connection between those pieces as part of the user experience: the team needs the conversation and its workflow to stay connected.

LOOKING AHEAD

Where I’d take it next.

  • Capture timings around individual workflow steps so future regressions can be traced to a specific stage.
  • Keep a repeatable set of webhook and workflow scenarios for checking integration changes.
  • Make workflow failures easier for a team to understand and act on inside the product.