Saltar al contenido principal
The Support module connects the voice of the customer with your support team. woku evaluates every negative response it receives and, if it detects a case that warrants attention, builds a complete support ticket and sends it to the customer support platform you have configured. Your team receives the case already assembled: what happened, what the customer is asking for and what action is suggested, without anyone having to read and transcribe the original feedback.

Which responses generate tickets

A response enters the ticket engine when it meets all of these conditions:
  • It is classified as improvement (requires action). See Actionability and sentiment.
  • The customer is identified and did not choose to respond anonymously.
  • It is a production response. Sandbox responses do not generate tickets.
  • There is at least one enabled destination in the Support module.
Responses from wokus, NPS, CSAT and CES with a classified comment generate tickets. Forms do not generate tickets, but their responses are part of the customer history that the AI uses as context.

Routing by trackers or by folder

Before going through the AI, the response is routed to a destination. Each destination chooses how it receives tickets, in one of two ways (never both at once):
  • By trackers: based on the external attributes that accompany each piece of feedback (for example country, store or line of business).
  • By folder: based on where the tool lives in Tools. The destination receives the tickets of every tool (wokus, NPS, CSAT and CES) inside that folder, at any depth. The folder is read when each response arrives: if you move a tool out of the folder, its next responses stop reaching that destination.

Conditions by trackers

  • Each destination defines in which cases it receives tickets through conditions on trackers, grouped with And also and Or if: the destination matches when some Or group has all of its rows And true.
  • Each condition uses the operator equals (an exact value) or is any value (all values of the tracker, without typing them one by one). To listen to several complete trackers, add an is any value condition for each tracker, joined with Or if. There is a maximum of 20 conditions per destination.
  • The ticket reaches every enabled destination whose conditions match the response’s trackers. Destinations are ordered by priority (highest first) and, at equal priority, by creation order; the first one is the ticket’s primary destination. The destinations you create have priority 0; an integration can give a more specific destination a higher priority, such as a sales team’s in Sperant.
  • If no condition matches, no ticket is created. There is no default destination.

Destinations by folder

  • A destination by folder matches when the tool of the response is inside its folder or one of its subfolders.
  • If several destinations match (for example one on Stores, another on Stores > Santiago and another by trackers), the ticket reaches all of them. It is a single ticket: it is not duplicated per destination.
  • Forms do not live in folders, so they are only routed by trackers.
  • The ticket keeps the folder of the tool when it was created. You see it in the detail, can filter the list by folder, and it reaches the destination with the case.
  • If you delete the folder configured on a destination, the destination is deleted with it, together with its tickets. Before deleting, woku shows you which destinations and groups would be lost.

AI triage

With the destination resolved, the AI decides whether the case warrants escalation. For this it receives the complete customer history (their responses by tool, how many were negative and how long they have been a customer) and the AI context defined in the destination. If several destinations match, it receives the context of each one. If it escalates, the AI builds the case: title, severity (high, medium or low), summary, description, history milestones, what the customer is asking for, suggested action, churn risk and language. All the content is marked as AI generated.
The customer’s identity (name, email, phone) is added to the ticket deterministically and never passes through the AI model.

Delivery to the destination

Delivery is asynchronous and with automatic retries: up to 5 attempts with increasing wait time between each one. The ticket timeline records Sent to the support team only when the destination confirms receipt. In Zendesk, in addition, the link to the remote ticket is saved, visible as View in customer support. An email destination records the delivery to the team, but does not save a remote link because the ticket travels as an email.

Available destinations

Zendesk

Requires an active Zendesk connection in Company → Integrations. When creating the destination you choose the connected account and, optionally, a Zendesk Group ID so that tickets reach a specific group. Check how to connect your account in Zendesk connector.

Custom service

Sends the tickets over HTTP to any of your own systems. You configure:
  • URL and method of the request.
  • Authentication: none, username and password, Bearer token or API key in a header. The credential is stored encrypted and is not shown again.
  • JSON template of the body, with {{...}} placeholders that are replaced with the case fields.

