IQ Option Peru Support and Customer Service 2026

Support channels

All contact happens through digital channels: the account panel itself, email, and, when it's enabled, a chat inside the platform. There's no in-person service and no local Peruvian phone number.

Live chat and email

Live chat, when it's available, is the most direct route for short queries: questions about where to find an option, the status of a request, or clarifications about a rejected document. It works well for unblocking simple situations and leaves a written record if you save the transcript before closing the window.

Email works better for anything that needs evidence attached: cashier screenshots, receipts, or the detail of a specific trade. It has the advantage of creating a thread with a reference, and that thread is exactly what you need if the case has to be escalated later. Data verified against the broker's official pages in August 2026; conditions can change without notice.

In-app help

Both the mobile app and the desktop version include access to support from the profile menu. Writing from there has a practical advantage: the request arrives already linked to your account, without you having to prove who you are at the start of the conversation. For access issues the opposite applies, because if you can't log in you'll need to use the public form from the browser.

The help center

Before writing in, the broker's knowledge base answers a considerable share of common questions. It's worth checking for standardised topics:

• Document requirements for the verification process.
• General rules on withdrawal methods and returning funds to the same payment method.
• Differences between account types and the instruments available.
• Steps to reset your password or recover access.

Arriving at support having already read that shortens the conversation and skips the first round of generic replies.

Chat for anything urgent and brief, email for anything that needs attachments and a paper trail: picking the wrong channel drags out any case.

Times and resolution

Speed depends on the type of query, not the channel. Standardised questions get resolved on first contact; ones that involve reviewing documentation or fund movements go through another team and take longer.

Response times

We don't publish a specific timeframe because the broker doesn't commit to a service-level agreement for Peruvian users, and any figure would be made up. The sensible approach is to separate two categories: the informational query, which usually gets resolved in the same exchange, and the request that requires internal review, which moves through phases and can sit waiting while another department evaluates it. Volume spikes, weekends and holidays stretch out both.

Complex cases

There are three situations that almost never get closed in a single message: KYC verification with rejected documents, access issues involving two-factor authentication, and anything tied to money, from a deposit that doesn't show up to a delayed withdrawal. In these cases first-line support gathers the information and passes it along; what you control is the quality of that initial information.

Escalation paths

When a case stalls, the correct order is this:

1. Reply in the same thread instead of opening a new one, so the history isn't lost.
2. Explicitly ask for the case's reference number and current status.
3. Request escalation to a higher level if several rounds pass with no substantive progress.
4. Check the broker's site for the formal complaint procedure and follow it in writing.

Keeping a neutral tone throughout the process helps more than it seems: threads written with accusations tend to get defensive, template replies. Opening parallel tickets is the most common and the most costly mistake: it fragments the case and restarts the conversation from zero.

A single thread with a reference number and orderly follow-up moves faster than five new requests about the same problem.

The quality of the help

Reviews published across Latin America draw a recognisable pattern: good coverage of routine matters and more friction as soon as a case departs from the usual script.

Knowledge of common topics

For questions that come up every day, the answer is usually correct and fast: how to deposit, where to see the history, which documents work, how to change the account currency. That material is standardised and first-line agents handle it smoothly. The perception shifts when a user raises something specific and gets a template that doesn't address their question; rephrasing precisely is usually enough to break out of the loop.

Support in Spanish

Support in Spanish is available, which removes the main barrier for a Peruvian user. Even so, it's worth writing in clear Spanish and avoiding very local idioms when the matter is sensitive, because part of the support team works with multilingual teams and an ambiguous phrase can get translated badly. Referring to amounts with the currency stated avoids another common misunderstanding.

Help with KYC

Identity verification accounts for a good share of both queries and complaints. Support can point out what's wrong with a rejected document, but rarely gives away the final decision in advance. To cut down on back-and-forth:

• Send the complete document, with all four corners visible and nothing cropped out.
• Check that the name matches exactly what's registered on the account.
• Use a recent proof of address with a legible address.
• Ask for the specific reason for the rejection before uploading anything again.

With those four points covered, most rejections stop repeating and the case moves forward in a single round instead of three.

Routine matters get handled well; for anything specific, the key is rephrasing precisely instead of repeating the same query.

Getting help faster

A good part of the resolution time is decided by the first message. A complete, well-organised request with evidence attached gets resolved in one round; a vague one takes three just to be understood.

Account details to prepare

Before writing in, gather what the agent is going to ask for anyway. With this in hand the exchange starts at the right point:

• The email the account is registered under, written with no typos.
• The approximate date and time of the event, stating the Peruvian time zone.
• The transaction or trade identifier affected, if there is one.
• Screenshots of the error or the cashier's status, without cropping out the status bar.
• The payment method used and the currency it was executed in.

Never send passwords, one-time codes or your full card number: no legitimate support asks for them, and whoever does isn't support.

A clear description of the problem

The text matters as much as the attachments. A good message runs about five lines and follows a simple structure: what you were trying to do, what you expected to happen, what actually happened, what you've already tried, and what you specifically need. Writing it in that order forces you to separate the facts from the frustration, and a request with no accusations almost always gets a more useful reply than one written in the heat of the moment.

The right channel

Contacting support through the right route saves whole rounds. Questions about how the platform works go well through chat; anything related to money, documents or disputes should go by email, where there's a record. If the problem is that you can't get into the account, start with the account recovery steps before writing in, because support is going to ask you for exactly that.

Five well-structured lines with screenshots attached are worth more than ten follow-up messages with no details.

The verdict on support

Judged as part of the overall service, support delivers on everyday matters and shows its limits on exceptional ones. It sets a reasonable standard for the industry, without being a differentiator.

Reported strengths

The points users mention repeatedly are specific:

• Support in Spanish available at no extra cost.
• Access to support from the panel itself, with no intermediate steps.
• A knowledge base that covers the most repeated questions.
• Correct, fast answers on operational questions about the platform.

Areas for improvement

The criticisms also repeat, and it's worth stating them plainly: template replies to specific queries, a lack of visibility into what phase a case handed to another department is in, and the absence of a phone or in-person channel in Peru. None of this is unique to this broker, but for a user watching their money sit frozen, the lack of information about the case's status weighs more than the wait itself. Telling that apart from fraud matters: a slow case isn't the same as an ignored case, and that difference is what separates real withdrawal problems from scam accusations.

The overall level of response

For the average Peruvian user, support is good enough to trade normally, as long as you arrive with your documentation in order and realistic expectations. If support is a deciding factor for you, compare it against what other platforms offer before deciding, and remember that trading digital options, FX and CFDs carries a high risk of losing the capital invested.

It delivers on everyday matters and falls short on visibility once a case escalates: come prepared and you'll save most of the friction.