Voice Agents for Renewal and Upsell Outbound: UK SaaS

A 30-person UK SaaS company had 44 contracts up for renewal in Q3. Their standard process was an email sequence starting 30 days before the renewal date. Renewal rate from that sequence: 17% of at-risk accounts. We moved the first voice call to 45 days before expiry, ahead of any email. Q3 renewal rate on the same contact list: 31%. The script did not change. The timing did.

Renewal call timing: why calling 14 days before the email sequence outperforms calling after it

Most SaaS renewal sequences start with email at day 30 and treat a voice call as a last resort at day 7. That order is backwards.

By the time a call fires after three emails, two things have happened: the customer has formed an opinion — usually negative — and the decision has often escalated to finance, who never touched the product and have no loyalty to it. Both conditions make the renewal harder to close.

Call first, at day 45. The voice call surfaces the actual objection before the email sequence can bury it. When the first email arrives at day 30, the customer has already spoken to a real voice and the email reads as a follow-up, not as the start of a process they did not consent to.

The 14-day-before-email framing refers to positioning the voice call 14 days ahead of where most SaaS companies start their email sequences (day 30). Whether your business runs the call at day 45 or day 60 matters less than the directional rule: call before email, not after.

A Gainsight analysis of renewal timing patterns found that outreach initiated in the 46–60 day window before renewal outperformed later outreach by 18 percentage points on at-risk accounts. Earlier contact gives you time to fix problems, not just accept answers.

One rule: do not open with the renewal. Open with a usage check-in — "I wanted to see how the team was getting on with [feature]" — and let the renewal surface from the customer's answer. Opening with "your contract is up for renewal" makes the customer feel processed.

Script design for renewal conversations: the 90-second call that surfaces objections before they become churn

The renewal call has one job: surface the real reason an at-risk account might not renew, while there is still time to do something about it. Not to close. Not to upsell. To diagnose.

The 90-second structure:

• 0–15 seconds: Identify and frame. "Hi [name], it's [agent] from [Company]. I'm calling to check in on how the team is getting on with the platform — do you have 90 seconds?"
• 15–45 seconds: One open question about usage or outcome. "Is there anything the team is finding tricky, or a workflow you're not getting as much from as you'd expected?"
• 45–75 seconds: Listen for flags. The signals that matter: "we're not really using it", "I've been meaning to call you about something", "the team has changed", "our budget's been reviewed".
• 75–90 seconds: Close with a clear next step. A callback with the account manager, a short feature walkthrough, or confirmation that a commercial summary is being sent.

The 90-second window is a promise, not a hard cut-off. Most calls that surface an objection run 2–3 minutes — that is the right outcome, the objection surfaced before the email sequence could bury it.

One thing that does not work: giving the agent rebuttals. Every time we have tested an agent with embedded counter-arguments in the renewal script, it makes the call feel adversarial. The agent's job is to listen, log, and route. Rebuttal is the account manager's job.

Upsell identification during renewal: the conversation signals that indicate readiness to upgrade

The renewal call is not an upsell call. It is an upsell intelligence call. Every call is transcribed and processed for three signals:

1. Team growth signal: "We've taken on two more people" or "the team is expanding" — seat-count upsell trigger.
2. Feature hunger signal: "I didn't know you did that" or "we use [other tool] for that bit" — tier or feature upsell trigger.
3. Workflow friction signal: "We do that manually" or "we export it and then..." — services or add-on trigger.

None of these are handled on the renewal call. The agent logs a structured note into the CRM — upsell_signal: seat_expansion — and the account manager picks it up before the commercial conversation.

One mistake to avoid: asking the voice agent to score upsell readiness numerically during a single call. The scoring models in ChurnZero's renewal intelligence tooling work because they process 90 days of engagement data. A single call gives you a directional signal. Treat it as a flag, not a forecast.

CRM trigger design: firing renewal calls from Xero contract dates or HubSpot deal close dates automatically

The trigger fires from a daily scheduled n8n workflow. Here is the HubSpot version, condensed to its functional nodes:

{
  "nodes": [
    {
      "name": "Daily Schedule",
      "type": "n8n-nodes-base.scheduleTrigger",
      "parameters": {
        "rule": { "interval": [{ "field": "days", "daysInterval": 1 }] }
      }
    },
    {
      "name": "HubSpot — Deals Due in 44–46 Days",
      "type": "n8n-nodes-base.hubspot",
      "parameters": {
        "resource": "deal",
        "operation": "getAll",
        "filters": {
          "closedate__gte": "={{ $now.plus(44, 'days').toISO() }}",
          "closedate__lte": "={{ $now.plus(46, 'days').toISO() }}",
          "dealstage": "closedwon"
        },
        "additionalFields": {
          "properties": ["dealname","closedate","hs_forecast_amount","associated_contacts","renewal_date"]
        }
      }
    },
    {
      "name": "Enqueue Outbound Call",
      "type": "n8n-nodes-base.httpRequest",
      "parameters": {
        "method": "POST",
        "url": "https://api.retellai.com/v2/create-phone-call",
        "body": {
          "from_number": "+441234567890",
          "to_number": "={{ $json.contact_phone }}",
          "agent_id": "agent_renewal_uk_v2",
          "metadata": {
            "deal_id": "={{ $json.id }}",
            "renewal_date": "={{ $json.properties.renewal_date }}",
            "account_name": "={{ $json.properties.dealname }}",
            "login_frequency": "={{ $json.product_login_count_30d }}",
            "open_tickets": "={{ $json.support_open_ticket_count }}"
          }
        }
      }
    }
  ]
}

For Xero: query the Invoices endpoint with DueDate in the 44–46 day window and Status: AUTHORISED, then look up the company in HubSpot by domain to pull the contact's mobile number.

