18% Conversion Lift with Amazon Connect Customer Outbound

A leading SMB financial services company built its business on speed — qualifying small business financing leads and connecting them with the right funding partner before a competitor could. But its sales team worked across two disconnected systems: Salesforce for lead management, Five9 for outbound calling. Every interaction meant bouncing between the two, logging the same information twice, and losing agent time that could have gone toward the next prospect.

D3Clarity partnered with the company to rebuild that workflow around Amazon Connect Customer, weaving Salesforce data directly into the agent's contact center experience and automating the outbound process end to end — from call classification and revenue-based routing to a live handoff with an external funding specialist. The result reshaped how the sales team spent its time and how much visibility leadership had into every call.

CASE STUDY
7-MINUTE READ
Business case study showcasing conversion improvement
The Challenge at Hand

Two Systems, One Fragmented Workflow

A leading SMB financial services company helps connect small businesses with financing opportunities, qualifying leads and matching them with funding providers across the U.S., Mexico, and Puerto Rico. Its sales organization ran on two disconnected systems: Salesforce for lead management, Five9 for outbound calling.

At a Glance

  • Client: A leading SMB financial services company (name withheld)
  • Industry: Financial Services
  • Platform: Amazon Connect Customer (Outbound Campaigns, Contact Lens, Salesforce integration via Amazon API Gateway)
  • Key Results: 18% increase in lead conversion · 38% improvement in agent efficiency · 100% QA coverage (up from <5%) · 4–6 week implementation

Completing a single customer interaction meant constant switching. Agents pulled up a lead in Salesforce, jumped to Five9 to place the call, returned to Salesforce to log notes, completed forms, and scheduled follow-up — for every contact, every time.

Nearly 38% of agent time went to non-revenue-generating administrative work instead of live prospect conversations.

Quality visibility was just as thin. Less than 5% of interactions were ever reviewed, and the client's per-seat contact center licensing model kept adding cost without adding insight.

The client didn't just need a new dial tone. It needed Amazon Connect Customer to become the primary workspace for front-line agents, while Salesforce stayed the system of record behind it.

Innovative Solutions Unleashed

Bringing Salesforce Into the Amazon Connect Customer Workflow

D3Clarity designed and implemented an Amazon Connect Customer outbound solution — the same kind of outbound campaign management D3Clarity has applied in other outbound campaign modernization engagements — that brought the client's Salesforce-driven sales workflow directly into the agent's screen, as part of D3Clarity's broader Customer Experience practice.

Rather than sending agents back to Salesforce for every task, D3Clarity configured Amazon Connect Customer agent views to surface the Salesforce data and prompts each lead needed. The workflow could store up to 30 Salesforce attributes tied to a lead, with up to 20 of those editable by agents and written straight back into Salesforce. Agents captured and updated customer information as part of the call itself, rather than running a parallel Salesforce session.

Amazon API Gateway and Salesforce-provided JSON objects handled the connective tissue — passing the information needed to launch an outbound interaction and build the matching customer profile inside Amazon Connect Customer. Lead assignment, customer engagement, and post-call follow-up now moved through one continuous flow instead of two disconnected systems.

A Smarter, Automated Outbound Process

The new workflow automated the outbound calling process end to end. Amazon Connect Customer confirmed agent availability, placed the call, and used machine-learning-based call classification to tell a live person from an answering machine — the kind of automated call handling that also supports compliance with regulations like the Telephone Consumer Protection Act. Calls a person answered were routed to an available agent by revenue-based priority; calls that went unanswered triggered automated follow-up messaging instead. Both English and Spanish agent experiences were supported, with WhatsApp used for Spanish-language follow-up.

D3Clarity configured revenue-based prioritization and callback logic so higher-value opportunities got faster attention, while lower-priority leads still followed a structured, repeatable cadence. New leads took priority over callbacks within the same revenue tier, and automated callback scheduling ran within defined business hours. A largely manual outbound process became a consistent, rules-based one.

Once an agent qualified a lead, the solution supported a live handoff to an external funding specialist — bringing the right expert into the conversation without making the customer restart.

Redesigning the Agent Experience Around Amazon Connect Customer

The bigger shift wasn't a feature — it was where agents actually worked.

Instead of treating Salesforce and Amazon Connect Customer as two applications agents had to run side by side, D3Clarity built a CRM-embedded agent workflow: Salesforce attributes and prompts lived inside the Connect Customer interaction itself, and agents could edit that information and send it back to Salesforce without ever leaving the call.

The result was a contact center built around how the sales team actually worked — not simply a swap of one telephony platform for another.

Quality, Reporting & Visibility

D3Clarity configured Amazon Connect Customer Contact Lens for call recording and transcription in English, Spanish, and Brazilian Portuguese, storing recordings in Amazon S3 and feeding them straight into the client's existing QA process.

The solution also introduced reporting on outbound performance indicators the client hadn't tracked before:

  • Speed to first contact attempt
  • Absolute contact rate
  • Abandon rate
  • Speed to answer
  • Bounce rate when an interaction had to move to another agent

Average handle time landed at 3 minutes and 2 seconds per interaction — a clear, trackable benchmark the client's previous under-5%-reviewed QA process couldn't have produced.

Transformative Results Achieved

18% increase in lead conversion. The redesigned outbound process helped the client reach qualified prospects faster, contributing directly to the lift.

38% improvement in agent efficiency. Automating outbound dialing and cutting the need to switch between Salesforce and the contact center platform gave agents back time for revenue-generating conversations.

100% QA coverage, up from under 5%. Amazon Connect Customer Contact Lens now captures and reviews every recording and transcript.

50% of implementation costs offset through AWS Migration Acceleration Program (MAP) funding, which helped make the transformation financially feasible.

4–6 week implementation. D3Clarity completed this legacy contact center migration — from Five9 to a modern, Amazon Connect Customer–based outbound engagement solution — in a rapid deployment window.

Ready to Unify Your CRM and Contact Center?

Talk to D3Clarity's Amazon Connect Customer team about what a rapid, MAP-funded migration could look like for your outbound program.

FAQ

How long did the Amazon Connect Customer outbound migration take? D3Clarity moved the client from Five9 to Amazon Connect Customer in 4–6 weeks, from legacy platform to a fully automated outbound solution.

How did the migration affect lead conversion and agent efficiency? The client saw an 18% increase in lead conversion and a 38% improvement in agent efficiency after the new Amazon Connect Customer workflow replaced the manual Salesforce/Five9 handoff.

How does Amazon Connect Customer stay connected to Salesforce? Amazon Connect Customer syncs with Salesforce through Amazon API Gateway, storing up to 30 Salesforce attributes per lead — 20 of them editable by agents — so information captured in a call writes straight back into Salesforce.

How did AWS funding help pay for the project? The AWS Migration Acceleration Program (MAP) covered 50% of the implementation cost, helping make the transformation financially feasible for the client.

18%

increase in lead conversion

38%

improvement in agent efficiency

100%

QA coverage

Meet the team

Data & AI
Secure Cloud