Broker automation for FX/CFD brokerages that runs itself.
Automations & AI is TradeCore's workflow engine for FX/CFD brokerages: client journeys drawn on a canvas, rules that fire the instant an event lands, and AI blocks that decide and write. 200+ event triggers across 17 areas of the brokerage.
100+ brokerages run on TradeCore, including MultiBank Group, AvaTrade, IC Markets, FP Markets and Trade Nation.
A journey, running
What is broker automation in a broker CRM?
Broker automation turns the events a brokerage already produces — deposits, KYC decisions, trades, tickets — into work nobody has to do. BrokerIQ is TradeCore's modular CRM and back-office product line for FX/CFD brokers, and Automations & AI is its engine: native on the BrokerIQ CRM core, or standalone on your existing CRM with two-way sync.
Events in — 17 areas
& AI
Hover an area to see what it fires.
Actions out — every module
Messages out — 8 channels, usable inside one sequence
- SMS
- Telegram
- Push
- Webhook
- Slack
- Inbox (in-app)
How do automated client journeys work?
A TradeCore sequence is a graph a broker draws: an event lets a client in, each block does one thing, and branches, waits and goals decide where they go next. Every step is logged as it happens, and the whole journey can be rehearsed on a real client before it is armed.
The journey
Block
Click a block on the canvas to inspect it.
Execution log
Every step keeps its evidence — which fields a branch read, what each edge decided, and which one won.
Starts when signup completes. Ends the moment the client makes a first deposit — the goal is met, so the rest of the journey never runs.
The three journeys play in turn. Pick one, rehearse it, or click any block to inspect it.
The three ready-made journeys on this canvas
New client onboarding
Starts when signup completes. Ends the moment the client makes a first deposit — the goal is met, so the rest of the journey never runs.
- Signup completed — Enrolment trigger
- Send welcome email — Templated email
- Branch on jurisdiction — Client's current data
- Wait until document approved — Or time out after 7 days
- Request a document — Compliance request
- Goal: first deposit — Journey ends when met
Deposit rescue
Starts when a payment fails. Every send has its own exit, so a client caught by quiet hours is routed somewhere different from one whose provider went down.
- Payment failed — Enrolment trigger
- Send SMS — One exit per send outcome
- Wait until morning — Durable timer
- Send templated email — Retry on the other rail
- Create ticket — Assign to next agent
- Goal: deposit completed — Journey ends when met
Win back a quiet client
Starts when the client enters the dormant segment. An AI Branch decides whether to write to them at all, and the journey ends the moment they stop being dormant.
- Entered segment: dormant — Enrolment trigger
- AI Branch — Worth re-engaging?
- AI Email — Written for this client
- Wait 3 days — Durable timer
- Assign sales manager — Round robin across the desk
- Exited segment: dormant — Journey ends
Seven block types, two of them AI
Every step on a TradeCore journey canvas is one of these seven blocks, and a journey is validated before it can go live.
| Block | What it does | Example |
|---|---|---|
| Action | Does one thing to the client or their account. | Email them, tag them, open a ticket, request a document, award a bonus. |
| Branch | Splits the path on the client's current data. | EU clients go left, everyone else goes right. |
| Delay | Waits a set amount of time. | Give them three days before the nudge. |
| Wait Until | Holds until something actually happens — or a timeout. | Wait for the document to be approved, or give up after seven days. |
| Exit | Ends the journey for that client. | Stop here — they converted. |
| AI BranchAI | Asks a model your question about this client and routes on the answer, with a confidence score. | “Is this client a good fit for a call from the sales desk?” |
| AI EmailAI | Writes this one client's email from your brief, inside your template. | “Re-engage them, mention their recent activity, stay professional.” |
Journeys move clients through your lifecycle. BrokerIQ CRM authors the client lifecycle as a state machine per brand and regulatory regime, and moving a client through those states is an action every journey can take.
When should you use a rule instead of a journey?
A TradeCore rule fires when one event needs an immediate reaction and nothing has to be remembered; a TradeCore sequence walks a client through several steps over time. Rules are stateless and instant — one or more triggers, a condition, up to 10 ordered actions.
Event
Deposit completed
Condition
Amount over
evaluating…
Actions — in order, fail-soft
Up to 10 actions per rule, executed in order. If one fails, the rest still run — and each outcome is logged separately.
76 rules already written, across 7 areas.
Onboarding, KYC & Compliance, Payments, Sales & Retention, Risk & Security, Support and Trading. Each one is a real prefill — adjust it and save.
Test it before you arm it
Run a rule against a sample event, see the condition verdict and every action's rendered parameters — with nothing executed.
Every firing is on the record
Which event, condition true or false, and per-action success, failure or skip with a reason. An operator can retry a failed action.
Decide at the payment gate
A rule can hold a deposit for review before it settles, rather than reacting after the money has landed.
Rules act at the payment gate. A TradeCore rule can hold a deposit for review before it settles, on the same rails that process every deposit and withdrawal.
How does AI work inside broker automation?
TradeCore puts AI where a judgement call is needed and a person would otherwise make it: routing a client inside a journey, writing that one client's email, and drafting the answer to a support ticket. Decisions and suggestions come with a confidence score, every AI step is logged, and all of it runs on your own provider key.
AI decides
Write the decision in plain English.
“Is this client a good fit for a call from the sales desk?”
→ took the Yes path
The model reads the client's context and returns a decision with a confidence score. The client takes the Yes path or the No path.
AI writes
Write the brief, not the email.
“Re-engage them, mention their recent activity, stay professional.”
Your template
The model composes a subject and body for that one client, from their own data, rendered inside your approved template.
AI works the queue
Suggest, never send.
“I requested a withdrawal three days ago and nothing has happened.”
Withdrawals
High — client is blocked from funds
Draft ready for review
SupportIQ suggests a ticket's category, its priority with a one-line rationale, and a first-pass reply. An agent accepts or discards each one, and which it was is recorded.
- Bring your own key and endpoint
- Choose the model per block
- No TradeCore AI markup
- Off until you switch it on, per brand
- Every AI step logged on the client
- Internal notes never sent to the model
- AI runs on a budget
AI works the support queue too. SupportIQ AI suggests a ticket's category, its priority with a one-line rationale, and a first-pass reply, and an agent accepts or discards each one.
What can start an automation, and what can it do?
200+ event triggers across 17 areas of the brokerage can start a TradeCore automation. Its actions reach back into the client record, payments, trading accounts, compliance, support, the sales desk and bonuses.
Events in — 17 areas, 200+ triggers
| Area of the brokerage | Example triggers |
|---|---|
| Client | Client created · Client state changed · Logged in from a new country |
| Payments & Wallets | Deposit completed · Withdrawal rejected · Payment account verified |
| KYC & Documents | Document approved · Document expiring in 30 days · KYC rejected |
| Trading | Trading account created · Trade executed · Trade closed |
| Tickets & Support | Ticket created · Ticket resolved · CSAT submitted |
| Partners | Partner approved · Partner suspended · Tier promoted |
| Deals | Deal created · Deal stage changed · Deal won |
| Bonuses | Bonus applied · Bonus expiring · Bonus converted |
| Segments | Entered a segment · Exited a segment |
| Tasks | Task completed · Task overdue · Task unassigned |
| Legal & Consent | Consent granted · Consent withdrawn |
| Questionnaires | Questionnaire completed · Deadline passed |
| Corporate | Beneficiary added · Ownership warning raised |
| Engagement & Rewards | Quest completed · Tier achieved · Coins credited |
| Marketing | Promo code applied · Referral qualified |
| Email engaged | |
| Bans | Client banned · Ban lifted |
Actions out — grouped by what they act on
The client record
- Add tag
- Remove tag
- Set sales status
- Set compliance status
- Move through your lifecycle states
- Archive client
- Restore client
Messages
- Send templated email
- Send SMS
- Send a webhook
- Notify staff
- Notify the client's portal inbox
Tasks & tickets
- Create a task
- Create a ticket
- Run a ticket macro
- Assign to the next agent
- Pause SLA
- Resume SLA
- Request CSAT
- Request NPS
The sales desk
- Assign sales manager
- Unassign sales manager
- Auto-assign sales manager
Trading accounts
- Enable trading accounts
- Disable trading accounts
- Archive trading accounts
Limits & permissions
- Set a limit override
- Remove a limit override
- Set a permission override
- Remove a permission override
Compliance
- Request a document
Payments
- Hold a deposit for review
- Verify a payment account
Bonuses & rewards
- Award a bonus
- Grant reward coins
- Unlock a quest
Journeys
- Enrol in another journey
The action library grows with your modules. Every TradeCore action belongs to a product area, so the Marketing module's bonus, coin and quest actions sit in the same builder your team already uses.
How do you automate on a client going quiet?
Most automation can only react to something happening. A TradeCore Dynamic Segment is a standing question about your book — clients who haven't traded in 30 days, clients whose last deposit was more than 30 days ago — that TradeCore keeps answering, and fires at the moment the answer changes.
A client goes quiet at 3am on a Tuesday.The journey starts at 3am on a Tuesday.
The standing question
Last deposit more than 30 days ago
and Total deposits over
Members
the segment
outside
inside
Segment entered — journey starts
The win-back journey enrols this client. Nobody ran a report.
Segment exited — journey ends
They deposited, so they are no longer dormant. The journey stops mid-flight.
A TradeCore Dynamic Segment is defined on three things.
| You can ask about | Which means |
|---|---|
| Client attributes | 24 of them, including country, nationality, jurisdiction, language, client type, profile state, sales status, compliance status, risk score, suitability score, registration date, email verified, has deposited, total deposits, last deposit, last withdrawal, last trade, last login, last contact, last client message, last document uploaded and brand. |
| Aggregates over their history | Deposits, withdrawals, bonuses and communications — with count, sum, average, min, max or distinct-count. |
| The window that matters | A rolling number of days, the current calendar week or month, all time, or measured from a date that differs per client — “since their last deposit”. |
Every event re-asks the question
Anything that happens to a client re-checks whether they still belong in each of your live Dynamic Segments.
Switching one on never floods you
Activating a Dynamic Segment that matches fifty thousand clients writes the membership and announces nothing. Nobody entered — the segment simply started existing.
A segment that drifts tells you
When the nightly reconciliation has to correct a Dynamic Segment, it reports what it corrected rather than healing quietly.
Segments reward, too. A TradeCore Dynamic Segment can trigger a coin multiplier boost in Loyalty & Rewards, the coin economy in the Marketing module.
How do you stop automation from over-messaging clients?
Every send in TradeCore passes nine checks before it leaves: consent, frequency caps, quiet hours in the client's own timezone, suppression, and how many competing journeys that client is already in, among them. A blocked send is recorded with its reason, not silently dropped.
Before it leaves
Marketing email, their time- Consent
- Frequency cap
- Quiet hours
- Suppression list
- Address on file
- Competing journeys
- Jurisdiction
- Renderable content
- AI budget
On the client's record
Sent
Delivered — every gate cleared
Consent, caps, quiet hours, suppression and competing journeys all checked before the message left.
A blocked send is never silently dropped. Each of the nine reasons is its own recorded outcome, and each one can route the client somewhere different.
A marketing email that clears every gate: Delivered — every gate cleared. Consent, caps, quiet hours, suppression and competing journeys all checked before the message left.
A marketing email stopped at quiet hours: Refused — quiet hours. The journey carries on down its quiet-hours exit. The refusal is recorded with its reason, on the client's record and in the journey's refusal list.
Change it safely
Editing a live journey freezes the previous version first, so execution history is never orphaned. Pausing lets a client finish the action they are in, then stops.
- Version freeze on edit
- Graceful pause
Nothing runs away
Per-client fan-out limits and a hard chain-depth cap stop a mis-drawn automation from cascading, and a stall detector raises stuck journeys as a fault.
- Fan-out limits
- Chain-depth cap
- Stall detector
Nothing fails quietly
Failing-send detection names a broken email or SMS rail, and withdrawing consent exits the client from every marketing journey with an audit entry per enrolment.
- Failing-send detection
- Consent auto-exit
- Field-level PII encryption
Every decision is on the record. Each refusal, retry and AI decision lands on the client's activity stream in BrokerIQ CRM, beside the audit log of every change made to the client.
How much automation you run, and how it grows
TradeCore's free plan runs 3 rules and 1 sequence on your live book, and its shop takes that up to 40 rules and 10 sequences. TradeCore's Core plan includes 10 rules and 5 sequences, and its packs stack with no ceiling. Every plan sends on email, SMS, WhatsApp, Telegram, push, Slack and the in-app inbox; outbound webhooks come with TradeCore's Core plan.
The free plan's shop lifts ceilings.Core removes them.
| Capacity | TradeCore's free planThe shop lifts ceilings | Core · €2,500 a month, flatPacks stack with no ceiling |
|---|---|---|
| Automation rulesInstant reactions: an event, a condition, up to 10 actions. | 3Up to 40 in the shop · €350 a month | 10+50 per pack · €300 a month · no ceiling |
| SequencesClient journeys drawn on the canvas. | 1Up to 10 in the shop · €650 a month | 5+10 per pack · €500 a month · no ceiling |
| Dynamic SegmentsLive client cohorts whose entry and exit start and end journeys. | 2Up to 10 in the shop · €15 a month each | 10+10 per pack · €100 a month · no ceiling |
| Automatic email triggersEmails the platform sends by itself when something happens. | 20Up to 60 in the shop · +20 for €80 a month | UnlimitedIncluded |
| Marketing emails a monthCampaign and journey sends. Sign-in, verification and payment emails are never counted. | 1,000+3,000 per pack · €99 a month · no cap | UnmeteredIncluded |
| Messaging channelsEmail, SMS, WhatsApp, Telegram, push, webhook, Slack and the in-app inbox. | 7 of 8Webhooks come with Core | All 8Included |
Every price is published. TradeCore lists every plan, capacity pack and add-on at a monthly price. No per-trader fees, no per-trade fees, no setup fees.
What's inside Automations & AI
The whole module, named — sequences, rules, actions, Dynamic Segments, AI, channels and guardrails.
Sequences
Client journeys drawn on a canvas, validated, rehearsed and logged step by step.
- Visual drag-and-drop canvas with a config panel per block
- Validated on save: one entry block, acyclic, every block reachable
- Every branch carries a default path — a journey that cannot be walked cannot be activated
- 7 block types, including AI Branch and AI Email
- Branch on the client's current data, with nested AND/OR conditions
- Wait Until a real event happens, or a timeout — a separate exit for each
- Durable delay timers that survive a restart
- Goals, event-driven or property-based, that end the journey the moment they are met
- A met goal is credited as a conversion
- Per-send-outcome routing — each outcome is its own routable exit
- Rehearsal mode: walk a real client with nothing sent, written or announced
- Six enrolment sources — an event, a schedule, a manual enrolment, a bulk enrolment, a rule, or another journey
- Re-enrolment policy per journey: never, after a cooldown, or always
- Journeys can hand over to other journeys
- Pausing is graceful — a client mid-action finishes it first
- Editing a live journey freezes the previous version
- Forensic per-step log: the fields a branch read, each edge's verdict, the winning condition verbatim
- Retries three times with 1-minute, 5-minute and 30-minute backoff
- 11 ready-made journeys in 3 categories — Onboarding, Funding, Retention
- Journey stats including goal conversion rate and completion rate
TradeCore Automations & AI — Sequences
Client journeys drawn on a canvas, validated, rehearsed and logged step by step.
- Visual drag-and-drop canvas with a config panel per block
- Validated on save: one entry block, acyclic, every block reachable
- Every branch carries a default path — a journey that cannot be walked cannot be activated
- 7 block types, including AI Branch and AI Email
- Branch on the client's current data, with nested AND/OR conditions
- Wait Until a real event happens, or a timeout — a separate exit for each
- Durable delay timers that survive a restart
- Goals, event-driven or property-based, that end the journey the moment they are met
- A met goal is credited as a conversion
- Per-send-outcome routing — each outcome is its own routable exit
- Rehearsal mode: walk a real client with nothing sent, written or announced
- Six enrolment sources — an event, a schedule, a manual enrolment, a bulk enrolment, a rule, or another journey
- Re-enrolment policy per journey: never, after a cooldown, or always
- Journeys can hand over to other journeys
- Pausing is graceful — a client mid-action finishes it first
- Editing a live journey freezes the previous version
- Forensic per-step log: the fields a branch read, each edge's verdict, the winning condition verbatim
- Retries three times with 1-minute, 5-minute and 30-minute backoff
- 11 ready-made journeys in 3 categories — Onboarding, Funding, Retention
- Journey stats including goal conversion rate and completion rate
TradeCore Automations & AI — Rules
Instant reactions to one event, tested before they are armed and logged per action.
- One or more triggers, a condition, then up to 10 ordered actions (5 by default)
- Fail-soft: if action 3 fails, actions 4 and 5 still run
- Fire immediately, or after a delay
- Priority ordering across rules on the same event
- The same event can never fire the same rule twice
- Test against a sample payload with nothing executed
- Full execution history per action, with skip reasons
- An operator can retry a failed action
- Hold a deposit for review before it settles
- Work distribution by declared percentage split across teams
- Then round-robin, least-loaded, random, or the client's own manager
- An allocation ledger proving the split was honoured
- 76 ready-made rules across 7 categories
- Onboarding 9 · KYC & Compliance 25 · Payments 12 · Sales & Retention 13
- Risk & Security 7 · Support 4 · Trading 6
TradeCore Automations & AI — Actions
What a rule or a journey can do, grouped by what it acts on.
- The client record: add tag, remove tag, set sales status, set compliance status, move through your lifecycle states, archive client, restore client
- Messages: send templated email, send SMS, send a webhook, notify staff, notify the client's portal inbox
- Tasks & tickets: create a task, create a ticket, run a ticket macro, assign to the next agent, pause SLA, resume SLA, request CSAT, request NPS
- The sales desk: assign sales manager, unassign sales manager, auto-assign sales manager
- Trading accounts: enable trading accounts, disable trading accounts, archive trading accounts
- Limits & permissions: set a limit override, remove a limit override, set a permission override, remove a permission override
- Compliance: request a document
- Payments: hold a deposit for review, verify a payment account
- Bonuses & rewards: award a bonus, grant reward coins, unlock a quest
- Journeys: enrol in another journey
- Every action belongs to a product area, so adding a module adds its actions to the same builder
TradeCore Automations & AI — Dynamic Segments
Standing questions about the book that keep answering themselves, and trigger journeys.
- A broker-configurable surface — no developer, no ticket
- 24 client attributes, from country and jurisdiction to last login and last trade
- Aggregates over 4 collections: deposits, withdrawals, bonuses, communications
- Count, sum, average, min, max or distinct-count
- Rolling, calendar, all-time, or measured from a date that differs per client
- Entering a segment and leaving one are both automation triggers
- Every client event re-asks whether they still belong
- A nightly reconciliation re-asks it of the whole book and reports what it corrected
- A boundary tick wakes exactly the clients whose rolling window has just elapsed
- Activating a segment announces nothing — a silent backfill, so nothing floods
- Lifecycle Draft → Active ⇄ Inactive; nothing returns to Draft
- A live definition is changed by deactivating, redefining and reactivating
- Amount questions are asked in one currency, so a cohort total is never a mixed-currency number
TradeCore Automations & AI — AI
AI where a judgement call is needed, on your own key, switched on per brand.
- AI Branch — write the decision in plain English, the model routes the client
- Every AI Branch returns a decision with a confidence score
- AI Email — write the brief, the model composes that one client's subject and body
- AI Email renders inside the brand's approved template
- AI Email sends inside a journey your team built and switched on
- Choose the model per block, or use the brand default
- Bring your own key and endpoint — any OpenAI-compatible provider works
- The key is stored encrypted; TradeCore never proxies, marks up or invoices AI usage
- AI is off until the broker turns it on, per brand
- AI steps are logged on the client's activity trail
- A step whose AI allowance is spent is recorded as skipped, never retried forever
- SupportIQ AI suggests a ticket's category, its priority with a one-line rationale, and a first-pass reply
- An agent accepts or discards every support suggestion, and which it was is recorded
- Internal notes are never sent to the model
TradeCore Automations & AI — Channels
All 8 channels, usable inside one sequence.
- SMS
- Telegram
- Push
- Webhook
- Slack
- Inbox — the client's portal inbox
- All 8 usable inside one sequence
TradeCore Automations & AI — Guardrails
The checks every send passes, and what stops an automation running away.
- Frequency caps — a per-brand ceiling, with optional per-channel sub-caps
- Quiet hours in the client's own timezone
- Consent withdrawal auto-exits every marketing journey, with an audit entry
- Conflict groups cap how many competing journeys one client can be in
- Nine recorded refusal reasons, each visible on the client's record
- Runaway protection: fan-out limits and a chain-depth cap
- A stall detector raises stuck journeys as a fault
- Failing-send detection names a broken email or SMS rail
- Personal data encrypted at field level
Automations & AI against the alternatives
Unlike legacy broker CRMs and generic marketing automation, TradeCore's Automations & AI is fed by the brokerage's own events and acts back on payments, trading, compliance, support and partners.
| Capability | BrokerIQTradeCore | Legacy broker CRMs | Generic marketing automation |
|---|---|---|---|
Event triggers | 200+ broker events across 17 areas | Custom-coded per event | Web and email events only |
Journey builder | Visual canvas: branch, wait-for-event, delay, goal, AI | Linear or none | Linear drip sequences |
Waits on real events | Wait until a deposit, a document approval, a ticket resolution | Not available | Time delays only |
AI inside the workflow | AI routing with a confidence score, and AI-written email inside your template | None | Subject-line suggestions |
Outcome-aware routing | Every send outcome is its own routable exit — sent, no consent, frequency-capped, quiet hours, no address on file, provider failed | Sent or not sent | Sent or bounced |
Trigger on inactivity | Fires when a client stops qualifying, on its own | Report plus a manual list | Time-since-last-open only |
Rehearsal | Full dry run on a real client, nothing sent | Not available | Test send only |
Guardrails | Caps, quiet hours, consent auto-exit, conflict groups | Manual discipline | Frequency caps only |
Reach of actions | Clients, payments, trading, compliance, support, partners, bonuses | Varies by build | Contacts and lists |
Runs on your existing CRM | Yes — two-way sync via APIs and webhooks | No | Partially |
Competitor columns describe categories of product, not any named vendor. TradeCore's counts are its own: 200+ event triggers across 17 areas of the brokerage, 76 ready-made rules and 11 ready-made journeys.
Questions about Automations & AI
What brokers ask before they let an engine work their book.
Use a TradeCore rule when one event needs an immediate reaction and nothing has to be remembered. Use a sequence — a client journey — when the client has to be walked through several steps over time. Rules are stateless and instant, with up to 10 ordered actions that keep running even if one of them fails. Sequences are stateful and patient, with branches, delays, waits on real events, and a goal that ends the journey the moment it is met.
Two block types put AI inside the workflow. AI Branch takes a question written in plain English, reads the client's context, and returns a decision with a confidence score that routes them down the Yes path or the No path. AI Email takes a brief and composes a subject and body for that one client, rendered inside your approved template. You choose the model per block or use your brand default, and both blocks log what they did on the client's activity trail.
Only inside a journey your team built and switched on. There, AI Email writes each client's email from your brief, inside your approved template, and logs it on the client's activity trail. In the SupportIQ queue, every AI suggestion is accepted or discarded by an agent, and which it was is recorded. AI stays off until you enable it per brand.
Yes. The Automations & AI module runs two ways: natively on the BrokerIQ CRM core, sharing one data layer with every other module, or standalone against the CRM your brokerage already runs, with two-way sync via APIs and webhooks. Salesforce, HubSpot and Pipedrive integrations are live today, Zapier is available, and in-house CRMs are supported.
Yes. In TradeCore, journeys are drawn on a visual canvas and rules are built from a trigger, a condition and a list of actions, with no code anywhere. Nobody starts from a blank page either: 76 ready-made rules across 7 categories and 11 ready-made journeys ship with the module. You can test a rule against a sample event and rehearse a whole journey on a real client before either one is armed.
TradeCore's free plan includes 3 rules and 1 sequence, running on your live book with no time limit, and its shop takes that up to 40 rules and 10 sequences. TradeCore's Core plan includes 10 rules and 5 sequences, and packs of 50 rules or 10 sequences stack on top with no ceiling. Every plan sends on email, SMS, WhatsApp, Telegram, push, Slack and the in-app inbox, and outbound webhooks come with TradeCore's Core plan.
Still have questions?
Contact our teamRun Automations & AI for free
TradeCore's free plan switches on the BrokerIQ CRM core and every module, with unlimited clients, no time limit and no card to sign up. Your environment is ready as soon as you finish signup.
What TradeCore's free plan includes · TradeCore plans and add-on prices