Messaging architecture, identity continuity and campaign governance for education services
Client: Conduira
Industry: Education / student services
Engagement: Messaging architecture, hands-on implementation and delivery oversight
The business priority
Conduira needed WhatsApp communication to work within its Salesforce processes. The solution established a common framework for individual messaging, personalised campaigns and workflow-driven communication, with recipient-level monitoring. All described capabilities are live.
The operating challenge
Sending a message was only one part of the requirement. The operation also needed to identify the right recipient, check eligibility, personalise approved templates, control campaign execution and distinguish API submission from actual message delivery.
My strategic contribution
I delivered this work in my role at Conduira, covering architecture, hands-on implementation and delivery oversight. I designed and implemented the communication lifecycle from recipient identification and eligibility through personalisation, sending, outcome tracking and recovery, connecting business requirements with Salesforce messaging and custom orchestration.
What made this complex
Lead conversion could change the CRM record linked to a WhatsApp identity. Campaign execution also crossed database and API transaction boundaries, while delivery receipts arrived after submission. Individual and bulk messages needed shared eligibility, identity and tracking rules.
Key decisions and their business purpose
Use one communication framework. Bring record-level, broadcast and workflow-driven messaging through common processing responsibilities. This gives identity, consent and monitoring a consistent place in the design.
Preserve recipient context. Resolve messaging identities and capture personalised parameters when campaigns are created. This addresses Lead conversion and later changes to CRM data.
Separate sending from outcome reconciliation. Queue preparation and sending, then track receipts and recoverable failures independently. This distinguishes accepted requests from delivered messages and makes failures actionable.
FROM DESIGN TO DELIVERY
What changed in the operation
What was delivered
Lead and Contact messaging interfaces using approved templates, dynamic parameters and image headers.
Broadcast and recipient records, with recipient-specific parameters captured at campaign creation.
Messaging identity resolution, phone validation, Lead-to-Contact association repair and consent checks.
Scheduled and queue-based processing, recipient-level status tracking, error information and controlled retries.
Design challenge and delivered capability
Recipient handling: CRM and messaging identities must stay aligned → Resolve identities and repair Lead conversion associations
Campaign processing: Platform and transaction constraints → Separate preparation, sending and reconciliation
Message outcomes: Submission is not proof of delivery → Recipient-level tracking and provider status receipts
The operational outcome
The live framework connects CRM-based messaging, campaign execution and recipient-level investigation. It brings individual and bulk communication into a shared processing architecture, with identity handling, consent checks, delivery tracking and controlled recovery.
Consulting perspective. CRM integration design must connect identity, eligibility, execution and recovery so that operational teams can understand and manage the communication lifecycle.
Technology foundation
Salesforce Enterprise and Service Cloud Messaging; WhatsApp Business Platform; Apex, Flow and Lightning Web Components
Start with a CRM Health Check
To start with a CRM Health Check, contact hello@growth-bridge.io, or see the services and prices.
