Deliver exceptional support with structured ticketing
Manage client support requests with SLA tracking, CSAT ratings, auto-assignment, canned responses, and full portal integration — separate from your task system, connected to your entire workflow.
Support requests deserve their own system
Tickets are external requests from clients. Tasks are internal work for your team. Keep them separate, connect them when needed.
Tickets vs Tasks
- Tickets — created by clients (bug reports, questions, change requests)
- Tasks — created by your team (internal work, deliverables)
- Ticket → Task bridge — convert a ticket into a linked task when work is needed
- Separate lifecycles — tickets have SLA tracking, CSAT ratings, and priority escalation
- Separate billing — ticket time and project time stay in distinct pipelines
A clear path from request to resolution
Six default statuses guide every ticket through a structured workflow. Customize with your own statuses on Pro plans.
7 Ticket Types
Bug, Question, Feature Request, Change Request, Support, Billing, and Other — color-coded badges for instant recognition.
5 Priority Levels
Low, Normal, High, Urgent, and Critical — each with configurable SLA targets and escalation rules.
Sequential Numbering
Every ticket gets a human-readable number (TKT-001, TKT-002) — sequential per agency, race-condition safe.
Watchers & CC
Add stakeholders as watchers — they receive all notifications and can follow progress without being the reporter or assignee.
Never miss a service level commitment
Configurable first-response and resolution targets per priority level. The SLA clock pauses automatically when you're waiting on the client.
Smart SLA computation
- Per-priority targets — set response and resolution times for each priority level
- Pause-aware — SLA clock pauses in "Waiting on Client" status automatically
- Warning at 80% — notification to assigned agent and agency owner
- Breach at 100% — escalation notification to owner and admin
- Live timer — real-time SLA countdown visible in ticket detail
Clients submit and track tickets from their portal
Three ways for clients to reach you — dedicated tickets page, floating help button, and project-level issue reporting.
Role-based visibility
- Org Owner & Admin — see all tickets for their organization
- Org Member — sees only tickets they created or are watching
- Clients can reply, upload attachments, and rate resolutions
- Org Owner and Admin can reopen resolved tickets and manage watchers
- Internal notes stay hidden — clients never see your private agent discussions
Measure client satisfaction after every resolution
When a ticket is resolved, clients can rate their experience on a 1–5 scale with optional feedback — closing the support feedback loop.
CSAT ratings built in
- 1–5 star rating with optional text comment
- Prompted via email notification and in-app on ticket resolution
- Feeds into CRM health scoring — low CSAT signals at-risk clients
- CSAT trend charts in the Reports → Support tab
- Resolution events logged to the CRM activity timeline
Power features for high-volume support
Canned templates, ticket merging, auto-assignment, custom statuses, and conversion to proposals — available on Pro and Enterprise plans.
Canned Templates
Save frequently used responses as templates with categories and shortcuts. Agents insert them with one click.
Ticket Merging
Merge duplicate tickets — replies, time entries, and watchers are consolidated into the target ticket automatically.
Auto-Assignment
Route tickets automatically with rules: assign to a specific agent, round-robin across a team, or route to the least busy member.
Custom Statuses
Create, rename, recolor, and reorder ticket statuses beyond the 6 defaults. Full drag-and-drop management.
Convert to Task
When work is needed, convert a ticket into a linked task in any project. The ticket tracks resolution; the task tracks work.
Convert to Proposal
Turn feature requests and change requests into proposals — bridging support requests to your sales pipeline.
Automate your support workflow
5 ticket triggers and 3 ticket actions integrate seamlessly with the automation engine — no code required.
Triggers & actions
- ticket_created — auto-assign, notify, or create a linked task
- ticket_status_changed — escalate, reassign, or send follow-ups
- ticket_assigned — welcome message to the assigned agent
- ticket_resolved — log to CRM, send CSAT prompt
- ticket_sla_breached — escalate to owner + send urgent email
Reports & dashboard widgets
A dedicated Support tab in Reports with KPIs, 7 chart types, and 3 dashboard widgets — giving you complete visibility into support operations.
5 KPI Cards
Open tickets, avg first response time, avg resolution time, SLA compliance rate, and CSAT score.
7 Chart Types
Volume over time, by type, by client, resolution trend, SLA compliance, team workload, and CSAT trend.
3 Dashboard Widgets
Open tickets count, SLA breaches today, and overdue tickets — right on your executive dashboard.
Health Score Impact
Ticket data feeds into CRM health scoring — SLA breaches and low CSAT signal at-risk clients automatically.
Track and bill support time
Log time on tickets with manual entries or live timers. Bill support hours separately from project work.
Two billing pathways
- Retainer deduction — if linked to a support service, hours auto-deduct from the retainer balance
- Invoice generation — unbilled ticket time surfaces on the CRM page with a "Generate Support Invoice" button
- Separate from projects — ticket time never appears in project budget tabs
- Live timer — start/stop timer directly from the ticket detail drawer
Support that scales with you
"Before Eidoncore, client support was scattered across emails, Slack, and spreadsheets. Now every request is tracked with SLA timers, and our resolution time dropped by 60%. The CSAT ratings showed us exactly where we needed to improve."
"The auto-assignment rules save us hours every week. Bug tickets go straight to our dev team, billing questions route to accounts, and everything has an SLA attached. Our clients love being able to submit tickets from their portal."
Frequently asked questions
Tickets represent external support requests from your clients (bug reports, questions, change requests). Tasks represent internal work for your agency team. A ticket CAN generate a linked task when work is needed, but the two systems stay separate — tickets track the conversation and resolution, tasks track the work.
SLA targets are configurable per priority level (first response time and resolution time). The system uses an accumulator approach that pauses the SLA clock when tickets are in "Waiting on Client" status, ensuring accurate measurement of your actual response time — not wall-clock time. You'll receive warning notifications at 80% and breach alerts at 100%.
Yes. Clients can submit and track tickets from a dedicated Tickets page in the portal, a "Need Help?" floating button on every portal page, or a "Report an Issue" button on project detail pages. Organization Owners and Admins see all tickets, while Members see only tickets they created or are watching.
Core ticketing requires the Starter plan or higher (limited to 50 open tickets). SLA tracking, CSAT ratings, custom statuses, canned templates, and ticket merging are available on Pro plans (unlimited tickets). Auto-assignment rules and email-to-ticket are Enterprise features.
Yes. Time logged on tickets follows a separate billing pipeline from project time. If the ticket is linked to a support retainer (OrgService), hours auto-deduct from the balance. Otherwise, unbilled ticket time surfaces on the client's CRM page with a "Generate Support Invoice" button.
Works great with
Turn client support into a competitive advantage
Structured ticketing, SLA tracking, and CSAT ratings — included in every Starter plan and above. Start your 14-day free trial.