Callback Request
Include the callback time with the support ticket; two details are enough: name and time.
4.4/5
Average rating
5,714
Reviews
223K+
Active users
99.3%
Uptime
This number shows how consistently the team works; when you consider communications, logins, and account issues together, responses are faster.
tk567 Contact means not only messages; if you want a callback, briefly write your name, region, and issue type, then the team routes the case to the right department.
Dhaka, Chittagong, and Sylhet users typically get a quick response between 10 AM and 2 PM; if you have questions about bKash or Nagad, include them in the same note.
Include the callback time with the support ticket; two details are enough: name and time.
Dhaka-based users get faster responses when the time window is kept short; specifying the district makes routing easier.
The Help Center in the footer has step-by-step answers for Login, submissions, and common questions there.
Describe the issue in one line: Login, account, or payment issue, as needed.
Helpline, Help Center, or in-app note whichever is easier to use; choose that.
Morning, afternoon, or after 8 PM, pick a time and note it; this ensures a return call at the right time.
The team first reviews the ticket, then calls; if there are small questions, it ends in 10 minutes.
| Daytime | Average wait |
|---|---|
| 10 AM to 2 PM | 812 minutes |
| 2 PM to 6 PM | 1218 minutes |
| 6 PM to 10 PM | 1015 minutes |
| Friday or holidays | 1520 minutes |
During busy times, the wait may increase a bit, but clear messages speed up the case, especially for bKash and Rocket issues.
For small questions, providing a screenshot makes it easier to understand.
For major issues, include the case number, login name, and time in the email.
First check the answer; many login and payment questions are found there.
Usually calls arrive within 10 to 20 minutes depending on the time of day and case complexity; Dhaka area users get faster responses before noon.
If urgent, clearly state the problem type in the message so the Support team doesn't route it to the wrong department.
Submit a ticket directly to the payment team; if you note bKash, Nagad, and Rocket separately, responses are organized.
Adding transaction time, amount, and screenshots speeds up verification.
Reset the password once, then try again; if needed, open the tk567 Help Center and follow the steps.
If the same issue repeats, request a callback; the team will pull up the case number.
When you log in to the app, Support, Help Center, and contact links are handy; login shows previous cases, so you need not repeat data.
For new users, first Download guide See it then Help Center And Payment information When matched, work goes faster
Sign up Login