Email

Sends the ticket to one or more email addresses, without depending on an external integration. When creating the destination you add the list of emails, up to 20 addresses. It does not require a connection or credentials. The email reads top to bottom in the order the team acts:
  1. Title, priority and response window (today, 24 h or 48 h), next to the churn risk. The subject carries the ticket code and the title it was created with, without the priority, so updates arrive in the same thread even when the case gets a new title.
  2. Where it comes from: the tool and its score, the trackers and the folder. Trackers that identify something in woku, such as a journey, show its name next to the ID.
  3. The customer’s contact, with their email and phone as links.
  4. What to do: up to three concrete steps and, once the follow-up has brought information from the customer, the actions the follow-up agent suggests, shown apart.
  5. The case: the customer’s verbatim comment, what happened, what they ask for and the milestones of their history.
  6. A link to view the ticket in woku.
Sections are split by a line and each piece of data appears once. Each ticket goes out in a single email to every recipient, even when the destination has several addresses or the ticket reaches several email destinations. A repeated address gets the email only once, and the email includes a Sent to line at the bottom with every address that received it.

Configuring a destination

From Support → New destination you define the destination on a single screen:
  1. Destination: the type of platform and a descriptive name, for example SAC Chile.
  2. Connection: the connection data according to the chosen type.
  3. AI context: free text of up to 2000 characters that the AI uses when deciding and drafting. The clearer the context (what this destination covers, which cases are critical), the better the AI decides.
  4. Which tickets go to this destination: you choose By trackers (the routing conditions) or By folder (a Tools folder), with a natural language preview of the rule.
The conditions by trackers require trackers with data, which are managed in Company → Trackers. You can also create a destination from a folder: in Tools, open the folder menu and choose Support and plans; there you see the destinations and groups that listen to it and can create a new one with the folder already chosen. Before saving you can use Test connection to validate the credentials against the real destination. Destinations can be enabled and disabled at any time. An inactive destination does not receive new tickets.

Tracking

The main Support view shows the operation by period (day, week, month, year or all time): cards with the created tickets and their severity, and one card per destination with its status. When you enter a destination you see its detail and a table of tickets with name, tool, score, severity, AI summary and date, with search and filters.

Ticket detail

Each ticket shows the origin of the feedback, the score, the original comment (with transcription if it was audio), the category, the summary, the case built by the AI, the churn risk, the history and the customer data, and the timeline with the delivery status to the destination. You can edit the ticket’s title, severity, summary and category before or after delivery, for example to adjust the priority that the AI assigned.

More information

Zendesk connector

Connect your Zendesk account with an API token to feed the ticket destinations.

Follow-up with the AI agent

An improvement comment, written or transcribed, from Woku, NPS, CSAT or CES starts a conversation outside a Flow (see Follow-up agent). A score alone does not activate the agent. Flow responses are excluded, including single-step and partial responses, while keeping their normal ticket evaluation. An individual Journey instrument remains eligible if captured as standalone. The initial ticket is processed immediately. If the agent is awaiting details, the initial email indicates this in red. When the conversation ends with at least one client response, including inactivity after that response, the same ticket is enriched with that evidence. Its internal ID and external case are preserved; a second email shows a green notice and the enabled destination updates its original resource. Without a client response there is no second delivery. The API and management SDKs expose followUp and contentVersion. completed only indicates closure; appliedSummaryVersion >= 1 indicates applied evidence. Lists stay lightweight and the thread is read with a management secret at GET /v1/follow-ups/:id, without response tokens or transport credentials. MCP offers the get_follow_up read. Historical records may omit follow-up. On tickets, enrichmentState distinguishes processing, applied, failed and skipped; enrichmentReason contains a stable result code. A failure preserves the previous case. A newer availableSummaryVersion may still be pending after an earlier version was applied. Destination delivery confirmation is separate. Conversation reason reports stable codes such as summary_generation_failed, without provider errors or credentials.
Última modificación el 30 de octubre de 2026