A shopper asks in a DM whether it comes in blue. Answering needs the catalogue, the stock position and their order history. By the time someone has checked all three, they have gone.
When the answer does arrive, it arrives as a link — asking someone who was ready to buy to start again somewhere else. Every handoff between the question and the checkout loses people who had already decided.
Ephanti answers from your connected commerce data and completes the purchase where the question was asked. In-channel where the channel supports payment, at a prepared checkout with the cart already built everywhere else.
Stock, price, promotion eligibility, delivery date, compatibility with what they already own. Each lives somewhere different, and the shopper is waiting in a chat window.
DM to link, link to site, site to checkout. Each step loses people. Somebody who was ready in the conversation arrives at the product page as a cold visitor.
Three emails and a code. It works on the people who were only waiting for a reason, and teaches everyone else to abandon deliberately. The shopper who left over a delivery date gets the same code, which answers nothing.
It is available two miles away and the website says out of stock. Nobody can see across the two, so the sale goes to whoever can.
Eleven at night, a weekend, a launch. The questions that decide a purchase arrive when the team that can answer them is not working.
Shoppers who had already decided and left anyway. Margin given away as discount to people who did not need one. Stock sitting in a store while the website says no.
Intent understood against your connected catalogue — the variant, the size, the use they have in mind, what they already own.
Stock, price, promotion eligibility and delivery dates read from your connected commerce systems, not guessed from a script.
Items added, alternatives offered when something is unavailable, and the order confirmed without leaving the conversation.
Payment in-channel where the channel supports it; a prepared checkout with the cart already built everywhere else. Nothing is re-entered either way.
You decide how far any of this goes on its own — suggest something and wait, do it and tell you, do it once someone approves, or pass it straight to a person. Set per solution, and changeable.
A shopper messages on Instagram at ten past nine on a Sunday: “do you have the walking boot in a 42, and would it get here before Friday?”
| How it goes today | With Ephanti | |
|---|---|---|
| The question arrives | It sits until Monday. Someone replies with a link to the category page. | Answered in the thread: that variant, that size, in stock, with the delivery date for their postcode. |
| They have a second question | “Are they waterproof?” goes to a different person, who checks the product page. | Answered from the catalogue attributes, alongside the two alternatives that also fit the requirement. |
| They decide | They are sent to the site, where they search for the product again and abandon at the size selector. | The cart is built in the thread. Payment completes in-channel, or at a prepared checkout with everything already in it. |
| The order exists | If it exists at all, it exists without any of the conversation behind it. | Written to your store as an ordinary order, with the conversation attached to the customer record for whatever happens next. |
This walkthrough needs a recorded demonstration behind it — the same sequence, end to end in the actual interface. One approved customer result naming the workflow and the measurement period.
You start with one thing, not the list. Each is a job somebody in your business already owns, measured by a number they are already judged on. The brief for each sets out exactly what it covers and what it needs from your systems.
Completed purchases from assisted conversations
Read the brief →Add-to-cart rate
Brief in productionNot sure which? Abandoned Cart Recovery if there is already a leak you can measure. Conversational Commerce if pre-purchase questions are the bottleneck.
| Solution | Who owns it | What it moves | Detail |
|---|---|---|---|
| Conversational Commerce | Head of e-commerce | Completed purchases from assisted conversations | Read the brief → |
| Abandoned Cart Recovery | Head of e-commerce | Recovered carts | Read the brief → |
| Product Discovery | Head of e-commerce | Add-to-cart rate | Brief in production |
| Gift Services | E-commerce or merchandising lead | Gift-attributed revenue | Brief in production |
| Store Stock & Click-and-Collect | Retail operations lead | Store-fulfilled revenue | Brief in production |
| Direct BookingsHospitality | Revenue or commercial manager | Direct booking rate, OTA commission avoided | Brief in production |
| Donation ConversionNonprofit | Development lead | Completed gifts | Brief in production |
Connects to: your commerce platform, catalogue and inventory, payment provider, and the channels you sell in.
Ephanti can be all of it. Customers, conversations, campaigns, orders and cases live here, so you can start without connecting anything first.
Keep them. Your CRM, store or service desk stays the one that counts. Ephanti reads what it needs and writes back what it changed, and nothing moves.
The common case. Service can run in Ephanti while sales stays in your CRM. We agree upfront which system owns which information, so you never end up with two versions of the same customer.
The solution costs the same whichever way you run it. Connecting your systems and setting it all up is quoted separately, because that part genuinely differs between businesses.
No. Your store stays in charge of the catalogue, the stock and the orders. Ephanti sells against it and writes the order straight back.
In the thread, in the channels that support it. Elsewhere the shopper is taken to a checkout with the cart already built.
It says so and brings in a person, with the conversation and the basket attached. It does not invent an availability or a delivery date.
No. The discount rules are yours, including having none. Answering the objection is often what recovers the cart, and it costs nothing.
The question is asked where you cannot sell, and answered where the shopper has already stopped looking.