1. Submit
Describe the problem, user ID, and time; providing a screenshot helps the Dhaka-based team understand quickly
Submitting a ticket alone does not fix the issue; first information goes in, then verification, then it goes to the right team, and finally a solution is sent
Describe the problem, user ID, and time; providing a screenshot helps the Dhaka-based team understand quickly
Support team looks at three things: account, login, and payment history; this reduces wrong routing
Ticket, deposit, app and general support go to separate lines
Clear answers come, and follow-ups if needed; most common questions are resolved at once
Questions requiring documents are best via a ticket; login, account verification, bKash transactions and old ticket records in a thread help; the support team later replies on the same thread, so no hassle to follow up
If the task is small, directly spi9 Help Center See new users often FAQ Read and match the problem, especially after noon when the net is slow
After submitting a ticket, the message history is visible here; updates arrive in 3 steps, so conversations are not lost
If you have questions about bKash, Nagad and Rocket, this section helps Dhaka users who often keep reference numbers
If you have problems signing into the spi9 App, notifications, or device setup, write here; on Android it can be checked in 2 minutes
Whichever channel you choose, keep the same information: user ID, phone number and time of issue, and the support team can quickly match it
A clear ticket has four items: what happened, when it happened, which device, and which method you used; including these helps the first reply move the work forward
If you have login issues from Dhaka or Chattogram, keep the screenshot brief, but do not leave information blank
If you still haven't logged in, then first spi9 Login Do it, then you'll see the support ticket, help center and account history together
Open Account Log in