<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>phygital on Blog</title>
    <link>https://blog.ivrpowers.com/tags/phygital/</link>
    <description>Recent content in phygital on Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 29 Aug 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://blog.ivrpowers.com/tags/phygital/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Served by Someone Who Isn&#39;t in the Branch — and Rated as If They Were</title>
      <link>https://blog.ivrpowers.com/post/industries/served-by-someone-who-isnt-in-the-branch/</link>
      <pubDate>Sat, 29 Aug 2026 10:00:00 +0200</pubDate>
      
      <guid>https://blog.ivrpowers.com/post/industries/served-by-someone-who-isnt-in-the-branch/</guid>
      <description>Photo source: Interactive Powers Served by Someone Who Isn&amp;rsquo;t in the Branch — and Rated as If They Were In a branch already running this way, the customer takes a ticket and chooses:
A. On-site position — 20 to 25 minutes&amp;rsquo; wait. B. Floating or remote position (virtual) — 0 to 3 minutes.
Same operations, same resolution, same ownership of the case. Nobody steers the choice. The only variable that changes is where the advisor is sitting.</description>
    </item>
    
    <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>
    
    <item>
      <title>The Phone We Stopped Using — Except in Every Hotel Room</title>
      <link>https://blog.ivrpowers.com/post/trends/the-phone-we-stopped-using/</link>
      <pubDate>Wed, 19 Aug 2026 10:00:00 +0200</pubDate>
      
      <guid>https://blog.ivrpowers.com/post/trends/the-phone-we-stopped-using/</guid>
      <description>Photo source: Interactive Powers The Phone We Stopped Using — Except in Every Hotel Room That landline is still there, in every hotel room, whatever the category. Sometimes there are even two — one on the nightstand, one in the bathroom. Younger guests have already made up their minds about it: they no longer know how to use it, or want to.
Street phone booths disappeared entirely, and nobody missed them.</description>
    </item>
    
    <item>
      <title>Telepresence: Your Branch Doesn&#39;t Need More Square Meters</title>
      <link>https://blog.ivrpowers.com/post/trends/telepresencia-your-branch-doesnt-need-more-square-meters/</link>
      <pubDate>Fri, 14 Aug 2026 15:00:00 +0200</pubDate>
      
      <guid>https://blog.ivrpowers.com/post/trends/telepresencia-your-branch-doesnt-need-more-square-meters/</guid>
      <description>Photo source: Interactive Powers Telepresence: Your Branch Doesn&amp;rsquo;t Need More Square Meters A branch closes at 6:00pm. The customer arrives at 6:05. A counter with no one behind it, lines that grow at peak hours, one specialist who can&amp;rsquo;t physically be in three locations at once. For years the only answer to this was more square meters, more local staff, or fewer hours of service — none of which scale well.</description>
    </item>
    
  </channel>
</rss>
