Emelia

@emelia show me all active campaigns and how many contacts are enrolled in each one

Based on your Emelia account, you have 4 active campaigns: 'Q1 Product Launch' (237 contacts), 'Customer Winback' (89 contacts), 'Partnership Outreach' (156 contacts), and 'Event Invitations' (412 contacts). The Product Launch campaign has the highest open rate at 34%, while Partnership Outreach is seeing the most replies. This is an illustrative example—actual campaign metrics will reflect your account's real-time data.

This read operation requires API key authentication and returns campaign-level statistics. Emelia's API may rate-limit frequent polling, so avoid running this query in tight loops. The response shape depends on which campaigns exist in your account and their current enrollment status.

@emelia add sarah.chen@techcorp.com to the 'Partnership Outreach' campaign with the title 'VP of Engineering'

I've added Sarah Chen (sarah.chen@techcorp.com) to your 'Partnership Outreach' campaign with the title 'VP of Engineering'. She'll enter the sequence at step 1 and receive the first email according to your campaign's send schedule. This is an illustrative example—the actual contact will be enrolled immediately upon confirmation, and you'll see her appear in the campaign dashboard within a few minutes.

This write operation permanently adds the contact to the campaign and triggers email sends. Make sure the email address is valid and the contact has opted in where required by your compliance policies. Once added, use the delete tool if you need to remove them—there's no undo.

@emelia review all bounced emails from the last 7 days and add those addresses to the blacklist so we don't waste sends

I found 12 hard-bounced email addresses in the past week across your campaigns: 8 from 'Q1 Product Launch', 3 from 'Customer Winback', and 1 from 'Event Invitations'. I've added all 12 addresses to your blacklist to prevent future send attempts. The most common bounce reason was 'mailbox does not exist'. This is an illustrative example—the AI would retrieve bounce data via list/search tools, then batch-add to the blacklist using the appropriate tool.

This synthesis example combines read operations (fetching bounce reports) with write operations (blacklist additions). The AI interprets 'bounced' to mean hard bounces, not soft bounces or temporary failures. Confirm the time range and bounce type match your intent before running, as blacklist additions are permanent.

When Emelia fits a 2-person sales team running multi-channel sequences

A two-person B2B sales team needs to launch a 50-contact pilot campaign mixing email and LinkedIn touches. Emelia's 21 tools cover the full loop: create the campaign, enroll contacts, set up webhooks for reply tracking, and manage the blacklist when prospects opt out. The API key auth means the team can script enrollment from a shared Airtable or CSV without per-user OAuth friction. This works until you hit about 500 contacts per month—beyond that, the manual contact-add calls get tedious and you want a CRM integration that Emelia doesn't natively provide. If your workflow is 'upload list, launch sequence, track replies in Slack via webhook,' Emelia's MCP gives you the control without the enterprise CRM overhead.

Use Emelia's webhook tools when your team triages inbound in a shared channel

A 4-person customer success team runs re-engagement campaigns and routes replies into a shared Slack channel for same-day follow-up. Emelia's create-webhook and delete-webhook tools let you programmatically subscribe to campaign events (opens, replies, bounces) and pipe them to your notification stack. The MCP shines here because you can spin up event listeners per campaign without logging into the Emelia UI—useful when you're running 3-5 concurrent sequences and need different routing rules for each. The ceiling is webhook volume: if you're sending 10k emails a week, the event firehose can overwhelm a simple Slack integration. Below that threshold, this is the fastest way to close the loop between outbound and inbound without a full marketing-automation platform.

When to automate blacklist updates with Emelia's contact tools

A 3-person agency manages outreach for five clients and needs to keep a shared suppression list current across all campaigns. Emelia's add-contact-to-blacklist and delete-contact-from-campaign tools let you script the cleanup: when a contact replies 'unsubscribe' or bounces hard, your workflow removes them from active sequences and adds them to the global blacklist in one call. This prevents the compliance headache of manually syncing opt-outs across campaigns. The trade-off is that Emelia's blacklist is account-wide, not per-campaign—if you need client-specific suppression rules, you'll need to layer that logic in your own database before calling the MCP. For teams under 10 campaigns, the simplicity wins; beyond that, you want a dedicated compliance tool.