Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Unified experience: Users only have to engage with one chatbot, regardless of the department they seek to engage with.

  • Centralized Design/Development: The chatbot will follow a singular design pattern and set of best practices.

  • Fine-tuned for Tufts: Models can be fine tuned to Tufts data and provide a more reliable/accurate experience.

  • Cost Savings: Chat bots in general can yield savings by making certains roles or systems obsolete. Additionally, in-house development can yield cost savings over off-the-shelf chatbots and models.

  • Time savings: Staff can spend less time on mundane, repetitive tasks, and spend more time on meaningful, interesting projects.

Risks

  • Data Quality: “Garbage in, garbage out” The training of any model hinges on accurate, high quality data in an optimal format. If a department lacks this, it can hinder development and even worse, lead to unreliable model output. Data can broken down into the following aspects:

    • Accuracy: The data for a process is accurate and up-to-date

    • Volume: There’s an adequate amount of data to train, per model requirements

    • Format: Data is in an adequate format for training

  • Hallucinations: If a model lacks adequate data on a particular topic it can potentially provide false information. Tuning of model parameters (e.g temperature) can help minimize hallucinations.

Design

The chatbot will be designed around a modular architecture, with each department being assigned it’s own model trained and fine-tuned on it’s specific data. This will allow for modular development and training of models, minimizing the impact to models of other departments.

...