Haton — CRM and lead service layer
An integration backend for leads, CRM, telephony, analytics, Telegram notifications, and scheduled sales operations.
- Client
- Haton
- Duration
- backend and integrations
The service accepted leads, connected external systems, and kept CRM workflows technically disciplined
This was not a website. It was a sales operations node.
What the service handled
Leads
We built an input layer for leads from multiple sources: forms, partner flows, statuses, checks, phone normalization, and handoff to the next system.
CRM
We connected the service with Bitrix24: lead search and updates, contacts and deals, responsible-user correction, deduplication, and regular synchronization.
Communication
We connected telephony, Telegram, and mail webhook flows so sales events did not disappear between systems and reached the right people.
Operations
We set up background commands, queues, schedules, health monitoring, and service operations that keep integrations from turning into manual chaos.
A layer between business and a zoo of services
Haton had many working loops: CRM, telephony, analytics, leads, notifications, managers, and scheduled fixes. We built a service layer that receives messy external events, normalizes them, and sends them further so sales can work without constant manual stitching.
Why this is in the portfolio
This is an engineering project without a glossy showcase, but with real operational weight. Such systems matter because they quietly remove losses: duplicate leads, missed calls, wrong statuses, CRM drift, and invisible failures in background jobs.
In short
- Focus
- leads and CRM
- Stack
- Laravel and Vue
- Scope
- sales integrations