Skip to content
Tessolva
Get started
Tessolva Get started
← All use cases

Industry guide / Brokers

Investigate the account behind the question.

A deposit, withdrawal or rejected order can involve several systems. Customers need the recorded reason and the appropriate next step, without being asked to repeat their story.

Bring account records, platform events and the broker’s policies into the same support workflow.

01 / BrokersIllustrative example

Explain why a withdrawal cannot proceed.

The request

“My account has money in it. Why was my withdrawal rejected, and can I use a different bank account?”

The result / Example reply

The customer-visible record shows the requested amount exceeded the funds available for withdrawal at that time. I’ve separated settled cash from funds committed to open positions and explained the withdrawal method rules for your account. Adding a new destination requires the broker’s secure verification step; I can guide you through it.

A clear explanation of availability and destination rules in one response.

See the work behind the reply

  1. Authenticate the customer and locate the exact withdrawal attempt and legal entity.

  2. Read the official rejection reason, settled funds, margin commitments and source-of-funds restrictions.

  3. Explain permitted options and open the approved destination-verification or support process.

What this workflow needs

Connected context

Broker back office, withdrawal attempt, available-to-withdraw amount, deposit-method history and entity-specific policy.

Where the boundary sits

The agent does not liquidate positions, move money, approve a new beneficiary or advise the customer to change investments.

02 / BrokersIllustrative example

Reconcile a deposit with the account ledger.

The request

“My bank sent the deposit yesterday, but it is missing from my trading account. Where is it?”

The result / Example reply

I found the payment reference in the deposit record, but it has not yet been credited to your trading account. I checked the applicable processing window and opened a reconciliation case because the record needs investigation. The payment reference and timeline are already attached, so you won’t need to repeat them.

One investigation across the payment and trading-account records.

See the work behind the reply

  1. Check verified ownership, currency, payment reference and target trading account.

  2. Compare processor receipt, settlement and ledger-credit events; check duplicate or returned records.

  3. Explain the recorded stage and create a reconciliation case when allowed, then monitor its status.

What this workflow needs

Connected context

Deposit processor, bank reference, settlement events, ledger and reconciliation case tool.

Where the boundary sits

A bank receipt is not proof of a settled broker credit. The agent does not manually credit funds or promise a settlement time absent from the record.

03 / BrokersIllustrative example

Explain a rejected platform order.

The request

“My pending order was triggered, but it never opened. Was the platform broken?”

The result / Example reply

The platform log records a rejection for insufficient available margin at the trigger time. I’ve linked the order event and the broker’s explanation of how triggered orders are checked. I can also check for a service incident affecting that timestamp.

An evidence-based answer rather than a guess about the platform.

See the work behind the reply

  1. Locate the recorded order, instrument, timestamp and rejection code.

  2. Compare the official margin check, market/session status and service incident record.

  3. Explain the event using approved platform documentation and submit a technical case if records conflict.

What this workflow needs

Connected context

Order/event logs, recorded margin check, instrument sessions and incident status.

Where the boundary sits

No investment recommendation or order execution. Compensation and execution disputes remain within the broker’s authorized review process.

04 / BrokersIllustrative example

Restore access to the correct trading environment.

The request

“I can log in to the client portal, but my trading platform says the account is invalid.”

The result / Example reply

The portal shows an active account, and the connection guide identifies a different server for this account type. I’ve opened the secure setup guide with the correct environment. If the login still fails, I can check the next recorded error and continue troubleshooting.

Get the customer into the right environment with fewer repeated checks.

See the work behind the reply

  1. Check the verified account’s active status, demo/live environment and assigned server.

  2. Compare the user’s non-secret connection details with the platform’s setup guidance.

  3. Guide the secure reset or server-selection process and verify the next login status when available.

What this workflow needs

Connected context

Account directory, platform/server mapping, login status and secure recovery flow.

Where the boundary sits

Passwords, two-factor codes and API secrets are never requested in chat. Security locks are not bypassed.

One system, improving over time

Resolve the exception.
Keep the useful procedure.

Tessolva’s proposed improvement loop turns verified resolutions into reusable guidance. Private details are removed, the procedure is validated and tested, and approved guidance can help the AI handle a similar request next time.

Investigate → Resolve → Remove private details → Validate & test → Reuse

Your team handles critical decisions, missing permissions and genuine exceptions. Complexity alone does not mean the request needs a person.

Reference topics

Public documentation helped inform these support topics. Examples use fictional data and your own policies would apply. These references do not indicate partnerships or available Tessolva integrations.

Built around your business

What should your support agent resolve?

Bring us a recurring request and the tools behind it. We can explore the right workflow, connections and boundaries.

Discuss your workflow