Vectra24

The challenge

Small teams could not staff specialists across marketing, sales, and support, and juggling a separate tool for each function slowed the work down. They needed coworkers they could direct from Telegram, WhatsApp, or Slack, not another dashboard to babysit.

Collaboration

Built as a TrueLogics engagement. I architected the coordinated agent teams and the messaging integrations people actually work through, so Marketing, Sales, and Support could be directed from chat as well as from a dashboard.

From discovery to production

• Role-based Marketing, Sales, and Support specialists, shipped as coordinated teams rather than one general assistant
• Control from Telegram, WhatsApp, and Slack, using the channels the team already lived in
• A dashboard for the same teams when a chat thread was the wrong place
• A shared workflow engine so an automation in one domain can compose with the others

How it was solved

Each specialist has a role and a tool contract. A shared workflow engine runs automations across Marketing, Sales, and Support instead of forking a bot per channel. Telegram, WhatsApp, and Slack are tool-calling surfaces on the same Node.js API and PostgreSQL store as the dashboard, so a request from chat and a request from the product hit the same teams.

Key technical decisions

• 01Meet people inside Telegram, WhatsApp, and Slack instead of asking them to adopt a separate dashboard.
• 02Role-based specialists over one general-purpose agent, so Marketing, Sales, and Support stay distinct.
• 03One workflow engine across all three domains, so automations compose instead of being rebuilt per team.

Screenshots

Impact

• Small teams got specialist coverage across Marketing, Sales, and Support without hiring a person for each seat.
• The same teams are directed from Telegram, WhatsApp, Slack, or the dashboard.
• Shared workflows cut the manual handoff between those three functions.