SleekView for Interakt for WordPress: lead syncs & WhatsApp events as tables
Interakt for WordPress pushes leads and WooCommerce events to the Interakt WhatsApp engagement platform. SleekView reads its API config and event log so push status, template usage, and per-customer activity become a single auditable workspace.
♾️ Lifetime License available
An audit layer over the WhatsApp bridge
Interakt for WordPress is a connector for the Interakt WhatsApp engagement product. The plugin stores its API key, account identifiers, and trigger configuration in wp_options under keys like interakt_settings, and logs each outbound event (lead push, WooCommerce order, abandoned cart, template send) to a small log table or rolling option record. The canonical contact list, conversations, and chats live inside Interakt's hosted dashboard.
The default plugin screens focus on configuration. They show whether the connection is live and which events are enabled, but they don't give an operations table over what actually shipped. "Which leads pushed today, which failed, and what template fired" needs a flat scrollable log instead of grouped, filterable rows. Per-template usage and per-trigger failure rates aren't surfaced.
SleekView reads the connector's options, event log, and per-template usage metadata. Each outbound event becomes a row with status, template name, recipient, and API response. Filters cover trigger type, template, and time range. Inline retry calls the plugin's own send function so behaviour matches a normal trigger.
Workflow
From WhatsApp log to operations table
Pick the source
interakt_settings and the plugin's event log table or rolling option record.
Compose columns
wp_postmeta on the order ID where present.
Save and scope per role
Retry inline or in bulk
Sample columns
A typical Interakt event log view
wp_options (interakt_settings) + plugin event log table or rolling option record
| Recipient | Trigger | Template | Status | API response | Sent |
|---|---|---|---|---|---|
| +44 7700 900 451 | Order placed | wc_order_confirmed | Sent | 200 OK | Apr 24 |
| +1 415 555 0188 | Lead capture | lead_welcome | Sent | 200 OK | Apr 24 |
| +91 98765 43210 | Abandoned cart | ac_reminder_1 | Queued | 202 accepted | Apr 23 |
| +33 6 12 34 56 78 | Order placed | wc_order_confirmed | Failed | Template not approved | Apr 22 |
Comparison
Default Interakt for WordPress admin vs SleekView
Default Interakt for WordPress admin
- Settings screen shows connection state but no operations log
- Per-template usage and failure rates require scrolling raw events
- Trigger-level filters are not exposed in the default admin
- No queue separating approved-template failures from delivery errors
- Lead pushes and WooCommerce events live in the same flat list
SleekView
- Filter the event log by trigger, template, and status together
- Group by template to surface per-template failure rate
- Coloured status column for sent, queued, and failed
- Bulk retry through the plugin's own send function
- Save "order events today" or "lead pushes this week" as named queues
Features
What SleekView gives you for Interakt for WordPress
Per-template audit
Group sends by template name to see which approved template is firing the most and which is silently failing. Approval issues stand out from the delivery noise.
Trigger-level filters
Filter by order, lead capture, abandoned cart, or custom trigger. The same view that powers ops reports also powers the daily "what failed" review.
Bulk retry
Select queued or failed events and retry through the plugin's send routine. Each row refreshes with the new response, so the audit trail stays consistent.
Audience
Who uses SleekView for Interakt for WordPress
WooCommerce ops
Confirm every order today fired its WhatsApp confirmation. Filter by trigger to spot the day a template approval lapsed and the order confirmations stopped going out.
Growth and lifecycle
Group abandoned-cart sends by template to compare their volume. The view becomes the basis for a per-template optimisation review.
Support
Filter by phone number to confirm whether a customer received the order confirmation and which template went out. Read the API response inline.
The bigger picture
Why a WhatsApp connector earns an audit table
WhatsApp messaging is a high-trust channel: customers expect the order confirmation in seconds, the abandoned cart reminder before the end of the day, the lead acknowledgement before they bounce. When that flow breaks, the failure mode is silent. The default Interakt connector settings screen is fine for setup, but it does not show operations the operational picture they need: which trigger is firing, which template is approved, which sends are failing right now.
That gap pushes teams to export the log and script over it. SleekView reads the same option and log records the plugin already writes, surfaces them as a queryable table, and lets retries route through the plugin's own send code. That turns an invisible bridge into one the WooCommerce team and the lifecycle team can actually watch.
Questions
Common questions about SleekView for Interakt for WordPress
No. Conversations live in Interakt's hosted dashboard. SleekView reads the WordPress connector's options and event log, which is the outbound side the plugin records locally.
Mapping and trigger configuration still render from interakt_settings. Event-level views require the plugin's log to be enabled; SleekView surfaces whichever fields are available.
Yes. The event log records the template identifier; SleekView promotes it to a named column so you can filter and group by template approved in Interakt.
Yes. For order-driven events, the row can join against wp_postmeta on the order ID to add total, currency, or coupon columns alongside the WhatsApp status.
Bulk retry calls the plugin's send routine. If a template was not approved at send time, retry runs the same path; once the template is approved in Interakt the next attempt will go through.
No. Queries hit existing options and the log table; pagination and indexed reads stay quick even on stores with high WhatsApp volume.
Per-role scoping limits who sees full phone numbers. A masked-phone column is available for support views; admins keep the full column.
Yes. If a developer added a custom trigger via the plugin's hooks, its trigger identifier will appear in the log and can be filtered like any built-in trigger.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkoutBrowse more
- Edd Active Campaign
- Woocommerce Pre Order Pro
- Surecart Cart
- Surecart Affiliates
- Woocommerce Additional Variation Images
- Yith Woocommerce Anti Fraud
- Customer Reviews For Woocommerce
- Yith Woocommerce Request A Quote
- Wp Ecommerce
- Woocommerce Pdf Invoices Packing Slips
- Dokan
- Woocommerce Shipworks
- Winwar Aelia Currency Switcher
- Woocommerce Bitpay
- Edd Convertkit
- Wp Members
- Nextend Social Login
- User Registration
- Memberpress Affiliate Royale
- Wishlist Quickfront
- Userpro
- Woocommerce Paid Courses
- Restrict Content Pro
- Accessally
- Memberium Infusionsoft Pro
- Register Plus Redux
- Ultimatemember Real Time Notifications
- Ultimatemember MyCRED
- Paid Memberships Pro Addons
- Joinup Membership