Desklane – Self-hosted AI Help Desk with Tickets, Live Chat, Knowledge Base and Email to Ticket

Tickets, a public help center, an AI chat widget that answers only from your own articles, live chat with your team and email to ticket. A PHP script you install on your own server, with your own AI key and no monthly fee.

 

Desklane is a help desk you install on your own server. Your customers find answers in a help center, ask an AI chat that answers only from your own help articles, talk to your team in a live chat or send a request that becomes a ticket – by the contact page or by email. Your team answers every ticket in one place, with the AI to draft and translate replies, and there is no monthly fee and no limit on agents, tickets or chats.

The AI uses your own key (OpenAI, Anthropic, Google Gemini or an OpenAI-compatible service such as Mistral, Groq, OpenRouter or a local Ollama): you pay the provider for what you use. Without a key, everything still works: the chat shows the help articles that match the question. When the AI does not know, it says so and offers “Talk to a person”.

Features

– Tickets: conversation with internal notes and private files, departments, tags, priorities, saved replies, assignment, views (mine, unassigned, waiting for us, first reply late, waiting for the customer, solved), search and email notifications
– Customers: public contact page with a spam trap, a private link for each request, a customer portal with sign-in by email link (no password)
– Knowledge base: Markdown articles with pictures, categories, team-only articles, public help center with search, related articles, “Was this article helpful?” votes and a sitemap
– Article suggestions while the customer types the subject of a request
– AI chat widget for any website (one script tag, allowed sites only): answers from your published articles only, shows its sources, hands over to a person or a ticket
– AI safety: instructions written by visitors are never followed; emails, phone and card numbers and IBANs are masked before anything is sent; a daily cap on AI calls
– AI in tickets: draft a reply, make it clearer, friendlier, shorter or more formal, fix the spelling, translate into the customer’s language, summarize a ticket, draft a help article from a solved ticket (a person always reads and sends)
– Live chat: available team members take chats, take over from the AI, transfer, close or turn a chat into a ticket
– Email to ticket: IMAP mailboxes (no PHP imap extension needed), pipe forwarding or an email service; replies thread into their ticket; auto-replies, mailing lists and loops ignored
– Automations: opening hours and a first-reply target, assignment in turn, if/then rules, a satisfaction survey, and alerts in Slack, Discord or Telegram
– Purchase checks for sellers: Envato purchase codes or your own licence server, with the end of support shown on the ticket
– Reports: volume, first reply and resolution times, target met, satisfaction, team, chat and AI, and the questions the AI could not answer
– Team roles (owner, admin, agent, viewer), two-factor sign-in, an activity log, signed webhooks (Zapier, Make, n8n), dark mode; admin and customer pages in English, French, Spanish, German, Portuguese and Tagalog
– Web installer, MySQL / MariaDB or SQLite, cron by command or URL, one-click updates from a zip with an automatic backup first

Requirements

– PHP 8.3 or later (pdo, mbstring, openssl, curl, json, tokenizer, xml, ctype, fileinfo, zip, iconv)
– MySQL 8 / MariaDB 10.6+ (an empty database), or SQLite (no database server needed)
– A domain or subdomain with HTTPS; any PHP host, shared hosting included
– A cron job every minute (command line or web cron)
– Optional: an API key of an AI provider, billed by that provider; an email account (SMTP) to send emails, and IMAP to receive them as tickets

About the AI: answers come from your help articles and can still be incomplete or wrong, so the widget says so under every answer and offers a person.

Live demo: https://demos.alulethmarketing.com/desklane/
Documentation: https://market.alulethmarketing.com/docs/desklane/

Changelog:

Desklane 0.1.4 – self-hosted AI help desk (PHP script, Laravel)

