---
title: "Latest reads"
description: "The engineering internet, summarised so you can actually read it."
---

# Latest reads
> The engineering internet, summarised so you can actually read it.

## Articles

### [2021 in conversation: Learnings from the podcast - The Intercom Blog](https://yomu.fyi/post/2021-in-conversation-learnings-from-the-podcast-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

In this 2021 year-end compilation, Intercom reflects on insights from its podcast series Inside Intercom, featuring conversations with business leaders and pioneers like CEO Karen Peacock, Hubert Palan from Productboard, and Amanda Renteria from Code for America. They discuss leadership, product strategy, customer experience, and the challenges of running a business during the pandemic, including building world-class customer experiences and addressing diversity gaps. Speakers like Farhan Virji from Later share how B2C support strategies can inform B2B teams, while Will Larson of Calm explores technical leadership careers beyond management. The episode also marks Intercom’s 10th anniversary, with founders Des Traynor and Paul Adams reflecting on maintaining speed as the company scales and avoiding unnecessary processes that slow progress. Zanade Mann and Janeen Uzzell offer insights on allyship, diversity, and ensuring knowledge equity in government services, as well as the importance of advocating for underrepresented groups.


### [Intercom presents Engineer Chats - The Intercom Blog](https://yomu.fyi/post/intercom-presents-engineer-chats-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

Intercom released Engineer Chats, an internal podcast about engineering topics, making its episodes publicly available. The podcast explores disambiguation, described by Senior Principal Engineer Mike Stewart as narrowing a wide solution space based on evidence, applied throughout product development from roadmap planning to coding. Another episode recounts Intercom’s worst outage, where a premature automation command triggered a cascading failure that queued SMS messages incorrectly for hours, revealing risks of automation. The podcast also discusses the importance of speed for startups, advising teams to run and do things this week instead of next quarter. Additionally, a conversation between engineering and legal teams emphasizes that legal is not there to slow R&D but to ensure responsible growth within legal confines through compliance by design.


### [The Ultimate Customer Support Tech Stack for 2024](https://yomu.fyi/post/the-ultimate-customer-support-tech-stack-for-2024.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

Customer support teams face inefficiencies from outdated and disconnected tools, with 54% unable to personalize support and 50% wasting time switching between applications. The modern support tech stack should be built around a connected framework like Intercom’s Support Funnel, which integrates three layers: proactive messaging to preempt issues, self-serve bots and knowledge bases for repetitive queries, and human support with automated workflows. An all-in-one platform such as Intercom provides the foundation, offering live chat, chatbots, a team inbox, integrations, and reporting capabilities. The stack should also integrate with specialized tools like Stripe for subscription management, Aircall for phone support, and RemoteHQ for co-browsing, as well as automation tools like Zapier. This approach aims to scale personalized support without proportional cost increases, improving customer satisfaction and retention while shifting support from a cost center to a value driver.


### [Upgrade your support: Announcing Intercom’s WhatsApp integration](https://yomu.fyi/post/upgrade-your-support-announcing-intercom-s-whatsapp-integration.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Announcement

Intercom has partnered with WhatsApp to offer an integration that lets businesses manage customer support conversations directly from the Intercom Inbox, reaching WhatsApp’s 2.5 billion users across over 100 countries. The integration simplifies omnichannel support by bringing WhatsApp messages into the same tool where teams already handle other channels, eliminating the need for separate software or new processes. Customers can initiate a conversation through the Intercom Messenger and then seamlessly switch to WhatsApp by scanning a QR code, making it easier to receive support on their preferred platform. Support teams continue using their existing workflows because core inbox tools such as rules, SLAs, and macros work with WhatsApp conversations, and messages appear directly in their usual inbox. Additionally, reporting features allow businesses to compare WhatsApp’s conversation volume, response times, and customer satisfaction against other channels to optimize their omnichannel strategy.


### [How Support Leaders Can Empower Their Teams - The Intercom Blog](https://yomu.fyi/post/how-support-leaders-can-empower-their-teams-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Problem & solution

Human support remains critical for customer satisfaction even as automation improves, especially for complex or emotionally charged issues that bots cannot handle. The Conversational Support Funnel framework helps companies balance proactive, self-serve, and human support layers to route only the most impactful queries to live agents. Automating repetitive tasks and integrating support tools frees team members to focus on meaningful problem-solving. Support leaders should rethink traditional metrics like CSAT to account for the difficulty and emotional toll of complex work, and provide clear escalation paths for difficult situations. Investing in team development and well-being through these practices improves retention, morale, and long-term customer loyalty.


