Contacts

Leads arrive as raw CSVs from events, webforms and partners, with mismatched headers, malformed phone numbers and duplicates baked in. Someone spends hours hand-mapping columns in a spreadsheet, and bad rows still slip through and bounce when the team starts dialing or messaging.

Standard contact fields don't capture where a lead actually came from, so attribution lives in someone's memory or a side spreadsheet. Without a lead_source on the record, you can't segment by channel or judge which campaigns are worth repeating.

A WhatsApp campaign is ready, but a large share of the audience sits in a pending consent state. Messaging them risks policy strikes and blocked numbers, while opening each contact one at a time to update consent is hopelessly slow before a launch.

Spam and abusive numbers clog the inbox and waste agent time, but a hard block is too blunt when a real contact occasionally needs short-term access. Teams end up either tolerating the noise or permanently locking out people they shouldn't.

An external tool, agency or ad platform needs a contact file, but the data is locked inside the portal with no clean way to hand it off. People resort to manual copy-paste or ask engineering for a one-off pull, which is slow and error-prone.

Before reaching out, a rep needs to know who the person is, what they've consented to, and what's happened so far — but that context is spread across tools or simply missing. Acting blind leads to off-base messages and contacting people who opted out.

People reach out across WhatsApp, SMS and other channels, but the inbound contacts get scattered and the team loses track of who actually started a conversation. Real interest goes cold because no one has a single view of recent inbound by channel.

The source of truth for contacts often lives in a CRM like HubSpot, Zoho or Pipedrive, while messaging and campaigns happen elsewhere. Maintaining two disconnected contact sets means stale data, manual re-entry and people who exist in one system but not the other.