Chatwoot Client Portal by ICT Shift
Chatwoot Client Portal by ICT Shift turns your WordPress site into a Chatwoot-backed support portal. Built by ICT Shift. Give clients a familiar, branded support area inside WordPress while your team continues working in Chatwoot. Ideal for businesses that want to: Let logged-in users view and reply to support tickets without leaving your website Offer contact-style intake pages for non-logged-in visitors Keep omnichannel conversations centralized in Chatwoot inboxes (email, livechat, WhatsApp, and more) Sync useful customer context from WordPress and commerce plugins into Chatwoot contact records For help with Chatwoot setup, self-hosting, or hosting guidance, you can contact ICT Shift at https://www.ictshift.com/. Plugin support is also available in the WordPress.org support forum. Features: Ticket list and detail shortcodes Dedicated new-ticket shortcode/form Reply support with optional attachments Ticket status display and update flow Floating livechat widget + embedded chat modes Logged-in user livechat identity (setUser) with optional identity validation (identifier_hash) Contact sync to Chatwoot from WordPress profile, WooCommerce, and FluentCart (best effort) Multi-inbox filtering support Webhook-based synchronization support Translation-ready text domain 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 URL ticket_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 URL show_unassigned_assignee="yes|no" (default no) – when yes, always show Assigned as Unassigned if no agent is set New ticket shortcode [ictss_support_new_ticket] Optional new ticket attributes: show_attachments="yes|no" (default yes) show_priority="yes|no" (default no) inbox_id – override the Chatwoot inbox used for ticket creation mail_to – override mail transport recipient(s) for this page only require_login="yes|no" (default yes) – set to no for public/contact intake pages tickets_url – override the “Back to My Tickets” button URL after successful submit debug_console="yes|no" (default no) – 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. 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.
Translate WordPress with GTranslate
Translate WordPress with GTranslate plugin uses Google Translate AI translation service to translate wordpress site with Google power and make it multilingual. With 103 available languages your site will be available to more than 99% of internet users. Our paid versions are fully SEO compatible which will increase your international traffic and sales. This translate plugin is a budget multilingual WordPress solution which combines automatic and human translations to save money and is easy to implement. GTranslate is a leading website translation services provider since 2008, it moves away the language barriers. Compared to other translation plugins for WordPress, we use cloud based approach which does not slow down your website. In addition to that, we can offer complete SEO features based on sub-domains with our paid options, which can make your website appear in search engines in different languages which will increase your international traffic and sales. In our paid versions we DO NOT limit the number of words or the number of translated pageviews. You DO NOT pay additionally for automatic translations. Please use GTranslate Support for your questions and support requests! We are multilingual! Please check our FAQ to get quick answers. Free translation service: permitted use Under the GTranslate Terms of Service, the free translation service is available for personal, educational, internal testing, nonprofit and governmental purposes, provided the use does not directly generate revenue from the service. Nonprofit use must further nonprofit activities; governmental use includes public institutions and other public-sector entities. Commercial or revenue-generating use requires an applicable paid subscription. This free-service restriction does not apply to free trials of paid subscriptions. These service conditions do not change the WordPress plugin code’s GPLv2-or-later license. Features Automatic machine translation Translate website on the fly Translate posts and pages Translate categories and tags Menus and widgets translation Themes and plugins translation Right to left language support Google Translate website translator widget alternative Auto-switch language based on browser defined language Available styles Float, Dropdown, Flags, Flags with dropdown, Nice dropdown with flags, Flags with language names, Flags with language codes, Language names, Language codes, Globe, Popup Floating language selector WooCommerce shop translation Multilingual language names in native alphabet Alternative flags for Quebec, Canada, USA, Brazil, Mexico, Argentina, Colombia Lazy loading for language flags and js libraries to boost performance Lightweight vanilla javascript without dependencies Forum Support Paid Features Multilingual SEO – Enable search engine indexing Neural machine translations with human level translation quality Increase traffic and AdSense revenue Search engine friendly (SEF) URLs Yoast SEO compatible – translate meta keywords, meta description, schema.org data structures, translate sitemaps WooCommerce compatible – translate products, schema.org data structures You can have sub-directory (example.com/es/) or sub-domain (es.example.com) URL structure URL Translation aka slug translation is possible (example.com/about-us → example.es/sobre-nosotros) Add hreflang tags for translated alternatives You can manually correct translations In context translation interface (make corrections without losing the context) Meta data translation (meta keywords, meta description) Translating schema.org microdata for better search engine appearance Seamless updates (cloud service updated on our side – SaaS, you do not need to worry about backups on your side) JSON format translation Translate WooCommerce emails AMP translation (Accelerated Mobile Pages translation) Image localization – Media translation Translation Proxy (aka Translation Delivery Network) Centralized Translation Cache – We revise and improve translations over time Language Hosting (example.fr) User Dashboard with Analytics Live Chat Support See also If you are looking for unlimited, high-quality automatic translations, check out TranslateX – an automatic translation API offering unlimited translation for your website or application. We also offer integration plugins: TranslateX for Loco Translate – integrate TranslateX API directly into Loco Translate for seamless, unlimited automatic translations. TranslateX for TranslatePress – bring unlimited automatic translation to TranslatePress using TranslateX API. These solutions make it easy to supercharge your WordPress multilingual setup with TranslateX’s secure and affordable API. GTranslate WordPress Demo Watch GTranslate Tour Edit Translations Demo (paid) External services This plugin uses external services to load the language selector and obtain automatic translations. GTranslate widget delivery When the widget loads, the visitor’s browser requests its files from cdn.gtranslate.net over HTTPS. GTranslate, Inc. provides the widget, which connects the visitor’s browser to the translation service. Google translation requests When page translation is requested, the widget sends page text for translation from the visitor’s browser to translate-pa.googleapis.com over HTTPS. Google processes these translation requests. The content sent is the page text being translated. Loading widget files and requesting translations are separate network operations. These requests also expose standard connection and HTTP request information, such as the visitor’s IP address and browser headers, to the receiving service. Provider processing and retention practices are described in the applicable policies; browser-based translation does not mean that no data leaves the browser or that providers retain no data. If you configure a paid translation proxy service, translated versions of your website are processed and served through GTranslate’s cloud infrastructure according to your service configuration. GTranslate, Inc.: Terms of Service, Privacy Policy Google: Terms of Service, Privacy Policy Review these services when updating your website’s privacy information and configuring any consent or content-security controls. The plugin requires access to the relevant external services for translation to work.
