FibeAI Suite

Pipeline · CRM sync

CRM & platform sync

Monitor connector health, field mapping and sync errors across Fibe's growth and loan origination stack.

Pilot estimate

Connectors healthy

4 / 5

WhatsApp BSP degraded

Records synced today

10,464

↑ 6.1% · pilot estimate

Avg API latency

240 ms

↑ 30 ms · pilot estimate

Open sync errors

3

Requires retry

CRM core (Salesforce)

Last sync 2 min ago

Healthy

Ad platforms (Google/Meta)

Last sync 6 min ago

Healthy

WhatsApp BSP

Last sync 24 min ago

Degraded

Telephony (DeployOne voice)

Last sync 1 min ago

Healthy

LMS / loan origination system

Last sync 4 min ago

Healthy

Sync run history

Recent synchronization jobs across connectors

RunConnectorStartedRecordsStatus
R-3301CRM core10:02 AM1,842Success
R-3302WhatsApp BSP09:48 AM612Partial
R-3303Ad platforms09:30 AM4,210Success
R-3304LOS09:15 AM980Success
R-3305Telephony08:55 AM3,120Success
R-3306WhatsApp BSP08:40 AM540Failed

Field mapping

Growth lead fields mapped to CRM/LOS schema

Source fieldTarget fieldType
lead.mobile_numberContact.PhoneString
lead.bureau_bandCustom.Bureau_Band__cPicklist
lead.loan_purposeOpportunity.Purpose__cPicklist
lead.requested_amountOpportunity.AmountCurrency
voice.intent_scoreCustom.AI_Intent_Score__cNumber
los.sanction_statusOpportunity.StageNameString

API health

Median sync latency across the day (ms)

Error & retry queue

Failed sync events awaiting resolution

ErrorConnectorMessageStatusAction
E-771WhatsApp BSPTemplate approval mismatch for EMI reminderFailed
E-772CRM coreDuplicate contact conflict on mobile numberFailed
E-773LOSTimeout syncing sanction status batchFailed

Deduplication rules

Rules preventing duplicate borrower records

  • Match on mobile number (exact)Active
  • Fuzzy match on name + cityActive
  • Merge on PAN hash when availableBeta
  • Cross-channel WhatsApp/voice reconciliationNeeds tuning