Connection Descriptions

Introduction

Descriptions can help improve the accuracy of your results by guiding Chat Aid to know where to look for answers. When you ask Chat Aid a question, it first checks the description of the source to know whether or not it should prioritize information found through that connection. You can also use the descriptions to guide Chat Aid to know how information within that connection is used. Descriptions should provide additional context as to the nature and purpose of those documents. Generic descriptions typically do not help.

Example Descriptions

Notion Example

We use Notion at work to maintain all our employee documents.

These include reimbursement policies, time-off policies, links to employee portals, credentials to corporate accounts on productivity apps and more. The HR team also documents all company-wide announcements like townhall events in Notion.

Azure DevOps Example

## // **IN_PROGRESS:**

- Action required, Added to sprint, Assigned, Awaiting Approval, Backlog, Bug opened, Build broken, Building, Contents Team, Design ready, Escalated, Feedback (External)

## // **TODO:**

- Approved for Implementation, Blocked, Blocked (external), Blocked (internal), Completed DPA, New, On hold, Open, Pending response, Pending response/On Hold (IMT), Reopened

## // **DONE:**

- Canceled, Closed, Declined, Done, Duplicate, Live, Rejected, Resolved