Close
Native Close integration: every iMessage conversation lands on the right lead's activity feed, matched by phone, with optional lead creation for unknown numbers.
What you get
A native connection, not an API build. Once connected, Blue Reacher writes each iMessage conversation into the matching Close lead's activity feed, so reps see the thread where they already work.
- Lead activity. Outbound messages and inbound replies appear on the lead's activity feed as they happen.
- Phone matching. Contacts match to leads by phone number. Numbers stored without a country code will not match; fix the field, not the integration.
- Optional lead creation. An inbound message from a number Close does not know can create a new lead automatically, or be left unmatched if you prefer a clean list. Your call, set once.
Connecting
Done-for-you setups get this connected during onboarding: we authorize the connection with you and confirm matching against a handful of real leads before anything goes live. There is nothing to host.
Where the API fits alongside it
The native sync covers reading and logging. For triggering sends from Close automations, or anything the native path does not express, the REST API and webhooks work the same as for any CRM; the patterns are in CRM integrations.
Salesforce
The native Salesforce integration puts iMessage threads on Contact and Lead timelines with an embedded reply panel; the Flow build below covers record-triggered sends.
Pipedrive
Native Pipedrive integration: iMessage conversations on the matching contact's timeline, matched by phone, with optional person creation for unknown numbers.