Synthflow Cancellation Hell: How to Get Off (and What Stack to Move To)

You want to leave Synthflow. The platform is not what you need anymore, the pricing has outpaced your margins, or you found something that actually fits how your agency operates. So you open the dashboard to cancel. And you look. And you keep looking. There is no cancel button. There is no "close account" link. Multiple G2 reviews published in 2026 describe this exact experience: users search every settings menu, every billing page, every account section, and find nothing. Some report being charged for another cycle after they believed they had canceled.

This post is the full exit checklist. How to actually stop the billing, how to get your data and phone numbers out intact, how to rebuild your agents on a new platform without losing client continuity, and what platforms are worth landing on once you are out. The process takes 2 to 4 weeks done properly. It takes 3 days done badly, which usually means one missed client call and one very unhappy retainer conversation.

By builders, for builders. We have helped agency owners navigate three separate platform exits in the last six months. The playbook below is what actually works.

Why is Synthflow so hard to cancel?

The short answer is that Synthflow does not surface a self-serve cancellation path from the main dashboard. The official path is Settings, then Plan & Billing, then the billing portal. Some users reach that path and find a cancellation option. Others do not, and the discrepancy appears to be plan-tier dependent, with lower tiers requiring a direct support email to complete the process.

The deeper issue is account deletion. Under Synthflow's billing documentation, billing management happens through the billing portal, but there is no dashboard-level "delete account" button. Reviewers on both G2 and Trustpilot in 2026 flag this as a significant problem, with one reviewer explicitly calling it an "unacceptable practice for any SaaS in 2026, especially under European GDPR rules where users have an explicit right to erasure." GDPR Article 17 requires that users be able to request the deletion of their personal data. A platform that does not offer a self-serve deletion path creates a friction barrier to that right.

"There is no way to close your account from the dashboard. I searched every settings menu and billing page. This is an unacceptable practice for any SaaS in 2026, especially under GDPR." [G2 reviewer, 2026]

One separate Trustpilot reviewer reports being charged after cancellation, with Synthflow claiming the cancellation was not processed correctly. This pattern, friction on exit plus continued billing, is what earns the "cancellation hell" label from operators who have been through it.

What should I do before I cancel?

Do not cancel first and then figure out the rest. That sequence gives you active clients, no platform, and no fallback. The right order is: inventory everything, export everything, rebuild in parallel, test in parallel, notify clients, cut over, then cancel. Here is each step in detail.

1. Inventory all active agents and their client mappings. List every agent by name, which client it serves, what phone numbers it is attached to, and what integrations it touches (CRM, calendar, Zapier/Make). This is your migration map. Do not start without it.
2. Export every agent as JSON. Synthflow allows you to export individual agents as portable JSON files from the agent editor, per their agent FAQ documentation. This preserves the prompt structure, flow logic, and configuration. Export every agent before you do anything else. Note that entire subaccounts cannot be exported as a single file, so you will need to export each agent individually.
3. Download all call logs. Export your call history with date range filters before canceling. If a client ever asks for historical call data post-migration, that export is the only copy you will have. Synthflow's data retention applies 30-day limits by default on the newer compliance setting, and accounts are deleted within 90 days of closure.
4. Screenshot all prompt configurations. Even with a JSON export, a visual record of how each agent was configured, including any conditional logic branches, is useful for rebuilding. The JSON is the source of truth but screenshots are faster to reference during rebuild.
5. Note every phone number and its carrier details. If you have Synthflow-provisioned numbers, those run through their underlying telephony stack. If you have custom numbers linked via SIP or Twilio, document the E.164 format, SIP domain, authentication username, and password for each. You will need these for porting.

How do I get my phone numbers out of Synthflow?

This is usually the most stressful part of a migration, and the most important. A live client phone number tied to a dead platform is not theoretical, it has ended retainers.

Per Synthflow's phone number documentation, porting takes 1 to 2 weeks and may include a one-time porting fee depending on your carrier. The key distinction is whether your numbers are Synthflow-provisioned or custom-imported.

Synthflow-provisioned numbers (the ones you bought directly inside the platform) are Twilio or Vonage numbers at the carrier layer. You can port these out by initiating a port-out request with your destination carrier. The process is identical to porting any Twilio number: you need the account SID, the auth token, and confirmation from Synthflow support that the number is releasable. Start this request at least 2 weeks before your intended cutover date.

