Help desk software for forex brokers: why tickets need the client's account state

What does a broker's support desk actually handle?

A broker's queue looks like any other until you read the tickets: missing withdrawals, uncredited deposits, rejected documents, locked logins, disputed trades and partner commission. Some of them are complaints, whether or not the client uses the word.

Each answer lives in the account record, not in the message. The table shows what the agent needs for each type, and what happens on a help desk that holds only the email thread.

Why does a help desk without account state slow agents and create risk?

Speed is the visible cost: every question put to another team, or back to the client, adds a round trip. The hidden costs are risks:

• Wrong promises. An agent who cannot see a compliance hold or an unfinished KYC review may tell a client a withdrawal is on its way. The client then complains about the broker's own words.
• Social engineering. Someone trying to take over an account may start at support with a plausible story; an agent who sees recent security events, two-factor changes and the registered contact details can check the story against the record.
• Data sprawl. When agents paste balances, document numbers and screenshots into tickets, personal and financial data ends up in a system with weaker access controls than the CRM (customer relationship management system).
• Missed patterns. If tickets are not linked to the account, nobody notices that one client has written four times about the same withdrawal.

A help desk that reads status from the system of record when the ticket opens, and groups tickets per client, answers all four. The forex CRM guide covers that record.

How should a broker design support SLAs?

A broker needs two kinds of clock. The first is the service level agreement (SLA) you choose: first-response and resolution targets per queue and priority, in business hours that match when your clients trade. The second is the complaint clock, which a regulator sets and you do not.

• Queues by topic and risk: funding, verification, platform, dealing disputes, partners and complaints, each with a named owner.
• Priority from the account, not the subject line: a long-held withdrawal, a fresh security event or a client in a vulnerable situation goes first.
• Fast acknowledgement: the Australian Securities and Investments Commission (ASIC) expects firms to acknowledge a complaint within 24 hours (or one business day) of receiving it, or as soon as practicable.
• Written pause rules: the service clock may stop while you wait for a client's document; ask compliance whether the complaint clock does.
• Escalation to a person, not a team, for every queue at every hour of the trading week.

Report attainment per queue and per agent each week, and read SLA breaches next to the complaint register.

Which tickets are complaints, and what do the rules say?

This is not legal advice: complaint rules depend on where you are licensed and what you sell, so map each jurisdiction with your compliance adviser. Three published regimes show what the desk must support.

In Australia, ASIC's Regulatory Guide 271, in force for complaints received from 5 October 2021, uses the definition in the AS/NZS 10002:2014 standard (since reissued as AS 10002:2022): an expression of dissatisfaction where a response or resolution is explicitly or implicitly expected or legally required. The client does not have to say 'complaint', and firms should not label such a message feedback or an enquiry merely because it was made verbally. A standard complaint needs a written response within 30 calendar days, stating the outcome and the client's right to take it to the Australian Financial Complaints Authority (AFCA).

In the UK, the Financial Ombudsman Service tells businesses they have 8 weeks to consider most complaints, and 15 days for complaints about payment services, electronic money, and fraud and scams. Check with your adviser how your rules count those days; a broker's trading complaints fall under the 8-week limit unless they concern a payment or e-money service. The final response should tell the customer they can refer the complaint to the ombudsman within six months.

In the EU, the joint guidelines on complaints-handling from the European Securities and Markets Authority (ESMA) and the European Banking Authority (EBA), JC 2014 43 of June 2014, tell national supervisors to ensure that firms register complaints internally, for example in a secure electronic register, analyse complaint data for root causes, answer in plain language within national time limits, and explain any delay and when the investigation should be complete.

For the help desk that means a complaint flag any agent can set, a deadline computed from the date of first dissatisfaction for the client's jurisdiction, final-response templates that carry the right referral wording, and a register you can export.

Audit trails, AI-drafted replies and who may see what

Records first. ASIC's guide says firms must record every complaint in a system that tracks its progress, should record the outcome, remedy and any compensation on closing, and expects high-volume firms to use specialised complaints software or add complaint fields to their CRM. Whatever your regime, the audit trail should show every message, note, status change, reassignment and macro, with the agent and the time.

AI can draft a reply from your knowledge base and the ticket's account context; the risk is a confident answer about a client's money that nobody checked. Keep a named agent as the sender, store the draft beside the sent reply, and never let a draft promise a withdrawal date or complaint outcome the account does not support. If a bot answers clients directly, Article 50(1) of the EU AI Act, which applies generally from 2 August 2026, requires providers to design it so people are told they are dealing with an AI system, unless that is obvious. Ask counsel how your set-up is treated.

