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.