Pocket Broker Customer Service and Contact

Contact channels

There are three contact routes: in-platform chat, email or the ticket system, and the help center with articles. Each serves a different kind of problem, and it's worth not mixing them up.

Before you write, choose the right channel. Half of the complaints about slow support come from having used the wrong channel for the type of problem.

In-platform chat

This is the fast route for how-to questions: where a feature is, why a button isn't showing, how to switch to the practice account. It also works as a first record of a bigger problem, because it leaves a dated trail. Screenshot the conversation before closing it; chat histories don't always stay available afterward.

Email and tickets

This is the channel for anything involving money, documents, or your identity: verification, a withdrawal that isn't moving, a charge you don't recognize, a bonus with conditions you don't understand. It leaves a trail, lets you attach files, and gives you a reference number to point back to. If your case matters, write it here even if you already raised it in chat.

Help center

The help center's articles solve more than people expect, especially questions about verification and payment methods. Search it before opening a ticket: if your answer is there, you have it in two minutes instead of waiting on an email cycle.

How to reach the channels safely

• Always enter by typing the official address yourself or from the app you already have installed, never from a link received in a message.
• Distrust social media accounts offering support that aren't linked from the site itself.
• Use the email you registered with; writing from a different one delays any process for security reasons.
• Keep your account ID on hand: it's the first piece of information they'll ask for.

If you don't have an account yet and want to avoid clone sites, the sensible move is to sign in from the official site and bookmark the address from day one.

Use chat for how-to questions and email or tickets for anything involving money or documents; the help center resolves a good part of it before you even write in.

Common complaints

Complaints repeat in three forms: the wait gets long, the answer arrives generic, and language gets in the way. Almost all of them have an identifiable cause and, in large part, one you can avoid on your end.

It's worth separating the complaint from the diagnosis. A slow response doesn't mean no one's working on it, and a generic response almost always means the original message didn't carry enough information.

Response times

This is the number-one complaint across the whole category, not just here. The platform publishes its own service timeframes in its help center, and those are the ones that count; we won't invent a number. What can be said is that the clock starts running once the ticket has everything needed, not when you opened it.

Generic responses

The second frequent complaint is receiving a template reply that doesn't address your case. This happens when the original message is too short or mixes up two different problems. A ticket that says "I can't withdraw" forces the agent to guess among half a dozen causes, and what comes back is the house's general answer. A ticket that says which method you used, on what day, at what verification status, and what exact message you saw on screen gets a specific answer.

Language barriers

Service covers Spanish, but in international support it's normal for the response to go through translation, or for the agent not to know local details well. Write short sentences, avoid idioms, and name elements by their interface label. If you mention a local method, also describe it in generic terms: "national bank transfer" is understood in any language, and it saves you an extra round of emails.

Complaints that aren't support failures

• Losing money trading. This is the product's risk, not a service error, and support can't reverse it.
• Being asked for documents. Identity verification is standard compliance, not a maneuver to delay your withdrawal.
• A bonus conditioning the withdrawal. If you accepted the promotion, you accepted its volume requirement; it's in its terms.
• A third party's account being rejected. Money only goes out to accounts in your name, on this and on any serious platform.

A good share of complaints about generic responses gets solved on the user's end: a specific ticket gets a specific answer.

Why responses are delayed

Three causes explain almost every delay: volume spikes on the team, cases moved to review by another area, and files stuck because the user's verification is incomplete.

Understanding why a response is delayed changes how you act. If the cause is on your end, insisting doesn't speed anything up; completing what's missing does.

Volume spikes

Support teams get overloaded at predictable times: highly volatile markets, promotional campaigns, weekends, and holiday periods. In those windows everything takes longer, and there's no trick that avoids it. If your matter isn't urgent, raise it outside those spikes.

Cases under review

Some matters leave first-line support and move to another area: security, payments, or compliance. When that happens, the agent you were talking to no longer has control of the case and can only tell you it's still under review. It's frustrating and it's normal. That shift in wording is exactly the sign your case has moved forward.

Dependence on verification

This is the most frequent cause and the easiest to fix. An incomplete file stops whatever you're requesting, and often the platform already sent the notice to an email you didn't check. Before complaining about slowness, check this:

