Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://social.linux.pizza/@bigTanuki" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>bigTanuki</span></a></span> <span class="h-card" translate="no"><a href="https://social.coop/@BillySmith" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BillySmith</span></a></span> I'm convinced <span class="h-card" translate="no"><a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>frameworkcomputer</span></a></span> uses <a href="https://infosec.space/tags/GoogleForms" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GoogleForms</span></a> not as a sole tool, but merely <a href="https://infosec.space/tags/ingress" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ingress</span></a> pipeline for their <a href="https://infosec.space/tags/support" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>support</span></a> workflows, so there is like demand to design a whole workflow and architecture from the ground up to handle and process supoort queries.</p><ul><li>Personally I wished for something like <a href="https://infosec.space/tags/HubSpot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HubSpot</span></a> or <a href="https://infosec.space/tags/JiraServiceDesk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>JiraServiceDesk</span></a> as tools like <a href="https://infosec.space/tags/OTRS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OTRS</span></a> are not easy.</li></ul><p>Maybe someone will enhineer somethibg aroubd <a href="https://infosec.space/tags/Gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Gitlab</span></a> or <a href="https://infosec.space/tags/Girea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Girea</span></a>'s <a href="https://infosec.space/tags/issue" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>issue</span></a> <a href="https://infosec.space/tags/Ticketing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ticketing</span></a> system?</p><p>I am however shure something like a customer chat can be done with like <a href="https://infosec.space/tags/Zulip" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Zulip</span></a> and for <a href="https://infosec.space/tags/RemoteDesktop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RemoteDesktop</span></a>-based <a href="https://infosec.space/tags/TechSupport" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechSupport</span></a> there's an excellent tool called <em>"<a href="https://infosec.space/tags/Dayon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Dayon</span></a>!"</em> which is super easy to use for the support-requesting side, doesn't rely on centralized services being available and only needs a few settings by the supporter to get up and running...</p><ul><li>If I were running my own company, I'd propably sponsor the development of Dayon to the same amount as it would cost to pay for AnyDesk instead!</li></ul>