Full ownership
The code, the prompts, the data and the roadmap are yours.
Details
Nobody else decides what ships next or when.
About 30 minutes, on your own catalogue.
Updated
Build in-house if you have an AI and engineering team, want to own every part of the assistant, and can keep it tested as models and your catalogue change.
Build in-house if you have an AI and engineering team, want to own every part of the assistant, and can keep it tested as models and your catalogue change.
Choose bisky if you want dialects, branch prices, pack sizes, WhatsApp checkout and order confirmation already built, and tested on your catalogue before launch.
Some retailers do both: buy first, then build the parts that are unique to them.
Reads each branch's own prices and stock from your live catalogue, synced on a schedule.
You can build exactly what your systems allow, because you own both sides. Your team writes the sync and keeps it running.
Picks the cheapest pack that covers the amount asked for. Fruit, vegetables, meat and cheese show in steps such as 250 g and 500 g, with the price per kilo.
Your team designs and tests it: pack comparison, weight steps and price per kilo.
Saudi, Gulf and Lebanese Arabic, Arabizi and mixed messages, answered in the language and script of the question.
A general model understands a lot of Arabic. Steady dialect replies and matching Arabizi to products take test sets and tuning.
On your own WhatsApp Business number: product cards, a basket and checkout inside the chat. Voice notes and photos of a shopping list work too.
You build on the WhatsApp Business Platform yourself: product cards, basket, checkout and message approvals.
Adds Arabic names and spelling variants, cleans up brand names and gives every product a type before search goes live.
Your data team does it, with the advantage of knowing the catalogue better than anyone.
Reported to your team as a list of what shoppers asked for and you do not stock.
Available once you build the logging and the reports.
Every conversation sits in one inbox, and your team can take over any chat.
You build an inbox for your team, or connect the help desk you already have.
Nothing is ordered until the shopper confirms. The order then goes to your platform, your orders API, or your team as an order ticket.
You design the confirmation step and test that the assistant can never skip it.
StrongPartlyNot its job
The code, the prompts, the data and the roadmap are yours.
Nobody else decides what ships next or when.
An in-house assistant can use loyalty history, dietary profiles and internal systems in ways a vendor would need a project to reach.
bisky is a small company.
If you build, you carry the risk yourself instead of placing it with us.
You pick the cloud and the region. bisky is hosted in the European Union today, in Gravelines, France.
Salaries for engineers and a product owner, model usage, hosting, and the upkeep that follows every model update and catalogue change. Most of the cost comes after launch.
By the number of brands or branches and your monthly orders, plus a one-time setup that depends on how your catalogue and orders connect. Every retailer starts with a paid pilot on one brand.
Compare three years, not the first three months. Count the people who keep the assistant tested and current, and what else they would have built in that time.
Yes. You can try bisky without switching.
You can test the decision before making it. Run a bisky pilot on one brand while your team builds a prototype, and give both the same list of real shopper messages.
After a month you will know which parts are hard on your catalogue and which are not. Some retailers then keep bisky for shopping and build the parts tied to their own loyalty data.
Spotted a fact that is out of date? Write to us and we will correct it.
Write to hello@bisky.aiA demo that chats about products takes days. An assistant that handles branch prices, weighed items, dialects, WhatsApp checkout and safe order confirmation takes a team many months, and then needs upkeep.
It depends on how your catalogue and orders connect. Every retailer starts with a demo on their catalogue and a paid pilot on one brand.
Yes. bisky has SDKs for iOS, Android, Flutter, React Native and web, and a REST API with webhooks, so your team can build its own screens and connect its own systems.
Each retailer's data is kept separate, hosted in the European Union, and we never train a model on your conversations. We do not hold SOC 2 or ISO 27001 certification today.
Yes. A pilot shows you what shoppers ask for and which parts are hard on your catalogue. That is useful whichever way you go next.
Bring the questions you would ask any vendor. We answer them live, on your products.