1. Your identity verification is complete, and the documents are legible, current, and in your name.
2. Your personal details match those on the document and on your bank account.
3. You don't have an active promotion with pending requirements.
4. You checked your spam folder, where automatic notifications tend to land.
5. You're writing from the registered email, not a different one.

If your case is specifically a withdrawal that isn't moving, this site's withdrawal-problems guide breaks down the causes one by one and saves you this detour.

Before complaining about slowness, check whether the holdup is in your own file: incomplete verification stalls more cases than any team overload.

How to get help faster

A well-written ticket gets resolved in one round. Include your account ID, the problem in one sentence, a timeline with dates, the method used, what you already tried, and the screenshots that back it up.

The difference between a case that gets solved and one that goes in circles is almost always in the first message. Write it once, complete, and save yourself four rounds of back-and-forth.

What to include in the message

1. Account ID and registered email, in the first line.
2. The problem in a single sentence: what you expected to happen and what happened instead.
3. A timeline with dates: when you deposited, when you requested, when the error showed up.
4. The method used, also described in generic terms so it's understood without local context.
5. The exact on-screen message, copied as is, not paraphrased.
6. What you already tried, so you're not asked to repeat steps you've already taken.
7. What you're asking for, specifically: an explanation, a correction, an estimated timeframe.

What to attach

• A full screenshot with the device's date and time visible, not a crop of just the error message.
• Proof of the bank transaction with its reference number, blocking out anything unnecessary.
• A screenshot of your request's status inside the platform.
• Never your password, your verification codes, or a photo of your full card.

What not to do

• Don't open duplicate tickets. Each one resets the queue and splits up your history; reply within the thread that already exists.
• Don't threaten or insult. It doesn't speed anything up and usually moves your case into a more formal, slower process.
• Don't request a chargeback from your bank as your first move. It's a last-resort route that tends to freeze the account and close off the channel you were actually going to resolve things through. Exhaust it with the platform first, with your file in order.
• Don't hand your credentials to anyone. No legitimate support team messages you first through a private channel or asks for your password, two-factor code, or a deposit to another account. That script is always a fraud, even if the profile uses the correct logo.

Escalating politely

If the response doesn't resolve things, escalate in order and without changing your tone: reply within the same thread asking for it to be reviewed at a higher level, summarize the case in three lines and attach the evidence again; if a reasonable cycle passes with no progress, explicitly ask for the status and an estimated date; if the case involves your personal data, raise it in writing through the formal channel named in the site's policies. Switching channels midway through the process, on the other hand, is what delays a case the most.

One complete ticket, with a reference number, dates and screenshots, works better than five insistent messages: order is your main tool of leverage.

Weighing up support

Support is reachable and functional for everyday matters, with room to improve on timeframes and template answers. Well-documented cases get resolved; vague messages keep spinning.

The honest assessment is decent service, not exceptional service, and that's typical of international platforms in this category. It's worth saying plainly.

Reachable and functional

There are several contact routes, service in Spanish, and a help center covering what most people ask. For how-to questions, verification, and payment methods, the system does its job.

Room to improve

The weak points are the same ones reported by any user in the sector: waits that stretch out during spikes, template answers on first contact, and a translation layer that sometimes blurs the details. None of that is exclusive to this platform, and it isn't worth downplaying either.

Your real leverage

Here's the part almost no article says. Since this is an international platform outside Mexican financial supervision, there's no local body to escalate a dispute to. Your strength is two things: documentation and orderly persistence. A file with reference numbers, dates, screenshots and receipts, presented calmly and without switching channels, is what moves a difficult case forward. Keep that evidence from your very first deposit, not once the problem shows up.

Cases do get resolved

Most matters that reach support end up resolved, and the causes repeat so often they're predictable by now: incomplete verification, badly entered bank details, a bonus with pending conditions, or a method different from the deposit's. Close those four fronts on your own and the odds of needing support at all drop sharply.

Conditions and service channels change over time: confirm current contact details and timeframes on the platform's official pages. Reviewed September 2026.

Without a local complaints channel, your organized documentation and polite persistence are the leverage that actually moves a difficult case.