### [Building bots for success: The custom bot that saved logistics platform Stuart over 2.5k hours per week - The Intercom Blog](https://yomu.fyi/post/building-bots-for-success-the-custom-bot-that-saved-logistics-platform.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Problem & solution

Stuart, a logistics platform owned by GeoPost, faced the challenge of scaling support for its delivery partners without slowing response times or losing the personal touch. After analyzing their support journey, Head of LiveOps Andrew Baylis and Program Manager Marina Alejo identified that manual handling of every conversation was inefficient and implemented an Intercom Custom Bot, the courier bot. The bot operates across four delivery stages, resolving common queries automatically and collecting context before routing complex issues to agents, reducing manual intervention to 55%. As a result, the bot saves over 2,500 support team hours and automatically resolves 55,000 chats per week, with response times under 30 seconds and resolutions four times faster. Additionally, handling time per case is two minutes faster and delivery partner satisfaction has increased by 4%, with plans to further expand self-service capabilities.


### [Announcing The Ultimate Modern Support Tech Stack Guide](https://yomu.fyi/post/announcing-the-ultimate-modern-support-tech-stack-guide.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Announcement

Intercom announced a new guide titled ‘The Ultimate Modern Support Tech Stack,’ addressing the need for support teams to move beyond outdated, disconnected tools. The guide cites a Forrester study finding only 37% of support leaders are satisfied with their current tools, highlighting widespread dissatisfaction. It promotes the emerging conversational support category as a solution that balances personal and efficient customer service. The guide provides a framework for optimizing support tech stacks and recommends integrations with tools like HubSpot, Zapier, and Stripe. Internal research predicts conversational support will capture over a third of the support software market in coming years.


### [Tactics to stay ahead of the curve and boost efficiency with proactive support - The Intercom Blog](https://yomu.fyi/post/tactics-to-stay-ahead-of-the-curve-and-boost-efficiency-with-proactive.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Problem & solution

Customer support is shifting from a reactive cost center to a proactive value driver, with leaders adopting conversational, messenger-based approaches to meet rising customer expectations. Proactive support uses targeted messages, banners, and custom bots to address known issues before customers ask for help, reducing inbound volume. Tanda doubled its client base while keeping its support team the same size, achieving better first-response times through proactive communication. TrueCommerce cut contact rates for temporary issues by nearly 80% by sending outbound alerts to affected users. These tactics help companies scale support, improve efficiency, and maintain customer satisfaction scores above 90%.


### [Intercom turns 10: Highlights from our first decade - The Intercom Blog](https://yomu.fyi/post/intercom-turns-10-highlights-from-our-first-decade-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Announcement

Intercom marked its 10th anniversary by reflecting on major milestones from its first decade. The company was founded in August 2011 by Eoghan McCabe, Des Traynor, David Barrett, and Ciaran Lee, who sought to make internet business personal. Intercom released the world’s first in-app messenger in 2011, which later evolved into a full-fledged Business Messenger with a homepage and embeddable apps. The company also published a series of books on product management, customer engagement, and Jobs-to-be-Done. In July 2020, Karen Peacock became CEO, succeeding Eoghan McCabe, who moved to Chairman.


### [3 Questions to Ask Before Scaling Your Customer Service](https://yomu.fyi/post/3-questions-to-ask-before-scaling-your-customer-service.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

Companies scaling their customer service should first ask whether their tools are scalable, as legacy channels like phone and email are labor-intensive and difficult to scale. A next-generation messenger-based support solution can improve efficiency by collecting information upfront, enabling reps to handle multiple chats, and using bots for simple queries. Second, teams must maintain high standards as conversation volumes rise by using automation to resolve repetitive questions, freeing agents for complex issues. Third, businesses should adapt to evolving customer needs by incorporating self-serve and proactive support layers, reducing inbox volume and allowing focus on high-value VIP customers. Laying this infrastructure early can result in significant time and cost savings while improving customer satisfaction.


### [What Is Proactive Support and Why Do You Need It? - The Intercom Blog](https://yomu.fyi/post/what-is-proactive-support-and-why-do-you-need-it-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

