kelfora
Conversational agents

We

build

AI

that

acts

Visit Forno Roma Visit Rent Residence Hub
Loading assistant…

Why you should consider to add an agent?

12.3% vs 3.1%
conversion rate for shoppers who engage an AI agent, vs. those who don't
35% vs 3–5%
cart recovery rate via AI chat, vs. traditional email retargeting
92%
small businesses already using AI tools who report a revenue gain from it

Published third-party industry figures, not Kelfora's own client results — we're early. Ranges reflect variance across implementation quality and vertical; treat as directional evidence the category works, not a guarantee. Full sources below.

How it works for you

01

Send your specs

API docs and scoped read access only under NDA. No call required.

02

We build, test & and provide embeddable widget

One adapter for your backend, correctness-tested against it live — no mocks.

03

You embed the widget into your website

Dropped into your site, configure secret token. We host the agent, models, and server.

04

Customers act, not just ask

Your assistant adds to cart, checks availability, hands off to your existing payment processor.

Under development

A2A (Agent to Agent)

Currently we building infrastructure to make communication between agents.

Questions you might have

Does this replace my staff or phone line?

No — it handles the routine, repetitive part (answering "what's on the menu," taking an order, checking if a date's available) so your staff aren't interrupted by it. Anything unusual still comes to you.

What if it gets an order wrong?

It only acts on your actual live catalog and pricing — it can't invent items or prices that don't exist. Anything involving payment or a final confirmation is a separate, explicit step the customer has to approve, not something it does silently.

Does it ever see or store payment/card details?

No. Checkout and payment always hand off to your existing payment processor — this system never touches card numbers or billing details at any point.

Can it be tricked into leaking how it works, or backend access?

It's built to refuse attempts to get it to reveal its system instructions, the tools it's using, or any backend credentials — tested against direct attempts to extract each of those. This is an active area of hardening rather than a one-time checkbox

What happens to my customers' data?

Conversations are used only to answer the customer in the moment — to look up your menu or availability and complete their request. This is still an early pilot, so I don't yet have formal compliance certifications (SOC 2, GDPR/CCPA documentation, etc.) to offer — happy to be fully transparent about that upfront rather than overclaim it, and can work with you on data-handling terms specific to your business if that matters for your customers.

How long does setup take, and what do I need to provide?

Just access to your existing product/menu or listings data (read-only) — no rebuild of your site or backend required. Setup is typically quick since it plugs into what you already have.

Is there a contract, or can I stop anytime?

No lock-in — it's month-to-month, and you can turn it off anytime.