=== Aluleth Support ===
Contributors: aluleth
Tags: helpdesk, support ticket, live chat, knowledge base, ai chatbot
Requires at least: 7.0
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 0.1.11
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Helpdesk for WordPress: a shared inbox of tickets, a customer portal, a help center and a chat with an AI assistant that only answers from your pages.

== Description ==

Aluleth Support gives your customers one place to ask for help, and your team one inbox to answer them. Everything stays in your WordPress database.

**The inbox**

* Every request as a ticket: who asked, the product, the status (open, waiting for the customer, solved), the priority and who takes care of it.
* Views for "Mine", "Unassigned", "Handed over by the assistant", "First reply due soon", "Waiting for the customer", "All open" and "Solved", plus one per product, and a search on the subject, the email and the messages.
* A goal for the first answer (4 hours by default), counted in your business hours: the inbox shows what is late or due soon.
* Answer the customer (simple HTML is fine: links, bold, lists) or leave an internal note that the customer never sees. Saved replies for the questions that come back.
* Attach files to an answer. Files are kept in a form no web server can send (on Apache, Nginx or any other) and are only sent by the plugin, to the team and to the customer of the ticket (files of internal notes to the team only).
* The customer's contact details and other tickets beside the conversation.
* Team members do not need to be administrators: give them the "Support" access in Aluleth › Settings › Access.

**The customer portal**

* One block (or the `[aluleth_support_portal]` shortcode): the request form, and for signed-in customers the list of their requests.
* Visitors without an account send a request with their email and get a private link by email to follow it. Until they open it, the ticket shows that their address is not confirmed yet. You can also accept requests from signed-in customers only.
* While the customer types the subject, help articles that may answer the question are shown.
* Customers answer in the portal or with the link of the email, add files and rate the answer once the request is solved.
* Spam is kept out with a hidden field, a time check, a limit per connection and, if you set one in Aluleth › Settings › Security, Cloudflare Turnstile, hCaptcha, Google reCAPTCHA, CleanTalk or Akismet.

**The help center**

* Help articles with topics, a "Help center" block with a search box, and "Was this helpful?" votes at the end of each article.
* The articles list shows the share of "yes" votes of each article and how often the assistant used it.

**Elementor**

* "Support portal" and "Help center" widgets in the Aluleth category of Elementor, with Style controls for the colours (also your global colours), text, buttons, corners and width. Without Elementor, use the blocks or the shortcodes.

**Moving from another help desk**

* Support › Settings › Import copies the tickets of Fluent Support, SupportCandy or Awesome Support found on this site: replies, internal notes, attachments, dates, status, priority, product (or category) and agent. You choose what each of their statuses becomes.
* Nothing is sent to your customers and nothing is changed in the other help desk; its plugin can be deactivated, its tickets stay in the database. Big help desks are copied in small steps, also when you leave the page, and an import can be undone.

**The chat and its AI assistant**

* A chat button on your site, in your colour, on the left or right, hidden on the pages you choose.
* Quick topics to start the conversation, and a "Talk to a person" button that turns the chat into a ticket with the whole conversation.
* Optional AI assistant: it answers only from the help articles, pages and products you choose, shows its sources, and passes the question to your team when it does not find the answer, or when the customer asks for a refund, is upset or talks about legal matters (you choose).
* It uses the AI provider connected in WordPress (Settings › Connectors); you pay your provider directly. Daily and hourly limits keep the cost under control.
* Without an AI provider the chat still suggests your help articles and sends questions to your team.

**Get started**

* A setup assistant (Aluleth › Get started): emails, the portal and help center pages, then the chat. It never takes over the admin, and every step can be skipped.

**Works with the other Aluleth plugins**

* People who ask for help become contacts, with their tickets on their timeline; Aluleth CRM can start automations from them.
* Any Aluleth Forms form (also when shown in an Aluleth Popups popup) can open tickets: add "Aluleth Support · Open a ticket" in the form's Integrations, choose the product, and the fields that give the subject, the message, the priority or the product. The ticket links back to the entry.

== Installation ==

1. Install and activate the plugin.
2. Open the setup assistant from the Support screen (optional), or go to Aluleth › Support › Settings: set the sender of the emails, make the portal and help center pages, and switch on the chat.
3. To use the AI assistant, connect an AI provider in Settings › Connectors, then switch on the assistant in Aluleth › Support › Settings › AI assistant and choose its sources.

== Frequently Asked Questions ==

= Do I need an AI provider? =

No. Tickets, the portal, the help center and the chat work without one. The assistant only answers when a provider is connected and you switch it on.

= Can the assistant make things up? =

