The WordPress bridge plugin is a separate integration that pulls tickets via the Gorgias REST API. If your Gorgias account is Shopify-only, the bridge still works as long as the API token is provisioned, but order linkage will reference Shopify order IDs in postmeta rather than WooCommerce orders. SleekView shows those as plain columns instead of clickable WC links.

Yes. Tags applied by Gorgias auto-tagging rules sync down via webhook into _gorgias_tags postmeta. SleekView reads that postmeta and shows tags as a filterable column. Tag changes from inline edits POST back through the API, so server-side rules continue to run on the updated tag set.

Yes. The bridge stores the linked WC order ID in _gorgias_wc_order_id postmeta. SleekView joins wp_wc_orders or wp_posts (shop_order) depending on whether HPOS is active, and surfaces order total and status as columns. Clicking the order number opens the WC edit screen in a new tab.

LTV is computed by Gorgias from connected commerce platforms and synced as a numeric value into _gorgias_ltv. SleekView reads that postmeta directly. If the bridge plugin includes a refresh button, calling it updates LTV via API; otherwise the value refreshes on the next webhook from Gorgias.

Yes. Agent assignment syncs into _gorgias_assignee postmeta. Inline reassignment POSTs through the API, fires Gorgias workflows, and updates postmeta on the next webhook. SleekView keeps the row in a pending state if the API call fails instead of writing a stale value.

Yes. Any saved view exports to CSV with the columns and filters as configured. A common pattern is a monthly export of refund-tagged tickets joined to WC order amounts, which gives finance a self-contained file without granting Gorgias access.

Inline edits queue and retry with exponential backoff while the API is unreachable. SleekView keeps the affected rows visually distinct (pending state) until the next successful sync. No stale value is written to _gorgias_status in postmeta, which avoids the bridge masking a sync failure.

If Gorgias SLA policies are active on your account, the remaining-time value syncs into _gorgias_sla_remaining as a postmeta value. SleekView exposes it as a sortable column. A saved view sorted by SLA-remaining ascending with status=open is your real-time at-risk queue.