Esputnik

@esputnik show me all contacts added in the last 7 days who haven't opened any emails yet

Based on the contact data in your Esputnik account, here's an illustrative summary: 47 contacts were added in the past week with zero email opens. The list includes contact IDs, email addresses, and signup dates. Most joined through your website signup form (32 contacts) and mobile app registration (15 contacts). All contacts are currently in 'active' status but show no engagement metrics yet.

This example demonstrates Esputnik's contact querying capabilities. The actual response depends on your account's contact volume and segmentation setup. You'll need API key permissions for contact read access. Note that bulk contact operations are limited to 3,000 records per request, so large result sets may require pagination.

@esputnik create a new SMS campaign to send order confirmation messages to customers who purchased in the last hour

I've prepared an SMS campaign draft in your Esputnik account. The campaign targets 12 customers with completed orders in the past 60 minutes. Each SMS will include order number, total amount, and estimated delivery date pulled from the order data. The campaign is saved as a template (ID: SMS_89472) but not yet activated—you'll need to review the message content and manually approve sending to avoid accidental sends.

This showcases Esputnik's SMS campaign creation and order integration. The MCP can draft campaigns but typically requires manual approval before sending to prevent unintended bulk messages. Be aware that SMS sends consume your account's message credits, and Esputnik enforces rate limits on campaign sends (check your plan tier for specifics).

@esputnik analyze our mobile push token activity over the last month and tell me which app versions have the highest deactivation rates

Here's an illustrative analysis of your mobile push tokens: App version 2.3.1 shows a 34% deactivation rate (highest), followed by version 2.2.5 at 18%. Version 2.4.0 has only 7% deactivations. Total active tokens: 8,942. Total deactivated: 1,203. The spike in 2.3.1 deactivations correlates with a known bug in notification handling that was patched in 2.4.0. Consider re-engaging users on older versions with an update prompt campaign.

This example pairs Esputnik's token management data with AI reasoning to surface actionable insights. The MCP can retrieve token states and change activation status, but cross-referencing with app version metadata may require additional context you provide. Token operations are immediate and affect live push delivery, so use caution when bulk-deactivating.

When Esputnik fits a Shopify store doing email + SMS

A 6-person DTC brand runs lifecycle campaigns (abandoned cart, post-purchase) across email and SMS. Esputnik's bulk order import (up to 1000 at once) and contact sync (3000 per batch) let the team pipe Shopify order data into segmented campaigns without writing custom ETL. The 14 tools cover domain registration for web tracking, token management for mobile push, and message deletion for template cleanup. This works if your store processes under 50k orders per month and you're comfortable with API key auth—no OAuth means you manage credential rotation manually. If you need real-time event streaming or sub-second order sync, look at a CDP with native Shopify webhooks. For weekly batch imports and campaign orchestration, Esputnik's tooling matches the scale and the team can own the integration in-house.

Bulk contact deletion when migrating CRM platforms

A 3-person support team is moving from Esputnik to a new CRM and needs to purge 10k stale contacts before the cutover. Esputnik's delete-by-ID and delete-by-external-ID tools let you script the cleanup in batches, but there's no bulk-delete endpoint—you're looping through individual contact removals. If your contact list is under 5k and you can afford a few hours of API calls, this works. Beyond that threshold, the rate limits and lack of batch deletion make the process slow enough to justify asking Esputnik support for a manual export-and-purge. The tooling is fine for ad-hoc contact hygiene (removing duplicates, GDPR requests), but it's not built for large-scale data migrations. Plan the timeline accordingly or negotiate a direct database operation with the vendor.

When in-app messaging needs template version control

A 4-person mobile product team sends onboarding tips and feature announcements via Esputnik's app inbox. The get-message and delete-message tools let you fetch drafts, review translations, and remove outdated templates before they go live. This is useful if your release cycle is weekly and you're coordinating message content with product launches—pull the latest message JSON, confirm the copy in Switchy, delete the old version. The workflow breaks down if you need multi-stage approval or rollback: there's no versioning API, so you're managing message state in your own tracker. If your team ships daily or runs A/B tests on in-app content, you'll outgrow this quickly and need a feature-flag platform. For low-frequency, high-touch messaging where a human reviews every send, Esputnik's tooling keeps the process simple and the team stays in one workspace.