Designing a simple chat box is easy.
Building a real messaging system is what eats up all your time.

That’s exactly what Wirechat was built for.

A buyer inquires about a listing. A customer opens a private support thread. Your team coordinates inside a group chat. The conversation belongs to the workflow around your product.

Once users rely on it, the requirements grow fast: broadcasting, unread states, permissions, message requests, groups, invites, attachments, notifications, encryption, and conversations tied to your own models.

Wirechat delivers all of that battle-tested. For Laravel + Livewire applications, so you can focus on shaping your product workflow instead of rebuilding the entire messaging layer from scratch.

Read the docs Upgrade to Pro

Use cases

Wirechat helps when conversation is part of the product experience: support, marketplaces, communities, teams, and workflows tied to real records.

Private conversations

Give users a direct line for one-to-one conversations without designing the entire message lifecycle yourself.

Group spaces

Add group chat for teams, communities, cohorts, vendors, customers, or private members inside your own application.

Contextual conversations

Keep a conversation attached to an order, listing, project, ticket, service, or any model that gives the thread meaning.

Support threads

Build customer support flows where messages stay inside the product instead of sending users to a separate inbox.

Message requests

Let unknown or first-time senders wait for approval before a private conversation becomes active.

Secure messaging

Use encryption, permissions, settings, and server-side action checks when conversations need stronger guardrails.

Start with a panel, then shape the chat around your app.

Wirechat panels give you a working conversation surface first. From there, panel settings decide what the experience can do, where it appears, and how it fits the product you are building.

Pick the surface

Run chat as a full panel, tray, embedded component, or contextual conversation beside the record it belongs to.

Enable the workflow

Choose the pieces your product needs: private chats, groups, requests, attachments, actions, notifications, and security controls.

Keep control in Laravel

Panel configuration works with your users, models, policies, and routes, so each chat app can follow the rules of the product around it.

Panel provider

use Wirechat\Wirechat\Panel;

public function panel(Panel $panel): Panel
{
    return $panel
        ->id('messages')
        ->path('messages')
        ->middleware(['web', 'auth'])
        ->chatsSearch()
        ->attachments()
        ->deleteMessageActions(false)
        ->webPushNotifications();
}