<?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>DEV Community: Rawan Tattan</title>
    <description>The latest articles on DEV Community by Rawan Tattan (@rawan_tattan).</description>
    <link>https://dev.to/rawan_tattan</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3985066%2F91832b5d-5f81-431c-bb84-1c1418e1a4dc.png</url>
      <title>DEV Community: Rawan Tattan</title>
      <link>https://dev.to/rawan_tattan</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rawan_tattan"/>
    <language>en</language>
    <item>
      <title>Wrote about why we built ARK a unified inbox for customer support across WhatsApp, Instagram, email, and live chat, with AI handling the busywork. Would love feedback from anyone managing multichannel support!</title>
      <dc:creator>Rawan Tattan</dc:creator>
      <pubDate>Mon, 15 Jun 2026 10:09:42 +0000</pubDate>
      <link>https://dev.to/rawan_tattan/wrote-about-why-we-built-ark-a-unified-inbox-for-customer-support-across-whatsapp-instagram-5hli</link>
      <guid>https://dev.to/rawan_tattan/wrote-about-why-we-built-ark-a-unified-inbox-for-customer-support-across-whatsapp-instagram-5hli</guid>
      <description>&lt;div class="crayons-card c-embed text-styles text-styles--secondary"&gt;
    &lt;div class="c-embed__content"&gt;
        &lt;div class="c-embed__cover"&gt;
          &lt;a href="https://dev.to/rawan_tattan/we-built-ark-because-our-customer-support-was-spread-across-4-apps-4k7e" class="c-link align-middle" rel="noopener noreferrer"&gt;
            &lt;img alt="" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8o6gwvbknqt6psnofmnz.png" height="418" class="m-0" width="800"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="c-embed__body"&gt;
        &lt;h2 class="fs-xl lh-tight"&gt;
          &lt;a href="https://dev.to/rawan_tattan/we-built-ark-because-our-customer-support-was-spread-across-4-apps-4k7e" rel="noopener noreferrer" class="c-link"&gt;
            We Built ARK Because Our Customer Support Was Spread Across 4 Apps - DEV Community
          &lt;/a&gt;
        &lt;/h2&gt;
          &lt;p class="truncate-at-3"&gt;
            We Built ARK Because Our Customer Support Was Spread Across 4 Apps The Problem A few months ago, our...
          &lt;/p&gt;
        &lt;div class="color-secondary fs-s flex items-center"&gt;
            &lt;img alt="favicon" class="c-embed__favicon m-0 mr-2 radius-0" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8j7kvp660rqzt99zui8e.png" width="300" height="299"&gt;
          dev.to
        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
&lt;/div&gt;


</description>
      <category>ai</category>
      <category>discuss</category>
      <category>saas</category>
      <category>showdev</category>
    </item>
    <item>
      <title>We Built ARK Because Our Customer Support Was Spread Across 4 Apps</title>
      <dc:creator>Rawan Tattan</dc:creator>
      <pubDate>Mon, 15 Jun 2026 09:56:44 +0000</pubDate>
      <link>https://dev.to/rawan_tattan/we-built-ark-because-our-customer-support-was-spread-across-4-apps-4k7e</link>
      <guid>https://dev.to/rawan_tattan/we-built-ark-because-our-customer-support-was-spread-across-4-apps-4k7e</guid>
      <description>&lt;p&gt;We Built ARK Because Our Customer Support Was Spread Across 4 Apps&lt;br&gt;
The Problem&lt;br&gt;
A few months ago, our small team was drowning. Not in customers (well, a little) but in tabs.&lt;br&gt;
WhatsApp open in one window. Instagram DMs in another. A live chat widget buried in a third. Email in a fourth. Every time a customer reached out, someone had to figure out: which channel did this come from, has anyone replied already, and what was the context of the last conversation?&lt;br&gt;
The result was predictable: slower replies, repeated questions to customers, and a support workflow that didn't scale past a handful of conversations a day.&lt;br&gt;
Why Existing Tools Didn't Fit&lt;br&gt;
We looked at the usual suspects Intercom, Zendesk, Front. They're solid products, but they're built for large support teams with big budgets and dedicated admins. We needed something simpler: a single inbox, AI doing the repetitive work, and a setup that doesn't take weeks to configure.&lt;br&gt;
What We Built&lt;br&gt;
ARK pulls every customer conversation  WhatsApp, Instagram, Messenger, email, live chat  into one inbox. On top of that, AI handles three things:&lt;/p&gt;

&lt;p&gt;Drafting replies based on conversation history and context&lt;br&gt;
Summarizing long threads so anyone on the team can jump in without reading 40 messages&lt;br&gt;
Routing conversations to the right person automatically based on topic or channel&lt;/p&gt;

&lt;p&gt;The goal wasn't to replace human support it was to remove the busywork so the team can focus on actually helping people.&lt;br&gt;
Where We Are Now&lt;br&gt;
ARK is live with a 7-day free trial (auto-renews after that).  we're shaping the roadmap based on real feedback from teams managing support across multiple channels.&lt;br&gt;
If you're dealing with the same multichannel chaos we were, I'd love to hear how you're handling it — and what's still missing from the tools you've tried.&lt;br&gt;
🔗&lt;a href="https://byark.ai/" rel="noopener noreferrer"&gt;https://byark.ai/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>saas</category>
      <category>showdev</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
