This instruction describes the current Braincore capabilities. When the interface or scenario changes, we update the material.
When you need a table
A table is more useful than plain text when the data changes often or must be looked up by fields. Typical examples: a price list, a service catalog, an assortment, vacancies, a schedule, and availability statuses.
Make the data unambiguous
One row should describe one object, and each column should hold one type of data. Give columns clear names and do not hide several values in a single cell. This reduces the risk of a wrong answer.
- Include the name, identifier, or category of the object.
- Store price, status, and deadline in separate columns.
- Add an update date if the information changes quickly.
Connect the table to the employee
After you upload or prepare a table, review its contents and enable it for the relevant AI employee. In answers it can then use the connected data instead of relying on outdated instruction text.
Still have a question? Contact support.