Pocket Broker Customer Support and Contact

Contact channels

There are three, and each serves a different purpose: the support email for formal complaints, the help area inside the account for day-to-day queries and the Telegram bot as an alternative route.

It is worth choosing the channel according to the type of matter, because they do not all leave the same trail. These are the ones the operator publishes on its own pages, with none added that does not appear there.

Support email

The address is [email protected], and the operator's Public Offer names it as the channel for submitting formal complaints. It is the route to use when the matter involves money, documentation or a decision you want to be able to evidence later on: an email leaves a record with a date, with attachments and with the full thread, something a chat does not always keep accessible.

Help inside the account

The platform includes its own assistance area, reachable once you have logged in. It is the natural route for operational queries: doubts about a screen, about the status of a formality or about how to do something inside the system. It has one practical advantage over email, which is that the team on the other side already knows which account you are without you having to identify yourself from scratch.

Telegram bot

The platforms menu on the operator's site lists three routes: the Android APK download, the web app and a Telegram bot. That bot is an additional route published by the operator itself. As on any messaging channel, caution counts double: no legitimate channel will ask you for your password, and impersonation attempts tend to appear exactly where the user is expecting help.

The application listings on Google Play declare round-the-clock support and localisation in several languages, and the site offers a switcher with more than 38 languages, Spanish among them. These are statements by the operator about its own service, useful as a reference and nothing more than that.

The support email is the formal route the Public Offer names, the in-account help area handles operational matters and the Telegram bot appears among the routes the operator publishes.

Common complaints

The complaints circulating in forums and app stores keep coming back to four subjects: replies perceived as generic, language, documentation formalities and queries about movements of money.

It is worth saying where these subjects come from: from what users write publicly, not from any measurement of our own. They serve to anticipate what kind of friction is likely to come up, not to grade the service.

• Replies that look like templates. This comes up above all when the opening message is short and ambiguous. A case described in two lines usually gets the general reply that matches those two lines.
• Language barrier. The operator declares localisation in several languages, but a technical exchange can end up mixing terms across languages. Writing in short sentences and without idioms cuts a lot of that noise.
• Documentation formalities. It is the point where a conversation gets stuck most, because the outcome does not depend on the agent replying but on the area reviewing the documentation.
• Queries about movements of money. Deposits that are not showing up, withdrawals in progress or doubts about the method used. These are the cases where detail matters and where a screenshot is worth more than three paragraphs.

What is not a support complaint

A good part of the complaints you read about customer support are in fact complaints about a rule of the operator that the user discovered late. The rule of withdrawing to the same payment system and with the same identifier used to deposit, which the Payment Policy sets out expressly, is the most frequent case. Support cannot lift that rule, and mixing one thing up with the other means the conversation starts off crooked. That full circuit is explained in the withdrawals guide.

Public complaints group into generic replies, language, documentation and movements of money, and part of them are not failures of service but rules of the operator discovered late.

Why they get delayed

A case moves fast when it can be resolved by reading it, and it drags when it forces someone to ask for information, to wait for a review by another area or to coordinate with a third party that is not the platform.

Understanding the mechanism is worth more than any expectation about timing, above all because the operator publishes none for customer support. These are the structural causes that make a case take longer.

The opening message is missing information

It is the commonest cause and the most avoidable. Every missing detail adds a whole round of back and forth, and every round depends on both sides being available at the same time. A case that could have closed in one exchange ends up taking five.

The case depends on a review

Identity documentation is not resolved by whoever answers the message. On that review the operator publishes a single period, and it runs from the client to the Company, not the other way round: its anti-money-laundering policy establishes that the client must complete identification within 10 business days of the Company's request, and that the Company can extend that period to 30 business days. There is no published period for the review itself. The detail of the formality is in the verification guide.

The case depends on a third party

When the matter is a movement of money, the platform is only one of the links. The operator's Payment Policy describes its own step as withdrawing the funds from the client's account within five business days, and for the transit afterwards it distinguishes between electronic methods, where the transaction time can run from seconds to days, and direct bank transfer, which it places between 3 and 45 business days. A case opened while that circuit is under way cannot close before the circuit ends, however complete the message may be.

