EasyReply: Laravel Shared Inbox with Reverb & Inertia | Mohamed Said [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://www.msaied.com) [ Home ](https://www.msaied.com) [ Projects ](https://www.msaied.com/projects) [ Articles ](https://www.msaied.com/articles) [ Certificates ](https://www.msaied.com/certificates) [ Contact ](https://www.msaied.com#contact-section) [ ](https://github.com/EG-Mohamed) [ Home ](https://www.msaied.com) [ Projects ](https://www.msaied.com/projects) [ Articles ](https://www.msaied.com/articles) [ Certificates ](https://www.msaied.com/certificates) [ Contact ](https://www.msaied.com#contact-section) [ home ](https://www.msaied.com) [ articles ](https://www.msaied.com/articles) Building EasyReply: How Laravel Powers a Unified AI Customer Support Inbox On this page 1. [ The Problem: Customer Support Fragmented Across Too Many Tools ](#the-problem-customer-support-fragmented-across-too-many-tools) 2. [ The Laravel Architecture That Powers EasyReply ](#the-laravel-architecture-that-powers-easyreply) 3. [ Real-Time Updates with Laravel Reverb ](#real-time-updates-with-laravel-reverb) 4. [ SPA Feel Without a Separate API: Inertia.js + React ](#spa-feel-without-a-separate-api-inertiajs-react) 5. [ Asynchronous Processing with Laravel Queues ](#asynchronous-processing-with-laravel-queues) 6. [ Integrations Built for Developer Workflows ](#integrations-built-for-developer-workflows) 7. [ Key Takeaways ](#key-takeaways) ![Building EasyReply: How Laravel Powers a Unified AI Customer Support Inbox](https://cdn.msaied.com/669/fd8bb22561b1756195e7872aecd3335b.png) [ Laravel ](https://www.msaied.com/articles?category=laravel) [ AI ](https://www.msaied.com/articles?category=ai) #Laravel #Laravel Reverb #Inertia.js #Laravel Queues #Shared Inbox #AI Building EasyReply: How Laravel Powers a Unified AI Customer Support Inbox ============================================================================ 11 Sep 2026 3 min read ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said Table of contents 1. [ 01 The Problem: Customer Support Fragmented Across Too Many Tools ](#the-problem-customer-support-fragmented-across-too-many-tools) 2. [ 02 The Laravel Architecture That Powers EasyReply ](#the-laravel-architecture-that-powers-easyreply) 3. [ 03 Real-Time Updates with Laravel Reverb ](#real-time-updates-with-laravel-reverb) 4. [ 04 SPA Feel Without a Separate API: Inertia.js + React ](#spa-feel-without-a-separate-api-inertiajs-react) 5. [ 05 Asynchronous Processing with Laravel Queues ](#asynchronous-processing-with-laravel-queues) 6. [ 06 Integrations Built for Developer Workflows ](#integrations-built-for-developer-workflows) 7. [ 07 Key Takeaways ](#key-takeaways) The Problem: Customer Support Fragmented Across Too Many Tools -------------------------------------------------------------- Growing support teams often juggle Gmail, Slack, Instagram DMs, and a CRM simultaneously. Messages get lost, response times suffer, and engineers waste time hunting down bug reports across three different apps. [EasyReply](https://easyreply.io) was built to solve this by consolidating every channel into a single shared inbox, enhanced with AI. The entire platform runs on Laravel — and the architectural choices behind it are worth examining closely. The Laravel Architecture That Powers EasyReply ---------------------------------------------- ### Real-Time Updates with Laravel Reverb When a WhatsApp message arrives or an email enters the support queue, agents need to see it immediately — no page refresh required. EasyReply relies on **Laravel Reverb** to provide a scalable WebSocket server that pushes updates to the client the moment a new message arrives or a teammate begins typing. Because Reverb integrates directly with Laravel's event broadcasting system, triggering a real-time UI update requires minimal PHP code: ```php // Broadcast an event when a new message arrives broadcast(new NewMessageReceived($conversation))->toOthers(); ``` This tight integration means the team avoids maintaining a separate WebSocket service while still getting production-grade real-time performance. ### SPA Feel Without a Separate API: Inertia.js + React The team wanted a dynamic, component-driven interface without the overhead of building and versioning a standalone REST or GraphQL API. By combining **Inertia.js** with **React**, EasyReply gets the interactivity of a single-page application while keeping Laravel in charge of routing and data fetching. Controllers pass data directly to React components as props — no serialisation layer in between: ```php // Laravel controller returning data to a React component via Inertia return Inertia::render('Inbox/Show', [ 'conversation' => $conversation->load('messages', 'assignee'), ]); ``` This approach shortened time-to-market and keeps the codebase unified under one repository. ### Asynchronous Processing with Laravel Queues Parsing incoming email threads, processing webhooks from social platforms, syncing CRM data, and generating AI-drafted replies are all resource-intensive operations. Handling them synchronously would block the UI. EasyReply offloads every heavy task to **Laravel Queues**, keeping background workers busy while the interface stays fast and responsive. Whether it is an AI model generating a reply or a Hubspot sync running after a conversation closes, queue workers handle it without the user noticing. Integrations Built for Developer Workflows ------------------------------------------ EasyReply ships with integrations that align with how engineering and support teams actually work: | Integration | Purpose | |---|---| | **Linear** | Link support tickets directly to engineering issues | | **Hubspot** | Auto-sync customer interactions with your CRM | | **Slack** | Collaborate on support without leaving your workspace | | **Betterstack** | Sync incident reports with customer communications | | **MCP** | Allow AI agents to securely access your support data | The **Model Context Protocol (MCP)** support is particularly notable. It lets EasyReply's AI bridge the gap between the support inbox and a team's own data sources, providing contextual awareness that generic SaaS tools cannot match. Key Takeaways ------------- - **Laravel Reverb** delivers production-ready WebSocket broadcasting with minimal configuration, ideal for real-time collaborative tools. - **Inertia.js + React** eliminates the need for a separate API layer while preserving a modern SPA experience. - **Laravel Queues** are essential for any platform that ingests webhooks, processes emails, or calls external AI models asynchronously. - Combining these three Laravel primitives enables a small team to ship a scalable, multi-channel SaaS product quickly. - MCP support signals a growing trend of AI agents needing structured, secure access to business data. --- *Source: [Building EasyReply: How We Used Laravel to Unify Customer Support — Laravel News](https://laravel-news.com/easyreply-laravel-shared-inbox)* Found this useful? [ ](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.msaied.com%2Farticles%2Fbuilding-easyreply-how-laravel-powers-a-unified-ai-customer-support-inbox&text=Building+EasyReply%3A+How+Laravel+Powers+a+Unified+AI+Customer+Support+Inbox) [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.msaied.com%2Farticles%2Fbuilding-easyreply-how-laravel-powers-a-unified-ai-customer-support-inbox) Frequently Asked Questions ---------------------------- 3 questions Q01 Why did the EasyReply team choose Laravel Reverb over a third-party WebSocket service? Laravel Reverb integrates natively with Laravel's event broadcasting system, allowing the team to push real-time UI updates with minimal PHP code and without maintaining a separate WebSocket infrastructure. Q02 How does Inertia.js help EasyReply avoid building a separate API? Inertia.js acts as a bridge between Laravel controllers and React components, passing server-side data directly as props. This gives the app a single-page application feel while keeping routing and data fetching entirely within Laravel — no REST or GraphQL API required. Q03 What role do Laravel Queues play in EasyReply's architecture? Laravel Queues handle all resource-intensive background tasks — parsing emails, processing social media webhooks, syncing CRM data, and generating AI-drafted replies — asynchronously, so the user interface remains fast and responsive at all times. Continue reading More Articles --------------- [ View all ](https://www.msaied.com/articles) [ ![Laravel Concurrency Facade and Process Pools for Parallel Work](https://cdn.msaied.com/667/241195c7a202f534b71ced2e321e27b5.png) laravel concurrency performance ### Laravel Concurrency Facade and Process Pools for Parallel Work Laravel's Concurrency facade and process pools let you run independent tasks in parallel without reaching for... ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said 14 Sep 2026 3 min read Read ](https://www.msaied.com/articles/laravel-concurrency-facade-and-process-pools-for-parallel-work-4) [ ![Job Batching, Chaining, and Catch Callbacks: Reliable Async Workflows in Laravel](https://cdn.msaied.com/666/f8aaa3879dc7efd419291ffa3e0b15c1.png) laravel queues async ### Job Batching, Chaining, and Catch Callbacks: Reliable Async Workflows in Laravel Go beyond fire-and-forget jobs. Learn how to compose Laravel job batches, chains, and catch callbacks into rel... ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said 13 Sep 2026 4 min read Read ](https://www.msaied.com/articles/job-batching-chaining-and-catch-callbacks-reliable-async-workflows-in-laravel) [ ![Partial Indexes and Covering Indexes in PostgreSQL: A Laravel Developer's Guide](https://cdn.msaied.com/665/ced6904aad758906b6047d70ea25e267.png) postgresql laravel performance ### Partial Indexes and Covering Indexes in PostgreSQL: A Laravel Developer's Guide Learn how partial and covering indexes eliminate wasted index space and redundant heap fetches in Laravel apps... ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said 13 Sep 2026 4 min read Read ](https://www.msaied.com/articles/partial-indexes-and-covering-indexes-in-postgresql-a-laravel-developers-guide-1) [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://www.msaied.com)Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow. Explore - [Home](https://www.msaied.com) - [Projects](https://www.msaied.com/projects) - [Articles](https://www.msaied.com/articles) - [Certificates](https://www.msaied.com/certificates) - [Contact](https://www.msaied.com#contact-section) Connect - [ hello@msaied.com ](mailto:hello@msaied.com) - [ +20 109 461 9204 ](tel:+201094619204) © 2026 Mohamed Said. All rights reserved. [ ](https://github.com/EG-Mohamed) [ ](https://www.linkedin.com/in/msaiedm/) [ ](https://wa.me/201094619204) [ ](mailto:hello@msaied.com) [ ](https://drive.google.com/file/u/0/d/1MF20IPRJyzfy32mhEutjL5EpSls0w2Q8/view)