= 0.1.4 – 18 November 2026 =
* Email to ticket (app/Services/Inbound.php): an email is acknowledged only once it is done. Inbound::receive() now returns "pending" when another attempt holds the claim and "duplicate" only when an earlier attempt completed it. The webhook answers 503 with Retry-After for pending emails (200 only for final results), the pipe command exits 75 (EX_TEMPFAIL, the mail server keeps the email and retries, no bounce), and an IMAP message is marked read or deleted only for a final result (Inbound::handleMessages); pending and failed messages stay unread. Each claim has a random ownership token (new column inbound_emails.claim_token): the takeover of a stale claim writes a new token, the transaction first locks the claim and checks the token, and completing or giving back a claim is a conditional UPDATE/DELETE on that token. An attempt whose claim was taken over stops (ClaimLost), rolls back and keeps no ticket, reply, file or notification.
* Web server (.htaccess files, INSTALL.md "Web server", app/Support/Exposure.php): the root .htaccess (document root = Desklane folder) now refuses everything when mod_rewrite is missing, and refuses .env, database files, logs, archives and tool files by name; app, bootstrap, config, database, lang, resources, routes, storage and vendor each have a deny .htaccess (Apache 2.4 and 2.2 syntax). When the document root is not "public", the installer requests a random probe file in storage/, .env, vendor/composer/installed.json and a storage listing over HTTP and refuses to install if any comes back (DESKLANE_SKIP_EXPOSURE_CHECK=true only after a manual check). Supported setups are documented: any server with "public" as the document root (with an Nginx server block), and Apache 2.4 with AllowOverride All and mod_rewrite; servers that ignore .htaccess with another document root are documented as not supported. Installations updated from an earlier version get storage/.htaccess on their first page after the update.
* Installer (app/Http/Controllers/InstallController.php, app/Support/Setup.php): the form requires a setup key that only the deployer can read: DESKLANE_SETUP_KEY in .env, or a random key written once to storage/app/setup-key.txt (mode 600; also printed by php artisan desklane:setup-key). Installations are serialized with an exclusive lock on storage/app/install.lock (and the installed marker is checked again under the lock). A state file records the database and the tables present before the run; a run that stopped half-way can be sent again on the same database: it drops only the tables that run created, then migrates again. Before closing, the installer checks that every migration ran, that exactly one owner account exists and that the settings were saved; the installed marker is then written atomically and the setup key and state are deleted.
* Updates (app/Services/Updater.php, app/Support/AutoMigrate.php, bootstrap/recovery.php, bootstrap/update-guard.php, bootstrap/recover.php): updates are serialized with an exclusive lock on storage/app/updates/update.lock. The complete release is extracted and compared with the zip (every file, size) before anything changes. The backup zip now holds every file replaced, vendor/ included, and is read back; a journal (storage/app/updates/journal.json) records the steps and the files new in this release. Files are written next to their target and renamed. On the next request the new release writes a snapshot of every table (structure and rows, storage/app/updates/database-*.json.gz, read back) before running its migrations. If a copy fails, a migration fails, or the process stops at any step, the update is undone: files from the backup (new files removed) and, from the migration step on, every table from the snapshot. A plain-PHP guard included before the Composer autoloader in public/index.php and artisan undoes an interrupted update before mixed code is loaded, and answers 503 "being updated" while an update holds the lock. php bootstrap/recover.php undoes an unfinished update by hand; --database restores a snapshot. INSTALL.md documents the backup contents and the manual recovery. The update to 0.1.4 itself runs with the updater of the installed version; these protections apply from 0.1.4 on.
* AI (app/Services/Ai/Answerer.php, app/Support/Pii.php): a provider reply is shown as an answer only when its SOURCES line names at least one of the articles it was given; replies with no or only invalid references fall back to the matching articles (and "Talk to a person"). Masking now also covers IBANs in any case and grouping (mod-97 check), card numbers with spaces, dashes or dots (Luhn check), phone numbers with slashes, emails with non-Latin letters or written "name [at] domain [dot] com", and lists of numbers on one line (each match is searched again until nothing changes). The admin, INSTALL.md and the listing now describe the prompt rules and the pattern-based masking as safeguards with limits.
* Live chat (public/js/live.js): the queue keeps one button per conversation (keyed by its id) and updates its texts in place on each 3-second refresh, so keyboard focus stays on it, also when it moves to another queue. When the focused conversation leaves, focus goes to its neighbour in the same queue, then to the first conversation shown, then to the "I am available for chats" switch.

= 0.1.3 – 18 November 2026 =
* Live chat to ticket: LiveChat::toTicket() is now one atomic unit (Atomic::run). It locks and re-reads the chat row (lockForUpdate on MySQL/MariaDB, the write lock on SQLite), checks ticket_id again, and creates the ticket, its first message and the chat's link to it in the same transaction. A request that finds the chat already converted returns that ticket, so the widget sent twice, or the visitor and a team member at the same moment, all get the same ticket. The customer and team emails, alerts and webhook events are still sent once, after the commit. A conversion that fails half-way is rolled back completely and sends nothing. The widget answer now includes the ticket number.

= 0.1.2 – 17 November 2026 =
* AI and personal data: masking of emails, phone numbers, card numbers and IBANs now runs at one final boundary (AiClient::prepare()), on the whole request just before it is sent to OpenAI, Anthropic, Gemini or an OpenAI-compatible service. It now covers the titles and passages of the help articles quoted to the AI (public and team-only ones), the AI notes and every message, in chat answers and ticket drafts alike. Stored articles and tickets keep their original text.
* AI daily cap: each billable request reserves a slot of "Most AI calls per day" with one atomic conditional UPDATE (new ai_quota table) before it is sent, so concurrent requests can no longer go over the cap. The chat widget and the AI in tickets share the same counter. A slot is given back only when the provider was never reached (DNS, connection refused) or refused the request at once (HTTP 401, 403, 404, 429); answers, errors, timeouts and interrupted calls keep it. Calls already made today before the update still count.
* Email to ticket: each email is claimed by its Message-ID (or a SHA-256 of the raw email when it has none) with a unique INSERT before anything is written. The ticket or reply, its attachments and the email's final status are saved in one transaction; team and customer emails, alerts and webhook events are sent after it commits. If handling fails, everything is rolled back, stored files are removed, the claim is freed and the error is returned (HTTP 500 for an email service, unread for IMAP) so the email is received again. A claim left by a stopped attempt shows as "Being handled" and is taken over after 15 minutes.

