[Blog] Images for best practices articles (#2487)

blog/src/pages/2023-08-31-boost-customer-satisfaction.mdx

@@ -17,6 +17,8 @@ export const Line = () => (
 
 ## Boost Customer Satisfaction with Custom AI Assistants {{ date: '2023-08-31T00:00Z', id: '2023-08-31-boost-customer-satisfaction' }}
 
+![](@/media/2023-08-31-boost-customer-satisfaction/cs-happy.png)
+
 Based on our experience rolling out Dust assistants to augment our users’ customer service teams, we’ve compiled below some best practices to serve this use case better. Please reach out at team@dust.tt with any questions!
 
 We’ve repeatedly seen that a general-purpose assistant with access to the entire company data is not optimal for customer service teams. The more data you give access to an assistant, the lower the chance of retrieving the correct information at the right time. Exploring this tension with our customers, we’ve discovered that customer service use cases are generally better supported by focused custom assistants that serve a dedicated set of instructions. The assistant then becomes a specialized tool more than a general helper.
@@ -38,6 +40,8 @@ For each, we provide recommendations on the instructions, model configuration, a
 - We prompt the assistant not to answer the question if a definite answer cannot be found in the retrieved information.
 - The assistant should not be used to answer an external user/customer question directly but to answer a question by a customer service agent about curated internal company knowledge while answering an external user/customer question.
 
+![](@/media/2023-08-31-boost-customer-satisfaction/customer-satisfaction-screenshot.png)
+
 ### Assistant specification
 
 **Instructions**

blog/src/pages/2023-09-28-automating-sql-query.mdx

@@ -17,6 +17,8 @@ export const Line = () => (
 
 ## Automate SQL Query Generation with a Custom Dust Assistant {{ date: '2023-09-28T00:00Z', id: '2023-09-28-automating-sql-query' }}
 
+![](@/media/2023-09-28-automating-sql-query/sql-header.png)
+
 Take the load off your data analysts with a Dust assistant specialized in SQL.
 
 From wide-scale rollouts, we've seen immense value in AI assistants that automatically generate SQL queries.
@@ -33,6 +35,8 @@ While this use case is straightforward, feel free to ask any questions. With the
 - We prompt the assistant by providing a full description of the database schemas, as well as a general translation of business terms to table and field names if necessary. This name correspondence is useful if table or column names are not clearly aligned with the general business terminology used within the company. As an example: it can be useful to define what your company consider an active user and similar concepts.
 - If your company is large, the number of tables may be prohibitively large (say 100+). In that case, we encourage shipping one custom assistant per team or function focusing on the tables that are useful to their general use cases. We sugget to not exceed 50 table definitions per assistant. We’re here to help, get in touch in case of doubt: team@dust.tt
 
+![](@/media/2023-09-28-automating-sql-query/sql-screenshot.png)
+
 In the instructions below we prompt the model to follow instructions specific to our systems. You can obviously adapt these instructions to your own systems.
 
 ### Assistant specification

blog/src/pages/2023-10-23-track-project-status.mdx

@@ -17,6 +17,8 @@ export const Line = () => (
 
 ## Build an AI Assistant to Track Internal Project Status {{ date: '2023-10-23T00:00Z', id: '2023-10-23-track-project-status' }}
 
+![](@/media/2023-10-23-track-project-status/track-project-img.png)
+
 Stay on top of key projects with a custom Dust assistant.
 
 From rolling out Dust and assistants across companies, we've seen tremendous value in creating AI assistants that provide project status updates.
@@ -34,6 +36,8 @@ Please reach out to team@dust.tt with any questions!
 - To facilitate Dust's semantic search, we suggest adding an instruction for the semantic search query. This will give more guidance to your assistant on where to focus.
 - Finally, we included a template of the desired format. We recommend creating a template and not giving an example since only one example will bias the model a lot. You can add examples at the end of the instructions but limit them to 3-4.
 
+![](@/media/2023-10-23-track-project-status/track-project-screenshot.png)
+
 In the instructions below, we prompt the model to follow instructions specific to our systems. You can adapt these instructions to your own systems.
 
 ### Assistant specification

blog/src/pages/index.mdx

@@ -10,6 +10,8 @@ export async function getStaticProps() {
 
 ---
 
+![](@/media/2023-10-23-track-project-status/track-project-img.png)
+
 ## Build an AI Assistant to Track Internal Project Status {{ date: '2023-10-23T00:00Z', id: '2023-10-23-track-project-status' }}
 
 Stay on top of key projects with a custom Dust assistant.
@@ -20,6 +22,8 @@ This best practice outlines how to build an assistant that delivers timely, rele
 
 ---
 
+![](@/media/2023-09-28-automating-sql-query/sql-header.png)
+
 ## Automate SQL Query Generation with a Custom Dust Assistant {{ date: '2023-09-28T00:00Z', id: '2023-09-28-automating-sql-query' }}
 
 Take the load off your data analysts with a Dust assistant specialized in SQL.
@@ -30,6 +34,8 @@ This article outlines building a Dust Custom assistant that outputs analysis-rea
 
 ---
 
+![](@/media/2023-08-31-boost-customer-satisfaction/cs-happy.png)
+
 ## Boost Customer Satisfaction with Custom AI Assistants {{ date: '2023-08-31T00:00Z', id: '2023-08-31-boost-customer-satisfaction' }}
 
 Based on our experience rolling out Dust assistants to augment our users’ customer service teams, we’ve compiled below some best practices to serve this use case better. Please reach out at team@dust.tt with any questions!