kevinhug commited on
Commit
fa93fef
·
1 Parent(s): 2b6273e

image correct

Browse files
Files changed (1) hide show
  1. app.py +19 -1
app.py CHANGED
@@ -284,6 +284,17 @@ Example of Customer Profile in Graph
284
  ![Customer Needs and Pain Points](https://i.postimg.cc/D03Sstqd/knowledge-graph1.png)
285
  ![Accumulated Interaction for the same Customer Needs and Pain Points](https://i.postimg.cc/9ffZQ5pD/knowledge-graph2.png)
286
 
 
 
 
 
 
 
 
 
 
 
 
287
  Benefits of a Knowledge Graph
288
  ============
289
  - Smarter Data Relationships
@@ -450,6 +461,13 @@ Example of Call Resolution
450
 
451
  ![Resolution for Clear Picture about Customer Issue](https://i.postimg.cc/J4qsDYtZ/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
 
455
  How can teams automatically stitch together fragmented mentions of the same customer, product, or issue—across call transcripts, CRM records, and support tickets—to form a unified view of the actual problem?
@@ -460,4 +478,4 @@ For example, Comcast reduced repeat service calls by 17% after deploying entity
460
 
461
  The result? Less agent time lost, higher customer satisfaction, and data pipelines that actually speak human.
462
  """)
463
- demo.launch(allowed_paths=["./"])
 
284
  ![Customer Needs and Pain Points](https://i.postimg.cc/D03Sstqd/knowledge-graph1.png)
285
  ![Accumulated Interaction for the same Customer Needs and Pain Points](https://i.postimg.cc/9ffZQ5pD/knowledge-graph2.png)
286
 
287
+ ![Customer Needs and Pain Points.](./knowledge-graph1.png)
288
+ ![Accumulated Interaction for the same Customer Needs and Pain Points.](./knowledge-graph2.png)
289
+
290
+ ![Customer Needs and Pain Points..](file=./knowledge-graph1.png)
291
+ ![Accumulated Interaction for the same Customer Needs and Pain Points..](file=./knowledge-graph2.png)
292
+
293
+ #### Customer Needs and Pain Points
294
+ https://i.postimg.cc/D03Sstqd/knowledge-graph1.png
295
+ #### Accumulated Interaction for the same Customer Needs and Pain Points
296
+ https://i.postimg.cc/9ffZQ5pD/knowledge-graph2.png
297
+
298
  Benefits of a Knowledge Graph
299
  ============
300
  - Smarter Data Relationships
 
461
 
462
  ![Resolution for Clear Picture about Customer Issue](https://i.postimg.cc/J4qsDYtZ/entity.png)
463
 
464
+ ![Resolution for Clear Picture about Customer Issue.](./entity.png)
465
+
466
+ ![Resolution for Clear Picture about Customer Issue..](file=./entity.png)
467
+
468
+ #### Resolution for Clear Picture about Customer Issue
469
+ https://i.postimg.cc/J4qsDYtZ/entity.png
470
+
471
  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.
472
 
473
  How can teams automatically stitch together fragmented mentions of the same customer, product, or issue—across call transcripts, CRM records, and support tickets—to form a unified view of the actual problem?
 
478
 
479
  The result? Less agent time lost, higher customer satisfaction, and data pipelines that actually speak human.
480
  """)
481
+ demo.launch(allowed_paths=["."])