How do we set up Forethought Triage to auto-tag, prioritize, and route tickets by intent/urgency/sentiment?

Managing ticket volume by hand is where most support teams start—and where they eventually get stuck. If you’re still relying on manual tagging, first-in-first-out queues, or brittle rules in your helpdesk, you’re leaving deflection, CSAT, and time-to-resolution on the table.

Forethought Triage is built to fix that. It uses agentic AI to understand customer intent, sentiment, urgency, language, and product context, then auto-tags, prioritizes, and routes tickets so the right work hits the right queue at the right time.

Below is a practical, operator-level walkthrough of how to set up Forethought Triage to auto-tag, prioritize, and route tickets by intent/urgency/sentiment—without creating another “automation monster” you can’t maintain.

---

What Forethought Triage Actually Does

Before you configure anything, it helps to align on the job Triage is doing inside your stack:

• Auto-tagging: Uses agentic AI models to classify tickets by:

  • Customer intent (e.g., “refund request,” “billing issue,” “bug report”)
  • Sentiment (positive, neutral, negative, highly negative)
  • Urgency (time-sensitive vs routine)
  • Language
  • Product or plan type
  • Other business-specific attributes you define

• Prioritization: Applies your business policies to those tags to assign:

  • Priority levels (P0–P3, Urgent/High/Medium/Low)
  • SLAs and internal response targets
  • Escalation paths for at-risk customers/situations

• Routing: Pushes tickets into the right place automatically:

  • Queues/Groups in Zendesk, Salesforce, Freshdesk, Intercom, etc.
  • Specialist teams (Billing, Technical, VIP, Fraud, etc.)
  • Autoflows in Solve (for full AI resolution) or Assist (for agent copilots)

Think of Triage as the traffic controller of your support operation: understand → tag → prioritize → route—using your policies and your historical data.

---

Step 1: Connect Your Helpdesk and Core Systems

You can’t route what you can’t see. Start by integrating Triage into your existing CX stack.

1. Connect your helpdesk

In Forethought, you’ll:

• Connect to your primary system of record:
  • Zendesk Support
  • Salesforce Service Cloud
  • Freshdesk
  • Intercom
  • Or another platform via API
• Grant access to:
  • Ticket objects (subject, body, custom fields, tags, requester details)
  • Existing groups/queues
  • Macros or workflows you want to reuse

There’s no need to change your stack—Forethought works within your current workflows to start delivering value fast.

2. Connect key business systems (optional but recommended)

To make intent and urgency classification smarter, connect systems that hold context:

• Billing/Subscription (e.g., Stripe, Chargebee, Zuora)
• Order/Logistics (ecommerce platform, WMS, OMS)
• Authentication/User profiles (IDP, CRM, membership system)
• Product/backend APIs

These connections allow Triage to factor in plan tier, MRR, active orders, and more when judging urgency and routing.

---

Step 2: Train on Historical Tickets and Policies

Forethought is “trained on your data,” not a blank chatbot. This is where Triage learns how your team actually works.

1. Sync historical tickets

• Pull a representative sample of past tickets (ideally 3–12 months).
• Ensure you include:
  • High-volume topics (shipping, billing, login, etc.)
  • Edge cases (fraud, chargebacks, compliance)
  • Different customer segments (free vs enterprise, regions, languages)

Forethought uses this to:

• Learn patterns in intent, sentiment, and urgency
• Infer what “P0 vs P3” looks like in your real data
• Map which teams typically handle which topics

2. Upload or document your business policies

Triage needs your rules of the road:

• Written SLAs by plan/tier or channel
• Escalation rules (VIP, legal/compliance, outages)
• “Never auto-resolve” topics (e.g., legal, refunds over $X)
• Product or region-specific handling (e.g., EU data requests)

You can encode these as:

• Policy docs shared with Forethought
• Direct configuration in the Forethought admin (preferred)
• Rules tied to tags/fields (e.g., plan:enterprise → higher priority)

This is what allows Triage to reason through complex scenarios instead of just keyword-matching.

---

Step 3: Define Your Intent, Urgency, and Sentiment Taxonomy

Auto-tagging is only as useful as the tags you choose. The goal is a lean, operationally meaningful taxonomy—not a tag explosion.

1. Design your intent categories

Start from the metrics you care about: deflection, time-to-resolution, and handoff quality. Then break intents into groups that map to owners or workflows, such as:

• Account & Access
  • Login/Password reset
  • Account lockout
  • Profile update
