Automations for Albato

Albato is a similar tool to Zapier and was an AppsSumoDeal like Charla. Adding some basic Automations here like in Zapier would be great thing.

Better Link Highlighting

If the Chatbot provides links, these are not good to recognice. Make it bold, darker, or underline in the normal state.

Global Owner functions

As Charla Owner /Agency, I want to have the ability to change all options for my client accounts (like user image) or clients chatbots. At the same time I don’t want to be visible as agent in my clients properties.

Embed Booking Form (e.g., Calendly, TidyCal)

Request: Allow embedding booking calendar within the chat via iframe perhaps? Please see sample attachment. This will increase conversions by a mile! Use cases for e.g., coaching, agency, tech businesses that require consultation or demo meetings. Additional Request: Since Charla

Multiple User Account Logins on Mobile App

Use case for small businesses and solo entrepreneur: For one-person businesses (who doesn’t want to appear as a one-person team) or small teams wearing multiple hats per person, I want to be able to create e.g., 3 agents (or “skins”

Spam Filter to Prevent Junk Emails from Creating Tickets

The Problem: A significant number of spam emails are automatically creating support tickets, which clutters up our ticket queue. This makes it harder to find and respond to legitimate customer issues and forces our team to spend valuable time manually

Improved Website Scraping

Since my chatbot does not successfully train on any of my site pages with the /example subdomain for the page entered, can this functionality be improved? It is possible that the issue might be that the pages are not SSR.

SEO-friendly Knowledge Base with Custom Subdomain (CNAME) + Pre-rendering

Please add an SEO-friendly publishing option for the Knowledge Base. Today it’s only available as a JS embed that renders client-side, so search engines see an empty shell and can’t index articles. This blocks organic discovery, rich results, and clean,

Enhanced Ticket Status Policy

The Problem The current two-status system (“Open” and “Closed”) is inefficient. It makes it difficult for clients and managers to track which tickets are truly resolved versus which are awaiting a response. Marking a ticket “Closed” when the issue isn’t

Viber Integration

To support Viber Chat where Whatsapp not avaliable.