Enterprise engagements ยท Cross-industry

Knowledge assistants over Slack, Jira, Arabic texts and 20 years of pricing data

Retrieval assistants that unify Slack and Jira knowledge, answer Arabic questions accurately and let analysts query two decades of commodity pricing in plain language.

Client
Enterprise and trading clients, including an Arabic-language research use case
Engagement
Three related retrieval and question answering builds
Our role
Retrieval design, model selection, knowledge graph, APIs
Status
Delivered
Time-to-answer, down from about two days

Seconds

Answer accuracy on Arabic extractive QA

~90%

Of commodity pricing queryable in plain language

20 years

LLM deployment options for enterprise control

Cloud or on-prem

In brief

Teams were losing days hunting for answers across Slack threads, Jira tickets and long documents, one client needed accurate question answering over a large Arabic text corpus, and a trading group wanted analysts to question twenty years of commodity pricing without writing queries. Involabs built retrieval assistants that unify Slack and Jira knowledge with cloud or on-premise models, an extractive Arabic question answering system that returns exact passages, and a knowledge graph analysts can query in plain language. Time-to-answer on operational questions fell from about two days to seconds, with about 90 percent answer accuracy on Arabic extractive QA.

Architecture

How it works

  1. Sources

    Where knowledge lives

    • Slack threads
    • Jira tickets and Salesforce
    • Long Arabic texts
    • Pricing history
  2. Index

    Retrieval layer

    • Vector search
    • Knowledge graph for prices
  3. Answer

    Grounded answers

    • Extractive for precision
    • Open-weight models
  4. Deploy

    Where it runs

    • Cloud
    • On-premise with Ollama

The situation

Teams were losing days hunting for answers spread across Slack threads, Jira tickets and long documents. One client also needed accurate question answering in Arabic over a large religious text corpus, and a trading group wanted analysts to question two decades of commodity pricing without writing queries.

What we built

A unified operational assistant. A redesigned RAG system that brings Slack and Jira knowledge, and in a related build Salesforce, into one assistant. It supports cloud and on-premise LLM deployment, using LLaMA 3 and Mistral served with Ollama where data had to stay in-house.

Arabic extractive question answering. An extractive QA system built on open-source language models and vector search, returning precise spans from large Arabic corpora rather than generated paraphrase, which is what accuracy on religious texts requires.

Conversational querying over pricing history. Twenty years of commodity pricing modelled in a knowledge graph, so analysts can ask questions in plain language and get answers grounded in the stored series.

Results

  • Internal time-to-answer on operational questions reduced from about two days to seconds
  • About 90 percent answer accuracy on Arabic extractive QA
  • Twenty years of pricing data queryable in plain language

Why it matters

Extractive answers, citations and on-premise options are what make retrieval usable where precision and confidentiality matter. The same patterns carry directly into regulated healthcare and financial knowledge bases.

Have a similar problem?

Send us the problem and the constraints. We will tell you what it would actually take, starting with a fixed-scope assessment.