Building a Unified D365 CRM Architecture for Etisalat

The Etisalat Challenge

Etisalat (now e&) was operating D365 across 7 different business units with:

• Siloed pipelines per division
• No unified customer view across touchpoints
• Manual handoffs between sales channels
• CloudTalk calls not linked to CRM records

Architecture Solution

Centralized Pipeline Model

We created a hub-and-spoke D365 architecture:

             ┌─────────────────────┐
             │   Unified D365 Hub  │
             │  (Master Pipeline)  │
             └────────┬────────────┘
          ┌───────────┼───────────┐
     Enterprise   SMB Sales   Retail
      Channel      Channel     Channel

Each channel retained its own views and workflows, but shared the master customer record and opportunity chain.

CloudTalk Sales 365 Integration

We built a custom Power Automate flow to:

1. Auto-create D365 activity on call start
2. Capture call disposition on hang-up
3. Trigger follow-up task creation based on outcome

// D365 Web API – create call activity
var callActivity = new JObject
{
    ["subject"] = $"CloudTalk Call - {lead.FullName}",
    ["actualdurationminutes"] = callDuration,
    ["directioncode"] = true, // outbound
    ["regardingobjectid_lead@odata.bind"] = $"/leads({lead.Id})"
};
 
await _crmClient.CreateAsync("phonecalls", callActivity);

Results

• Single customer record across all 7 business units
• 35% improvement in lead-to-opportunity conversion visibility
• CloudTalk calls auto-logged — zero manual activity entry
• Sales managers got unified pipeline dashboards for the first time