Data protection sets the edge of the context panel. The UK Information Commissioner's Office (ICO) explains data minimisation as personal data that is adequate, relevant and limited to what is necessary for the purpose, and its security guidance says data should be accessed, altered, disclosed or deleted only by those you have authorised. For support, that usually means statuses rather than sources: KYC approved or pending, not the passport scan; withdrawal on hold, not the full bank details.

What to ask a help desk vendor

• Which account fields does the ticket view show, and are they read live from the CRM or copied when the ticket opens?
• Can we set which fields each role sees, and hide document images and full payment details from support?
• Can any agent flag a ticket as a complaint, and does the flag start a separate deadline per jurisdiction?
• Can we export a complaint register with dates, outcome, remedy and compensation?
• What does the audit trail record, can anyone edit it, and how long is it kept?
• If AI drafts replies, which sources does it use, who approves, and is the draft stored next to the sent message?
• Do email, chat and web-form messages from one client land on the same client record?
• Where is the data hosted, and can we run the desk on our own infrastructure?

Where EntropyX Labs fits

EntropyX Tickets is support desk software built around the account record. Every ticket carries the client's account state, KYC status and recent activity, read live from the CRM when the agent opens it, in a context panel that shows each role only its fields; SLAs are tracked per queue and priority, with business hours, escalation paths and pauses while you wait on the client, all defined by you; agents use macros and templates; and there is an audit trail per ticket and per agent. Email, web forms and chat feed one queue; phone or voice intake is built on request. AI-drafted replies are grounded in your knowledge base and the ticket context, and a human approves before sending. Deployment is self-hosted or in our managed cloud, with go-live in one to two weeks.

Brokerage CRM is the native source of that context, with roles for sales, support, compliance and finance; other CRMs connect through an adapter that supplies the context panel. EntropyX Chat, our self-hosted messaging platform, feeds the same queue, and its signed webhooks can pipe ticket events into team rooms.

EntropyX Labs supplies the software, not the service: it does not provide support agents, set your service levels, decide which tickets are complaints or give legal advice on complaint rules. A complaints queue with its own SLA clock and a report is configured per broker, and locking the audit trail, its retention period and keeping each AI draft beside the sent reply are set per deployment.

Sources and further reading

• ASIC Regulatory Guide 271: Internal dispute resolution (September 2021) — Read 13 November 2026: applies to complaints received on or after 5 October 2021 (RG 271.26); complaint defined as in AS/NZS 10002:2014; the word 'complaint' need not be used and a complaint should not be categorised as feedback merely because it was made verbally (RG 271.30-271.32); acknowledge within 24 hours or one business day (RG 271.51); IDR response with outcome and AFCA rights (RG 271.53); standard complaints no later than 30 calendar days (RG 271.56, Table 2); record outcome, remedy and compensation (RG 271.164); record all complaints and track progress (RG 271.179); specialised complaints software or complaint fields in CRM systems (RG 271.180)
• Financial Ombudsman Service: Time limits for businesses — Read 13 November 2026: 8 weeks for most complaints; 15 days for complaints about fraud and scams, payment services and electronic money; the final response should mention the right to refer the complaint to the ombudsman within six months
• Joint Committee of the ESAs: Final report on guidelines for complaints-handling for the securities (ESMA) and banking (EBA) sectors (JC 2014 43, 13 June 2014) — Read 13 November 2026: Guideline 3: register complaints internally in an appropriate manner, for example through a secure electronic register; Guideline 5: analyse complaints-handling data for root causes; Guideline 7: communicate in plain language, respond within national time limits and explain the causes of any delay and when the investigation is likely to be completed
• ICO: Principle (c): Data minimisation — Read 13 November 2026: personal data shall be adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed
• ICO: A guide to data security — Read 13 November 2026: the security principle requires that data can be accessed, altered, disclosed or deleted only by those you have authorised to do so; appropriate access controls
• EU AI Act Service Desk (European Commission): Article 50, Transparency obligations — Read 13 November 2026: providers shall ensure AI systems intended to interact directly with natural persons are designed so that the persons are informed they are interacting with an AI system, unless this is obvious
• EU AI Act Service Desk (European Commission): Article 113, Entry into force and application — Read 13 November 2026: the regulation shall apply from 2 August 2026, with listed exceptions that do not include Article 50

This guide is engineering and product guidance from EntropyX Labs, a technology provider. It is not legal, regulatory or investment advice.