<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Integration on transtorm.ai</title>
		<link>https://transtorm.ai/tags/integration/</link>
		<description>Recent content in Integration on transtorm.ai</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Thu, 08 Oct 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://transtorm.ai/tags/integration/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Agenda Sync</title>
				<link>https://transtorm.ai/usecases/agenda-sync/</link>
				<pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/usecases/agenda-sync/</guid>
				<description>&lt;h2 id=&#34;keep-your-calendars-aligned-without-replacing-your-existing-tools&#34;&gt;Keep your calendars aligned, without replacing your existing tools&lt;/h2&gt;&#xA;&lt;p&gt;In many medical organizations, patient appointments are managed in a legacy business software, while teams use Google Calendar to organize their daily routine: meetings, leaves, on-call shifts, availability, or external interventions.&lt;/p&gt;&#xA;&lt;p&gt;In the field, this separation quickly creates friction: slots blocked on one side but not the other, double bookings, oversights, manual corrections, and wasted time for teams.&lt;/p&gt;&#xA;&lt;p&gt;&lt;span class=&#34;gradient-wave&#34;&gt;transtorm.ai&lt;/span&gt; designs calendar synchronization solutions that connect your existing systems to Google Calendar in a reliable, secure, and traceable way.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Telegram Assistant</title>
				<link>https://transtorm.ai/usecases/telegram-bot/</link>
				<pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/usecases/telegram-bot/</guid>
				<description>&lt;h2 id=&#34;offer-quick-answers-on-telegram-without-overloading-your-teams&#34;&gt;Offer quick answers on Telegram, without overloading your teams&lt;/h2&gt;&#xA;&lt;p&gt;More and more organizations are using instant messaging platforms like Telegram to interact with their patients, customers, or partners.&lt;br&gt;&#xA;Users expect simple, fast, and accessible answers: opening hours, appointments, follow-ups, procedures, rescheduling, or practical information.&lt;/p&gt;&#xA;&lt;p&gt;Without automation, these requests quickly pile up. Teams then spend a large part of their time answering the same questions, at the expense of more complex, sensitive, or high-value cases.&lt;/p&gt;</description>
			</item>
			<item>
				<title>How a Reception Kiosk Builds the Clinical Worklist Itself</title>
				<link>https://transtorm.ai/blog/patient-check-in-kiosk-automated-worklist/</link>
				<pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://transtorm.ai/blog/patient-check-in-kiosk-automated-worklist/</guid>
				<description>How a patient check-in kiosk for an ophthalmology practice goes beyond mere registration: it identifies the patient, infers the consultation type from the last follow-up, and automatically creates the worklist item in the patient record, with a mobile companion, secured by physical presence, on which patients can see how late their doctor is likely to be running, self-hosted and GDPR-friendly. A comparison with Phreesia, Clearwave, Qmatic and the patient kiosk market.</description>
			</item>
	</channel>
</rss>
