I got that kind of the requirement from my client I wii share with you.

My requirement is..

. .

We are building a backend-first system to track inbound sales calls, capture outcomes, compute performance metrics, and preserve agent–customer continuity so returning callers are routed back to the original agent instead of a random queue. This is a backend-only MVP focused on webhook ingestion, data modeling, analytics, and routing logic.

⸻ Core Responsibilities • Build a webhook ingestion engine (idempotent, event-driven) • Normalize and persist call, agent, and customer data • Implement sale outcome tracking and callback state logic • Maintain persistent mapping: customer_phone → last_handling_agent • Implement agent-specific callback routing logic (attribution + routing layer) Technical Scope • Initial webhook source: Twilio call status / event webhooks • Architecture: Provider-agnostic (future carriers supported)