Elyvoq: AI Customer Support Across Every Channel
By IcoreSoft Team AI & Automation
Most support teams lose customers in the gap between channels. Elyvoq — our own product — puts WhatsApp, Messenger and Instagram in one inbox, answers instantly from your own knowledge base, and hands the conversation to a human at the right moment.
A customer asks a question on Instagram at 9pm, repeats it on WhatsApp the next morning because nobody replied, and gets a different answer from a third person on Messenger. Nothing is broken, exactly — but the customer has already decided how organised you are.
Elyvoq is the product we built to close that gap, first for ourselves and now for our clients.
One inbox, every channel
WhatsApp, Messenger and Instagram land in the same place, in one thread per customer. Your team stops switching between apps and stops answering the same question twice.
This matters more in Egypt and the Gulf than the feature list suggests. Most small businesses here sell across all three, and the customer does not think of them as separate places — they think they are talking to you.
Answers grounded in your business, not in guesswork
Elyvoq is trained on your own knowledge base: your prices, policies, working hours, shipping rules, product details. It answers from that rather than from a general model's idea of what a business like yours probably does.
When it does not know, it says so and escalates. That behaviour is deliberate. A support bot that invents a plausible shipping policy creates a promise you have to honour or apologise for, and one of those costs more than the question was worth.
Instant first response, human follow-up
The first reply arrives in seconds, at 3am as easily as at 3pm. The moment a conversation turns into a complaint, a negotiation, or an unusual case, it is handed to your team with the full history attached — nobody starts from "can you explain the problem again?"
What it handles, and what it hands over
| Handled automatically | Handed to a human |
|---|---|
| Prices, availability, working hours | Complaints and refunds |
| Order status and shipping rules | Negotiation and bulk pricing |
| Product details and comparisons | Anything the knowledge base does not cover |
| Booking and appointment questions | Conversations the customer asks to escalate |
The split is configurable. The default errs toward handing over, because an unnecessary handover costs a minute of staff time and a wrong automated answer costs a customer.
When it is the wrong answer
Three cases, honestly:
Very low volume. If you get five messages a day, a person answering them is faster to set up and better at it. The economics start working somewhere above a few dozen conversations a day.
No written policies. Elyvoq answers from your knowledge base. If your prices, shipping rules and return policy only exist in your team's heads, that has to be written down first — and that is genuinely the work, not the setup.
Highly bespoke sales. If every deal is negotiated from scratch, there is little for an assistant to answer. It can still triage and route, but the value is much smaller.
What setting it up actually involves
Connecting the channels is the quick part. The real work is assembling the knowledge base: prices, policies, hours, shipping, the twenty questions you already answer every week.
Most businesses have this scattered across a website, a price list, a WhatsApp broadcast and one person's memory. Pulling it into one place is work you benefit from regardless of whether you automate anything — it is the same document that onboards a new hire.
After that, the useful pattern is to watch the conversations for a week and keep tuning what gets handed over. The handover rule is the setting that decides whether customers trust the thing.