• Billing & Payments
  • Invoice question
  • Refund request
  • Upgrade/downgrade
• Orders & Delivery (ecom)
  • Order status
  • Damaged/returned items
  • Address changes
• Product & Technical
  • Bug report
  • Feature request
  • Integration issue

Forethought’s AI can propose a draft taxonomy based on your historical tickets; you refine it to what your teams can own.

2. Define urgency tiers

Urgency should reflect business impact, not just “customer says it’s urgent.” Common tiers:

• Critical (P0): Service down, payment failures, security issues, VIP outages
• High (P1): Live orders at risk, time-sensitive travel/appointment issues
• Medium (P2): General support with moderate impact
• Low (P3): “How do I” questions, feature requests, feedback

Triage will infer urgency from:

• Language (“can’t login,” “site down,” “urgent,” “deadline today”)
• Context (enterprise customer, number of users affected)
• External data (active order shipping today, payment failed, etc.)

3. Calibrate sentiment levels

Sentiment drives both prioritization and escalation risk.

Typical levels:

• Positive
• Neutral
• Negative
• Highly negative / At risk

Use this to do things like:

• Auto-prioritize highly negative sentiment from high-value customers
• Route at-risk tickets to specialized retention or escalation teams
• Trigger Assist to provide extra coaching for agents on sensitive replies

---

Step 4: Configure Auto-Tagging in Triage

With taxonomy set, you’re ready for the core configuration: telling Triage what to tag, and how.

1. Turn on intent detection

In the Forethought Triage settings:

• Enable Intent Tagging
• Map AI-detected intents to your internal tags/fields (e.g., intent_refund_request → tag:refund_request)
• Set a confidence threshold:
  • Start around 0.7–0.8 confidence (you can tune this later)
  • Below-threshold predictions can be:
    • Left untagged, or
    • Suggested to human agents via Assist for confirmation

2. Enable urgency classification

• Turn on Urgency Detection
• Map AI urgency levels (Critical/High/Medium/Low) to:
  • Helpdesk priority fields
  • SLA policies
  • Internal queues (e.g., P0/P1 dedicated queues)

You can define policy overrides, such as:

• “If plan = Enterprise and intent = ‘service down,’ force Critical, regardless of sentiment.”
• “If channel = Voice callback, never below High.”

3. Enable sentiment analysis

• Turn on Sentiment Tagging
• Map each sentiment level to:
  • A sentiment custom field or tag in your helpdesk
  • Optional routing rules (e.g., highly negative → escalation queue)
  • Optional Assist behaviors (e.g., flag for manager review)

4. Add secondary AI tags as needed

Depending on your operation, you can also turn on tagging for:

• Language (for language-based queues or BPO routing)
• Product/module (to send tickets to product specialists)
• Lifecycle (prospect vs customer vs churn risk)

These tags feed into more sophisticated routing and reporting later.

---

Step 5: Build Prioritization Rules on Top of AI Tags

Now that Triage can understand and tag tickets, you layer your business logic on top.

1. Create priority logic combining intent, urgency, and sentiment

In Forethought, define rules like:

• Example 1 – Critical outage

  • If intent = service_outage AND customer_tier = enterprise
  • THEN priority = Critical, SLA = 1-hour response, route = Incident Response queue

• Example 2 – At-risk billing issue

  • If intent = billing_issue AND sentiment = highly_negative
  • THEN priority = High, route = Billing Escalations, notify = CX Manager

• Example 3 – Deflection candidates

  • If intent = password_reset OR intent = order_status
  • THEN priority = Low AND route = Solve Autoflow for automatic resolution

2. Encode SLAs and business policies

Attach SLAs directly to priority levels or tags:

• P0 → 15 min first response, 2 hr resolution target
• P1 → 1 hr first response, 4 hr resolution target
• P2 → 1 business day
• P3 → 2–3 business days

Tie these to:

• Customer tier or MRR bands
• Channels (chat, email, voice)
• Regions (to accommodate hours and regulatory needs)

This is how Triage “reasons” through complex routing instead of just pushing everything into one generic queue.

---

Step 6: Configure Routing Rules to Queues, Teams, and Agents

Once priority is set, Triage needs to put tickets into motion.

1. Map AI tags to helpdesk queues/groups

In Forethought’s routing configuration:

• Match your AI tags to:
  • Zendesk Groups or Views
  • Salesforce Queues or Case Assignment Rules
  • Freshdesk Groups
  • Intercom Inboxes

Examples:

• intent = refund_request → Billing Queue
• intent = bug_report AND product = mobile_app → Mobile Support Queue
• language = Spanish → Spanish Support Queue

2. Use urgency and sentiment for routing modifiers

Layer in nuance:

• Critical + any intent → P0 queue with on-call rotation
• Highly negative sentiment → Specialist “save” team or manager-assisted queue
• Low priority, common intents → AI-first queue backed by Solve Autoflows

3. Integrate with Solve and Assist

To avoid unnecessary human handling:

• Route simple, high-volume intents (order tracking, password reset, appointment scheduling) into Solve to attempt full end-to-end resolution via Autoflows.
• Route complex or sensitive intents to Assist, where agents get:
  • AI-suggested replies
  • Summaries and context
  • Recommended next best actions

Triage becomes the decision layer: which tickets can be fully automated, and which need human judgment.

---

Step 7: Test, Monitor, and Tune for Accuracy

No triage model should go from “off” to “fully automated” in one jump. You want a tight proof-of-value loop.

1. Start in shadow or “suggest-only” mode

For the first phase:

• Let Triage tag and recommend priority/routing without actually changing queues.
• Compare:
  • AI tags vs agent-applied tags
  • AI priority vs actual escalation patterns
  • AI routing vs where tickets ended up

This gives you a baseline without risk.

2. Promote stable intents to full automation

Once you see 90%+ alignment on specific intents:

• Turn on auto-tag + auto-route for those intents.
• Keep more ambiguous or high-risk categories in “suggest” mode until they stabilize.

3. Monitor key metrics

In Forethought dashboards and your helpdesk, track:

• Deflection rate (for tickets routed to Solve)
• First response time by intent/priority
• Time-to-resolution by team and segment
• CSAT by intent/sentiment
• Mis-routed or re-routed ticket percentage

Forethought Discover can also surface:

• Knowledge gaps where AI cannot confidently respond
• Intents that need new Autoflows or updated policies
• Opportunities to merge or split tags for clarity

4. Iterate on thresholds and policies

Based on data:

• Raise confidence thresholds for high-risk categories.
• Lower thresholds for low-risk, high-volume intents to increase automation.
• Refine or reduce tags that are rarely used or not actionable.

This is how you avoid the “tag jungle” that plagues older rules-based setups.

---

Step 8: Governance, Controls, and Enterprise Readiness

Enterprise CX leaders need more than accuracy—they need control, compliance, and auditability.

1. Keep humans in control

Forethought is agentic but policy-bound:

• Role-based access controls define who can:
  • Edit tags and taxonomies
  • Change routing rules
  • Adjust priority or SLAs
• Change logs provide audit-ready records of configuration updates.

2. Protect customer data

Forethought is built for trust and operates with:

• SOC 2 Type II, HIPAA, GDPR, and CCPA compliance
• Alignment with the NIST Cybersecurity Framework
• Encryption in transit and at rest
• Access controls and audit trails for sensitive fields

This matters when you’re auto-routing tickets that may contain PII, PHI, or financial data.

3. Minimize hallucinations and routing errors

While Triage doesn’t “answer” customers directly, its classifications influence who does. Forethought’s Hallucination Mitigation and validation layers:

• Verify facts against your connected systems and help center content before answering in Solve/Assist.
• Reduce misclassification risk by grounding AI decisions in real tickets and policies, not generic models.

---

How This Setup Impacts Your Metrics

When Triage is configured as above, you should see movement on the board-level metrics:

• Deflection: More tickets automatically routed to Solve → higher AI resolution rate, fewer simple tasks on human queues.
• First response time: High urgency/negative sentiment tickets get to the right team fast, reducing wait time.
• Time-to-resolution: Specialists receive the right work at the right priority; no more “bouncing around” between queues.
• CSAT: At-risk customers are identified faster; sensitive issues get prioritized and handled by your best-equipped teams.
• Operational efficiency: Less manual tagging, fewer macros to maintain, and lower routing-related operational debt.

Forethought customers routinely see:

• Up to 98% resolution rate on automatable intents
• 55% reduction in first response time
• 15x average ROI, with median go-live in under 30 days

Those numbers are only possible when triage is handled by AI that can reason through intent, urgency, and sentiment—not just follow static rules.

---

Next Step

If you want to see how this setup would look against your real tickets—your intents, your queues, your SLAs—the fastest path is a POV, not a slideware demo.

Get Started and we’ll walk through a Triage configuration tailored to your helpdesk, your policies, and the metrics your board actually cares about.