Custom-imported numbers (your own Twilio, Telnyx, or SIP numbers that you connected via the custom phone number feature) are easier. You simply stop pointing them at Synthflow's SIP endpoint and point them at your destination platform instead. The number never moved, only the routing did. This is usually a same-day change.

The migration guide for keeping Twilio numbers intact when moving between voice platforms is covered in full in the Twilio number retention playbook. The approach is the same regardless of what destination platform you choose.

How do I rebuild my agents on a new platform?

The exported JSON from Synthflow is a reference document, not a drop-in import file. No competing platform accepts Synthflow's proprietary JSON schema natively. What the export gives you is the full prompt text, the flow logic, and the action configurations, which is everything you need to rebuild efficiently.

The rebuild sequence that works:

1. Set up the destination platform with a parallel workspace. Do not shut down Synthflow until the new platform is live and tested. Run both in parallel for at least 5 business days on a real client workflow before cutting over.
2. Rebuild your highest-volume agent first. The agent with the most calls per week has the most test surface area and the most to lose if the rebuild has issues. Do not save it for last.
3. Run parallel test calls. Set up a test phone number on the new platform pointing at the rebuilt agent. Run 20 to 30 test calls that mirror your real call scripts. Check latency, interruption handling, and transfer behavior. Synthflow reviewers consistently cite barge-in handling and complex branching as failure points, so test those specifically.
4. Migrate integrations one at a time. GHL, HubSpot, Zapier, and calendar connections each need to be re-authenticated on the new platform. Test each integration independently before combining them in a live agent.
5. Notify clients 5 business days before cutover. A one-paragraph email explaining that their service is migrating to a new platform, that there will be no interruption to their calls, and that their phone numbers are not changing is usually sufficient. Clients who do not get this email before the cutover are the ones who escalate.

Which platform should I move to after Synthflow?

The answer depends on what is actually broken for you. Not every Synthflow exit is the same. Here are the three most common reasons agencies leave, and the destination that matches each.

If you are leaving because of pricing and invoice opacity: Synthflow's model bundles a base subscription with per-minute overages at $0.12 to $0.13/min after you exhaust included minutes, plus the cost of LLM tokens and ElevenLabs voices on top. The Retell AI 2026 Synthflow review puts the real all-in cost at $0.18 to $0.22/min under the included tier, which gets significantly worse in chatty months. If your issue is not knowing what the bill will be at month-end, you need a platform with a single published rate and a ceiling. That is exactly what a platform like Hermes provides: one invoice, one rate.

If you are leaving because of white-label problems: Multiple G2 reviewers flag that Synthflow branding surfaces to end clients in edge cases, particularly in support tickets that get redirected to Synthflow's team rather than staying inside the agency's branded workspace. If your agency brand has been exposed to a client because of a support escalation, you need infrastructure that was built from the ground up for white-label isolation. Your clients should never see the word "Synthflow," "Hermes," or any vendor name. The platform should be invisible.

If you are leaving because of platform stability: The Retell review and Softailed's 2026 Synthflow review both cite API instability, calls that drop mid-conversation, and minutes that get consumed without a matching call event. If your clients have complained about dropped calls or if your usage reports do not match what actually happened, that is an infrastructure problem, not a configuration problem. Moving to a platform with published uptime SLAs is the fix.

How do the platforms compare for a migrating agency?

Side-by-side at the agency tier, using the three most common alternatives. Pricing sourced from the current public pages of each platform as of May 2026.

The Retell rate looks cheapest on paper, but Retell is an API infrastructure layer, not a full agency platform. You still need CRM, white-label configuration, campaign orchestration, and billing tooling on top. That adds invoices and developer time. The Vapi column is included because a significant portion of agencies migrating off Synthflow consider Vapi next, and the true all-in rate surprises them the same way Synthflow did. The 5-invoice problem is a Vapi-specific pattern worth reading before you land there.

What does a Synthflow migration actually cost?

The direct costs are the easy part. The hidden cost is time.

Per the Ringly 2026 Synthflow alternatives guide, agencies should plan 2 to 4 weeks for a full migration: export and setup (3 to 5 days), agent rebuild and parallel testing (1 week), client notification and phased cutover (3 to 5 days), and phone number porting (1 to 2 weeks, can overlap). Running both platforms during the overlap period means you are paying for two platforms simultaneously for roughly 2 weeks. Factor that in.

