Skip to main content

Updated Apr 10, 2026

Support tickets model

The support ticket model represents customer support cases. It powers ticket counts, sentiment, SLA-style signals where configured, and Support ticket created timeline activity.

Managed models from support connections​

For several integrations, FunnelStory creates a support ticket model automatically when you add and authorize the connection—you do not pick a manual SQL query. Examples include Zendesk, Freshdesk, and Pylon (exact behavior follows your workspace’s integration version).

Setup​

  1. Add the support connection from Data connections (for example Zendesk).
  2. Complete OAuth or credentials and authorize.
  3. Open Configuration → Data models and confirm a Support ticket model exists for that connection.
  4. Refresh the model and open an account that has tickets to verify the timeline.

Query-based configuration​

On database, warehouse, HubSpot, Salesforce, and other data sources that expose ticket-like objects, you can add a support ticket model manually:

  1. Add model → Support ticket.
  2. Select the connection and provide a query (or source) returning one row per ticket.
  3. Map properties below, validate, save, refresh.

Field reference​

Model keys​

PropertyTypeDescription
account_idstringAccount the ticket belongs to; must match your accounts model.
ticket_idstringStable ticket identifier from the source system.

Default properties​

PropertyTypeDescription
created_attimestampWhen the ticket was opened or created.
sentimentfloatOptional sentiment score if your pipeline produces one.

Optional properties​

PropertyTypeDescription
linkstringURL to the ticket in the source system.
typestringTicket type or category.
statusstringCurrent status (open, pending, solved, etc.).
prioritystringPriority label or code.
sla_breachstringSLA breach indicator if modeled in the source.
related_issuesstringRelated ticket or issue references.
text_analysisjsonStructured output from text analysis pipelines.
label_analysisjsonStructured label or topic output.

Custom-mapped columns become additional properties where the product consumes them.

Verification​

After refresh, pick an account with known tickets and confirm Support ticket created (or equivalent) appears on the account timeline and counts look correct.