Everything stays in your database. No external calls. Full autonomy.
// config/escalated.php
'mode' => 'self-hosted',Local database + automatic sync to cloud.escalated.dev for unified inbox across multiple apps. If the cloud is unreachable, your app keeps working — events queue and retry.
'mode' => 'synced',
'hosted' => [
'api_url' => 'https://cloud.escalated.dev/api/v1',
'api_key' => env('ESCALATED_API_KEY'),
],All ticket data proxied to the cloud API. Your app handles auth and renders UI, but storage lives in the cloud. Supports multiple domains per API key.
'mode' => 'cloud',All three modes share the same controllers, UI, and business logic. The driver pattern handles the rest.
# Email templates
php artisan vendor:publish --tag=escalated-views
# Config file
php artisan vendor:publish --tag=escalated-config
# Database migrations
php artisan vendor:publish --tag=escalated-migrations
# Translations (sourced from the central escalated-dev/locale package)
php artisan vendor:publish --tag=escalated-langTranslation strings for the escalated namespace are sourced from the
shared escalated-dev/locale
Composer package, which is consumed by every Escalated host plugin
(Laravel, Rails, NestJS, Django, …) so wording stays consistent across
backends.
The EscalatedServiceProvider wires three layers, lowest to highest
precedence:
- Central package —
vendor/escalated-dev/locale/locales/{locale}/...The canonical source. - Plugin-shipped overrides —
lang/vendor/escalated/{locale}/...in this repository, for Laravel-specific divergences. - Host-app overrides —
{app}/lang/vendor/escalated/{locale}/..., populated viaphp artisan vendor:publish --tag=escalated-lang. Apps edit those files to brand or relocalize Escalated.
Each layer is merged on top of the previous one with
array_replace_recursive (PHP groups) and array_merge (JSON), so a
layer only needs to define the keys it changes. See
lang/README.md for details.
Add these to your scheduler for SLA and escalation automation:
// app/Console/Kernel.php or routes/console.php
Schedule::command('escalated:check-sla')->everyMinute();
Schedule::command('escalated:evaluate-escalations')->everyFiveMinutes();
Schedule::command('escalated:close-resolved')->daily();
Schedule::command('escalated:purge-activities')->weekly();
Schedule::command('escalated:poll-imap')->everyMinute(); // Only if using IMAP adapterGuest ticket and widget routes share IP-based request budgets:
60 requests, 5 new tickets/chats, and 30 replies/ratings per minute. Configure
escalated.guest_rate_limits.requests_per_minute, submissions_per_minute, and
replies_per_minute for your deployment (minimum 1). Exceeding a budget returns
HTTP 429 with Retry-After. Reading ticket status does not spend the submission
budget. Changing transport, guest token, email or selected merchant does not
reset an IP's budget.
Configure Laravel's trusted proxies correctly so Request::ip() identifies the
client, and use a shared cache store for a deployment with multiple nodes. These
limits complement the mobile API's existing rate limit and signed attachment
download limits. They do not verify an email address or expire guest access.
All config lives in config/escalated.php. Key options:
'mode' => 'self-hosted', // self-hosted | synced | cloud
'user_model' => App\Models\User::class,
'table_prefix' => 'escalated_',
'connection' => null, // null = your app's default connection
'default_priority' => 'medium',
'routes' => [
'prefix' => 'support',
'middleware' => ['web', 'auth'],
],
'tickets' => [
'allow_customer_close' => true,
'auto_close_resolved_after_days' => 7,
],
'sla' => [
'enabled' => true,
'business_hours_only' => false,
'business_hours' => [
'start' => '09:00',
'end' => '17:00',
'timezone' => 'UTC',
'days' => [1, 2, 3, 4, 5],
],
],See the full configuration reference.
Department visibility, ticket accounts, account restrictions, and targeted SLAs are independent opt-ins. See ticket access and routing for host integration hooks and upgrade guidance.
Every ticket action dispatches an event you can listen to:
| Event | When |
|---|---|
TicketCreated |
New ticket |
TicketStatusChanged |
Status transition |
TicketAssigned |
Agent assigned |
ReplyCreated |
Public reply added |
InternalNoteAdded |
Agent note added |
SlaBreached |
SLA deadline missed |
TicketEscalated |
Ticket escalated |
TicketResolved |
Ticket resolved |
TicketClosed |
Ticket closed |
use Escalated\Laravel\Events\TicketCreated;
Event::listen(TicketCreated::class, function ($event) {
// $event->ticket
});| Route | Method | Description |
|---|---|---|
/support |
GET | Customer ticket list |
/support/create |
GET | New ticket form |
/support/{ticket} |
GET | Ticket detail |
/support/guest/create |
GET | Guest ticket form |
/support/guest/{token} |
GET | Guest ticket view (magic link) |
/support/agent |
GET | Agent dashboard |
/support/agent/tickets |
GET | Agent ticket queue |
/support/agent/tickets/{ticket} |
GET | Agent ticket view |
/support/admin/reports |
GET | Admin reports |
/support/admin/departments |
GET | Department management |
/support/admin/sla-policies |
GET | SLA policy management |
/support/admin/escalation-rules |
GET | Escalation rule management |
/support/admin/tags |
GET | Tag management |
/support/admin/canned-responses |
GET | Canned response management |
/support/inbound/mailgun |
POST | Mailgun inbound webhook |
/support/inbound/postmark |
POST | Postmark inbound webhook |
/support/inbound/ses |
POST | SES/SNS inbound webhook |
/support/agent/tickets/bulk |
POST | Bulk actions on multiple tickets |
/support/agent/tickets/{ticket}/follow |
POST | Follow/unfollow a ticket |
/support/agent/tickets/{ticket}/macro |
POST | Apply a macro to a ticket |
/support/agent/tickets/{ticket}/presence |
POST | Update presence on a ticket |
/support/agent/tickets/{ticket}/pin/{reply} |
POST | Pin/unpin an internal note |
/support/{ticket}/rate |
POST | Submit satisfaction rating |
All routes use the configurable prefix (default: support). Inbound webhook routes use the api middleware (no auth, no CSRF).
composer install
vendor/bin/pest