How do we enable Forethought Assist inside our helpdesk so agents get summaries and drafted replies?

Most teams start looking at Assist when their agents are buried in long tickets, copying and pasting from macros, or re-reading entire threads just to get oriented. Enabling Forethought Assist directly inside your helpdesk puts an agentic copilot in that workflow—summarizing context, suggesting next actions, and drafting on-brand replies without forcing agents to switch tools.

Below is a practical, operator-level walkthrough of how to turn Assist on, connect it to your systems, and configure it so your agents reliably get summaries and draft responses in their existing queues.

---

What Forethought Assist Does Inside the Helpdesk

Forethought Assist is the in-helpdesk copilot within Forethought’s multi-agent system. Once enabled, it:

• Summarizes tickets and conversations so agents see the key facts, sentiment, and history at a glance.
• Drafts suggested replies based on your historical tickets, help center content, and business policies.
• Stays policy-bound and on-brand using your workflows, guardrails, and Hallucination Mitigation (fact verification before responding).
• Works where your team already lives—inside tools like Zendesk, Salesforce, Freshdesk, Intercom, and other supported helpdesks.

There’s no new tab or separate app to manage. Assist is embedded directly in the ticket or conversation view.

---

Prerequisites Before You Enable Assist

Before you switch Assist on for agents, confirm the following foundations are in place:

• Helpdesk integration is connected

  • Supported platforms include Zendesk, Salesforce, Freshdesk, Intercom, and others.
  • Forethought should already be authorized to read tickets/conversations and write internal notes or suggested replies.

• Data sources are synced

  • Historical tickets/conversations for training and context.
  • Help center / knowledge base articles.
  • Any relevant policies or internal FAQs your team wants reflected in answers.

• Role-based access is defined

  • Decide which agent roles should see Assist (e.g., Tier 1 vs Tier 2, specific teams, or pilot groups).
  • Ensure SSO and permission models reflect your internal security standards.

If your helpdesk is not yet integrated, your Forethought implementation manager or admin will connect it first; Assist relies on that integration to generate accurate summaries and responses.

---

Step 1: Enable Assist in the Forethought Admin Console

1. Log in to the Forethought Admin Console

   • Use your SSO or admin credentials.
   • Ensure you have the appropriate admin or configuration permissions.

2. Navigate to the Assist Module

   • Go to the main navigation and choose Assist (sometimes under “Agent Experience” or “Agent Tools” depending on your configuration).
   • Confirm the status of Assist for your environment (Sandbox vs Production).

3. Turn on Assist for Your Helpdesk

   • Locate your helpdesk integration (e.g., “Zendesk – Production”, “Salesforce Service Cloud”).
   • Toggle Assist Enabled to “On” for that integration.
   • Save your changes.

Enabling Assist at the platform level makes it available to be surfaced inside your helpdesk UI. The next steps focus on how it appears and behaves for agents.

---

Step 2: Configure Agent-Facing Features (Summaries & Drafted Replies)

Inside the Assist settings, you can control exactly what agents see and how Assist behaves.

A. Ticket and Conversation Summaries

1. Open the “Summaries” settings under Assist.
2. Choose when summaries generate
   • On ticket open.
   • After new customer messages.
   • On-demand only (agent clicks to generate).
3. Set summary format
   • Bullet-point overview (e.g., “Issue, Context, Customer Ask”).
   • Structured template (e.g., “What happened, What’s been tried, Current status, Recommended next step”).
4. Enable language and tone preferences
   • Align with your brand tone (formal vs conversational).
   • Control whether internal jargon or specific tags are referenced.

Summaries should help agents cut through noise, not rewrite the whole ticket. Start with a short, structured format and adjust based on feedback.

B. Drafted Replies (Suggested Responses)

1. Open the “Drafted Replies” or “Suggested Responses” settings under Assist.
2. Enable reply drafting
   • Turn on the “Generate Reply Suggestions” toggle.
3. Connect data sources for reply generation
   • Historical tickets: so replies reflect real agent behavior and resolutions.
   • Help center / KB: so Assist can cite existing articles and workflows.
   • Policies/Playbooks: so sensitive flows (billing, identity, compliance) follow your rules.
4. Configure tone and style
   • Select the default tone (“friendly professional,” “formal,” etc.).
   • Set length preferences (short, medium, detailed).
5. Decide where drafts are inserted
   • As an internal note for review.
   • Directly into the reply composer as an editable draft.
   • Behind a “Generate Reply” button to keep the workflow deliberate.

With Hallucination Mitigation enabled, Assist verifies facts against your connected data before recommending an answer, lowering the risk of off-policy responses.

---

Step 3: Control Visibility by Role, Team, or Queue

You stay in control of who can use Assist and where it appears.

1. Open Permissions or Access Control in the Admin Console.
2. Define which roles see Assist
   • For example: only Tier 1 agents and Team Leads during pilot.
3. Scope Assist to specific queues or ticket types
   • High-volume, repetitive queues (e.g., “Account Access,” “Order Status”) are ideal starting points.
   • You can disable Assist for highly regulated or edge-case queues if needed.
4. Set per-channel behavior
   • Email tickets vs chat conversations.
   • Voice/phone follow-ups where summary support is especially useful.

Permissions are enforced with role-based access and audit-ready logs, aligning with enterprise security expectations.

---

Step 4: Embed Assist Inside Your Helpdesk UI

How Assist shows up varies slightly by helpdesk, but the pattern is consistent: an in-context panel or widget inside each ticket.

