kevinhug commited on
Commit
d026c09
·
1 Parent(s): 40d8579

image correct

Browse files
Files changed (1) hide show
  1. app.py +4 -3
app.py CHANGED
@@ -281,8 +281,8 @@ Customer: "No, thank you."
281
  gr.Markdown("""
282
  Example of Customer Profile in Graph
283
  =================
284
- ![Customer Needs and Pain Points](file=knowledge_graph1.png)
285
- ![Accumulated Interaction for the same Customer Needs and Pain Points](file=knowledge_graph2.png)
286
 
287
  Benefits of a Knowledge Graph
288
  ============
@@ -447,7 +447,8 @@ Customer: "No, thank you."
447
  gr.Markdown("""
448
  Example of Call Resolution
449
  ===============
450
- ![Resolution for Clear Picture about Customer Issue](file=entity.png)
 
451
 
452
  Companies like RBC, Comcast, or BMO often face a recurring challenge: long, complex customer service calls filled with vague product references, overlapping account details, and unstructured issue descriptions. This makes it difficult for support teams and analytics engines to extract clear insights or resolve recurring pain points across accounts and products.
453
 
 
281
  gr.Markdown("""
282
  Example of Customer Profile in Graph
283
  =================
284
+ ![Customer Needs and Pain Points](file=./knowledge_graph1.png)
285
+ ![Accumulated Interaction for the same Customer Needs and Pain Points](file=./knowledge_graph2.png)
286
 
287
  Benefits of a Knowledge Graph
288
  ============
 
447
  gr.Markdown("""
448
  Example of Call Resolution
449
  ===============
450
+
451
+ ![Resolution for Clear Picture about Customer Issue](file=./entity.png)
452
 
453
  Companies like RBC, Comcast, or BMO often face a recurring challenge: long, complex customer service calls filled with vague product references, overlapping account details, and unstructured issue descriptions. This makes it difficult for support teams and analytics engines to extract clear insights or resolve recurring pain points across accounts and products.
454