BotPenguin

@BotPenguin list all contacts in our 'High Value Customers' segment and show me their last interaction date

Based on your BotPenguin segments, 'High Value Customers' contains 247 contacts with filters set to purchase_value > $500 AND last_purchase < 90 days. The segment was last updated 6 hours ago. To see individual contact interaction dates, you would need to list inbox contacts separately — segments show aggregate counts and filter rules, not per-contact activity timestamps. The top 3 segments by size are: High Value Customers (247), Trial Users (1,832), and Churned Accounts (94).

This example shows how BotPenguin organizes contacts into filtered segments. The MCP returns segment definitions and counts, not individual contact records — you'll need a follow-up prompt to list inbox contacts if you want per-person detail. Useful for understanding audience size before a broadcast campaign.

@BotPenguin import these 50 new trial signups from our CSV into the contacts database and tag them 'Q1-2025-trial'

Bulk import initiated for 50 contacts. BotPenguin will create new records or update existing ones based on phone number match. Note: the import operation does not return individual contact IDs, so you won't receive confirmation of which records were created versus updated. All contacts will be tagged 'Q1-2025-trial' as specified. You can verify the import by listing inbox contacts filtered by that tag after a few minutes, or by checking the segment count if you've configured a segment with that tag filter.

This demonstrates BotPenguin's bulk contact import capability. The key trade-off: you don't get back contact IDs or a success/failure breakdown per row, so plan to verify imports through segment counts or inbox listing. Ideal for onboarding leads at scale, less suited for workflows that need immediate per-contact confirmation.

@BotPenguin check which WhatsApp templates are approved for our 'Customer Support' bot and show me the dynamic fields needed for the 'order_status_update' template

Your 'Customer Support' bot has 12 approved WhatsApp templates. The 'order_status_update' template requires these dynamic fields: {{customer_name}}, {{order_id}}, {{current_status}}, and {{estimated_delivery}}. This template was approved by Meta 8 days ago and is in the 'Transactional' category. Before sending, ensure you have all four field values populated — missing fields will cause the send to fail. The template's preview text reads: 'Hi {{customer_name}}, your order {{order_id}} is now {{current_status}}. Estimated delivery: {{estimated_delivery}}.'

This example pairs two BotPenguin tools: listing templates and fetching dynamic field requirements. Useful before launching a WhatsApp campaign — you'll know exactly which data points to pass. Remember that WhatsApp template approval status can change if Meta flags content, so verify template availability close to send time for critical campaigns.

Why BotPenguin's bulk import works for weekly CRM syncs under 5k contacts

A five-person sales team syncs leads from HubSpot to BotPenguin every Monday to enable WhatsApp outreach. The Import Contacts tool handles bulk uploads and updates existing contacts, so the team runs one prompt per week to refresh the list. The MCP's API key auth means no OAuth dance, and the operation completes in under a minute for their 3,000-contact list. The trade-off: BotPenguin doesn't return contact IDs after import, so if your CRM workflow depends on matching BotPenguin records back to HubSpot, you'll need a separate lookup step or a custom script. For teams that treat BotPenguin as a downstream outreach channel—not the source of truth—this MCP keeps the sync simple. If you're over 10k contacts or need bidirectional sync with field-level mapping, you'll want a dedicated iPaaS tool or BotPenguin's Zapier integration instead.