<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Univerx Blog</title>
    <link>https://univerx.ai/en/blog</link>
    <description>Articles on AI in customer service, contact centres, workforce and European regulation.</description>
    <language>en</language>
    <atom:link href="https://univerx.ai/en/blog/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A pilot with one team and one channel: why starting small holds</title>
      <link>https://univerx.ai/en/blog/pilot-one-team-one-channel</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/pilot-one-team-one-channel</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <category>Customer experience strategy</category>
      <description>A pilot is not a scaled-down big project. It is an experiment with one clear question. Here is how to ask it well.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Accessible web messaging: ten points to start with</title>
      <link>https://univerx.ai/en/blog/accessibility-web-messaging</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/accessibility-web-messaging</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <category>Practice &amp; how-to</category>
      <description>A chat window is small, but it packs in almost everything that makes accessibility hard. Ten points to start with.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Consent in outbound: what German competition law means for campaigns</title>
      <link>https://univerx.ai/en/blog/consent-outbound-germany</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/consent-outbound-germany</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <category>Europe &amp; regulation</category>
      <description>Consent first, contact second. What German law requires and how a campaign keeps to it every day.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Informing proactively: appointments, deadlines and status in citizen service</title>
      <link>https://univerx.ai/en/blog/proactive-notifications-logistics</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/proactive-notifications-logistics</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <category>Public sector</category>
      <description>Many calls to citizen services are questions about progress. A good notification answers them before anyone picks up the phone.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Talking to the works council about analytics: a preparation</title>
      <link>https://univerx.ai/en/blog/works-council-and-analytics</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/works-council-and-analytics</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <category>Practice &amp; how-to</category>
      <description>If you plan to introduce analytics, know the works council&apos;s questions before they are asked. A preparation in documents, roles and configuration.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>When everyone calls at once: communication during outages</title>
      <link>https://univerx.ai/en/blog/peak-load-outage-communication</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/peak-load-outage-communication</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <category>Contact centre</category>
      <description>In an outage, the best answer is the one that arrives before anyone has to ask. A sequence for the first few hours.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Data residency: the five questions procurement and privacy ask</title>
      <link>https://univerx.ai/en/blog/data-residency-questions</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/data-residency-questions</guid>
      <pubDate>Sun, 01 Nov 2026 09:00:00 GMT</pubDate>
      <category>Europe &amp; regulation</category>
      <description>&quot;The data stays in Europe&quot; is a good start, but not an answer. Five questions procurement and privacy teams follow up with, and what makes an answer reliable.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Grounded answers: why a knowledge base keeps AI honest</title>
      <link>https://univerx.ai/en/blog/knowledge-base-grounded-answers</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/knowledge-base-grounded-answers</guid>
      <pubDate>Sun, 01 Nov 2026 09:00:00 GMT</pubDate>
      <category>AI in customer service</category>
      <description>Search first, then write, then show the source: that is how a plausible answer becomes one you can check.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Journey first, not channel first: another way to plan service</title>
      <link>https://univerx.ai/en/blog/journey-first-vs-channel-first</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/journey-first-vs-channel-first</guid>
      <pubDate>Sun, 01 Nov 2026 09:00:00 GMT</pubDate>
      <category>Customer experience strategy</category>
      <description>Nobody wants to &quot;use the chat&quot;. People want to move house, switch tariffs or understand a bill. Plan service along those paths and you see breaks no channel report shows.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Measuring customer experience without vanity metrics</title>
      <link>https://univerx.ai/en/blog/measuring-cx-without-vanity-metrics</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/measuring-cx-without-vanity-metrics</guid>
      <pubDate>Sun, 01 Nov 2026 09:00:00 GMT</pubDate>
      <category>Customer experience strategy</category>
      <description>A good metric changes a decision. A vanity metric only changes the mood in the meeting. Three questions help to tell them apart.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Team leads see topics, not just numbers</title>
      <link>https://univerx.ai/en/blog/supervisor-view-topics-coaching</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/supervisor-view-topics-coaching</guid>
      <pubDate>Sun, 01 Nov 2026 09:00:00 GMT</pubDate>
      <category>Workforce</category>
      <description>From wallboard to topic map: what changes when team leads see what people are talking about, not only for how long.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>What Semantic² reads, and how a finding is made</title>
      <link>https://univerx.ai/en/blog/semantic2-finding-anatomy</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/semantic2-finding-anatomy</guid>
      <pubDate>Sun, 01 Nov 2026 09:00:00 GMT</pubDate>
      <category>Practice &amp; how-to</category>
      <description>A finding is not a gut feeling. It has four parts, and each of them can be checked. This is how it is made.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Appointments and reminders in healthcare: proactive instead of reactive</title>
      <link>https://univerx.ai/en/blog/appointments-and-reminders-health</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/appointments-and-reminders-health</guid>
      <pubDate>Sat, 31 Oct 2026 09:00:00 GMT</pubDate>
      <category>Health &amp; insurance</category>
      <description>Someone reminded of an appointment does not need to call to confirm it. Someone who can move it with a reply does not need to call either. Proactive service starts with that simple logic.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Forecasting with events: holidays, campaigns, outages</title>
      <link>https://univerx.ai/en/blog/forecasting-with-events</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/forecasting-with-events</guid>
      <pubDate>Sat, 31 Oct 2026 09:00:00 GMT</pubDate>
      <category>Workforce</category>
      <description>The past is a good guide as long as the future resembles it. For every other day, a forecast needs events.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Reviewing claims and benefit documents: where document intelligence helps</title>
      <link>https://univerx.ai/en/blog/claims-documents-review</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/claims-documents-review</guid>
      <pubDate>Sat, 31 Oct 2026 09:00:00 GMT</pubDate>
      <category>Health &amp; insurance</category>
      <description>Many checks are reading and comparing. Others are weighing up. Document intelligence helps with the first and leaves the second where it belongs.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Shift swaps as self-service: rules that relieve both sides</title>
      <link>https://univerx.ai/en/blog/shift-swaps-self-service</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/shift-swaps-self-service</guid>
      <pubDate>Sat, 31 Oct 2026 09:00:00 GMT</pubDate>
      <category>Workforce</category>
      <description>A swap by word of mouth is fast but risky. A swap by formal request is safe but slow. With clear rules, you get both.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>The EU AI Act in customer service: transparency duties, explained briefly</title>
      <link>https://univerx.ai/en/blog/ai-act-transparency-duties</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/ai-act-transparency-duties</guid>
      <pubDate>Sat, 31 Oct 2026 09:00:00 GMT</pubDate>
      <category>Europe &amp; regulation</category>
      <description>Article 50 of the AI Act is short, yet it affects almost every customer service operation that uses AI. What it says, and what follows for bots and assistance.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>The online ID card in customer contact: what works today</title>
      <link>https://univerx.ai/en/blog/online-id-in-customer-contact</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/online-id-in-customer-contact</guid>
      <pubDate>Sat, 31 Oct 2026 09:00:00 GMT</pubDate>
      <category>Europe &amp; regulation</category>
      <description>ID copies, selfies, callbacks to the number on file: identification is often the slowest part of a request. With the online ID card it becomes one step in the conversation.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Callback instead of hold: a small switch with a big effect</title>
      <link>https://univerx.ai/en/blog/callback-instead-of-hold</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/callback-instead-of-hold</guid>
      <pubDate>Fri, 30 Oct 2026 09:00:00 GMT</pubDate>
      <category>Contact centre</category>
      <description>Waiting is unavoidable when more people call than there are seats staffed. Your customers do not have to stay on the line while they wait.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Citizen service without broken hand-offs: what has to come together</title>
      <link>https://univerx.ai/en/blog/citizen-service-without-media-breaks</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/citizen-service-without-media-breaks</guid>
      <pubDate>Fri, 30 Oct 2026 09:00:00 GMT</pubDate>
      <category>Public sector</category>
      <description>Broken hand-offs rarely happen in the portal. They happen at the handovers. Four building blocks close them: identity, shared view, signature and case.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Disclosing AI without breaking the conversation</title>
      <link>https://univerx.ai/en/blog/disclosing-ai-in-dialogue</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/disclosing-ai-in-dialogue</guid>
      <pubDate>Fri, 30 Oct 2026 09:00:00 GMT</pubDate>
      <category>AI in customer service</category>
      <description>A disclosure has to be clear, but it does not have to read like a package insert. A few rules for text, voice and the switch to a person.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>One queue for every channel: what changes day to day</title>
      <link>https://univerx.ai/en/blog/one-queue-every-channel</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/one-queue-every-channel</guid>
      <pubDate>Fri, 30 Oct 2026 09:00:00 GMT</pubDate>
      <category>Contact centre</category>
      <description>Separate teams for each channel look tidy, until a customer switches channel. What changes when everything runs into one queue.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Social data protection in the contact centre: roles, recording, analytics</title>
      <link>https://univerx.ai/en/blog/social-data-protection-contact-center</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/social-data-protection-contact-center</guid>
      <pubDate>Fri, 30 Oct 2026 09:00:00 GMT</pubDate>
      <category>Public sector</category>
      <description>Social data needs more than a tick in the privacy notice. It needs roles that fit, recording with a reason, and analytics that show topics rather than people.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
    <item>
      <title>Why the handover decides: AI agents and context</title>
      <link>https://univerx.ai/en/blog/ai-agent-handover-context</link>
      <guid isPermaLink="true">https://univerx.ai/en/blog/ai-agent-handover-context</guid>
      <pubDate>Fri, 30 Oct 2026 09:00:00 GMT</pubDate>
      <category>AI in customer service</category>
      <description>The most delicate moment in an automated conversation is not the hard question. It is the switch to a human. Plan it, and neither side has to repeat itself.</description>
      <dc:creator>Univerx editorial team</dc:creator>
    </item>
  </channel>
</rss>
