Send iMessage from Pipedrive.
Pipedrive shut off its native messaging API on February 1, 2026. Tuco is a live alternative: message warm leads on iMessage and log every reply as a Note and Activity on the Pipedrive Person and Deal.
Private integration, set up during onboarding. No public Marketplace install yet — access is by request.
98%
Delivery rate
vs 68% SMS
3x
More replies
than SMS
Notes
+ Activities
on every record
Feb 1
API shut off
2026
The messaging gap
Pipedrive killed its messaging API.
Announced Nov 14, 2025. Shut off Feb 1, 2026. No drop-in replacement. Here's how messaging works now.
Native Channels API
- ✕Shut off February 1, 2026
- ✕No replacement messaging API
- ✕messengers-integration scope is dead
- ✕Old threads frozen as Notes
- ✕No way to text from Pipedrive natively
With Tuco AI
- ✓Send iMessage to warm contacts
- ✓Logged as Notes + Activities
- ✓Two-way reply sync to the record
- ✓SMS fallback for Android numbers
- ✓Set up with you during onboarding
Pipedrive's own deprecation notice said historical channel messages would be preserved in your account as Notes — which is exactly the model Tuco uses to keep your iMessage history on the record.
Features
iMessage that lives on the record.
Built around how Pipedrive actually stores conversation history.
💬
iMessage from the record
Send iMessage tied to a Pipedrive Person or Deal. No copy-pasting numbers between tabs.
📝
Logged as Notes + Activities
Every message and reply writes back to the Person and Deal as a Note and an Activity — a durable timeline, not a side inbox.
🔁
Two-way sync
Replies sync back to the record so the owner sees the full conversation history inside Pipedrive.
📈
3x reply rates
iMessage gets roughly 3x more replies than SMS on warm contacts. Better follow-up, same pipeline.
📱
SMS fallback for Android
iPhone contacts get a blue-bubble iMessage; non-iPhone numbers fall back to SMS automatically.
🛟
A live messaging alternative
Pipedrive shut off its native Channels API on Feb 1, 2026. This is a working way to text from Pipedrive again.
Workflow patterns
Six Pipedrive plays that win with iMessage.
Each send and reply lands on the Person and Deal as a Note and Activity — your timeline stays in Pipedrive.
| Pipedrive trigger | iMessage flow / how it logs | Typical outcome |
|---|---|---|
| Person created from web form | Send first-touch iMessage from the deal owner; logged as a Note + Activity on the Person | Lead-response speed under 2 min |
| Deal moved to 'Demo Booked' stage | Confirmation iMessage + 24h reminder + 1h heads-up, each logged on the Deal | No-shows down 30-45% |
| Activity due: follow-up call | Owner sends an iMessage nudge first; reply syncs back as a Note on the Person | More connects per dial |
| Deal stuck in pipeline 14+ days | iMessage re-engagement nudge from the owner; outcome logged as an Activity | Stalled deals reopened |
| Won deal → onboarding | Welcome + scheduling iMessage; thread preserved as Notes on the Person | Faster kickoff, fewer dropped handoffs |
| Inbound reply on iMessage | Reply lands as a Note on the Person and Deal; owner is alerted to take over | Nothing falls through the cracks |
Outcomes above are typical ranges from iMessage follow-up on warm audiences, not guarantees. iMessage is for contacts who already know you — form-fills, repliers, and customers.
Text from Pipedrive again.
The Pipedrive integration is private today. Book a demo to see the iMessage flow and request access for your account.
Private integration set up during onboarding. No public Marketplace install yet.
No refunds or returns.
FAQ
Questions. Answered.
Does Pipedrive still have a native messaging API?
No. Pipedrive announced the deprecation of its Channels API (the Messaging App Extension) on November 14, 2025 and shut it off on February 1, 2026, stating it wanted to concentrate on the next generation of its CRM. No drop-in replacement messaging API was offered. Existing conversation data was preserved in accounts as Notes.
How does Tuco send iMessage from Pipedrive then?
Because there is no native messaging channel anymore, Tuco logs each iMessage and reply as a Note and an Activity on the Pipedrive Person and Deal. That mirrors how Pipedrive itself preserved historical channel messages — as Notes — so your communication history lives on the record, not in a separate inbox.
Is this a one-click self-serve install from the Pipedrive Marketplace?
Not yet. Today this is a private integration we set up with you during onboarding, starting with select customers. There is no public Marketplace listing or self-serve install at this stage. Book a demo to request access and we'll walk through the setup.
Who can I message on iMessage?
iMessage is a lead-to-close channel for warm contacts — people who filled out a form, replied on another channel, are existing customers, or already know your brand. It is not for cold first-touch outreach to strangers. Use email or LinkedIn for that.
Do I need A2P 10DLC?
No. iMessage bypasses carrier A2P 10DLC registration entirely. The SMS fallback for Android numbers follows standard SMS rules.
What about non-iPhone contacts?
iPhone contacts receive a blue-bubble iMessage; non-iPhone numbers automatically fall back to SMS so the message still lands.
Will replies show up inside Pipedrive?
Yes. Two-way sync writes replies back to the Person and Deal as Notes, so the deal owner sees the full thread in the record they already work from.
What response rates should I expect?
On warm audiences (form-fills, replied prospects, customers) iMessage typically sees 5-10%+ reply rates and 15-25% booking from responders. Sending to anyone who hasn't opted in or interacted with you will tank reply rates and risk Apple ID bans.
How do I get started?
Book a demo. We'll show the Pipedrive iMessage flow, confirm fit, and set up the integration for your account. Access is by request while the integration is private.