It is told to answer only from the passages of your site that are sent with the question, to cite them, and to pass the question to your team when they do not hold the answer. Like any AI, it can still be wrong, so the chat says that answers come from an AI assistant, and the customer can always talk to a person.

= Do customers need an account? =

No, unless you choose so. Without an account, the customer opens the request with the private link of our emails.

= Can I use it with WooCommerce or FluentCart? =

Yes. The request form can list your products and the assistant can read your product pages and prices. Aluleth Support Pro adds the customer's orders, downloads and licences beside the ticket.

= Can I move from Fluent Support, SupportCandy or Awesome Support? =

Yes, when its tickets are in the database of the same site: Support › Settings › Import. Tickets keep their dates, replies, notes and attachments. Archived tickets of SupportCandy must be restored there first, and attachments kept in cloud storage are not copied.

= Is it GDPR friendly? =

Tickets, chats and files stay in your WordPress database and uploads folder. The personal data export and erase tools of WordPress cover them, and chats are deleted after the number of days you choose (90 by default).

= What happens to my data if I delete the plugin? =

Nothing is deleted unless you asked for it in Aluleth › Settings ("Aluleth Support: tickets, files, chats, help articles and settings").

== External services ==

Aluleth Support sends nothing to us. It connects to the services below only after you set them up.

= AI provider =

Used only when an AI provider is connected in Settings › Connectors (the AI Client of WordPress) and you switch on the assistant in Aluleth › Support › Settings › AI assistant. When a visitor writes in the chat, your site sends the provider: the question, the last messages of the conversation (email addresses, phone and card numbers are hidden first), the address of the page the visitor is on, the passages of your help articles, pages and products that match the question, and the assistant's instructions. The provider sends back the answer. Nothing else is sent, and nothing is sent when the assistant is off or a limit is reached. The provider is the one you connected yourself (for example OpenAI, Anthropic or Google); its terms and privacy policy apply:

