<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>telepresencia on Blog</title>
    <link>https://blog.ivrpowers.com/tags/telepresencia/</link>
    <description>Recent content in telepresencia on Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 23 Aug 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://blog.ivrpowers.com/tags/telepresencia/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Better Coordinated in the Consultation, Not After It</title>
      <link>https://blog.ivrpowers.com/post/industries/coordinated-in-the-consultation-not-after-it/</link>
      <pubDate>Sun, 23 Aug 2026 10:00:00 +0200</pubDate>
      
      <guid>https://blog.ivrpowers.com/post/industries/coordinated-in-the-consultation-not-after-it/</guid>
      <description>Photo source: Interactive Powers Better Coordinated in the Consultation, Not After It Some things come up mid-consultation that the doctor could settle right there:
→ requesting a test from an internal service → closing out a medical or administrative step → checking something with another department All three normally wait until the visit is over. And once it&amp;rsquo;s over, each one becomes a workflow of its own — its own call, its own queue, its own explanation from the beginning.</description>
    </item>
    
  </channel>
</rss>
