Zixflow

@Zixflow show me the delivery status for our last email campaign — how many opened vs bounced?

Here's the email campaign report from Zixflow: **Campaign:** Product Launch Announcement **Sent:** 1,247 messages **Delivered:** 1,198 (96%) **Opened:** 487 (41% open rate) **Clicked:** 143 (12% click rate) **Bounced:** 49 (4%) The bounce rate is slightly elevated — 32 hard bounces suggest outdated contacts. The 41% open rate is above your account average of 35%. Most clicks occurred within the first 3 hours after send.

This example shows Zixflow's campaign analytics retrieval. The MCP returns delivery metrics but doesn't automatically clean your contact list — you'd need to follow up with a separate action to handle bounces. Requires read access to campaign data in your Zixflow API key scope.

@Zixflow create a new custom attribute called 'Renewal Date' for our customer list — make it a date field.

Created custom attribute in Zixflow: **Attribute Name:** Renewal Date **Type:** Date **Collection:** Customers **Status:** Active The attribute is now available for all records in your Customers collection. You can populate it via CSV import, manual entry in Zixflow's UI, or through the API. This field will appear in contact detail views and can be used for filtering, segmentation, and workflow triggers.

This demonstrates Zixflow's schema customization. Creating attributes is immediate, but populating them across existing records requires a separate bulk-update step. The MCP can define the field structure but won't backfill historical data — plan your migration separately. Requires write permissions on list/collection settings.

@Zixflow check what variables I need to fill in for the 'Order Confirmation' WhatsApp template before I send it.

The 'Order Confirmation' WhatsApp template in Zixflow expects these variables: 1. **{{customer_name}}** — Recipient's first name 2. **{{order_number}}** — Unique order ID 3. **{{order_total}}** — Total amount with currency symbol 4. **{{delivery_date}}** — Expected delivery date (format: MMM DD, YYYY) 5. **{{tracking_link}}** — Full URL to tracking page All five variables are required. Missing any will cause the send to fail. The template is pre-approved by WhatsApp, so don't modify the text structure — only substitute variable values.

This example highlights Zixflow's WhatsApp template inspection, useful before bulk sends. The MCP surfaces required variables but doesn't validate your data against them — you'll need to ensure your contact records contain all five fields before triggering the campaign. WhatsApp template approval is outside the MCP's scope; handle that in Zixflow's dashboard first.

When Zixflow wins for multi-channel send diagnostics

A 3-person growth team runs weekly email, SMS, and WhatsApp campaigns to a 2,000-contact list. Every Monday morning, they need to know which messages bounced, who opened, and where to follow up. Zixflow's report tools let you pull delivery status across all three channels in one workspace session—no switching between vendor dashboards. The AI can compare open rates, flag bounce patterns, and draft follow-up segments in real time. This works best when your campaigns are under 10k sends per week; above that, the API rate limits start to slow down bulk report pulls. If your team sends multi-channel and needs fast triage without logging into three separate tools, Zixflow keeps the standup under 15 minutes.

When this MCP handles ad-hoc contact schema changes

A 5-person sales team uses Zixflow to track leads, but every quarter they need to add a new field—last demo date, competitor mentioned, referral source. Normally this means a Slack thread, a ticket to ops, and a two-day wait. With the Create Attribute tool, a rep can ask the AI to add a "competitor_name" text field to the Contacts collection, then immediately log it during a call. The AI validates the field type and scope, creates it, and confirms in under 30 seconds. This breaks down if your schema changes require complex validation rules or multi-step approval workflows—Zixflow's attribute API is simple by design. For teams that iterate on contact data structure weekly and trust reps to self-serve, this MCP cuts schema change time from days to seconds.

When you need template prep before bulk sends

A 2-person customer success team sends WhatsApp check-ins using pre-approved templates. Each template has 3-5 variables (customer name, plan tier, renewal date), and getting the variable list wrong means a failed send to 200 contacts. Before a campaign, they ask the AI to pull the template variables for "renewal_reminder_v2", confirm the order, and draft a CSV upload format. The Get WhatsApp Template Variables tool returns the exact schema in 5 seconds, and the AI maps it to their contact list. This is overkill if you only use one or two templates—you'll memorize the variables. But if your team rotates through 10+ templates or onboards new CSMs monthly, this MCP prevents the "oops, wrong variable order" failure mode that costs an hour of re-work.