Upzelo MCP. Stop cancellations and win back revenue with AI.

Upzelo MCP Server - Manage Churn & Retention Flows

Don't let customers slip through your fingers again. You connect this server to your AI client, and your agent handles the whole customer lifecycle conversationally. Instead of logging into the Upzelo console—and having to manually click through five different screens just to check on one user—you tell your agent what you need, and it gets the job done immediately.

This server lets you intercept cancellations and launch those personalized win-back campaigns the second a high-risk customer even thinks about leaving. It's pure power, built right into your chat window.

Managing Your Customer Base

You can get detailed info on any single user using get_customer by feeding it just their ID; you'll instantly know their current status and all the associated data points Upzelo keeps on file. Need to see who's in your pool? You run list_customers, and that pulls a full roster of every customer profile tracked in Upzelo.

If you find a record with bad segmentation info, you can use save_customer to either create an entirely new user record or just update the details on an existing one—it's how you keep your targeting sharp.

Tracking Subscriptions and Billing Details

Managing billing shouldn't be guesswork. You pull all the specific financial data for a single account using get_subscription when you need to check rates or plan structures. Want to audit everything? Run list_subscriptions, and you get a complete list of every subscription managed within your Upzelo account. If something changes—say, a customer upgrades their tier mid-cycle—you can use update_subscription to programmatically change specific attributes like the plan name or status directly through the agent.

You'll never have to manually update a billing record again.

Running Retention Campaigns and Monitoring Status

The main goal here is keeping people subscribed, so retention flows are your bread and butter. First, you check what strategies you even have available by running list_flows, which gives you the names of every existing retention template. You can then pull the specific blueprint for any single flow using get_flow to see exactly how that sequence is built out.

When a customer shows signs of canceling, you tell your agent to start the process with start_flow; this kicks off the automated, multi-step win-back sequence immediately for that user.

Don't assume it worked just because you hit 'send.' You run into potential roadblocks, and you need proof. To check if a retention sequence is actually running right now or what its final outcome was, you use get_flow_session. This tool tells you the real-time operational status of the flow—did it succeed? Did it fail on step three? You get that granular detail every time.

The Full Workflow Picture

This combination means you're never blind. You start by listing all customers via list_customers and checking out their billing details using list_subscriptions. Then, if a user looks shaky, you check the flow structure with get_flow, manually trigger the sequence with start_flow, and keep monitoring that session status until it's complete.

You can refine the entire operation by saving new customer segments via save_customer before kicking off the whole thing. This server lets your agent handle every single touchpoint, from initial data retrieval to final subscription update, without you ever leaving your chat window.