Slots / App
goll365 has put together this FAQ to help you move through account access, payment steps, and session controls without needing to contact support for every query. Whether you are checking a bKash deposit status or sorting out a login issue, the answers below cover the situations we hear about most.
Every question in this FAQ comes from real account interactions. We have grouped them by topic so you can jump straight to what you need rather than reading through content that does not apply to you. The payment section covers bKash, Nagad, and Rocket steps in plain terms, matching what you will actually see in the account wallet interface.
These four markers show the structural coverage of this FAQ page. Each figure reflects the categories and access routes built into the platform, not a count of anything that changes day to day.
4
3
2
1
If the FAQ does not resolve your query, these are the routes we actually publish. Each one is accessible from inside your signed-in account.
Open your account dashboard and select the Help option from the main menu. From there you can submit a query directly. This route is visible once you are logged in and is the most direct way to reach the team for account-specific issues like a wallet discrepancy or a login problem that the FAQ does not cover.
The chat option is available within the signed-in area. It connects you with the support team in real time. Use this for urgent queries such as a bKash transaction that shows as sent but has not yet reflected in your wallet balance, or a session that did not close correctly on a shared device.
For queries that need a record — such as a disputed transaction or a request to update account details — email support is available through the contact form in your account settings. Response handling follows the queue order shown in the support panel; check there for current wait context.
We apply four standards to every FAQ entry to make sure the answer you read matches what you will actually encounter in the platform.
Every answer here is written against the actual account interface, not a general template. If a step is described, it is because that step exists in the current version of the platform. We do not describe features or payment flows that are not yet active for Bangladesh accounts.
The bKash, Nagad, and Rocket deposit and withdrawal entries are checked against the payment fields visible in the account wallet. We do not invent timing, fee, or limit information — if a figure is not supplied by the payment provider interface, we say to check the field shown at the time of the transaction.
Login state, device continuity, and session timeout entries reflect how the platform actually handles those states. If your experience differs from what is described here, that is a signal worth reporting through the in-account support route rather than assuming the FAQ is current.
FAQ entries are revised when a platform update changes the described flow. We mark the account help section when a recent change affects a step. If you are following an older bookmark to this page, refresh it so you are reading the current version.
Not every query needs a support ticket. This comparison helps you decide which route gets you to an answer faster.
Deposit and withdrawal steps for bKash, Nagad, and Rocket; login and session questions; wallet balance display queries; account verification process questions; and understanding what a status message in the account panel means.
A transaction that sent from bKash or Nagad but has not arrived in your wallet after the standard processing window; a login you cannot complete after following the FAQ steps; and any account change that requires identity verification or document submission.
Urgent session issues such as a device you did not recognise appearing in your login history, a payment that is time-sensitive, or a wallet action that appears to be processing but has not resolved within the window shown at transaction time.
Formal requests that need a written record — account closure queries, transaction disputes, and requests to update registered contact details. The email route creates a reference number you can follow up on if the matter is not resolved in the first response.
Four elements define how accounts on goll365 work in practice. These are not marketing claims — they are the structural features that come up most often in support queries and FAQ searches.
The account interface is built to work on a mobile browser without a separate download. You can log in, check your wallet, review transaction history, and reach the help desk from the same screen you use for everything else. Session continuity across Android and iOS is handled automatically once you are signed in.
bKash, Nagad, and Rocket are integrated directly into the account wallet. Deposits and withdrawals follow the same flow as other local wallet transfers you already use. The payment fields in the wallet show the current limits and reference numbers at the time of each transaction — check those fields rather than relying on remembered figures.
Your full transaction history is available inside the account dashboard under the wallet section. Each entry shows the method used, the amount, the timestamp, and the current status. If a bKash or Nagad deposit does not appear immediately, the history panel is the first place to check before contacting support.
You can review active sessions and log out of individual devices from the account security section. This is the recommended first step if you think your account was accessed from a device you do not recognise. The session list updates in real time so the view you see reflects the current state of your account.
These are the questions we receive most often through the support queue and the in-account help desk. Each answer is written against the current platform flow.
Go to the wallet section inside your signed-in account and select Deposit. Choose bKash or Nagad from the payment options shown. Follow the reference number and amount fields displayed on screen. Complete the transfer from your bKash or Nagad app using the details provided. The transaction status updates in your wallet history once the payment is confirmed on the provider side.
Check your wallet transaction history first — the entry should appear there even if the balance has not yet reflected. If the status shows as pending, allow the processing window shown at the time of the transaction to pass. If it has passed and the status has not changed, use the in-account live chat with your bKash transaction reference number ready.
Open your account security settings from the main menu. Select Active Sessions to see all devices currently logged in. Find the device you want to remove and select the log out option next to it. The session ends immediately.
Yes, your account can be active on more than one device. The session is tied to your login credentials, so each device maintains its own active session. If you want to review which devices are currently logged in, the Active Sessions section under account security shows a real-time list. You can close individual sessions from there at any time.
Open your wallet history and confirm the withdrawal shows a completed status rather than pending or processing. If the status is completed on the platform side, the delay is on the Nagad network. Check your Nagad account transaction history directly. If neither side shows the transaction, contact support through the in-account help desk with the wallet reference number from your transaction history.
Your verification status is visible in the account settings page under the profile section. A verified account shows a confirmation status next to the relevant details. If a step is incomplete, the page shows what is outstanding and how to complete it.
The terms applicable to your account are linked in the account settings page and in the footer of the main site. Availability and eligibility depend on your local law and the eligible regions listed in those terms. We recommend reading the relevant sections before making any transaction, particularly around withdrawal conditions and account activity requirements.