Skip to main content
Tickets are the primary unit of work in the Thena Platform, representing customer inquiries, issues, requests, and other actionable items. They provide a structured way to track, manage, and resolve customer interactions across your organization.
Each ticket can be customized with various fields, workflows, and automations to match your business processes. Tickets can be created through multiple channels including email, chat, API, and web forms.

​
What is a ticket?

A ticket in Thena platform represents:
  • A customer inquiry or request
  • An internal task or issue
  • A trackable work item
  • A collaboration point for teams

​
Ticket structure

​
Core components

Basic information

• Unique identifier
• Title and description
• Status and priority
• Creation timestamp

Relationships

• Customer association
• Team assignment
• Agent ownership
• Related tickets

​
Field types

  • Title (required)
  • Description
  • Status
  • Priority
  • Type
  • Source
  • Tags
  • Due date
  • Customer ID
  • Contact information
  • Company details
  • Preferences
  • Service level
  • Assigned team
  • Assigned agent
  • Assignment rules
  • Escalation level
  • Handling time
  • Business-specific fields
  • Industry requirements
  • Process tracking
  • Integration data

​
Ticket management

​
Creation methods

Direct creation

• Web interface
• API endpoints
• Email
• Slack
• MS Teams

Automated creation

• Chat integration
• Form submissions
• Workflow triggers

​
Lifecycle stages

1

Creation

  • Initial submission
  • Channel processing
  • Field population
  • Rule evaluation
2

Assignment

  • Team routing
  • Agent assignment
  • Priority setting
  • SLA calculation
3

Processing

  • Status updates
  • Work tracking
  • Communication
  • Collaboration
4

Resolution

  • Solution implementation
  • Customer confirmation
  • Quality checks
  • Knowledge capture

​
API endpoints

​
Sample ticket

{
  "title": "Unable to access account",
  "description": "Customer reported login issues on mobile app",
  "type": "INCIDENT",
  "priority": "HIGH",
  "status": "NEW",
  "source": "EMAIL",
  "customerId": "cust-123",
  "teamId": "team-456",
  "tags": ["mobile-app", "login"],
  "customFields": {
    "impactedSystem": "Mobile Authentication",
    "deviceType": "iOS",
    "appVersion": "2.1.0"
  }
}
When creating a ticket, the system will add additional fields in the response such as uid, createdAt, updatedAt, number (human-readable identifier), and tracking information.

​
Available operations

# List tickets
GET /v1/tickets

# Create ticket
POST /v1/tickets
Content-Type: application/json

# Get ticket by ID
GET /v1/tickets/{id}

# Update ticket
PATCH /v1/tickets/{id}
Content-Type: application/json

# Delete ticket
DELETE /v1/tickets/{id}
All endpoints require authentication and appropriate permissions.
For detailed API specifications, see Ticket Management
# Add comment
POST /v1/tickets/{id}/comments
Content-Type: application/json

# Assign ticket
POST /v1/tickets/{id}/assign
Content-Type: application/json

# Change status
PATCH /v1/tickets/{id}/status
Content-Type: application/json

# Link tickets
POST /v1/tickets/{id}/links
Content-Type: application/json

​
Comment request

{
  "content": "Investigating the login issue...",
  "isPublic": true,
  "mentions": ["user-789"]
}
For detailed API specifications, see:

​
Best practices

1

Ticket creation

  • Use clear, descriptive titles
  • Include relevant details
  • Set appropriate priority
  • Add proper categorization
2

Processing

  • Follow standard workflows
  • Maintain communication
  • Document actions taken
  • Update status promptly
3

Resolution

  • Verify solution
  • Get customer confirmation
  • Document resolution
  • Update knowledge base

Lifecycle

Understand ticket lifecycle

SLA

Configure SLA policies

Fields

Manage ticket fields

Teams

Team management