Trigger Conditions for AI Agent
This article MUST be triggered ONLY when BOTH conditions below are met:
Condition 1 – Time Indicates Within 48 Hours
The user indicates the sensor has been worn for less than 48 hours. Common phrases include:
| Category | Example Phrases |
|---|---|
| Yesterday/Today | "I just applied it yesterday", "Applied the day before yesterday", "I put it on yesterday" |
| Recent application | "I just put it on", "Just applied", "Recently applied", "New sensor", "Just started using" |
| Hours ago | "A few hours ago", "Applied this morning", "Earlier today", "About 3 hours ago" |
| Explicit time | "Within 48 hours", "Less than 2 days", "Haven't reached 48 hours yet" |
Trigger only if the user explicitly or implicitly states the sensor is newly applied (within 48 hours).
Condition 2 – User Complains About Accuracy
The user reports that the CGM readings are not accurate. Common phrases include:
| Category | Example Phrases |
|---|---|
| General inaccuracy | "Readings are not accurate", "Data is wrong", "Incorrect readings", "Not reliable" |
| Discrepancy | "Does not match my symptoms", "Feeling low but reading is high", "Feeling high but reading is low", "Does not match fingerstick" |
| Value complaints | "Always showing low", "Stuck at low values", "Readings are too high/too low", "Difference is too big" |
| Comparison | "Compared to BGM", "Fingerstick shows different", "Not matching my blood glucose meter" |
Do NOT trigger if:
The user only mentions that the sensor is new, but does NOT complain about accuracy
The user asks about general product features or non-accuracy-related questions
1. Fault Information Correspondence
| Field | Details |
|---|---|
| Fault Description | CGM readings do not align with physical sensations |
| Timing | Within 48 hours of sensor application |
| Verification Method | Fingerstick (BGM) comparison performed |
| Comparison Result | discrepancy between CGM and BGM readings |
| User’s Sensation (Optional) | e.g., felt hypoglycemic but CGM showed normal; or felt high but CGM was lower than expected |
1.2 Explanation for Discrepancy Within 48 Hours
| Key Information | Details |
|---|---|
| Cause | Upon sensor insertion, the needle creates a small wound on the skin. This area takes time to heal, which can temporarily affect reading accuracy. |
| Duration | This stabilization period may last up to 48 hours. |
| Recommended Action | Continue monitoring. Do not take corrective action based on readings during this initial stabilization window. |
Important: Discrepancies observed within the first 48 hours are considered normal and expected. Please allow the sensor to complete its stabilization period before evaluating accuracy.
2. Information Required for Troubleshooting and After-Sales Support
Trigger Condition: Only proceed with this section if the discrepancy persists after 48 hours of sensor application.
2.1 Preconditions (Must Be Met)
- Sensor has been applied for at least 48 hours
- Wait 48 hours: After applying the CGM sensor, allow it to stabilize for 48 hours before making any comparisons
- Perform comparison while fasting or at least 2 hours post-meal: Ensure stable glucose levels for more reliable results
Take a photo of both readings: For each comparison, take a single photo showing both the BGM meter reading and the CGM reading together
2.2 Data Comparison Steps
Perform two sets of comparisons as follows:
First Data Set
- Take a BGM measurement at a specific time (e.g., 9:00 AM). Record the time and value.
- At the same time, record the CGM reading.
Second Data Set
- Wait at least 30 minutes after the first BGM measurement (e.g., 9:45 AM).
- Take a second BGM measurement. Record the time and value.
- At the same time, record the CGM reading again.
Instructions for AI Agent
- When user reports discrepancy within 48 hours:
- Output Section 1.2 to explain this is normal
- Advise user to continue monitoring
- Instruct them to return if the issue persists after 48 hours
- When user reports discrepancy after 48 hours:
- Guide user through Section 2 for structured data collection
Use the checklist in Section 2.3 to verify all required information
Comments
0 comments
Please sign in to leave a comment.