Case Study · Atlas24h

Sales chatbot · Q3 · July–September 2026

3,751 contracts.
Every one verified in the client's system.

A bot that answers is a cost. An agent that closes the sale is a revenue line.

In Q3 2026, one sales chatbot for Atlas24h booked 3,751 contracts and €249,330, every contract checked in the client's own system. Alongside it run a sales voice agent and a service voice agent; they add volume but do not count toward this figure and are not API verified. Volume followed the travel season and eased into autumn. Conversion did the opposite: it climbed from 61% to 77%, because the agent kept getting better at turning a qualified lead into a confirmed sale.

Download PDF

€249,330

verified revenue

3,751

verified contracts

28,791

AI conversations

161 h

human work freed

Production data · July–September 2026 · Chatbot conversions verified through the Atlas production system

Before

People at every step

  • –The call center took every sales and service call
  • –Web chat did not complete purchases
  • –Contract change requests handled manually
  • –Problem reports arrived unevenly, without structure
↓

After

Three AI channels in production

  • ✓Chatbot qualifies, sells and collects contacts
  • ✓Sales voice agent completes orders without an agent
  • ✓Service voice agent resolves part of the calls on its own
  • ✓1,750 requests collected in structured form, ready to process
  • ✓Every chatbot contract verified in the Atlas database

Three channels, one picture

01

Chatbot

Drives the purchase on the site and collects contacts.

02

Sales voice

Takes calls with purchase intent and completes the order.

03

Service voice

Checks packages, answers and collects requests.

04

Requests

Problem reports and contract changes go to admin in structured form.

05

Verification

Chatbot contracts are verified in the Atlas database.

Production results

Verified contracts from the chatbot, month by month

1,705

Jul

1,572

Aug

474

Sep

Lead → contract

61.4%→77.1%→73.4%

Volume follows the travel season. Roadside assistance sells hardest in summer, when everyone is on the road, so the drop from 1,705 contracts in July to 474 in September is the expected seasonal curve, not a drop in performance. The number that matters is conversion, and it rises: lead to contract climbs from 61.4% in July to 77.1% in August, settling at 73.4% in September. Across the quarter that is roughly two thirds of qualified leads closed; the monthly trend shows the agent getting better at closing the leads it gets. Three months: 3,751 verified contracts and €249,330 in revenue from the chatbot alone.

Quarterly sales funnel (chatbot)

14,933conversations
5,461qualified leads
3,751verified contracts

68.7%

lead → contract, quarter

Two paths to a sale

Direct purchase

1,719 orders in the chatbot

1,374 verified contracts

Follow-up

contact left, purchase later

2,377 verified contracts

3,751

verified contracts

Two thirds of contracts do not come from a completed chatbot order, but from users who left their contact and bought later through the team, the website or a branch. The chatbot's value is as much in collecting contacts as in closing the sale.

The bigger picture

466→1,284

161 hours of human work freed across three months, with 1,750 requests collected in structured form.

Chatbot conversions and revenue are verified in the Atlas database. Sales-line value and time saved are conservative estimates, not verified the same way.

“We expected a chatbot. We got a system that changed how we operate: 3,751 verified contracts in a single quarter, checked in our database rather than estimated.”

Marios Skutelis

COO, Atlas24h

One quarter. Three channels. Checked numbers.

Every chatbot contract was checked by calling the Atlas API. Where a figure is not verified that way, it is clearly marked.

Bring us a real process

See what this looks like on your data.

Show us where customers drop off and where work piles up. We'll map the process, identify what can be automated and define how the result is measured.

Talk to us →