Events

use Escalated\Laravel\Events\TicketCreated;

Event::listen(TicketCreated::class, function ($event) {
    // $event->ticket
});

Events work in both UI-enabled and headless modes.

Available events

• TicketCreated -- New ticket submitted
• TicketStatusChanged -- Status transition
• TicketPriorityChanged -- Priority updated
• TicketAssigned -- Agent assigned to ticket
• TicketUnassigned -- Agent removed from ticket
• ReplyCreated -- Public reply added
• InternalNoteAdded -- Agent internal note
• TicketUpdated -- Ticket metadata changed
• TicketReopened -- Ticket moved back to active state
• DepartmentChanged -- Department reassigned
• TagAddedToTicket -- Tag applied to ticket
• TagRemovedFromTicket -- Tag removed from ticket
• SlaWarning -- Ticket approaching SLA deadline
• SlaBreached -- SLA deadline missed
• TicketEscalated -- Ticket escalated by rule
• TicketResolved -- Ticket marked resolved
• TicketClosed -- Ticket closed

Events are dispatched via ActiveSupport::Notifications. Subscribe with ActiveSupport::Notifications.subscribe("escalated.ticket_created").

Events work in both UI-enabled and headless modes.

Events are dispatched via Django signals. Connect with escalated.signals.ticket_created.connect(handler).

Events work in both UI-enabled and headless modes.

Events are dispatched via the AdonisJS event emitter. Subscribe with emitter.on('escalated:ticket:created', handler).

Filament uses the same Laravel events from escalated-laravel. Listen to them exactly as you would with the standard Laravel package.

Events are dispatched via WordPress action hooks. Use add_action('escalated_ticket_created', $callback) to listen for ticket lifecycle events.

Events are dispatched server-side through your backend's native event system. The Flutter package does not implement a client-side event bus.

Reactive Data

The package uses Riverpod providers that automatically refresh data when mutations occur. When a user creates a ticket, adds a reply, or changes a status, the relevant providers invalidate and re-fetch automatically.

// Ticket list stays up-to-date after creating a new ticket
final tickets = ref.watch(ticketListProvider);

// Replies refresh after posting
final replies = ref.watch(ticketRepliesProvider(ticketId));

No manual event listeners or refresh logic is needed — the provider system handles cache invalidation for you.

Note: If you need to react to server-side events (e.g., real-time agent replies), configure push notifications through your backend and handle them at the platform level.

Events are dispatched server-side through your backend's native event system. The React Native package does not implement a client-side event bus.

Reactive Data

The package uses React Query, which automatically handles cache invalidation when mutations succeed. When a user creates a ticket, adds a reply, or changes a status, the relevant queries re-fetch automatically.

import { useCreateTicket, useTickets } from '@escalated-dev/escalated-react-native';

function TicketListScreen() {
  const { data: tickets } = useTickets();
  const createTicket = useCreateTicket(); // invalidates ticket list query on success

  return (
    // Ticket list stays current — no manual refresh needed
  );
}

No manual event listeners or refresh logic is needed — React Query handles cache invalidation for you.

Note: If you need to react to server-side events (e.g., real-time agent replies), configure push notifications through your backend and handle them at the platform level.