Common embedding patterns

• Zendesk: Assist appears as a side panel app in the ticket view. Agents can:

  • Click “Summarize” to get a conversation summary.
  • Click “Draft Reply” to generate an editable response.

• Salesforce Service Cloud: Assist is added to the page layout for Cases/Conversations:

  • A component surfaces summaries and suggested replies.
  • Autoflows and related actions can be exposed as buttons or quick actions.

• Freshdesk / Intercom / Others:

  • Assist frequently appears as a right-hand panel or inline widget.
  • It reacts to the currently open ticket or chat thread.

Your Forethought implementation team typically configures this with your admin during onboarding, but you can adjust styling and placement later to fit your agents’ workflows.

---

Step 5: Align Assist With Your Business Policies

Assist is fully agentic, meaning it can reason over your policies—not just rephrase content. To keep it aligned with your governance:

1. Upload or link to policy documents
   • Refund rules, SLAs, escalation criteria, security/compliance must-knows.
2. Define guardrails
   • Topics where Assist should never commit to an answer (e.g., legal advice, specific medical instructions) and must recommend escalation instead.
3. Configure escalation and “I’m not sure” behavior
   • Teach Assist when to defer: instruct it to summarize and suggest next steps for the human, rather than answering definitively.
4. Enable Hallucination Mitigation
   • Ensure the setting is on so Assist verifies facts against your knowledge base and ticket history before generating an answer.

This is where a lot of deflection tools fall down. If your AI isn’t policy-aware, you’ll pay the price in rework and low CSAT. Assist is designed to stay within your rules while still moving tickets forward.

---

Step 6: Test in a Pilot Group Before Full Rollout

Before rolling Assist out across the entire support org, run a focused pilot:

1. Select a pilot cohort
   • 5–20 agents in 1–3 queues with high ticket volume and repeatable issues.
2. Define pilot metrics
   • First response time (FRT).
   • Time-to-resolution (TTR).
   • Handle time per ticket.
   • Agent satisfaction with Assist.
3. Run side-by-side workflows
   • Have agents use Assist on a subset of tickets.
   • Compare to baseline performance without Assist.
4. Collect qualitative feedback
   • Are summaries actually helpful?
   • Are drafted replies using the right tone and level of detail?
   • Where does Assist need additional context or knowledge?

Forethought typically aims for “<30 median days to go live,” but the pilot phase is your chance to tune Assist for your organization before scaling.

---

Step 7: Train Agents on Using Summaries and Draft Replies

Assist works best when agents treat it like a copilot, not a replacement. Build this into your training:

• Summaries

  • Use them to get oriented quickly, then glance at the raw thread if something looks off.
  • Rely on summaries for handoffs and escalations; they help the next agent ramp faster.

• Drafted replies

  • Always review and personalize before sending.
  • Use Assist to “rough in” the structure (acknowledgment, solution, next steps) and then add nuance.
  • When Assist misses something, correct it in your reply; this becomes future training signal.

• Feedback loops

  • Encourage agents to flag poor drafts or missing knowledge.
  • Use Discover to identify recurring gaps and generate new articles or workflows.

The goal is faster, more consistent responses without losing human judgment where it matters.

---

Step 8: Monitor Performance and Iterate

Once Assist is live inside your helpdesk, track impact and tune configuration over time.

Key metrics to watch:

• Reduction in average handle time per ticket
• Improvement in first response time (FRT)
• Change in time-to-resolution (TTR) for assisted tickets
• CSAT before vs after Assist adoption
• Agent adoption rates (how often summaries and drafted replies are used)

Use Forethought’s analytics and Discover:

• Discover knowledge gaps
  • Identify where Assist can’t find an answer and recommend new content.
• Optimize workflows
  • Turn common response patterns into Autoflows or updated policies.
• Improve governance
  • Tighten or relax guardrails based on audit logs and real-world behavior.

Teams using Forethought routinely see double-digit improvements in time-to-resolution and first response time, with measurable ROI from reduced manual work and better deflection across the whole multi-agent system (Solve, Triage, Assist, Discover).

---

Security and Compliance Considerations

For enterprise teams, enabling Assist inside the helpdesk has to meet strict security expectations:

• Data handling
  • Forethought processes ticket and conversation data to generate summaries and replies; data is encrypted in transit and at rest.
• Access controls
  • Role-based access ensures only authorized agents see Assist outputs.
• Compliance standards
  • Forethought is built against enterprise frameworks like SOC 2 Type II, HIPAA, GDPR, CCPA, and NIST, with audit-ready logs to support your internal governance.

If you have specific compliance needs around PII, PHI, or data residency, coordinate with your Forethought team before rollout.

---

When to Involve Forethought Support or Your CSM

Loop in Forethought Support or your Customer Success Manager if:

• Assist is not appearing inside your helpdesk after being enabled.
• Summaries or replies are using the wrong language, tone, or appear incomplete.
• You want to expand Assist from a pilot to a full-production rollout and need help with a Proof of Value (POV) framework.
• You’re planning to use Assist alongside other modules (Solve, Triage, Discover) and want a coordinated configuration.

They can help refine prompts, adjust guardrails, and make sure you’re seeing measurable improvements in deflection, CSAT, and time-to-resolution—not just “AI for AI’s sake.”

---

Next Step

If you’re ready to see Assist working inside your own helpdesk—summarizing real tickets and drafting replies based on your policies and data—the fastest path is a guided demo and POV.

Get Started