Proactive support is a strategic approach to helping customers before they contact support, using tools such as outbound messages, banners, and Product Tours to deliver targeted assistance. By preemptively answering common questions, it reduces inbound conversation volume, frees support teams for complex queries, and improves long-term metrics like customer retention and satisfaction. A commissioned Forrester Consulting study conducted on behalf of Intercom in April 2021 found that 59% of support leaders and decision makers view a lack of proactive support as a barrier to conversational support at scale. Implementing a proactive strategy requires understanding the customer journey and pain points to deliver targeted, non-intrusive help via messenger-based channels at key moments. This approach creates a better customer experience while optimizing support team resources, making it crucial for a future-ready support strategy.


### [Automation in action: Proven ways to boost the bottom line with self-serve support - The Intercom Blog](https://yomu.fyi/post/automation-in-action-proven-ways-to-boost-the-bottom-line-with-self-se.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

Self-serve support combines automation and human expertise to deliver scalable yet personal customer service. The Conversational Support Funnel framework integrates proactive, self-serve, and human support layers to balance efficiency and personalization. Case studies demonstrate significant gains: Stuart reduced support workload by over 2,500 hours weekly using Custom Bots, and in a test with a pharmacy client, 70% of inbound queries were resolved through self-serve. SMARTY saved 7,000 support team hours annually with Resolution Bot, achieving a 99% reduction in median first-response time. Livestorm maintained a 94% customer satisfaction score while automatically resolving one in four queries, and Rugs.com increased support efficiency tenfold by switching from phone to chat. The post notes that 57% of support teams now measure revenue impact, and self-serve support lowers response times, frees agents for complex issues, and drives retention and expansion.


### [How Every Team Benefits From Conversational Support - Scale by Intercom](https://yomu.fyi/post/how-every-team-benefits-from-conversational-support-scale-by-intercom.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

Conversational support is a digital-first, messenger-based approach to resolving customer queries, enabling real-time or asynchronous communication and preserving context across interactions. By combining custom chatbots and automation, it streamlines support workflows and reduces repetitive tasks. A 2021 Forrester study commissioned by Intercom found messaging-based support became the second most used channel, with 60% of leaders reporting improved customer retention and 58% reporting increased efficiency. The approach benefits multiple teams: sales and marketing can capture qualifying customer data upfront, such as company size and plan tier, while product teams identify trends from support topics for better development decisions, and customer success teams deliver personalized experiences. For agents, automating low-value tasks like password resets reduces burnout, improves job satisfaction, and lowers turnover costs from hiring and training replacements.


