Forethought Assist reduces D2L ticket close time by 13.7% and increases cases per hour by 32%
D2L support agents wasted time toggling between multiple windows and tabs to find help articles and past tickets, while keyword-based search tools returned long lists of irrelevant results from unstructured data sources, causing agents to spend more time searching than answering tickets.
D2L's previous search tools relied on keyword matching and produced irrelevant results, and the team could not find a partner capable of working with their unstructured, heterogeneous knowledge sources.
D2L reduced time to close tickets by 13.7%, increased cases answered per hour by 32%, and decreased First Response Time by 56%, while agents who used Forethought consistently were 3.5 times more likely to meet their weekly efficiency goals.
Show all 5 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
D2L reduced time to close tickets by 13.7%, increased cases answered per hour by 32%, and decreased First Response Time by 56%, while agents who used Forethought consistently were 3.5 times more likely to meet their w…
What tools did this team use?
Forethought Assist, NLU.
What results were reported?
Time to close tickets: 13.7%; Cases answered per hour: 32%; First Response Time: 56%; AI accuracy: over 90% (source-reported, not independently verified).
What failed first in this deployment?
D2L's previous search tools relied on keyword matching and produced irrelevant results, and the team could not find a partner capable of working with their unstructured, heterogeneous knowledge sources.
How is this customer support AI workflow structured?
Agent opens new case → AI retrieves relevant content → Agent adds past response → Help article added to response → Knowledge gap identification.