A shopping assistant inside your own app.
An AI shopping assistant inside your own app
It opens over your iOS, Android or web app, searches your catalog and adds to the cart your app already has, in your colours and your words.
Hephon Market
Voice assistant · 0:05
Assistantأبشر! حليب المراعي، بيض ١٥ حبة، وخبز عربي. أضيفها لك؟Sure! Almarai milk, 15 eggs and Arabic bread. Shall I add them?
Shopperإيه، أضفهاYes, add them.
Assistant
Almarai Full Fat Milk 1 L
Hawa Brown Eggs, 15
Al Forno White Pita 410 g
In short
Hephon Commerce puts an AI shopping assistant inside a retailer's own app and website, with SDKs for iOS, Android, React Native and Flutter and a script tag for the web. Shoppers ask in Arabic or English; the assistant searches the live catalog with their branch's prices and adds products to the cart the app already has.
The app keeps its checkout, payments and delivery slots. The retailer controls the assistant's colours, corners, light or dark mode and wording, and nothing is ordered without the shopper's confirmation.
Updated
Built into your app, not bolted on.
Your developers add the SDK; the assistant brings search, product cards, the basket and voice.
- iOS, Android and web
- SDKs for native, Flutter and React Native apps, and one script tag for a website. Chat, voice and product cards come with it.
- Your cart, not ours
- Every add and remove is sent to your app, which updates its own cart and checkout as usual.
- Your look
- Colours, corners, buttons and fonts from your dashboard, overridable by your app at launch.
- Knows the shopper
- A signed launch token tells the assistant who is shopping, without another login.
- Voice included
- Dictation, voice notes and hands-free live voice, in Arabic and English.
- Opens where it helps
- From a button, the search bar, a product page or a recipe: wherever your shoppers get stuck. Your app can send it a question and follow what it does.
A shopper in your app, start to finish.
A budget, a list, a switch to Arabic, and your own checkout at the end.
- Shopper:
Birthday party for 15 kids, need snacks and drinks, under 300 AED
- Assistant:
Here is a party list within 300 dirhams: juice boxes, crisps, popcorn, cups and plates.
One row per item. A product shows only if it fits the budget with the rest of the list.
- Shopper:
add the juice, 2 packs
- Assistant:
Added 2 packs of juice to your cart.
Your app receives the change with its own item id and updates its cart badge.
- Shopper:
عندكم كيك جاهز؟
Do you have ready-made cake?
- Assistant:
إيه، هذي الكيكات المتوفرة في فرعك:
Yes, here are the cakes your branch has:
The shopper switched to Arabic, so the assistant did too.
- Shopper:
(taps Checkout)
Your app opens its own checkout with these lines. Payment, slots and loyalty stay in your app.
How does the SDK fit into my app?
There is one SDK per platform: a Swift package for iOS (UIKit and SwiftUI), a library for Android, a package for React Native with an Expo plugin, and a package for Flutter. A website adds one script tag. Each one opens the same assistant for one shopper, loads it before the shopper taps so it appears at once, and keeps it loaded between opens.
The assistant runs in a web view on your store's chat page, managed by the SDK. Everything it does to the basket comes back to your app as typed callbacks in your own product ids, so your developers handle a few events instead of building a chat, a search and a product card from scratch. The Install screen in your dashboard shows the code for each platform with your values filled in, and a test code to try it.
How does the basket stay in sync with my app's cart?
Every product has two of your ids: its id in the shopper's store, which your cart lines are keyed on, and its id in your catalog. When the assistant or the shopper adds, changes or removes a product, your app receives both ids and the quantity, and updates its own cart. Your app can also send its cart to the assistant, so a product the shopper added from your own screens is already in the basket when they open the chat. When the shopper taps checkout, your app opens its own checkout with the basket lines.
It shops inside your app. Checkout stays yours.
Your cart, kept in step
The assistant finds products and fills the basket. Your app keeps the checkout, payments, delivery slots and loyalty it already has.
- Both of your product ids on every change, so carts match exactly
- Works the same in Arabic and English
Lunch boxes for 3 kids this week
Added 9 items to your cart
The store your app is showing
Prices and stock come from the branch the shopper is shopping in, so the assistant never offers what that store cannot deliver.
Delivering from your nearest branch
Almarai Full Fat Milk 1 L$1.70Hawa Brown Eggs, 15$2.99
Hawa Chicken Breast 650 g$10.25Who controls how it looks?
You do. In your dashboard you set the colours, corners, button shapes, font, header and the assistant's name, and whether the chat is light, dark or follows the device. Your app can override any of these when it opens the chat, so the assistant matches the screen it sits in, and it can switch the chat to dark mode when the app does. Colours are applied so that text stays readable on your brand colour in both light and dark mode.
Can my app change what the chat says?
Your app can replace the welcome title, the placeholder, the button labels and the assistant's name, and set the suggestions on the welcome screen. Wording goes through the SDK's bridge only, never through the chat's address: an address can be edited by anyone, while the bridge only accepts your app and the websites you allow. Your app can also send the assistant a question, open the basket, start a new chat or set its language.
What can we measure?
Your dashboard shows conversations day by day, what shoppers search for, the searches that found nothing, and the languages and departments they ask about. When your platform reports its orders through our API, the Conversions view shows which orders the assistant helped with and the revenue from them. Inside your app, the SDK tells you what the chat is doing (open, busy, items in the basket) and how long it took to open, for your own analytics.
Do shoppers need to log in again?
No. Your server signs a launch token for the shopper your app already knows, and the assistant opens for that shopper and their branch. Conversations and baskets then follow the shopper across devices. You can require a launch token for every chat, so no one can open your assistant anonymously.
What it does not do
- It does not take payment or replace your checkout. Your app's checkout, payment methods, delivery slots and loyalty stay as they are.
- It never places an order without the shopper's confirmation.
- It does not draw native screens you restyle line by line. The chat is a web view managed by the SDK, styled through the appearance settings.
- It does not use the microphone unless your app asks for the permission. Without it, the chat works by text.
When Hephon Commerce is not the right fit
- Your developers cannot ship an app update. The SDK is a few lines, but it goes out in a release of your app. The website script or WhatsApp is a faster start.
- You need a support bot for returns and complaints rather than a shopping assistant. This is built for shopping from a catalog.
- You have no online catalog with prices and stock per branch.
On your website, one line.
The same assistant as a chat button on any site, with the same catalog, basket and look.
<script src="https://commerce.hephon.ai/widget/v1.js"
data-org="your-store" async></script>Live in three steps.
- 1
Connect your catalog
From Shopify, WooCommerce, a product feed or our API, with each branch's prices and stock, keyed on the ids your app already uses.
- 2
Add the SDK
The Install screen shows the code for your platform with your values filled in, and a test code to try it in a build.
- 3
Style it and ship
Set the look and wording in your dashboard, test it on your own catalog, then release it in your next app update.
In-app assistant, answered.
See it on your own catalog.
We set up a demo with your products, your branches and your shoppers' languages.
