Loading…
Browse by type
Explainer reads
Explainer posts on Yomu, summarised newest first.
- 1,318 posts
- 20 companies
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Explainer posts
Intercom presents Engineer Chats - The Intercom Blog
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
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.
3 Questions to Ask Before Scaling Your Customer Service
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
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
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
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.
Building Reliable Data Analytics Agents: Lessons from the KDD Cup
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]
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.
Product Teams: How to Build & Structure Product Teams for Growth
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
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.
Intercom's product principles: Start with the problem to achieve better solutions - The Intercom Blog
Intercom’s primary product principle “Start with the problem” guides all its teams to focus on understanding real customer issues more deeply before designing any solutions. The company argues that many businesses fail because they quickly jump to solutions without thoroughly exploring the underlying problem, leading to solutions that often miss the mark, do not match real customer needs, and end up unused entirely. Common pitfalls include insufficient problem comprehension, failing to update problem understanding over time, and solving problems that are too niche, not urgent, or not aligned with customer needs. To counter this, Intercom dedicates about a third of a team’s effort to problem definition before any building begins, using problem statements and customer research. This whole-team approach builds shared understanding, ensures accurate solutions, and allows “porpoising” between problem and solution understanding while defining measurable success metrics upfront to validate impact.
Clear career paths for high-performing Data Science and Research teams
Intercom created a unified RAD function 18 months ago, merging Product Research and Product Analytics to drive evidence-based decisions. To build a high-performing team, they developed career ladders with two paths: individual contributor and manager, where management is a lateral move, not a promotion. The IC track spans Associate to Senior Principal and assesses six skill sets: mastery, partnerships and influence, impact, leadership, communication, and feedback and collaboration, with specific competencies like tools and methods, product knowledge, and mentorship. The management track focuses on five skill sets: leadership, people management, business strategy, product strategy, and execution and impact, where managers are expected to be role models, uplevel the RAD function, and coach their teams. These ladders, created with managers Nick, Louis, and Hayley, clarify roles, align expectations, promote development, and enable fair performance calibration, prioritizing mastery and communication across both paths.
The 6 Stages of an Effective, Quick Decision-making Process
According to research by Wal McConnell and Lynsey Duncan, quick decision-making is a startup’s biggest competitive advantage, but it is often dismissed as reckless. The post proposes a six-stage process that addresses two key challenges: balancing intuition, experience, and data as inputs, and creating a feedback loop that studies the decision itself rather than just the outcome. The stages begin with defining the dilemma and establishing a default decision—what you would choose immediately—then ask what evidence would change that choice, research that evidence, identify a set of meaningful alternatives, and make a risk-versus-reward decision with documented rationale. Finally, the process requires reviewing both the outcome and the decision quality, independent of the outcome, to extract learnings and improve future decisions. The approach advocates breaking large decisions into smaller experiments, continuously reviewing assumptions, and iterating quickly to maintain agility and momentum.
How (and Why) We Refreshed Our Brand - The Intercom Blog
Intercom refreshed its brand after stress-testing the 2018 rebrand over several years, revealing scalability issues in illustration, color, typography, product visuals, and voice. The illustration style was difficult to replicate without a full-time illustrator, the mint-and-black color palette was constraining and at times appeared childish, and typography lacked personality. The team introduced thinner-lined illustrations with strategic usage guidelines, created a custom headline font called Honey complemented by Smile and Intercom Brand fonts, and reduced product abstraction to let the product itself do the heavy lifting. They defined voice characteristics as conversational, clear, confident, and delightful while avoiding goofy, oversimplified, flashy, or corporate tones to ensure consistent scaling. The year-long refresh was led by the internal Brand Studio, leveraging in-house talent across design, typography, and copywriting, and included an extensive brand audit.
Product strategy best practices [with examples]
Product strategy requires being great at saying no, not maybe or later, to maintain a cohesive product with well-defined parameters. When a product gains traction, good ideas for features come from customers, colleagues, and oneself, each with reasons to say yes. The post presents 12 common arguments used to sneak features in, such as selective data analysis, feature blackmail, and appeals to anecdote or raw numbers. It argues that even good ideas should be rejected if they do not fit within the product’s purview, as every addition adds hidden complexity and weakens product definition. Saying no to good ideas is the hard part of product decisions, distinguishing a repository of features from a true product.
Product Judgment: How to repeatedly create product success
Product judgment is the ability to use your own intuition to repeatedly and accurately predict what customers need, want, and value, and to design and ship the right solution for them. It is not innate but learned through years of deliberate, wide-ranging direct experiences with real customers using your product, covering both the product and the market sides and all customer types. Indirect sources like summarized feature requests, survey data, or recorded interviews cannot create it, only supplement judgment already built through direct contact. You must also deeply know your product by using it yourself to fully interpret customer feedback and ask perceptive questions, and you must continually check your predictions against outcomes to refine your judgment. Building strong judgment requires never-ending customer contact as technology and competitors evolve, is domain specific, and typically demands at least 100 to over 1,000 direct interactions.
Run less software - The Intercom Blog
To survive intense competition from copycats and dominant tech companies, software businesses must execute faster and more efficiently than their rivals. Run Less Software is a three-pillar philosophy that helps teams achieve this: choose standard, boring technologies to build deep expertise and reduce operational overhead; outsource undifferentiated heavy lifting like infrastructure to specialized third-party providers; and focus all engineering effort on creating enduring competitive advantage that directly serves customers. For example, Intercom consolidated from MongoDB and Postgres to AWS Aurora and DynamoDB, standardizing on MySQL and gaining 5x throughput at a 30% cost reduction with minimal custom code. By constraining the toolset, teams become expert operators who can make faster, cheaper decisions. The philosophy enables companies to manipulate time and stay ahead of competitors by systematically reducing the cost and risk of their engineering decisions.
Systems Thinking: How to Apply in Product Design [+Tips]
Systems thinking is a top-down design approach that considers the overarching system before diving into specific interface interactions, preventing premature detail fixation. It is based on Donella H. Meadows’ definition that a system is an interconnected set of elements coherently organized to achieve something, prompting questions about elements, interconnections, and purpose. For Intercom’s Articles product, the team identified the article as the core element and mapped how articles are created, delivered, and interact with other systems, resulting in a complex system diagram. This systems view revealed opportunities like an intelligent suggestion engine that recommends articles during conversations and allowed the team to prioritize the most important parts to build first. The approach also encouraged reusing the Messenger Reactions component for article feedback, sharing design and implementation details like hover effects and clicked states across contexts.
Prioritizing product announcements in a SaaS world - The Intercom Blog
SaaS companies ship continuously, creating endless marketing opportunities, but announcing everything leads to audience fatigue. Intercom experienced over 12X growth in new signups since investing in marketing in 2014, with product announcements as a primary contributor. They shipped over 100 features in a year and needed a framework to prioritize announcements. Their framework uses two axes: value (existing versus new customers) and innovation (catch-up versus new solution), yielding four priority levels: P1 for big announcements attracting new customers, P2 for features valuable to existing customers, P3 for gap-filling features, and P2 also covers features that unblock sales. Each priority maps to specific tactics: changes page entries accessible inside the app, targeted in-app messages based on usage, email for inactive users, video for demonstration, landing pages, and press coverage only for major announcements.
How Customer Service Metrics Are Changing in the Age of AI - The Intercom Blog
Customer service metrics must evolve as AI chatbots become the first point of contact for support teams. Traditional metrics like first response time and average handle time now need separate reporting for bot and human interactions, since AI delivers near-instant responses and handles simpler queries. Cases handled loses relevance as support reps focus on more complex issues and tasks such as help center content creation; automated resolution rate becomes a key productivity measure. New emerging metrics include bot involvement rate, bot engagement rate, and AI-powered conversational insights that analyze customer interactions at scale. Leaders should reset SLAs and benchmarks while tracking both bot and human performance to get a true measure of success, as 69% of support leaders plan to increase AI investment.
Top topics
- Architecture830
- Performance812
- LLMs649
- Machine Learning617
- Open Source561
- AI Agents543
- AI456
- Developer Experience447
Weekly digest
The best engineering reads, once a week.