What’s the chat history?

Since our AI Agent operates 100% independently—based on the protocols set up by providers—it is crucial to be able to review how conversations between patients and our AI Agent progress. This functionality ensures providers have full control of the AI, allowing them to review any responses that may have gone off-track and continuously improve the Agent’s performance.

Below is our chat history view:

Data in the view

1. Internal ID: An internal reference ID that helps our technical team locate specific conversations to investigate on behalf of our clients.

2. External ID: A customizable field that can be set by providers or automatically populated by the patient’s name.

3. Message count: The total number of messages exchanged between both the patient and the AI Agent.

4. Last message date: Useful for identifying conversations in which patients may still be active, so providers can step in if needed. (We’ll show you this human-in-the-loop feature later.)

   
   

Buttons

• Chat history: Clicking this button takes you to the complete conversation thread.

• Patient dashboard: A customized view of patient status, including details such as symptoms, medication intake, educational videos viewed, and blood pressure (if our Agent is connected to a medical device). We’ll cover this in a specific module.

  
  

Below is the chat history view:

In the chat history, providers can see the content of each message and its exact time stamp.

By opening the activity log, providers can view each step the AI Agent follows in the protocol and see how it transitions from one section to another. It starts in a set order but may move back and forth between sections depending on the user’s answers.

For example, this protocol might cover symptoms, blood pressure monitoring, and then medication assessment. However, while discussing medication adherence, patients may bring up new symptoms that could be side effects.

Finally, scheduled events displays every manually managed scheduled event set by the provider. These events can be recurring or one-time for a specific reason.

🔗 See how it works in this video