Support Hours in EAT, and What Happens Over the Weekend (Kenya)
Account holders reach Binomo support around the clock through in-platform chat and email. This guide is independent and is not the support desk itself.
Open a Binomo demo →Reaching Binomo's support is not the part that depends on the hour. A registered user opens live chat or writes an email at any point in a Kenyan day or night, and the stored help text needs nobody on duty. What depends on the hour is the subject of the question. Some questions concern something written down — a rule, a threshold, a document under review, a contract that has already settled — and those lose nothing at all by waiting until the middle of a Nairobi night. Others describe a state that exists only while an asset is trading, and once that session has closed there is nothing left for a reply to look at. This site is not part of Binomo and cannot see an account.
Ways to contact Binomo — and when to use each
| Channel | Best for | When |
|---|---|---|
| In-platform live chat | Anything about the account, funding or a withdrawal | Around the clock for registered users |
| Email support | Verification and cases that need detail | Response times vary |
| Help centre / FAQ | Step-by-step guides | Anytime, self-service |
The current contact routes live inside the platform and the app.
A question that keeps, and a question that closes with the session
Two things are easily blurred together on a page like this: when a question can be sent, and when it can be answered. The first has almost no interesting content from Kenya. A registered user reaches the chat or writes an email at two in the morning as readily as at two in the afternoon, and the stored help text answers without anyone being present at either end. The second is where the interesting part sits, and it belongs to the subject rather than to the channel.
One class of question is about something that has been written down and stays written. What a condition actually says. Which threshold belongs to which tier, as the account types page lists them. Whether a document sent for review has been looked at. How a contract that has already settled was settled. Nothing in that class moves overnight, so nothing is gained by holding the message until a weekday and nothing is lost by sending it at once. The other class describes a state instead of a record: what the asset list was showing at the moment of looking, what a notice on screen said, what was in front of a person while something was being opened. None of that is filed anywhere a reader can be pointed at afterwards. It lasts as long as the session it belongs to, and when the session closes the subject of the question closes with it. The channel is still open in every case; the thing the question was about is not.
Writing it down while it is still in front of you
The consequence is practical. A message describing something live is read at some later moment by a person who was not there, and everything that person will need has to be inside the message already, put there while it was still visible. Which asset. What the screen actually said, in its own words rather than in a summary. What was pressed, in the order it was pressed. And the hour it happened. Assembled afterwards from memory, each of those is a reconstruction standing in for an observation, which is exactly the gap the question was trying to close.
The hour is the part most often left out and the cheapest to include. A reader in Kenya works from one offset, UTC+3, so an hour noted in Nairobi keeps a single meaning and never has to be recovered later; writing it as a local time with that offset beside it settles the question of which clock it belongs to, since whoever reads the message need not be on the Kenyan one. A capture taken during the session does the same work for everything the words leave out. Neither can be produced once the asset behind the question has stopped trading, and that is the entire argument for taking them at the time rather than at the end of the evening.
Where the far end has to be present, and where it need not be
The routes to support differ in when the answering side is there, and that difference lines up with the two classes of question almost exactly. A live conversation puts each side in the same sitting, so a question and its reply arrive while what is being discussed can still be examined. Writing instead crosses a gap: the message is composed at one moment and read at another, and whatever it describes has to survive that gap in words alone. The stored help text sits at the far end of the same scale — continuously available, needing no one at all, and covering only what somebody thought to write in advance.
That produces a plain division. A question whose subject expires wants the route where the other side is present now, because presence is what allows the subject to be looked at rather than merely described. A question about a record is indifferent to all of it and is often already settled by the stored text, which replies immediately at an hour when nothing is trading anyway. Subjects that never depended on a session in the first place — how the browser platform is reached, for instance, on the web terminal page — sit in that second group by their nature and can be raised whenever it suits.
Deciding when to send, and what to send with it
- Sort the question before anything else: is its subject something written down — a rule, a threshold, a document, a contract already settled — or something that is only true while an asset is trading?
- Send a standing question whenever it suits you. Its subject does not move, and a Nairobi night costs it nothing at either end.
- Raise an expiring one while the session it belongs to is still running, so that the reply can reach the same thing you were looking at.
- Put the asset, the local hour with UTC+3 written beside it, and the wording that was actually on screen into the message itself, at the time.
- Capture the screen before leaving it. A capture cannot be taken once the session has ended, and a description written later is a different kind of evidence.
- Check first whether the answer is simply a calendar one — an asset that is not being traded is not offered, which is described on its own page, as gold is.
- Send nothing about an account to this site. The about page states plainly what it is and what it has no access to.
This describes when a question can be answered, not advice about trading. Fixed-time trading carries a high risk of losing the full amount staked.
Does the subject outlast the session, or end with it?
| What is being asked about | Does the subject outlast the session? | When it is worth raising |
|---|---|---|
| What a stated condition actually says | Yes — it is written down and stays written | Any hour; the stored help text often settles it outright |
| The state of a document sent for review | Yes — a record with a status attached | Any hour, a Nairobi night included |
| How a contract that has already settled was settled | Yes — the outcome is recorded | Any hour; nothing about it improves by waiting |
| Which threshold a given tier carries | Yes — a published figure, not a state | Any hour |
| What the asset list was showing at the moment of looking | No — it describes a session that has since closed | While that session is still running |
| What a notice on screen said at the time | No — the wording is not kept anywhere afterwards | At the time, quoted rather than summarised |
| What was in front of you while something was being opened | No — a screen is not stored for later reading | At the time, with a capture taken then |
The route to support is open in every row; the difference belongs to the question, not to the channel. Fixed-time trading carries a high risk of losing the full amount staked.
What a message can carry only if it is written during the session
| Detail | Why it cannot be supplied afterwards |
|---|---|
| The asset the question is about | Easy to name wrongly once several have been looked at in one sitting |
| The local hour, with UTC+3 written beside it | Whoever reads the message need not be on a Kenyan clock, and a bare hour tells them nothing |
| The wording that was on screen, quoted | Phrasing is the first thing memory rounds off |
| A capture of the screen | It cannot be taken after the session it belonged to has closed |
| What was pressed, in the order it was pressed | The order is what separates one account of an event from another |
| Whether the same thing had been seen before | Only the person who was there knows; nothing on the far side shows it |
Every line above is written by the person asking, while the session is still running. None of it concerns account access, which this site does not have.