Customer support · Production

Cyclr's embedded iPaaS drives a 25% increase in sales for Neural Voice's AI conversation platform

The problem

Neural Voice had to build integrations from scratch every time they wanted to connect their AI conversation platform to a new customer's system, consuming engineering resources that could otherwise go toward core product development.

First attempt

Prior to Cyclr, even simple integration changes required raising internal tickets, holding meetings, having engineers drop current work to code backend changes, update the frontend, and test — a process Neural Voice estimates would have cost around £2,500 per change.

Workflow diagram · grounded in source
1
AI Conversation triggers webhook
trigger
“with the Webhook being triggered by the AI Conversation”
2
Store data and upload transcript
integration
“Cyclr powers Neural Voice's AI Conversation with a workflow that stores the data in a CRM, uploads the conversation transcript and sends a message to the user. This is achieved using Webhooks that integrate Neural Voice with other system…”
3
Automated messages sent to user
output
“Automatic email or WhatsApp messages are then sent, with all the relevant information, without the need for any manual intervention”
4
Template copy for new customers
integration
“When a new customer signs up with them, they can simply copy the original template and customise it to suit the customer's exact requirements”
Reported outcome

Using Cyclr resulted in a 25% increase in sales for Neural Voice, saved days to months of engineering work, and allowed the team to focus on core product features while delivering new customer integrations within weeks.

Reported metrics
Sales increase25%
Engineering work saveddays (and in some cases months) of work
Estimated cost of previous manual integration change£2,500
Time to deliver new integrationa matter of weeks
Show all 8 reported metrics
sales increase25%
engineering work saveddays (and in some cases months) of work
estimated cost of previous manual integration change£2,500
time to deliver new integrationa matter of weeks
time to market for enterprise travel integrationa matter of a week
new connector build turnaroundtypically in the region of two weeks
team training time for Cyclraround three hours
time to achieve integration change with Cyclra matter of minutes
Reported stack
CyclrHubSpotBirdSalesforcePipedriveOpenAI APIWhatsApp
Source
https://cyclr.com/case-studies/neural-voice-case-study
Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

Using Cyclr resulted in a 25% increase in sales for Neural Voice, saved days to months of engineering work, and allowed the team to focus on core product features while delivering new customer integrations within weeks.

What tools did this team use?

Cyclr, HubSpot, Bird, Salesforce, Pipedrive, OpenAI API, WhatsApp.

What results were reported?

Sales increase: 25%; Engineering work saved: days (and in some cases months) of work; Estimated cost of previous manual integration change: £2,500; Time to deliver new integration: a matter of weeks (source-reported, not independently verified).

What failed first in this deployment?

Prior to Cyclr, even simple integration changes required raising internal tickets, holding meetings, having engineers drop current work to code backend changes, update the frontend, and test — a process Neural Voice e…

How is this customer support AI workflow structured?

AI Conversation triggers webhook → Store data and upload transcript → Automated messages sent to user → Template copy for new customers.

Related customer support cases