Urgent level
If you can't log in to the account, this comes first; typically a short answer provides guidance
Tickets can be opened after 11 PM as well, see how crickex support works, where to write, and what information to provide for a quick response—all in one place. Dhaka users ask the most about bKash, Nagad, and Rocket.
Start Contact Log in
Submitting a ticket isn't dropped; first it's captured, then the issue is reviewed, then routed, and finally a response is sent through crickex Contact. Understanding these steps reduces unnecessary waiting.
Enter account, time, and type of problem; with a screenshot the team can identify the issue in 2 minutes
First determine whether it's login, app, or payment-related questions so crickex Help quickly goes to the right team
With verified information, the lookup is faster; tickets from Dhaka, Chattogram, and Sylhet are also in the same queue
The answer arrives in the ticket; if needed you can follow up by writing again in the same thread
Now the main question is which issue is seen first; below I have clarified the priorities
Not all tickets are equal; some questions require fast review, some need a bit more verification, so the system has three levels, which set the work pace
If you can't log in to the account, this comes first; typically a short answer provides guidance
Questions about app settings, notifications, or identity verification here; with proof, work moves faster
General information, help center paths, and FAQ-type questions here; these are usually seen within a shift
Those writing for the first time typically send questions to the wrong place; checking the cards below will reduce this a lot
Many search at midnight with a phone in hand; where to write now? In practice there are three clear paths; all paths have the same crickex support team working, so you don't need to start over
First see crickex Help; common questions, steps, and ticket submission rules are neatly organized here
If you open a ticket from the app, the phone number and session data are on file, so explanations take less time
Dhaka-based users ask more about bKash, Nagad, and Rocket; with accurate information, follow-up is easier
To know what to write, it’s good to first look at a few real user questions
A short message can make a big difference; the problem is that writing slows things down. crickex Contact: not logging in, time 10:40 pm, phone Android 13; if you write it, the team can respond immediately
User name, email, and last login time; providing these moves verification forward in one step
If there are error images, it's easier to understand; sending two images in the same message will clarify most cases
Weak 3G, Wi-Fi, or mobile data; indicate what you're using, as network changes in Bangladesh can alter behavior
If you write a bit more clearly, the answer comes together, and the real advantage of crickex support becomes clear
The questions below often come; most answers are short, but a lot of work
General questions get quick replies; more thorough verifications may take a bit longer, especially if information is incomplete
Mention when, which method, and at which step the issue occurred; the same rule applies to Rocket-related questions
First see login instructions, then open a ticket; if needed, attach a crickex App screenshot in the same message
The best ticket is short, clear, and specific; we’ve matched that to the bottom part
crickex Support, crickex Contact, and crickex Help together make things easier; the more specific the problem, the faster the solution will come. Dhaka-based users take this route first for any questions, including about bKash, Nagad, and Rocket
If you want to do something now, first open the crickex App, then fill the ticket information correctly; this is the best way to contact crickex Support
Join for App Log in