=== SSF Support Desk ===
Contributors: ssfllc
Tags: support, tickets, customer support, helpdesk
Requires at least: 6.6
Tested up to: 7.1
Requires PHP: 8.1
Stable tag: 0.1.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Private text-only customer support tickets with a signed-in portal, administrator queue, replies and conversation export.

== Description ==

SSF Support Desk provides a focused helpdesk inside WordPress. Customers sign in with an existing WordPress account, create a plain-text ticket, see their own conversations and reply. Administrators use a private queue to respond and set open, pending, resolved or closed status.

* Authenticated customer portal using [ssf_support_desk].
* Object-level ticket ownership checks; records are not public posts or REST resources.
* Text-only subjects and messages, with input limits and escaped output.
* Public-conversation JSON export and explicitly confirmed permanent ticket deletion.
* Optional minimal update notices through the site's existing wp_mail configuration; OFF by default.
* Useful locally without AI, a subscription, remote service or a paid add-on.

The separate SSF Support Desk Pro add-on adds assigned support agents, private notes, priorities, target due dates, saved public replies, product/edition labels and scoped queue CSV reporting. Premium implementation code is not included in this Free package.

Do not submit passwords, licence secrets, payment information or sensitive documents in tickets. File attachments, guest access, inbound-email processing, AI, automated licence checks and automatic retention deletion are not provided. Order references in the separate add-on are manual, unverified labels.

== Installation ==

1. Upload and activate the ssf-support-desk folder or its ZIP.
2. Publish a support page containing [ssf_support_desk].
3. Exclude the portal from any page cache; the plugin also sets no-cache/noindex signals on a singular shortcode page.
4. Provision customers using ordinary WordPress accounts. Anonymous visitors must sign in first.
5. Open SSF Support Desk in the administrator menu. Notifications remain off until you explicitly enable and verify delivery.

== Frequently Asked Questions ==

= Does the plugin send data to SSF or an AI service? =
No. There is no telemetry, AI or remote support service. Optional email notices use your site's existing WordPress mail transport and the ticket owner's account email or the site's administrator email. The notices exclude message bodies.

= Is a successful wp_mail result proof of inbox delivery? =
No. Verify your mail transport and actual receipt separately. SSF SMTP Mailer may be used through ordinary WordPress mail hooks; this plugin does not configure or replace SMTP.

= What happens when I deactivate or uninstall? =
Records are retained. Customers and administrators can explicitly delete individual tickets with DELETE confirmation, which also removes messages and notes from the active site database. Backups can retain older data under your backup policy. WordPress privacy-tool integration and retention automation are not included in 0.1.0.

= Are ticket exports complete? =
Customer JSON contains that ticket's public conversation, never private staff notes or private order labels. The queue displays at most the newest 200 accessible records. The separate Pro queue report has the same documented limit.

== Privacy ==

The site stores account IDs, subjects, plain-text messages, status and UTC timestamps in private custom tables. The site owner controls accounts, access, retention, backups and optional email delivery. Publish appropriate privacy/support terms and set a retention process before collecting real customer data. This package does not include document processing, attachments, payment processing or analytics.

== Changelog ==

= 0.1.0 =
* Initial authenticated text-only ticket portal and administrator workflow.

== Upgrade Notice ==

= 0.1.0 =
Initial release. Back up the site before installing and test your support workflow on staging.