= 0.1.1 – 16 November 2026 =
* Package: public/js/quote-editor.js and public/js/sign.js, two script files of another product (a document editor and a signature pad) shipped by mistake, are removed, with their unused styles in desklane.css and two unused helper classes (App\Support\Csv, App\Support\Countries). No Desklane page loaded them.
* The unused "webhooks/*" CSRF exemption and the unused room for payment-service hosts in the Content Security Policy are removed. Only the chat widget and the email service post without a session, as before.
* Demo mode: the unused "company.online" entry is removed from the list of actions locked in the live demo.

= 0.1.0 – 15 November 2026 =
* First release on WPBay. This marketplace copy has no licence check: updates are installed from the new zip (Licence & updates > Update from a zip), with an automatic backup first.
* Tickets: conversation with internal notes and private files, departments, tags, priorities, saved replies, assignment, views (mine, unassigned, waiting for us, first reply late, waiting for the customer, solved, closed), search, emails to the customer and the team.
* Customers: contact page with a spam trap, a private link for each request, a customer portal with sign-in by email link (no password).
* Knowledge base and help center: Markdown articles with pictures, categories, team-only articles, a search that ignores accents and finds words while they are typed, "Was this article helpful?" votes, a sitemap, and article suggestions while a customer writes.
* AI with your own OpenAI, Anthropic, Gemini or OpenAI-compatible key: a chat widget for any site that answers only from your articles and shows its sources, visitor text never taken as instructions, personal data masked, a daily cap; without a key the chat shows the matching articles. In tickets: draft, improve or translate a reply, summarize a ticket, draft a help article from a solved ticket.
* Live chat: available team members take chats, take over from the AI, transfer, close or turn them into tickets.
* Email to ticket: IMAP mailboxes (no PHP imap extension needed), pipe or an email service; replies thread into their ticket; auto-replies, mailing lists and loops ignored.
* Automations: opening hours and a first-reply target, assignment in turn, if/then rules, a satisfaction survey, Slack / Discord / Telegram alerts, purchase checks with Envato codes or your own licence server.
* Reports: volume, reply and resolution times, target met, satisfaction, team, chat and AI, questions the AI could not answer.
* Base: web installer (MySQL / MariaDB or SQLite), roles (owner, admin, agent, viewer), two-factor sign-in, signed webhooks, activity log, cron by command or URL, 6 languages (English, French, Spanish, German, Portuguese, Tagalog).

Reviews

There are no reviews yet.

Only logged in customers who have purchased this product may leave a review.

Loading...
WPBay support Support by Aluleth

Aluleth supports this product through WPBay

Questions are handled in WPBay's private ticket system, keeping your purchase details and support conversation together.

Go to My Downloads

After purchase, open this item in My Downloads and choose Get Support.

What support includes

  • Answers to product-related questions
  • Help with reported bugs and issues
  • Guidance for included third-party assets

What support does not include

  • Customizations or new features
  • Installation or setup services
Script

Maintenance snapshot

See recent updates, compatibility, support, and developer activity.

  • Updated 1 day ago
  • Developer active recently
  • WPBay support available
  • Documentation available

Snapshot updated 7 hours ago

View details Hide details

Maintenance details

This is maintenance data. It does not measure product quality or sales.

  • Last update Updated 1 day ago
  • Compatibility Not used for scripts
  • Releases 5 releases in the 4 days since listing
  • Developer activity Developer active recently
  • Support No recent support tickets to measure
  • Docs and demo Documentation available · Changelog available · Demo available
How this snapshot works

Script Health

The score is out of 100 and uses data WPBay can check. Ratings, popularity, and sales are not used.

Last update 35 points

Scripts receive full recency points under 45 days, then step down at 120, 240, 365, and 545 days.

Compatibility Not scored

Scripts do not use WordPress or PHP, so compatibility is not scored.

Releases 20 points

One release earns 14, two or three earn 18, and four or more earn 20. Each accepted product ZIP counts once; reprocessing the same upload and listing-only edits do not count.

Developer activity 20 points

Based on WPBay login and dashboard activity. Exact last-login dates are never shown.

Support 15 points

There are no recent WPBay tickets to measure.

Docs and demo 10 points

Documentation: 3. Changelog: 1. Working demo or preview: 6.

Score ranges

  • 90–100 Excellent
  • 75–89 Healthy
  • 60–74 Fair
  • 40–59 Needs attention
  • 0–39 Limited

Long gaps

WPBay also checks for long gaps between updates, developer activity, support replies, and releases. Buyers do not see this score.

  • Time since update 45 points
  • Last developer activity 30 points
  • WordPress compatibility Not scored
  • Support replies 15 points
  • Fewer releases 10 points

Pricing Plans 

$59
1 Site
$179
10 Sites

Prices are in US dollars and exclude taxes

  • Marketplace Pillar
    3
  • Verified Seller
    1
View Store
  • Last Updated 20 Nov 2026
  • Type Script
Compare with similar scripts

© All Rights Reserved - Aluleth
Contact WPBay Market's Help Team