# Ishay Tentser

Ishay Tentser creates practical LinkedIn content about using WhatsApp with CRMs and sales and support workflows, including shared inboxes, conversation handoffs, and AI tools for managing customer chats.

- Profile: https://b2binfluencer.marketing/creators/ishay-tentser/
- LinkedIn: https://www.linkedin.com/in/tentser
- LinkedIn followers: 31,824
- Topics: artificial-intelligence, sales
- Based on 11 dated posts, latest 2026-10-07

## Summary

Ishay Tentser is most useful for practical LinkedIn content about WhatsApp-to-CRM workflows, shared inboxes, handoffs, and AI chat management.

- Best for: A B2B SaaS CRM or sales operations brand wanting WhatsApp-to-CRM content collaboration or paid advisory.
- Not for: A consumer brand wanting broad reach, lifestyle posts, personal stories, or general audience engagement.
- Check first: Confirm reach, engagement, follower job titles, and partnership terms before any paid commitment.

### Takeaways

- The CRM is rarely the real bottleneck; the gap between WhatsApp and the record is.
- A personally owned WhatsApp number is an ownership problem that starts on day one.
- AI should help find the right conversation, not send more messages.

## Main ideas

- **The CRM is rarely the real bottleneck; the gap between WhatsApp and the record is**: Ishay Tentser argues that slow deal cycles get blamed on the CRM when the delay actually sits between a WhatsApp conversation and the system that tracks the customer. A CRM can have pipelines, automation, reports and AI and still leave the most important message outside the record. The delay shows up in manual record creation, context split across separate numbers, handoffs that depend on someone forwarding or explaining messages, and follow-ups moved by hand between WhatsApp and the CRM. Swapping CRMs will not fix those problems; the focus should be the integration layer: what gets logged, how numbers are consolidated and what CRM events can trigger.
- **A personally owned WhatsApp number is an ownership problem that starts on the first day**: When a sales rep leaves, a personally owned WhatsApp number leaves with them, along with the account, chat history, unread threads and the customer relationship, even though the company may still own the CRM record. Tentser frames this as a design failure rather than a bad offboarding process. The practical risks: the company cannot reliably onboard, audit or offboard the account; managers reviewing work conversations may also see a rep's personal chats; and a later move to the WhatsApp Business API becomes harder when the company does not control the number. A conversation can still feel personal when the number belongs to the business: what keeps it human is how the rep talks to the customer, not who holds the SIM.
- **Say what an integration does not do**: Tentser puts boundaries alongside capabilities, spelling out what a connector will not do as well as what it will. That helps buyers burned by integration claims understand what actually lands in the CRM before trusting it. Unstated limits are where implementations fail; across the posts, the goal is not to put another tool between the rep and the customer.
- **AI should help find the right conversation, not send more messages**: Tentser argues that AI's value comes from context and triage inside the inbox teams already use. Customer context is often trapped in individual WhatsApp chats, spread across several numbers or copied into the CRM too late, leaving an assistant without anything useful to work from. Rather than simply sending more messages, AI should locate a stalled conversation and help the team decide what deserves attention.
- **Teach with a diagnostic and hand the decision back to the reader**: The method is consistent: open with a claim or named failure, explain why it matters, give a short checklist of checked and crossed items, add product or workflow specifics, then ask readers to find their own bottleneck. The operational vocabulary suits sales managers, sales-ops leads and support leads who already use WhatsApp as a working channel. The posts assume readers are deciding how to keep records, ownership and handoffs straight—not whether WhatsApp is worth using.

## Work to read

- [Your CRM may not be the reason deals move slowly](https://www.linkedin.com/posts/tentser_your-crm-may-not-be-the-reason-deals-move-activity-7511666293385928704-t7KB)
- [When a sales rep leaves, their personally owned WhatsApp number leaves with them](https://www.linkedin.com/posts/tentser_when-a-sales-rep-leaves-a-personally-owned-activity-7510216749787820032-723V)
- [Sugar AI may be the current name, but the old SugarCRM workflow problem is still familiar](https://www.linkedin.com/posts/tentser_sugar-ai-may-be-the-current-name-but-the-activity-7512028686028800000--T0f)
- [A useful GoHighLevel and WhatsApp setup does not have to force the entire conversation into the CRM](https://www.linkedin.com/posts/tentser_a-useful-gohighlevel-and-whatsapp-setup-does-activity-7511303907525160963-eZmY)
- [Today, TimelinesAI's WhatsApp MCP went publicly live in the ChatGPT plugin marketplace](https://www.linkedin.com/posts/tentser_today-timelinesais-whatsapp-mcp-went-publicly-activity-7513567840147329025-P6iA)

## Brand relationships

- **TimelinesAI** (disclosed_partnership)
- **GoHighLevel** (mention)
- **SugarCRM** (mention)

## Partnerships

All five posts center on TimelinesAI's WhatsApp tooling: integration walkthroughs for GoHighLevel and Sugar AI, a WhatsApp-to-CRM delay diagnostic, an argument for company-controlled numbers, and the announcement that TimelinesAI's WhatsApp MCP went live in the ChatGPT plugin marketplace. The posts are written from inside this product-vendor relationship. They don't state what a brand could commission from Ishay Tentser, what it would cost, or how to submit a proposal. Ask for available formats, rates and a partnership contact.

## Alternatives

- Corrina Owens: Choose Corrina Owens for a campaign aimed at buyers concerned with CRM data quality and AI-agent readiness, rather than WhatsApp mechanics. The two posts argue that agents layered on duplicate, poorly enriched CRM records make faster routing and outreach look efficient while producing more cleanup work. The practical sequence is waterfall enrichment, identity resolution and ownership, routing, scheduling, workflows and a unified data layer. That fits a campaign for buyers who worry their CRM data is not clean enough for AI and want a diagnostic-led post or advisory session on fixing the revenue data layer before adding agents.
- Meilech Biller: Choose Meilech Biller for a campaign aimed at prospects seeking an operator's firsthand account of AI running inside a business, not a category analyst's breakdown. The posts show Claude-built CRM and project systems, an onboarding flow with custom forms and emails, a daily review of CRM, projects, WhatsApp chats and email that produces a task list, and client-facing ecommerce lifecycle work. That suits a campaign asking prospects to copy a working AI-operations setup, or a vendor that wants WhatsApp shown as one part of a broader automated client-delivery stack. The ecommerce and agency detail gives the content practical, 'here is how I run it' credibility.
- Ross Keating: Choose Ross Keating for a campaign aimed at positioning around AI sales execution, CRM hygiene and manager coaching, with WhatsApp as one access channel rather than the integration story. The Overpath and Molly launch post describes an AI teammate that works through Slack, Teams, WhatsApp, web and voice, focuses on proactive deal execution, CRM hygiene and coaching, and argues that no CRM ever made a salesperson sell better. A second post contrasts AI-mature sales leaders who treat CRM as a data hub and build a context layer with teams still updating Salesforce or HubSpot manually. That fits a campaign aimed at sales leaders weighing an AI agent or coaching layer on top of CRM.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/