Complexity · Security · Full service

What happens when you call us.

Most organizations reach us after a standard product has already been tried. This page is what follows: how we work out whether we fit, what we build, and how far we go.

Talk to a specialist → See the capabilities
Usually the first sentence
“We have tried the standard tool. It does not do what we need.”
Step one

First we work out whether we fit.

Not every organization needs us, and we will say so. The first conversation is about three things, and it usually takes fifteen minutes.

01

The requirement

What the conversation has to do, which systems it touches, which channels are involved, and where the current solution stops working.

02

The constraints

Security, infrastructure, privacy, procurement and anything else that narrows the options. These usually decide the shape of the whole solution.

03

The responsibility

How much you want to run yourself and how much you want taken off your hands. That answer determines everything that follows.

Step two

Then we decide how far we go.

Not packages. Three levels of responsibility, decided by the requirement rather than by a price list. Most customers move up a level over time.

Platform

We provide the technology. You operate the solution.

  • When technology, infrastructure, security and control are the requirement
  • Private-cloud deployment available
  • Your team runs the conversations

Custom solution

Our platform combined with custom workflows, integrations, channels, infrastructure and development.

  • When an off-the-shelf implementation is insufficient
  • Built around your systems and journeys
  • We develop what does not exist yet

Full service

Technology alongside implementation, optimization and native-speaking human operations.

  • When you want one specialist responsible for both
  • Six native languages
  • From escalation to the full conversational journey
Step three

Then we build it, and where wanted we run it.

Because we own the platform, the sequence is the other way around from a SaaS implementation. Your requirements are not filtered through what the product happens to allow. They determine what gets built.

Where security or infrastructure requirements exist, they come first, not last. A private-cloud requirement is a starting point for us, not an exception to be negotiated.

Design
Conversational design, journeys, and the decision about what to automate and what deliberately not to.
Build
Platform configuration, custom development, integrations and the deployment your security context requires.
Launch
Implementation in your environment, with your systems, your channels and your team.
Run
Optimization and, where wanted, native-speaking operators handling the conversations in six languages.
Do you recognise this?

The sentences that bring organizations to us.

If one or more of these sounds familiar, your situation is probably not standard.

“Standard software does not support what we need.”
“Our security requirements are too demanding for a normal SaaS solution.”
“We require a private-cloud environment.”
“This needs to integrate deeply with our existing infrastructure.”
“Our customer journey is too specific for an off-the-shelf chatbot.”
“We need technology and humans to work together.”
“We need native customer service across multiple languages.”
“We do not want five vendors. We need one specialist for the whole challenge.”
To be straight about it

When you should not call us.

If a standard product covers your requirement, buy one. It will be cheaper and faster than anything we build. We are the right party when the interaction is too complex, too sensitive or too important to settle for that.

NoSelf-service signup. Every engagement starts with a conversation.
NoStandard packages. The requirement decides the scope.
NoFixed price list. Pricing follows the solution.
YesA straight answer in the first call about whether we fit.

Tell us what does not fit.

Fifteen minutes is usually enough to know whether we are the right party for your challenge, in either direction.

Talk to a specialist → info@conversation24.com
From our CEO
Most organizations that call us have already tried the standard product. That is not a failure of the software. It is a sign that the requirement was never standard.
Nick Blom CEO, Conversation24