Edit AI

Use the following tabs for configuration:

Basic Data

  • Name: Enter a name for the new chatbot here (e.g., "OpenAI/Support").
  • AI Type: Select the type or provider of the chatbot API you wish to integrate. Currently, OpenAI/ChatGPT, DeepSeek, and Empolis Buddy are supported.
    Many other providers have adapted their APIs to the OpenAI/ChatGPT format (e.g., the Ionos AI Model Hub).
  • Base URL: Enter the URL for the selected API here (e.g., https://api.openai.com/v1/chat/completions for OpenAI/ChatGPT).
  • Model: Enter the exact name of the model to be used, exactly as expected by the provider (e.g., `gpt-4o-mini` for OpenAI).
  • If available for the selected AI type, you can submit images and text documents—which are stored as attachments within a ticket—for analysis.
    To do so, enable the following options if desired:
    • Analyze Images: If enabled, image attachments will be passed to the chatbot and included in the request processing.  Analyze Attachments: If enabled, todo4teams will convert attachments in PDF, DOC, DOCX, and ODT formats and pass them to the AI ​​for analysis in addition to the prompt.
    • Attachment Analysis Limit: Enter the maximum number of characters to which the file analysis should be limited per file here. Thus, a value of 2000 means that the first 2000 characters of each attachment will be included. This corresponds to one fully printed A4 page.
  • Active: Use this toggle to enable or disable the ChatBot configuration.

Ticket Prompts

This is where you store the system prompts that are passed to the ChatBot. Depending on the specific processing context within todo4teams, different prompts are utilized; for each context, three distinct prompts are defined:

  • Prefix: This text is prepended to the agent's input/question. Example: 'I am a support agent.'
  • Postfix: This text is appended to the agent's input/question. Example: 'Answer briefly, in a maximum of three sentences.'
  • System Command: The system prompt provided to the ChatBot prior to the actual dialogue with the user. Example: 'You are a technical consultant speaking with technically proficient users.'

Ticket Creation

These prompts are used when the agent utilizes the ChatBot within the "Create Ticket" context.

Ticket Response

These prompts are used when the agent utilizes the ChatBot within the "Resolve Ticket" context, or when drafting an email response.

Ticket Default

These prompts are used in all other contexts—for instance, when the ChatBot is invoked via a script.

Ticket Context

todo4teams can pass the data from the current ticket to the ChatBot, replacing the placeholders enclosed in {} (as listed below) with the corresponding ticket properties. Leave this field blank if you do not wish to pass any ticket data to the AI.

Example:

The question refers to the following customer inquiry:
Subject: {title}
Email Sender: {from}
Addressed Team: {toteam}
Date of Inquiry: {startdate}
Scheduled Completion Date: {scheduledenddate}
Assignee: {username}
Inquiry: {description}

Use this example if you want to ask the AI ​​to provide a response to the customer inquiry.

The following placeholders are available:

  • title: Ticket title (and typically the subject line of the received email)
  • from: Sender address of the email
  • toteam: Name of the addressed team
  • startdate: Ticket start time
  • scheduledenddate: Scheduled completion date of the ticket
  • username: Full name of the ticket assignee (the current user)
  • description: Full text of the ticket (and typically the subject line of the received email)

Basic Facts

Insert facts here in a concise text format that should be added to the system prompt and are specific to the company or team—e.g.:

The Hamburg office will close on July 31, 2027.
The XK67-3 adapter requires a USB power supply with an output of at least 10 watts.

Properties

Depending on the AI ​​type, enter additional configuration details here—e.g., for OpenAI/ChatGPT:

apiKey=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
max_completion_tokens=16380

or for the Empolis Buddy:

tokenUrl=https://XXXXX.empolisservices.com/oauth2/token
docBaseUrl=https://XXXXX.empolisservices.com/XXXX
username=XXXXX
password=XXXXX
client_id=XXXXX
client_secret=XXXXX

Test

Click "Test" to open a chat window and test the configuration.