Financial services

    Renewal season, without renting a call centre for it

    An insurance book is decided by a handful of short conversations: the renewal nobody got around to, the premium that bounced, the quote that went quiet. Convershake runs those calls as deterministic outbound campaigns, in the languages your policyholders actually speak, and hands anything that needs judgement to a licensed person.

    Renewal line · Spain · ES/CACatalan

    He recibido la carta de renovación, ¿sube el precio?

    Su renovación es el 12 de septiembre y el precio de la carta es el que se aplica.

    Puc canviar la cobertura?

    Això ho ha de veure un company amb llicència — li passo la trucada.

    What actually breaks first

    The calls that protect a book are individually small, uniformly urgent, and arrive in bulk.

    01

    Renewals cluster, teams do not

    A portfolio renews in waves. Staffing for the wave is expensive, staffing for the average means the tail of each wave goes uncalled — and the uncalled tail is where churn lives.

    02

    A lapse starts as an admin failure

    A card expired, a mandate failed, a payment date moved. One short conversation fixes most of them; no conversation turns them into a lapsed policy and a re-acquisition cost.

    03

    Quotes go quiet and stay quiet

    A quote that gets no follow-up is a marketing spend that produced a PDF. Calling every one of them back is exactly the work nobody has capacity for.

    04

    Every market words it differently

    Disclosure requirements, contact windows and the language a policyholder expects change per market. Encoding them per campaign, by hand, is where the script drifts from the policy.

    Is that your shape of business?

    Is this you?

    Retention is a calendar problem before it is a pricing problem.

    This is you if

    • A portfolio whose renewals cluster into weeks the team cannot fully staff.
    • Lapses that start with one failed premium collection and end as a lost policyholder.
    • Quotes that go quiet, and no capacity to call every one of them back.
    • Several markets or brands, each with its own language and disclosure requirements.
    • A compliance function that has to evidence what was said about a policy — every call, in full.

    This is not us

    • Advice, suitability or cover recommendations — those stay with your licensed people.
    • Claims decisions and first-notification-of-loss handling — those belong with your claims people.
    • Anything where an automated conversation would be deciding something about someone's cover.
    See the calls we would actually run

    The campaigns we run

    Retention campaigns protect the book; revenue campaigns rebuild it. Both are authored flows, versioned and reviewable, and both stop at the advice boundary.

    Runs from
    Watch one get built, tested and launched

    04 · See it work

    From an idea to a live campaign — in one sitting

    Product interface shown as high-fidelity representation with synthetic data; the closing call is real recorded product audio from our demo tenant. Music: “Deliberate Thought” — Kevin MacLeod (incompetech.com), CC BY 4.0.

    What the platform enforces

    Product behaviours. The rules themselves stay yours.

    No advice, structurally

    Cover, price and suitability questions transfer to a licensed person rather than being answered.

    Disclosures as steps

    Required openings, including what kind of call this is, are flow steps stated the same way every time.

    Approved wording only

    Policy terms are stated as approved; forbidden wording is blocked in the flow and flagged in review.

    Contact rules and opt-outs

    Windows, attempt caps, suppression and opt-outs configured per market and enforced by the campaign.

    Sensitive data

    PII and PCI values masked in transcripts and logs; anything needing a secure channel is flagged for one.

    Audit pack per call

    Recording, transcript, flow version, policy version and tool calls — on every call.

    Verify it before you trust it

    Four things you can confirm yourself — the certificate, the method, and where this is built.

    BM Certification — ISO 27001

    ISO 27001 certified

    Certified by BM Certification. Data encrypted in transit and at rest.

    0%

    100% of calls audited

    Every call is scored against the same criteria — sampling never enters it.

    v4v5

    Deterministic by design

    Authored, versioned flows, with the running version recorded per call.

    Riga, EU

    Built in the EU

    Founded and headquartered in Riga, Latvia, for European multi-language markets.

    So how would we start? →

    From first conversation to live campaign

    One paid production pilot, built and bought in the same six steps — with a decision at the end of it. The numbers are a conversation; the shape never changes.

    01

    Pick one campaign

    One call type, one market, one owner accountable for the number it moves. Not a platform rollout.

    02

    Agree what winning means

    Success criteria and the ROI definition are written down before anything dials — never reconstructed afterwards.

    03

    We author the flow

    Your campaign, in the full language set the market requires. Your compliance function reads every step before it runs.

    04

    Hear it before it dials

    Simulated runs and live test calls. The version you approve is the version that runs — reviewed and numbered.

    05

    Run it paid, in production

    Real list, your contact rules, per-second billing — and no charge for ringing, failed connects or no-answers.

    06

    Decide at the review

    Convert, expand, repeat, pause or stop — against the criteria written at the start, with every call as evidence.

    Concurrency, included minutes and integration scope are set per tier, so the bill tracks what you actually run. We will tell you before the pilot which of those limits your campaign is likely to touch.

    Fits the stack you already run

    No rip-and-replace, no migration project. Convershake connects to your CRM, your telephony and your payment tools, takes its call lists from them, and hands every outcome straight back — so campaigns show up in the systems your teams already live in.

    CRM & servicing
    Telephony & CCaaS
    Convershake
    Identity & access
    Payments

    Works with

    VCC LiveGenesysEnreachFive9NICETwilio FlexSalesforceHubSpotZendeskServiceNow

    And if your system is not on the list, it connects the same way — through your carrier or our open API.

    Questions we get from this segment

    Short answers, including the ones where the answer is no.

    Bring us the campaign you would run first

    We will tell you what is enabled in your market today, what has already carried production calls, and what it would take to run it.