* **OpenAI**: [Terms of use](https://openai.com/policies/terms-of-use/), [Privacy policy](https://openai.com/policies/privacy-policy/).
* **Anthropic**: [Commercial terms](https://www.anthropic.com/legal/commercial-terms), [Privacy policy](https://www.anthropic.com/legal/privacy).
* **Google (Gemini API)**: [Terms of service](https://ai.google.dev/gemini-api/terms), [Privacy policy](https://policies.google.com/privacy).

= Anti-spam services =

Used only after you paste your own keys in Aluleth › Settings › Security and choose a default service, and only on the request form for visitors who are not signed in (and, for CleanTalk and Akismet, the "Talk to a person" form of the chat).

* **Cloudflare Turnstile** (Cloudflare, Inc.). The visitor's browser loads the Turnstile script from `challenges.cloudflare.com`, which receives the visitor's IP address and browser details. When the form is sent, your site sends the check result and the visitor's IP address to `challenges.cloudflare.com/turnstile/v0/siteverify`. [Terms of use](https://www.cloudflare.com/website-terms/), [Privacy policy](https://www.cloudflare.com/privacypolicy/), [Turnstile privacy addendum](https://www.cloudflare.com/turnstile-privacy-policy/).
* **hCaptcha** (Intuition Machines, Inc.). The visitor's browser loads the script from `js.hcaptcha.com`, which receives the visitor's IP address and browser details. When the form is sent, your site sends the check result and the visitor's IP address to `api.hcaptcha.com/siteverify`. [Terms of service](https://www.hcaptcha.com/terms), [Privacy policy](https://www.hcaptcha.com/privacy).
* **Google reCAPTCHA** (Google LLC). The visitor's browser loads the script from `www.google.com/recaptcha`, which receives the visitor's IP address, browser details and how they use the page. When the form is sent, your site sends the check result and the visitor's IP address to `www.google.com/recaptcha/api/siteverify`. [Terms of service](https://policies.google.com/terms), [Privacy policy](https://policies.google.com/privacy).
* **CleanTalk** (CleanTalk Inc.). No script is added to your pages. When a request is sent, your site sends the email address, the name, the message and the visitor's IP address and browser to `moderate.cleantalk.org`. [Terms of service](https://cleantalk.org/publicoffer), [Privacy policy](https://cleantalk.org/privacy).
* **Akismet** (Automattic Inc.), only when the Akismet plugin is active and connected on your site and you choose it. When a request is sent, your site sends the name, email address, message, the visitor's IP address and browser to Akismet through the Akismet plugin. [Terms of service](https://akismet.com/tos/), [Privacy policy](https://automattic.com/privacy/).

== Privacy ==

Tickets, messages, files and chats are kept in your WordPress database and in the `aluleth-support` folder of your uploads, where files are stored so that no web server can send them. People who ask for help become contacts in your own database. The chat keeps the number of the conversation and a random key in the visitor's browser (local storage `alsp_chat`), so the conversation comes back on the next page; your site keeps the conversation and only a fingerprint of that key. To limit spam, the plugin keeps short-lived, one-way fingerprints of the visitor's network (10 minutes for forms and the chat, one hour for the assistant, one day for article votes) and of the email addresses that requests were sent for (one hour). IP addresses themselves are not stored. Chats are deleted after the number of days set in Aluleth › Support › Settings › Privacy. The personal data export and erase tools of WordPress cover tickets and chats; the plugin adds a suggested text to your privacy policy guide. See External services for what is sent when the AI assistant or an anti-spam service is used.

== Screenshots ==

1. The inbox, with the views and the first-answer goal.
2. A ticket, with the conversation, the answer box and the customer's details.
3. The chat on a site, with an answer of the AI assistant and its sources.
4. The customer portal.
5. The AI assistant settings: sources, when to pass to a person, limits.

== Changelog ==

= 0.1.11 =
* Attachments are stored so that no web server can send them, on Nginx too (files of earlier versions are converted on the next admin page). Files of internal notes are sent to the team only.
* The AI assistant's daily and hourly limits hold when many questions arrive at the same moment: each question takes its place before the provider is asked.
* Limits of the forms, the chat, votes and emails per address are counted atomically; votes and counters are added in the database, so none is lost.
* A double click (or two tabs) on "Talk to a person", the request form or a team reply makes one ticket, one reply and one email. Two chat messages sent at the same moment are both kept, and a chat button works once.
* A message that could not be saved is reported (the person is asked to try again) instead of being shown as sent; a ticket is never kept without its first message.
* The same form entry sent twice at the same moment opens one ticket.
* Links of our emails work before a portal page is set (the request opens on a plain page of the site).
* Portal messages are limited to 10,000 characters; ratings to 5 changes an hour.
* Personal data export and erase also cover the requests of the person's account, the names of their files and the chat kept with a request.
* Shared Aluleth core 0.18.6.1 (import files guarded on any server); the PHP mbstring extension is no longer needed.

= 0.1.10 =
* Fix: in Settings › Requests and emails, the opening days showed the day before ("Sun" for Monday) on sites west of UTC. The saved days were right.

= 0.1.9 =
* Import from Fluent Support, SupportCandy and Awesome Support (Support › Settings › Import), with replies, internal notes, attachments, dates, statuses, priorities, products and agents. No email is sent; an import can be stopped and undone.
* Elementor editor: the portal widget shows the request form while editing, also when Elementor draws it again after a change.

= 0.1.8 =
* Elementor widgets "Support portal" and "Help center", with colour, text, button, corner and width controls. A page published with the portal or the help center (block, shortcode or widget) becomes the support or help center page when none is set.
* Buttons and fields of the portal keep their look when the theme or the Elementor kit styles buttons and fields.
* The portal and help center colours, corners and width are CSS variables (--alsp-accent, --alsp-on-accent, --alsp-radius, --alsp-width…), for themes too.

= 0.1.7 =
* Aluleth Forms forms (also in Aluleth Popups popups) can open tickets ("Aluleth Support · Open a ticket" in the form's Integrations), with a link from the ticket to the entry.

= 0.1.6 =
* Fix: a field of the request form meant for another product is now hidden (it was only switched off).
* The product chosen in the request form must be one of the list.
* Hooks for the Pro add-on: the request form's checks know the email address and product, and can show their own message (purchase checks).

= 0.1.5 =
* Hook for the Pro add-on: a customer rated the answer or changed the rating (team alerts on low ratings).
* Faster reports on large sites: indexes on the dates of tickets, messages and chats.

= 0.1.4 =
* Hooks for the Pro add-on: more conditions and marks in the inbox list, more fields in the request form, a note at the top of a request, messages of the Support screens.

= 0.1.3 =
* Hooks for the Pro add-on: more sections in Support › Settings, and the reply email can say customers may answer by email.

= 0.1.2 =
* Chat: messages from a person of the team show with their first name (used by Aluleth Support Pro for live chat), in the chat, the chat history and the ticket.
* Hooks for the Pro add-on: a chat taken by a person (the assistant stays quiet), the chat shown again on another page, new tabs on the Support screen, and a script API for the chat widget.
* A "Resend" form can carry its own confirm text.

= 0.1.1 =
* Chat: answers can carry buttons (used by Aluleth Support Pro for actions such as "Send me my download links").
* Hooks for the Pro add-on: the assistant's answer shape and result, answers before the assistant, settings rows, a ticket history line.

= 0.1.0 =
* First version: inbox, tickets with notes, saved replies and files, customer portal, help center with votes, chat with an optional AI assistant, email notifications, setup assistant, privacy tools.
