Blue for Service Tickets
Queues. SLAs.
Escalations.
Whether it's an internal IT helpdesk or customer support, the primitives are the same. Tickets in a queue, SLA timers that escalate before the breach, routing rules that send the right ticket to the right person, and a mobile UI for the field tech who actually fixes it.
Pick up a ticket. Move it through.
Below is the actual product, shaped like a ticket queue. Same UI your team gets — assign, comment, change status, attach a file.
What a ticket queue looks like on Blue.
Four moving parts. Every service team needs all four — Blue gives you all four in one product.
Queues & intake
Email, form, and webhook intake flow into the right queue. Public forms for customer support, internal forms for IT helpdesk — same primitive.
SLA timers
Conditional automations watch the clock. Approach a breach: notify the assignee. Cross the line: escalate to the manager. Different actions for different sides of the boundary.
Routing & escalation
Tickets route by priority, category, or customer tier. Stalled tickets escalate. P1s page on-call. The right ticket gets to the right person on the right schedule.
Mobile-first for the field
Field techs work from a phone. The same workspace renders cleanly on mobile — pickups, photos, status updates, and signatures all from the truck cab.
01 · Intake & routing
Ticket in. Right person notified.
Forms, inbound email, webhooks from your monitoring stack — every intake channel turns into a ticket record. Routing rules send P1s to on-call, P3s to tier 1, and customer tickets to the right CSM.
02 · SLA timers
Approach. Notify.
Breach. Escalate.
Conditional automations watch the clock. When a ticket transitions into "approaching SLA," notify the assignee. When it transitions into "breached," escalate to the manager and post to the on-call channel. Different primitives, different transitions, different outcomes.
Deal · Acme Corp
priority = 'high'ANDstage = 'open'03 · Scheduled sweeps
Daily digest. Weekly attainment.
Cron-style schedules sweep the queue at fixed times: an 8am overdue digest, a 5pm shift-handover summary, a Monday SLA-attainment report. Everyone gets the same numbers; nobody runs them by hand.
status = 'overdue'- Report · Q4 Launch
- Task · Ship v2
- Ticket · Billing bug
- Deal · Renewals Q1
- Task · Review design
04 · Mobile-first
From the desk. From the truck.
The same workspace renders cleanly on desktop, tablet, and phone. Field techs update tickets, attach photos, and capture signatures from the cab — and the dispatcher sees it on the dashboard back at the office.
Real-time webhooks for every event.
Connect Blue to your entire stack with reliable, real-time webhooks.
Instant delivery
Sub-second delivery
with automatic retries.
Signed payloads
Cryptographically signed for
end-to-end security.
Granular filtering
Stay in control and subscribe
to precise events only.
05 · Permissions
Tier 1, tier 2, on-call — each at the right level.
Workspace-, record-, and field-level controls. Tier 1 sees their queue. Tier 2 sees escalations. On-call sees P1s. Customers see only their own tickets.
One price. Pay once. Forever.
Pay once for your tier — no recurring per-seat fees. Size the tier to your team and move up only when you outgrow it.
Starter
For freelancers & small teams
One-time payment
- 5 users
- 5 workspaces
- 2,000 records per workspace
- 5,000 records per org
- 10GB storage
- 250 automations / month
- 3 webhooks
- 3 dashboards
- 1 custom role
- 20 req/s API rate limit
- Community support
Growth
For growing teams
One-time payment
- 30 users
- 25 workspaces
- 2,000 records per workspace
- 25,000 records per org
- 100GB storage
- 1,000 automations / month
- 10 webhooks
- 10 dashboards
- 3 custom roles
- 50 req/s API rate limit
- Email support
Scale
For large organizations
One-time payment
- 150 users
- 100 workspaces
- 2,000 records per workspace
- 100,000 records per org
- 500GB storage
- 5,000 automations / month
- 50 webhooks
- 25 dashboards
- 5 custom roles
- 200 req/s API rate limit
- Email support
One platform.
Every ticket.
Start with one queue, wire up the SLA timers, and roll the rest of your service ops onto Blue from there.