Volume and time zones

In its application listings the operator declares a round-the-clock service and it runs a multilingual operation. None of that removes peaks in queries or the asynchrony between time zones, and neither of those two variables is published, so it is not right to turn them into a numerical expectation. What is reasonable is to assume that the moment you send matters and that pressing with new messages about the same matter tends to fragment the thread rather than speed it up.

Cases drag because of missing information, because they depend on a documentary review or on an external payment circuit; the operator publishes no support periods and it is best not to assume any.

How to resolve it faster

The lever you do control is the first message: a case described with the exact detail, the moment it happened and a screenshot avoids half the rounds of back and forth.

This is the template worth keeping to hand. It requires no technical knowledge and it works the same in the support email as in the help area inside the account.

1. Identify yourself with the registered email. Write from the address linked to the account; doing it from another address forces an extra identification step before anyone looks at the problem.
2. Describe the fact, not the feeling. What you tried to do, where and what appeared on screen. Messages that start by describing annoyance usually take longer to reach the detail that resolves it.
3. State the moment. Date and approximate time, with the time zone. Without that, locating a movement in a log is slower.
4. Attach the evidence. A screenshot of the error, of the receipt or of the formality's screen. Cover up sensitive details that are not needed and never include your password.
5. Ask for one thing only. A message with three different matters gets answered on the easiest one. If you have three problems, open three threads.
6. Reply on the same thread. Opening a new message about the same matter duplicates the case and has two people working on partial information.
7. Escalate politely and with facts. If the reply does not resolve it, ask for escalation citing what you already sent instead of repeating the whole thing from scratch. The Public Offer names the support address as the channel for formal complaints, and that is where a case gets on the record.

Two things worth sorting out before you need support

• Identity documentation, prepared in advance and with the details matching exactly those of the registration. That is what stops a formality from starting up right when you want to cash out.
• The payment method, chosen with the exit in mind and not just the entry, because the Payment Policy requires withdrawing to the same system with the same identifier used to deposit.

Many queries are avoided simply by knowing the interface in advance, and that is what the demo account is for: going through the screens with a virtual balance resolves a good part of the operational doubts without opening any ticket.

A first message with the registered email, a concrete fact, the moment, a screenshot and a single request replaces several rounds of queries and is the only part of the process that depends on you.

A balance of the support

The honest reading is that the operator publishes concrete and verifiable channels and at the same time publishes no service commitment, so the user goes in without a reference they can hold anyone to.

It is worth separating what is documented from what is not, because that distinction is what lets you decide with your eyes open.

What is published

• A support address named in the Public Offer as the channel for formal complaints.
• A help area inside the account and a Telegram bot listed in the site's platforms menu.
• A declaration of round-the-clock support and of localisation in several languages in the Google Play listings.
• Concrete periods where they do exist: those of the anti-money-laundering policy for completing identification and those of the Payment Policy for the processing and the transit of a withdrawal.

What is not published

• No response time or resolution commitment for customer support.
• No statistics on cases resolved, and no complaints mechanism before an independent third party.
• No supervisory body: the operator does not publish a financial regulator licence on its site, and its Public Offer submits the agreement to the laws of the Republic of Costa Rica, with exclusive jurisdiction of its courts.

That last absence is the one that weighs most in a complex case, because it marks how far the possible route of a complaint reaches. It is not a verdict on the platform: it is a fact worth having before deciding how much money to put at stake, and it crosses with the rest of what the operator publishes in our review of what can be checked. Trading fixed-time options carries significant risk and can lead to the loss of the invested capital, and no quality of customer support changes that.

In practice, the approach that works best is that of a user who delegates nothing avoidable: documentation sorted ahead of time, payment method chosen with the exit in mind and cases put with facts. With that, support is left for what really needs it, which tends to be rather less than it seems at first. The commonest problems and their solutions are gathered in the guide to common problems.

There are published and verifiable channels, but no service commitment and no external complaints instance; getting documentation and the payment method sorted in advance reduces how much you depend on support.