The failure mode that kills this trigger: HubSpot's closedate field stores the original deal close date, not the contract renewal date. If your team has not recorded renewal dates as a separate custom property, the trigger fires on the wrong accounts. Audit and fix this first — our post on CRM pipeline hygiene for UK SMEs covers how to find and correct close date drift.

At-risk account segmentation: the three usage and engagement signals that change the renewal script

Not every account on the renewal list gets the same call. The script branches on three signals pulled from the product database 48 hours before the call fires:

Pre-call data injection matters. Our Voice AI and Document Analysis case study showed call scripts adapted to context data outperformed generic scripts by 22% on first-call resolution: a contact with two logins in 30 days needs a different opening line than one who logged in yesterday.

The segmentation data is injected into the Retell.ai call metadata at trigger time. The agent's system prompt includes conditionals keyed to those fields — if login_frequency is flagged LOW, the agent does not push for a renewal commitment on this call.

Objection handling for renewal calls: pricing pushback, budget freeze, and the champion who left

Three objections account for the majority of at-risk renewal calls. Each one requires a different agent response.

Pricing pushback ("it's too expensive"): the agent does not negotiate. It acknowledges briefly ("I hear you — cost is a real factor"), offers to send a commercial summary with current pricing options, and logs objection: pricing in the CRM. The account manager handles the negotiation.

Budget freeze ("our budgets are locked until April"): the agent asks when the review window opens, logs the date as a follow-up trigger, and offers a 30-day extension. Most SaaS platforms allow short extensions — the agent can offer this without escalation. A renewal that moves 30 days is not a loss.

Champion who left ("I'm not sure who handles this — Sarah left"): the highest churn signal in renewal conversations. When the named contact is no longer in post, close probability drops sharply. The agent logs contact_change: true and triggers an immediate notification to the account manager. Escalate it — every time.

The agent does not rebut any of these objections in real time. Surface, log, and route.

Human escalation triggers: when the renewal call surfaces a serious complaint and needs an account manager

The agent escalates to a live human in four situations:

1. The customer says "cancel", "terminate", or "we're leaving" — contract-level signals a voice agent should never handle alone.
2. The complaint names a specific incident ("the outage in June cost us a client") — requires a human who can acknowledge and offer redress.
3. The customer raises a legal or regulatory concern ("our solicitors have flagged something in the contract").
4. Contact change combined with a new decision-maker not in the CRM — the agent cannot build rapport with someone it has no context on.

For escalation, we use Retell.ai's built-in transfer function to hot-transfer the call to the account manager's direct line. If unavailable, the call goes to voicemail that fires a Slack notification within 30 seconds. See our post on voice agent transfer to human for the full handoff flow.

The ICO's guidance on AI in direct marketing is direct: AI-initiated calls must give the recipient a clear route to a human, and failing to provide it is a PECR compliance risk. The escalation trigger is not a UX nicety — it is a legal requirement.

What changed in 2025–2026: AI-native renewal intelligence in ChurnZero, Gainsight, and HubSpot Breeze

Three platform developments in the past 12 months changed what is practical for UK SaaS renewal teams without dedicated CS platforms.

ChurnZero's AI Renewal Assistant (released Q4 2025) surfaces churn signals 90 days out and recommends intervention type based on account health score. It now exposes a webhook that fires when a renewal risk threshold is crossed, so the signal-to-call pipeline can run without a CSM manually reviewing the health dashboard each morning.

Gainsight's Timeline AI (general availability January 2026) generates pre-call briefs from account history, support tickets, and product usage data — useful if you run a managed CSM team alongside voice agents for high-value accounts.

HubSpot Breeze added a Customer Agent feature in late 2025 that identifies renewal risk from deal and contact activity. The HubSpot Breeze API documentation covers the deal-risk scoring endpoint. For UK SMEs running HubSpot as their only CRM, it removes the need for a separate customer success platform.

One counterpoint worth reading: a Harvard Business Review analysis of AI in customer retention argues that AI renewal tools perform best when a human reviews AI-flagged accounts before outreach fires — not when fully automated end-to-end. That holds in our experience for high-ACV contracts above £50k ARR. Automate identification and first touch; route high-value renewals to a human for the close.

Good / Bad / Ugly: three renewal outbound programmes and their 90-day contract renewal impact

Good — SaaS HR platform, 85 contracts, day-45 pre-email call Renewal rate on at-risk accounts moved from 22% to 38% in one quarter. The trigger fired from HubSpot renewal_date properties, the script branched on login frequency, and escalation routed to two account managers via Slack. Cost per renewal saved: £180 in voice agent calls. Cost of a churned contract: £8,400 ARR average. The economics were not close.

Bad — SaaS finance tool, 120 contracts, day-14 post-email call Renewal rate held flat at 19%. The call fired after three emails — most customers had already decided. The agent was trying to reopen accounts that had mentally churned two weeks earlier. Timing was the failure, not the script. They chose not to rebuild the trigger logic, and it cost them the quarter.

Ugly — Professional services marketplace, 60 contracts, no segmentation The agent called every account with the same script regardless of usage, support status, or contact history. Three customers with open support tickets received renewal calls from an agent with no visibility of those tickets, and were offered contract extensions in the same breath. One account escalated to a formal complaint. One threatened to contact the ICO. Adding the support-ticket filter to the segmentation logic took two hours. Not adding it first took three customers to the point of formal action. Check PECR and TPS compliance for UK AI outbound calling for the compliance gates that should run before any renewal call fires.

The pattern across all three: timing and segmentation outweigh script quality by a significant margin. A well-timed call with an average script outperforms a polished script fired at the wrong moment to the wrong contact — every time.