Delighted

@Delighted show me everyone currently enrolled in SMS autopilot surveys and their next scheduled send date

Based on your Delighted account, 47 people are enrolled in SMS Autopilot. The next survey wave sends in 3 days to the cohort added between Jan 15-22. Recent enrollments include customers from your mobile app onboarding flow (23 people) and post-purchase follow-ups (12 people). The current frequency is set to 90 days after initial contact. Note that this reflects scheduled surveys only—responses and completion rates require a separate query.

This example demonstrates read-only listing of Autopilot memberships. The MCP requires API key auth with read permissions. Useful for auditing who's in your survey rotation before making bulk changes. Does not show response data or survey results—only enrollment status and scheduling metadata.

@Delighted add sarah.chen@example.com to email autopilot with custom properties: plan=enterprise, signup_date=2024-01-15, account_value=12000

Sarah Chen has been enrolled in Delighted Email Autopilot. Her profile now includes the custom properties you specified (enterprise plan, January signup, $12k account value). The first survey will send according to your Autopilot frequency settings—currently 7 days after enrollment. You can use these properties later for segmented analysis of responses by plan tier or account value cohort.

This write operation enrolls a person and sets custom properties for segmentation. Requires API key with write permissions. The MCP doesn't validate property schemas—you're responsible for consistent naming across your team. Side effect: triggers the Autopilot schedule immediately, so double-check frequency settings before bulk enrollment.

@Delighted check our current autopilot configuration for both email and SMS, then tell me if we're surveying too frequently for a B2B SaaS product

Your Delighted setup shows Email Autopilot active with surveys every 30 days, and SMS Autopilot active at 90-day intervals. For B2B SaaS, the 30-day email cadence is aggressive—industry benchmarks suggest 60-90 days for transactional products to avoid survey fatigue. Your SMS interval is appropriate. Consider that your enterprise customers (based on the custom properties in your account) may expect even less frequent outreach. The configuration was last updated 8 months ago, which suggests it hasn't been reviewed recently.

This synthesis example pairs configuration data with AI reasoning about survey best practices. The MCP retrieves raw settings; the AI applies domain knowledge about B2B norms. Useful for auditing your setup, but the AI's recommendations depend on general heuristics—your specific customer base may differ. Always A/B test frequency changes.

When Delighted wins for transactional feedback at checkout scale

A 6-person e-commerce team ships 200-400 orders a week and wants NPS scores tied to each purchase. Delighted's 'Create or Update Person' tool lets you trigger surveys from your order-confirmation webhook, passing custom properties like order value or product SKU. The Autopilot Email tool handles recurring surveys for repeat buyers without manual list management. This setup works cleanly if your customer base stays under 10k active contacts and you're comfortable with API-key auth (no OAuth refresh headaches). If you're running multi-brand storefronts or need survey logic that branches on Shopify metafields, you'll hit Delighted's segmentation ceiling fast. For single-brand shops doing straightforward post-transaction NPS, this MCP keeps survey ops off your sprint board.

When to use Delighted for triggered feedback in product funnels

A 4-person product team at a B2B SaaS wants to survey users 7 days after they complete onboarding. The 'Add Person to Autopilot Email' tool enrolls users automatically when your app fires a 'setup_complete' event, and Delighted handles the delay and send. You can pass custom properties (plan tier, feature flags) to segment responses later. This works if your onboarding funnel is linear and you're sending one survey type per milestone. If you need branching logic (different surveys for free vs. paid users at day 7), you'll write that branching in your app code and call separate Autopilot configs. The 13-tool surface is overkill for simple milestone surveys, but the 'Delete Pending Survey Requests' tool saves you when users churn before the survey fires. Best fit for teams that want survey timing decoupled from their email stack.

When Delighted fits post-ticket CSAT at support-team scale

A 3-person support team closes 50-80 tickets a week in Zendesk and wants CSAT scores without adding survey logic to their helpdesk. The 'Create or Update Person' tool triggers a survey when a ticket hits 'solved' status, passing ticket ID and agent name as custom properties. The 'Delete Person' tool handles GDPR requests without touching Zendesk. This setup works if your support volume stays predictable and you're okay with survey responses living in Delighted's UI, not inline in Zendesk. If your team needs survey data to auto-tag tickets or trigger escalations, you'll build a webhook listener to pull responses back into Zendesk. For small support teams that want clean CSAT tracking without helpdesk bloat, Delighted's API-key simplicity beats embedding survey widgets in ticket templates.