### [Introducing the Anthropic Cyber Mission](https://yomu.fyi/post/introducing-the-anthropic-cyber-mission.md)
- Company: [Anthropic](https://yomu.fyi/company/anthropic.md)
- Author: Anthropic
- Published: Oct 8, 2026
- Type: Announcement

State-sponsored adversaries have gained footholds in critical infrastructure such as power grids, water systems, and transportation networks, while open-source software faces increasing vulnerability exploits. To support defenders, Anthropic launches the Cyber Mission, a long-term commitment that includes the Critical Infrastructure Defense Program and OSS Scanner. The Critical Infrastructure Defense Program provides frontier Claude models, on-site engineers, and threat research to trusted providers like Accenture, CrowdStrike, and Rockwell Automation to secure operational technology. OSS Scanner offers open-source projects free regular security scans from Anthropic’s strongest models, and the expanded Cyber Verification Program gives more defenders access to advanced cyber capabilities. The mission aims to reduce cyber risk over years through collaboration, but challenges remain as verifying and fixing vulnerabilities is slow and depends on people.


### [Building Reliable Data Analytics Agents: Lessons from the KDD Cup](https://yomu.fyi/post/building-reliable-data-analytics-agents-lessons-from-the-kdd-cup.md)
- Company: [NVIDIA](https://yomu.fyi/company/nvidia-developer-blog.md)
- Author: Jiwei Liu
- Published: Oct 8, 2026
- Type: Explainer

The NVIDIA KGMON team placed second in the KDD Cup 2026 Data Agents competition by building a reliable agent system around a small, fixed LLM. The system constrained the agent’s action space through a harness that normalized data access by converting CSV and JSON files into SQLite tables, exposed a limited set of custom functions for schema inspection, SQL queries, and answer writing, and seeded the agent with schema context before analysis. Documents and videos were handled through targeted tools like prose\_helper for extracting rules from documents and keyframe extraction with aligned transcripts for video evidence, keeping the main LLM context focused. The team emphasized inspectability by recording execution traces and running repeated attempts, using evaluation and trajectory review to identify failures and refine the harness. The key lesson is that reliability for data analytics agents often comes from the harness design, not the model’s capabilities.


### [Principles of Bot Design: Successful Chatbot Design in 2021 \[+Tips\]](https://yomu.fyi/post/principles-of-bot-design-successful-chatbot-design-in-2021-tips.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

The post argues that early chatbot attempts have failed because they over-relied on natural language processing and artificial intelligence capabilities that do not yet exist, often making users feel duped. It presents eight opinionated design principles to guide practical conversational UI development, starting with never pretending to be human. Other core principles include keeping conversations incredibly simple and bounded to particular subjects with linear flows, using structured input like buttons and custom keyboards to avoid parsing errors, and respecting the chat medium by showing formatted card previews instead of raw URLs. The post also emphasizes providing a human escape hatch and optimizing for end-user experience rather than support team convenience, with admin views maintaining full conversation context. Finally, it notes that these principles should be strongly held as a decision-making north star but allowed to evolve as technical possibilities improve.


### [Intercom's New Book: A Guide to Project Management](https://yomu.fyi/post/intercom-x27-s-new-book-a-guide-to-project-management.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Announcement

Intercom published its first book, ‘Intercom on Product Management’, consolidating and updating their best articles from over two years on fundraising, pricing, process, design, and product management with new content to bridge gaps and clarify concepts. The book delivers practical, grounded advice for anyone who works with products, directly addressing the lack of value in abstract and clichéd guidance. The team optimized the reading experience across all devices, creating epub, mobi, and PDF formats with careful design, layout, and visuals, crediting Frantisek Kusovsky and Jeff Kriege for their tireless work. The book is free, with a request that readers share it with others, and even regular readers benefit from updated content that removes repetition and clarifies concepts. Intercom views this publication as the beginning of a series, with plans to continue writing and release more books, measuring value by impact rather than length or breadth.


### [Product Teams: How to Build & Structure Product Teams for Growth](https://yomu.fyi/post/product-teams-how-to-build-amp-structure-product-teams-for-growth.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

Intercom shares the process it used to scale its product team from a smaller size to four Product Managers, four Designers, and 25 Engineers over 12-18 months. The process is built on four areas: decision-making guidelines, clear role-based accountability, a lightweight transparent roadmap, and a culture of goal setting. The roadmap has three timeframes: solid releases for the next 4-6 weeks, planned high-level briefs for the following months, and speculative ideas beyond that. Accountability is assigned by role, with the PM responsible for problem analysis and success, the Designer for design quality, and the Engineering Lead for delivery and code quality. Teams set weekly goals tracked in an internal tool called Hustle and daily goals on whiteboards, with weekly demos every Friday to reinforce the cadence of building.


### [Designing Features Using Job Stories - Inside Intercom](https://yomu.fyi/post/designing-features-using-job-stories-inside-intercom.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

Personas rely on demographic attributes that fail to explain causality behind consumption, and User Stories couple implementation with motivations, obscuring reasons for feature failure. Job Stories overcome this by focusing on the situation, motivation, and desired outcome without prescribing a solution. A case study demonstrates the approach: designing a profile page for a car loan application, using a five-step process starting with the high-level job of helping salespeople secure loans. The team observed customers currently rely on physical proximity to assess trust, and wrote a Job Story about anxiety of sharing sensitive data electronically. The resulting UI featured the salesperson’s photo, title, cars sold, years at company, and contact options, each chosen to ease customer anxiety and ensure safe data sharing.


### [The dribbblisation of design - The Intercom Blog](https://yomu.fyi/post/the-dribbblisation-of-design-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Problem & solution

Paul Adams argues that the Dribbble community rewards superficial aesthetics, moving product design backward. He observes that job applicants often submit pixel-perfect PNGs lacking context, business constraints, or problem definition, focusing on visual polish rather than solving real problems. Strong candidates instead present sketches, whiteboard diagrams, and prototypes that show interactions with real data, documenting pros, cons, and tradeoffs made during the process. True product design begins with company mission and a clear product architecture defining system components and their relationships, such as Facebook’s directory of people, friends, and interests with its relationship map, then progresses through outcome, system, interaction, and visual layers. The Jobs framework, structured as ‘When \_\_\_\_, I want \_\_\_\_, so I can \_\_\_\_,’ forces designers to specify triggering events and desired outcomes, ensuring designs are mapped to the company mission and product architecture.


[Newer posts](https://yomu.fyi/posts/page/15.md) · [Older posts](https://yomu.fyi/posts/page/17.md)