The founder-hour cost is usually the larger number. If you have 10 client agents to rebuild, budget 3 to 5 hours per agent for rebuild plus testing. That is 30 to 50 founder-hours for the rebuild alone, before you count porting, integration re-authentication, and client communication. At $150/hour opportunity cost, the real migration cost for a 10-client agency is $4,500 to $7,500 in founder time, plus whatever you pay for the overlap period.

The agencies that spend the least on migration are the ones that rebuild on a platform with a shorter setup path per client. Hermes is designed around the per-client workspace model, so each client gets an isolated workspace with its own billing, numbers, and agents. The rebuild for each client is faster than rebuilding from scratch because the workspace structure mirrors how you already think about your book.

How do I stop the Synthflow billing and get the account closed?

Based on the documented user experience pattern, here is the specific sequence that works:

1. Go to Settings, then Plan & Billing in the Synthflow dashboard. Look for a billing portal link or manage subscription button. If present, use it to downgrade or cancel the subscription.
2. If no cancel option appears, email support@synthflow.ai directly. Include your account email address, your subscription tier, the date you want cancellation to take effect, and a written request to delete your account and all associated data under GDPR Article 17 (or CCPA, if you are US-based). Request written confirmation.
3. Screenshot the cancellation confirmation or email thread. If you are later charged, this is your dispute documentation for your credit card company or Stripe chargeback.
4. If you are on an annual plan, send the cancellation email at least 30 days before your renewal date. Cancellation for annual plans takes effect at the end of the current contract period. Do not wait until 3 days before renewal.
5. Monitor your payment method for one full billing cycle after cancellation. If you see a charge you did not expect, dispute it immediately with your documentation.

"Plan 2 to 4 weeks for full migration — export flows, rebuild on new platform, run parallel testing, then switch. Migrating between voice AI platforms mid-stream is expensive and disruptive." [Ringly, 2026 Synthflow Alternatives Guide]

What should the next platform look like?

The Synthflow exit is an opportunity to fix the structural problems, not just swap one logo for another. Most agencies that migrate from Synthflow are doing it because one of three things broke: the price, the white-label isolation, or the stability. Picking a destination that solves all three, not just one, is how you avoid this post in 12 months for a different platform.

The checklist for the destination platform:

1. Single invoice. If the destination platform bills STT, LLM, TTS, and telephony on separate statements, you are recreating the opacity problem with a different vendor. One invoice, one rate, one reconciliation at month-end.
2. Published overage ceiling. You need to be able to price your retainers against a number that is fixed. An overage rate that varies with LLM model selection or voice catalog choices is not priceable. A flat $0.24/min ceiling that includes everything is.
3. Native white-label. Your clients should never see a vendor name in a ticket, an email, an error message, or a support thread. This is not a configuration toggle, it is an architecture question. If the platform was built with white-label as an add-on rather than a default, the Synthflow branding problem will eventually resurface with the new vendor's name.
4. Self-serve account management including deletion. You should be able to cancel, downgrade, and delete your account from the dashboard without a support ticket. Any platform that does not offer this is creating the same friction on exit that you are experiencing with Synthflow right now.
5. Published uptime history. Ask for the status page before you commit. The platform should have a public incident history, not just an uptime claim.

Hermes was built against this checklist. One invoice. Flat $0.24/min overage. Native white-label where your clients never see the word Hermes. Standard account management. The Agency plan is $699/month with 2,000 included minutes and 20 client workspaces. Starter is $149/month with 300 minutes and 3 workspaces, Business is $399/month with 1,000 minutes and 7 workspaces. The migration path from Synthflow to Hermes follows the same steps described above.

If you are also evaluating what happened to the platforms that stayed focused on agencies while Synthflow pivoted upmarket, the context lives in the Synthflow enterprise pivot analysis. And if the billing confusion you are leaving Synthflow over is a pattern you have seen on Vapi as well, the 50-client margin math post puts an exact dollar figure on how that plays out at scale.

Frequently asked questions

The migration in summary

Leaving Synthflow is harder than it should be. The exit checklist is: inventory and export before you do anything, export every agent as JSON, download all call logs, document every phone number, initiate porting at least 2 weeks early, build and test in parallel on the new platform for at least 5 business days, notify clients before cutover, and follow up with a written cancellation to Synthflow support to ensure the account is actually closed.

The agencies that have the cleanest exits are the ones that treat the migration as a client-delivery project, not a back-office task. It has a timeline, a client communication plan, and a go/no-go test before the switch. By builders, for builders. The platform you land on should not require this post in 12 months.