Description
Chatwoot Client Portal by ICT Shift connects your WordPress site to Chatwoot. Give customers a familiar place to start conversations, follow ticket updates and contact your team, while agents continue working in Chatwoot.
Use it for customer support, service enquiries and other conversation-based workflows. The included starter flow is written for a general business and can be adapted to your organisation; it is not tied to a particular industry or helpdesk setup.
Key capabilities:
- Customer ticket portal: let logged-in customers view and reply to conversations, follow statuses and exchange attachments.
- Live chat: enable or disable the floating widget, then select either the native Chatwoot widget or the ICT Shift custom widget. Embedded chat shortcodes are configured separately. The custom widget footer includes a “Powered by ICT Shift” link to ictshift.com.
- Visual conversation flow builder: guide conversations with messages, choices, questions, conditions, team actions and hand-offs. Optional support-hours and phone-escalation steps are available for organisations that use them.
- New request forms: add ticket intake forms to pages, including public forms for visitors who are not logged in. Optional hCaptcha protection is available for public forms.
- Chatwoot inbox and webhook sync: keep customer conversations in Chatwoot and display the configured inbox conversations in WordPress.
- Optional customer context sync: connect WordPress profile information and supported WooCommerce, FluentCart, FluentCRM and FluentBoards data.
- Theme and language support: responsive presentation, compatibility with common WordPress themes and translation-ready interface strings.
The plugin connects one WordPress site to one Chatwoot account. Chatwoot cloud and self-hosted instances are supported. Plugin support is available in the WordPress.org support forum; for Chatwoot hosting or implementation services, visit ICT Shift.
Shortcodes:
[ictss_support_tickets]– ticket list view (+ New Ticket button)[ictss_support_ticket]– ticket conversation detail view (?ictss_ticket_id=)[ictss_support_new_ticket]– dedicated new ticket form[ictss_support_live_chat_full][ictss_support_live_chat_box]
Ticket list shortcode
[ictss_support_tickets]
Shows the ticket list only and includes the “+ New Ticket” header button.
Optional ticket list attributes:
new_ticket_url– override the “+ New Ticket” button URLticket_detail_url– override ticket detail page URL
Example:
[ictss_support_tickets new_ticket_url="https://example.com/new-ticket" ticket_detail_url="https://example.com/ticket-details"]
Ticket detail shortcode
[ictss_support_ticket]
Shows a selected ticket conversation using ?ictss_ticket_id= and includes a “Back to My Tickets” button.
Optional ticket detail attributes:
tickets_url– override the back-to-list button URLshow_unassigned_assignee="yes|no"(defaultno) – whenyes, always show Assigned asUnassignedif no agent is set
New ticket shortcode
[ictss_support_new_ticket]
Optional new ticket attributes:
show_attachments="yes|no"(defaultyes)show_priority="yes|no"(defaultno)inbox_id– override the Chatwoot inbox used for ticket creationmail_to– override mail transport recipient(s) for this page onlyrequire_login="yes|no"(defaultyes) – set tonofor public/contact intake pagestickets_url– override the “Back to My Tickets” button URL after successful submitdebug_console="yes|no"(defaultno) – for admins, logs submit diagnostics to browser console (helpful for mail transport troubleshooting)
Examples:
- Support intake:
[ictss_support_new_ticket show_attachments="yes" show_priority="yes"] - Contact intake (public form):
[ictss_support_new_ticket show_attachments="no" show_priority="no" require_login="no"]
When require_login="no", the form is available to non-logged-in visitors. Enable hCaptcha in plugin settings for public intake protection.
Recommended page setup:
- My Tickets page:
[ictss_support_tickets]and[ictss_support_ticket](can be the same page) - New Ticket page:
[ictss_support_new_ticket](can also be a separate page)
Optional URL overrides:
- Ticket list:
new_ticket_url,ticket_detail_url - Ticket detail:
tickets_url(back to list button) - New ticket:
tickets_url(back to list button after successful submit)
After submit, users are informed that a new ticket can take a few minutes to appear in the ticket list.
Theme compatibility notes:
- Supported compatibility targets: Astra, Divi, BeTheme, and default WordPress themes.
- BeTheme compatibility includes field/button normalization for the new-ticket form (including public contact intake pages).
- Divi compatibility includes suppression of inherited hover pseudo-icons on ICTSS buttons in WooCommerce-themed contexts.
Conversation flow builder
The visual builder in Support Portal > Settings > Chat Widget lets you
customise the assistant’s conversation path. The default flow offers a general
help-request branch and a general enquiry branch. Add or remove steps such as
messages, choices, questions, conditions, team notifications and hand-offs.
Support-hours and phone-escalation steps are optional integrations, not
requirements of the starter flow.
The flow is rules-based and follows the steps you configure; it is not a
generative AI chatbot. Existing saved flows are preserved when upgrading.
Floating chat widget
In Support Portal > Settings > Chat Widget, set Enable Floating Widget
to Yes, then choose either Chatwoot widget or ICT Shift custom widget.
Only the selected floating widget loads. Set the enable option to No to hide
the global floating widget. Embedded chat shortcodes are controlled separately.
External Services
This plugin relies on external services for support portal functionality and optional anti-bot verification.
Chatwoot
This plugin connects to a Chatwoot instance to provide support ticket, livechat, contact sync, and webhook functionality. The Chatwoot base URL is configured by the site owner in plugin settings and can point to either a self-hosted Chatwoot server or the Chatwoot cloud service.
- What it is: Chatwoot is an open-source customer support platform. This plugin uses the Chatwoot REST API to sync contacts, create tickets, post replies, and receive webhook events.
- Data sent: contact identity and profile data (name, email, phone, optional custom attributes), conversation and ticket metadata, message content, and optional file attachments.
- When data is sent: when loading the livechat widget/embed, creating support tickets, replying to tickets, syncing contacts, loading debug/API diagnostics, and processing webhook events.
- Browser storage: when the livechat widget or embed is enabled, Chatwoot and optional identity/session-reset flows may use browser cookies and local/session storage to maintain chat session state.
- Service URL: Determined by the Base URL configured in plugin settings (e.g. https://app.chatwoot.com/ for Chatwoot cloud, or a custom domain for self-hosted deployments).
If using Chatwoot cloud (app.chatwoot.com):
- Terms of service: https://www.chatwoot.com/terms-of-service
- Privacy policy: https://www.chatwoot.com/privacy-policy
If using a self-hosted Chatwoot instance:
- The data controller is the operator of that server. The site owner is responsible for ensuring appropriate terms and privacy policies are in place for their own Chatwoot deployment. Chatwoot’s privacy policy and terms of service do not automatically apply to self-hosted instances.
- Chatwoot is open-source (MIT licensed): https://github.com/chatwoot/chatwoot
hCaptcha (optional)
This plugin optionally integrates hCaptcha for anti-spam/bot protection on public ticket and contact intake forms.
- What it is: hCaptcha is a third-party CAPTCHA service. It is only loaded when hCaptcha is explicitly enabled in plugin settings.
- Data sent: a challenge response token and visitor IP address (
remoteip) for server-side verification, and the hCaptcha widget JavaScript for browser-side challenge rendering. - When data is sent: only when hCaptcha is enabled in plugin settings AND a visitor submits a public form that requires CAPTCHA verification.
- Service URL: https://www.hcaptcha.com/
- Terms of service: https://www.hcaptcha.com/terms.html
- Privacy policy: https://www.hcaptcha.com/privacy.html
Site owners are responsible for obtaining any consent required in their jurisdiction before enabling external-service features.
Credits
- Visual conversation flow builder canvas: Drawflow 0.0.60 by Jero Soler, MIT licence (bundled in
assets/vendor/drawflow).
Installation
- Upload the plugin folder to
/wp-content/plugins/. - Activate the plugin through the Plugins screen in WordPress.
- Go to Support Portal > Settings. Clicking Support Portal itself opens Tickets; a decorative divider separates ticket work from administration.
- Configure settings by tab:
- Connection: Chatwoot credentials, inbox IDs and webhook authentication.
- Chat Widget: Widget/embed behaviour, livechat identity and Conversation Flow.
- Customer Portal: Ticket list/detail/new-ticket URLs, reply and submission transport, attachment fallback and hCaptcha.
- Email: Notifications, email signatures and reply-by-email channel.
- Integrations: FluentCRM contact sync, revenue currency prefixes, FluentBoards and telephony.
- Save changes on each tab after editing.
- Add shortcodes to your portal pages.
Use Support Portal > Tools & Diagnostics for scheduled contact sync status, manual batch/full runs, emergency stop and the Debug panel. Settings and tools remain administrator-only; the ticket workspace honours the configured support-agent capability. Existing settings URLs remain valid.
FAQ
Does this plugin require Chatwoot?
Yes. A working Chatwoot instance is required.
Is the default conversation flow limited to IT support?
No. The starter flow uses general wording for help requests and enquiries and
can be edited for your organisation. Optional support-hours and phone-escalation
steps are available in the builder but are not included in the starter flow.
Is the conversation flow an AI chatbot?
No. The visual builder creates a rules-based conversation from the steps and
conditions you configure. It does not generate answers with an AI model.
Can I choose which floating chat widget appears on my site?
Yes. Enable or disable the floating widget, then choose the native Chatwoot
widget or the ICT Shift custom widget under Support Portal > Settings >
Chat Widget. Embedded chat shortcodes are configured separately.
Which channels are supported?
Ticket list/detail relies on configured Chatwoot inbox data, including email and other supported inbox channels. Livechat identity settings apply only to website widget/embed flows.
How do I prevent livechat impersonation?
Enable identity validation in your Chatwoot website inbox and in plugin settings, then use the same shared secret.
Can I sync WooCommerce and FluentCart fields?
Yes. Enable contact sync in plugin settings. The plugin syncs core profile fields and selected commerce attributes when available, including total revenue fields:
– ictss_total_revenue_woo
– ictss_total_revenue_fluentcart
You can also configure revenue display prefix in Support Portal > Settings > Integrations using Show Currency Prefix for Revenue and Revenue Currency Prefix (for example: EUR, $, USD).
How can I still expose extra customer context in Chatwoot contact records?
The plugin stores fallback context in Chatwoot contact additional attributes during contact sync (for example: FluentCRM URL, latest WooCommerce/FluentCart order summaries, and latest FluentBoards tracked time when available).
How can I show synced values in Chatwoot’s Attributes tab?
Create Contact Attributes in Chatwoot settings with keys: ictss_wp_user_url, ictss_fluentcrm_url, ictss_wc_last_order_summary, ictss_fc_last_order_summary, ictss_fluentcart_order_url, ictss_fb_last_time, ictss_fb_last_task (Text type is fine). The plugin will mirror values to custom_attributes when data exists.
If WooCommerce / FluentCRM / FluentBoards is not installed, sync still works; those specific values are simply skipped.
Can I test contact sync on production without WP_DEBUG?
Yes. In Support Portal -> Tools & Diagnostics, use the Manual Sync Now form (enter a WordPress user email). The same page shows latest sync status (including scheduler health and progress), supports Run Cron Batch Now with skip breakdown, Sync All Now (All Batches) for catch-up, and Emergency Stop Cron for lock/abort recovery.
Can I control how scheduled sync selects users?
Yes. In Cron Sync, choose scope as all users, commerce users (WooCommerce or FluentCart), WooCommerce-only, or FluentCart-only. You can also set interval (hourly, twice daily, daily). Scheduled sync runs in batches and auto-continues in the background with short-delay follow-up batches until the active cycle is complete.
How are local phone numbers normalized for Chatwoot?
Phone sync is strict E.164. The plugin first tries country/profile hints from WordPress/commerce data. The Default Phone Country Code setting is fallback-only and is used only if no hint resolves a country. If country still cannot be resolved, local phone updates are skipped to avoid wrong-country values.
How do I choose the correct FluentCRM contact URL route?
In Support Portal -> Settings -> Integrations, set FluentCRM Contact Route to subscribers or contacts.
How to verify: open a contact in FluentCRM and inspect the browser URL hash after #/.
Examples:
– #/subscribers/38/ -> choose subscribers
– #/contacts/38 -> choose contacts
How are company/city/country synced to Chatwoot contact details?
The plugin mirrors these values to Chatwoot additional_attributes for compatibility with Chatwoot contact sync behavior:
– company -> additional_attributes.company_name
– city -> additional_attributes.city
– country (ISO code when available) -> additional_attributes.country
WooCommerce and FluentCart billing fields are used as source values when present.
What happens when require_login=”no” is used on the new ticket shortcode?
The form is available for non-logged-in visitors and is suitable for contact-style intake pages. In this mode, the “Back to My Tickets” success button is not shown for non-logged-in users.
What happens on uninstall?
By default, uninstall removes plugin options, plugin transients, local conversation cache posts (ictss_conversation), and chatwoot_contact_id user meta mappings.
If you need to preserve data, define ICTSS_PRESERVE_DATA as true before uninstall.
Screenshots














Changelog
2.6.15
- Replace the industry-specific starter conversation with a general support and enquiry flow and neutral assistant defaults.
- Let site owners disable the floating widget or choose between the Chatwoot widget and the ICT Shift custom widget.
- Add opt-in daily reconciliation of local support copies confirmed deleted from Chatwoot, processed in bounded batches with fresh checks and connection-change protection.
- Expose cleanup progress, failures and last successful sweep for read-only monitoring. No age-based deletion; existing remote conversations, accounts, financial and time records are unchanged.
- Existing sites keep their saved bot name, email link and flow; only new installs receive the neutral defaults.
- Coding-standards hardening: escaped ticket output and exception messages, translator comments, WordPress file and URL helpers, sanitised admin notices and debug logging limited to WP_DEBUG.
2.6.14
- Add Tools > Support mirror review for administrator-approved cleanup of local copies verified missing from Chatwoot. No automatic deletion or retention period is enabled.
- Remove approved copies with their local message history, diagnostics, sharing anchors and caches; prevent delayed imports from recreating reviewed deleted conversations.
2.6.13
- The Yeastar PBX contact sync keeps exactly one contact per phone number. When several people or companies share a number, the new “Shared Number Owners” setting (one “number = company” per line) decides which one is shown; otherwise people win over extra contacts, which win over company main numbers. Inbound caller matching follows the same choice.
- Sync the main phone number of the FluentCRM companies of active customers to the PBX when no person already uses that number. Sites can adjust the list with the
ictss_company_sync_numbersfilter. - PBX contacts without an email address no longer send an empty email field.
2.6.12
- Contact sync now fills the company name in Chatwoot (
company_name) and Yeastar PBX (company): the billing company, otherwise the contact’s primary FluentCRM company. Sites can adjust it with theictss_contact_company_namefilter. - Add the
ictss_extra_sync_contactsfilter for contacts without their own active WordPress user, such as company finance contacts. With the Active customers scope they are synced to Chatwoot (email-only, marked with acontact_roleattribute) after each completed cycle, and to the PBX when they have a phone number.
2.6.11
- Fix Chatwoot contact sync for FluentCart 2.x: read orders, billing addresses, phone numbers and revenue from the FluentCart tables, and sync on the
fluent_cart/order_createdandfluent_cart/order_paidhooks. - Add the “Active customers” sync scope with an “Active Customers Since” date (FluentCart order on or after the date, or a running subscription). Sites can add customers through the
ictss_active_customer_user_idsfilter. - With the Active customers scope, logins and profile updates only sync active customers or users already linked to a Chatwoot contact.
- PBX contact sync and inbound caller matching now use the same active-customer set (no longer the hours ledger), read phone numbers from the FluentCart billing address, and the contact sync can run daily (new “Daily PBX Contact Sync” setting, off by default).
2.6.10
- Fix contact-sync continuation jobs failing on PHP 8 when WordPress passes stored cron arguments by name. Existing scheduled and manual full-sync jobs remain compatible.
2.6.9
- Add German (de_DE), French (fr_FR) and Belgian Dutch (nl_BE) translations for the chat widget and customer ticket portal.
- Recognise German and French yes/no answers, including explicit “not an emergency” replies, in the chat bot’s emergency question.
2.6.8
- Simplify the Support Portal menu to Tickets, Settings and Tools & Diagnostics, with a decorative divider before administration.
- Open Tickets from the top-level menu and keep settings in clearly named tabs, including Chat Widget.
- Preserve existing settings URLs, active-menu highlighting, ticket counts and support-agent access.
2.6.7
- Add explicit restricted/shared company support visibility with verified company membership hooks.
- Approved company portal members can view explicitly shared tickets and chats, excluding internal notes.
- Shared visibility is read-only: existing requester access, manual CC and email delivery remain unchanged.
- Authorised company admins and staff can explicitly share existing tickets or revoke company visibility without changing the bound company.
2.6.6
- Keep the mobile livechat header and composer inside the viewport, including browsers with dynamic toolbars.
2.6.5
- Add Dutch ticket-list, intake, detail/reply and customer-facing error translations.
- Keep configured support account links in the translated FluentCart dashboard namespace, preserving endpoint suffixes, queries and fragments.
2.6.4
- Live chat: configurable conversation prompts, quick-reply labels and matching keywords can now be translated through WPML String Translation.
- Live chat: retain the selected language in REST requests, later bot replies and contact handoffs without changing flow routing values.
- Add Dutch custom-widget interface translations and recognise Dutch emergency answers.
2.6.3
- The admin-bar “Tickets” item is now shown to ticket agents/admins on every page, including the front end, not only inside wp-admin. The live presence console stays wp-admin only.
2.6.2
- Chat widget: resolved conversations no longer reopen automatically (most visible for logged-in customers); the widget starts with a fresh greeting and past chats stay under the folder icon.
- Chat widget: new “End chat” button in the header (with confirmation) marks the active conversation resolved and starts fresh. The close (X) button still only minimises the chat.
- Chat widget: the conversation list loads immediately when opened.
- Chat widget: starting a new conversation no longer flips back to the previous one when a late message refresh arrives.
2.6.1
- Tickets: per-agent setting “Images in emails” (Users → Profile): load remote images automatically (default) or ask first, which blocks tracking pixels until you click “Load images”.
- Tickets: email style sheets are kept intact (selectors such as “a > b” were mangled by the HTML filter) and get a CSS-only filter; Outlook-only conditional blocks are dropped.
2.6.0
- Tickets: customer presence. The ticket header shows whether the customer is In the chat (widget open), Away (on the site with the chat closed) or Offline. Background unread checks of the widget no longer count as “in the chat”.
- Tickets: choose how a reply reaches the customer: Auto (chat; email only if they are not reading along), Chat + email (always email as well) or Chat only (never email). Applies to website chat and portal tickets; email-inbox tickets are emailed by Chatwoot as before.
- Tickets: delivery receipts under each reply: Emailed (time), Seen in the chat, Chat only, or waiting. Failed Chatwoot email deliveries show “Not delivered” with the reason.
- Email relay: replies the customer already read in the chat are no longer emailed by the fallback check.
- Email relay: no longer emails agent replies on Chatwoot email-inbox tickets. Chatwoot already emails those, so the customer could get the reply twice.
- Tickets: incoming emails are shown in their original HTML layout in a sandboxed frame (no scripts, no forms), with quoted history collapsed and a Plain text switch.
- Tickets: the plugin HTML email signature is shown under emailed replies and as a preview in the composer. Markdown images and links in Chatwoot signatures now render instead of showing as raw text.
2.5.0
- Tickets: live chat console. Open tickets update every few seconds without reloading, replies and notes are sent in place, and a “New messages” button appears when you have scrolled up.
- Tickets: Online / Away switch for each agent. Agents with the Tickets screen open count as “online” for the chat widget and the email relay timing, together with Chatwoot availability. After 15 minutes without activity you drop out automatically.
- Tickets: unread count in the admin menu, the admin bar and the browser tab title. Optional desktop alerts with a sound (bell icon) work on every admin page and only fire for tickets assigned to you or unassigned.
- Tickets: typing indicators both ways. You see when the customer or another agent is typing; the customer sees your first name typing in the chat widget.
- Tickets: “Customer is in the chat” indicator, a “Waiting for a reply” list on the ticket screen, and a refresh prompt when tickets in the list get new activity.
- Chat widget: the header shows the real team status (online, away or offline). Agent replies show the agent’s first name and avatar instead of the bot icon.
2.4.1
- Attachments: one shared allow-list for the Tickets screen, chat widget and client portal. Adds log, json, xml, yml, md, ini/conf, sql, eml and msg files to the WordPress defaults (csv, txt, office, images, pdf, zip…); HTML, JavaScript and executables stay blocked. Filter:
ictss_attachment_types. - Attachments: Chatwoot website inboxes refuse some text formats (e.g. .log); such files are now retried once as name.log.txt instead of failing.
- Tickets: new “Default inbox for new tickets” setting (Integrations). Without it the first email inbox is preselected. The inbox field now sits next to the subject and shows which address the ticket is sent from.
2.4.0
- Tickets: canned responses. Insert them from the composer’s Canned button or by typing / in the message box. Variables such as {{contact.name}} and {{agent.name}} are filled in automatically. Chatwoot stays the single source: responses are read from Chatwoot (cached for 5 minutes), and new, edited or deleted ones are written straight back.
- Tickets: new Canned responses screen to add, edit and delete responses, plus “Save text as canned response” in the composer.
- Tickets: attach up to 10 files to a reply or a new ticket by button, drag & drop, or pasting (Ctrl+V).
- Email relay: agent replies with attachments sent from the Tickets screen are now emailed to the customer with attachment links.
- Chat widget: attach files by drag & drop onto the chat window or by pasting into the message box (up to 3 files, 10 MB in total).
- Client portal: paste files (Ctrl+V) into the message field. Dropped files are now added to the selection instead of replacing it.
- Fix: the chat bot could answer an agent’s own message (for example a private note) because Chatwoot webhooks send the message type as text. Message types are now normalised before any listener runs.
- Fix: the chat bot now steps back when a human agent is assigned, also when Chatwoot only reports the assignee under meta.assignee (e.g. tickets created from the Tickets screen).
2.3.0
- Tickets: prepaid hours in the ticket header and sidebar when the customer is linked to a company or board (balance meter, purchased/used, last top-up; boards without a balance show billable time this month). Board membership in FluentBoards counts as a link.
- Tickets: dark mode. Pick Auto (follows the operating system), Light or Dark per user with the switch at the top of the Tickets screen.
- Tickets: agents can open a new ticket for a customer from the ticket list, a ticket’s customer box, the Users screen, or a FluentCRM contact or company profile. The first message is emailed to the customer, or saved as an internal note to log a call. Unknown email addresses are added to Chatwoot as contacts.
2.2.1
- Tickets are now worked as a Chatwoot agent: every WordPress user is linked to a Chatwoot agent (same email address, a personal token, or picked by an administrator on the user profile). Unlinked users see setup instructions instead of the ticket list.
- With a personal token, replies, notes, status and assignment changes are made by the agent’s own Chatwoot account and the agent’s Chatwoot message signature is added to customer replies. Through the shared plugin account, messages are signed with the Chatwoot agent name.
- Bulk actions on the ticket list: resolve, reopen, mark pending, mark as read, assign/unassign and (administrators only) permanently delete.
- Redesigned ticket view: header with Resolve/Reopen and Assign to me, avatars, day separators, collapsible quoted email history, image thumbnails and a tabbed reply/private-note composer. Opening a ticket marks it read.
- Ticket titles and list previews no longer show private notes or quoted email history.
2.2.0
- New Tickets page (Support Portal → Tickets): browse, search and filter Chatwoot conversations by status, assignee and inbox; read the full thread; reply or add private notes; change status and assignee without leaving WordPress.
- Optional FluentBoards integration on the ticket: create a task on the customer’s board (or a default support board), link existing tasks, and log billable/non-billable time with an hours-balance warning (time tracking needs FluentBoards Pro).
- Optional FluentCRM integration: customer contact/company shown on the ticket, and a “Support tickets” section on FluentCRM contact and company profiles.
- Ticket history on the WordPress user edit screen and a “Tickets” link in the users list. Agents can add a personal Chatwoot token on their profile so replies appear under their own name.
- Security: Chatwoot private notes are no longer relayed to customers by email, the live-chat widget or the chat assistant.
2.1.0
- New top-level “Support Portal” admin menu with separate pages for Connection, Live Chat, Customer Portal, Email, Integrations and Tools; every setting now lives on exactly one page. Old settings URLs redirect automatically.
- New visual conversation flow builder (Live Chat → Conversation flow): design the chat assistant with Start, Message, Multiple choice, Ask, Login, Condition, Action and End steps plus optional Support hours and Phone escalation integration steps. Import/export as JSON.
- The widget greeting and quick-reply buttons now come from the flow.
- The previous built-in assistant behaviour ships as the default flow template, so existing sites behave the same until the flow is edited. Conversations already in progress finish on the flow they started with.
- Reply-by-email: quoted history is stripped from imported replies, notification emails include a “reply above this line” marker and mention that customers can simply reply to the email.
2.0.12
- Removed duplicate screenshot files from plugin package assets to reduce plugin ZIP size.
- Kept WordPress.org listing screenshots in the repository root
/assetsdirectory.
2.0.11
- Updated plugin page documentation for clearer setup and usage guidance.
- Fixed screenshot visibility in the WordPress.org plugin listing.
- Improved readme text formatting and encoding for cleaner display in the plugin directory.
2.0.10
- Hardened new-ticket mail attachment handling by attaching uploaded files in-memory during send flow, avoiding temporary file writes while preserving attachment names.
- Excluded local docs/page-export artifacts from release packaging output to keep submission ZIPs clean and deterministic.
2.0.9
- Refactored shortcode/admin/webhook/API diagnostics logging to remove file-wide
error_logsuppressions and keep only narrow, WP_DEBUG-gated log helpers. - Completed shortcode request/upload hardening pass by fixing stale helper usage and keeping nonce-gated upload normalization paths explicit.
- Reduced suppression surface in settings/debug flows and narrowed SQL suppression scope where PHPCS allows line-level scoping.
- Reworked runtime contact/conversation lookup paths to avoid slow
meta_queryusage in hot flows by using bounded paged scans and deterministic conversation indexing. - Standardized request filtering to explicit sanitizing filters across runtime handlers (no unsafe raw filter usage) while preserving strict validation and context-aware output escaping.
- Added strict reviewer-facing development directives for WordPress-native methods first, sanitize/validate/escape lifecycle, nonce/capability fail-closed enforcement, and mandatory pre-submission pattern scans.
2.0.8
- Strengthened WordPress.org submission hardening for nonce verification and request sanitization reviews by aligning guarded superglobal reads with explicit checker-safe validation/sanitization paths.
- Added security-sniff coverage to local PHPCS ruleset (
WordPress.Security.NonceVerificationandWordPress.Security.ValidatedSanitizedInput) so recurring review points fail locally before release. - Improved release preflight pattern checks for settings slug/title detection to avoid brittle formatting dependencies during release validation.
2.0.7
- Hardened shortcode/admin/AJAX request handling by removing raw input filter patterns and enforcing immediate sanitization plus strict scalar validation for POST/GET reads.
- Refined nonce and permission guard flows across form submits and AJAX endpoints to keep security checks explicit and non-bypassable.
- Applied submission-readiness cleanup for WordPress.org review consistency across request, upload, and output handling paths.
2.0.6
- Restored shortcode hardening updates and fixed ticket-list first-load filtering by normalizing invalid/empty status query values to
all. - Prevented a regression where opening the ticket list with an empty
ictss_statusquery parameter could show “No tickets found” while searches still returned tickets.
2.0.5
- Hotfix: restored ticket-list shortcode request handling to the previous stable path to resolve a production regression where valid users could see “No tickets found.”
- Kept webhook authentication/security hardening introduced in 2.0.4 unchanged.
2.0.4
- Added progressive webhook authentication modes: token-only (default), token-or-signature transition mode, and signature-required strict mode.
- Added optional Chatwoot signature verification support with timestamp freshness checks and delivery replay protection.
- Hardened webhook diagnostics by redacting sensitive payload fields and trimming stored debug payload data.
2.0.3
- Hardened nonce, capability, and request sanitization checks across ticket forms, admin actions, webhook tools, and livechat identity AJAX handlers.
- Tightened upload request handling so file arrays are only processed through verified nonce-gated paths.
- Refreshed submission-readiness validation and packaging after WordPress.org review fixes.
2.0.2
- Removed legacy Chatwoot sidebar integration from plugin settings and runtime bootstrap.
- Cleaned documentation to remove deprecated sidebar-token and sidebar-endpoint instructions.
- Kept contact-context sync guidance focused on Chatwoot contact attributes/additional attributes.
2.0.1
- Clarified External Services section to correctly distinguish self-hosted Chatwoot deployments from Chatwoot cloud. Self-hosted instances are now documented separately, noting that the data controller is the server operator and that chatwoot.com terms/privacy do not automatically apply.
2.0.0
- Added contributor username to readme.txt Contributors header.
- Added External Services section to readme.txt documenting Chatwoot and hCaptcha integrations (data sent, terms, privacy links).
- Added .distignore entry to exclude design PSD assets from distribution archive.
- Removed DONOTCACHEPAGE global define, replacing with targeted nocache_headers() calls scoped to debug-mode form renders only.
- Refactored all GET parameter reads to use filter_input(INPUT_GET) via private helpers, removing direct $_GET superglobal access.
- Wrapped all inline script content in (new Function(wp_json_encode(…)))() boundary for safe dynamic JS injection.
- Removed JSON_UNESCAPED_UNICODE and JSON_UNESCAPED_SLASHES flags from JSON-encoded inline script output.
- Renamed livechat embed shortcodes from ict_shift_support_live_chat_* to ictss_support_live_chat_* for prefix consistency.
- Ensured all $_FILES access is routed through the allowlisted get_uploaded_files_from_field() helper.
1.9.9
- Added stronger release preflight checks for WordPress.org submission readiness (external-services docs and packaging exclusions).
- Hardened attachment upload handling by accepting only real uploaded temp files in multipart upload paths.
- Improved settings/admin compliance messaging and nonce handling for ticket status updates.
- Fixed frontend asset loading reliability for ICTSS shortcodes to prevent missing styling in builder/theme render paths.
- Removed explicit textdomain loading call to align with current WordPress.org plugin directory guidance.
1.9.8
- Improved ticket-list performance by reducing unnecessary enrichment calls and adding enrichment caching.
- Hardened release/package validation flow and resolved remaining plugin-check findings for submission readiness.
- Added compatibility hardening for BeTheme and Divi, including button/form UI normalization.
- Added public intake behavior refinement for
require_login="no"and asset cache-busting for CSS/JS updates.
1.9.7
- Added livechat identity controls (auto-identify, optional identity validation hash, auth-session reset)
- Added WordPress/WooCommerce/FluentCart contact sync service
- Added debug status panel and manual one-time contact sync action
- Fixed settings tab save behavior so tab saves no longer clear other-tab values
