Automation still needs an owner.

Convenience creates a responsibility question

The appeal of automated trading is that software can carry out a defined process without requiring you to place every order. That is useful. It also changes what you need to pay attention to. Instead of entering each trade, you need to understand whether the configured process is operating and who handles a problem when it is not.

A support conversation can become frustrating when the customer expects investment guidance and the team is equipped to diagnose a technical connection. A second source of confusion is assuming that someone monitors every account continuously simply because the software runs in the cloud.

The answer is to define responsibilities before an incident. What does the platform operate? What does the broker control? What information is available to support? What remains a decision for the customer? These questions belong in the product explanation, alongside the features.

Separate an investment question from an operational question

“Why is my account down?” can refer to market exposure, a strategy’s behaviour, costs, a cash movement or an execution problem. Technical support can investigate whether a service is running, whether a broker accepted an order and whether the configured state matches what the software received.

That is different from deciding whether you should continue holding a strategy, increase its allocation or take a different level of risk. A clear scope protects the conversation from turning a troubleshooting answer into a recommendation it was never designed to provide.

SquaredQ’s documented support role includes connection and execution diagnostics, infrastructure maintenance, entitlements and operational assistance. The supplied product workflow does not include personalised strategy selection or suitability recommendations. If your question concerns your broader financial circumstances, recognise that it goes beyond this technical support scope.

Useful monitoring starts with the broker account

The SEC’s April 2026 account-security bulletin encourages investors to use available multifactor authentication and account alerts. Alerts may cover events such as logins, transactions and transfers, depending on what the investment firm offers. Those are useful controls to review directly with your broker. Read the SEC’s updated account-security bulletin.

For an automated setup, combine the broker record with the platform’s operational view. Check the intended account and environment, connection state, execution state and relevant risk configuration. A dashboard balance alone is not a complete check of working orders or current holdings.

The appropriate review routine depends on the product and your situation; this article does not prescribe a universal frequency. The practical objective is that someone knows what should be happening and how to recognise a condition that requires attention.

Make a support request that can be investigated

Describe the expected action and the observed result separately. “I activated this configuration at this time, and the broker shows this rejection” is easier to investigate than “nothing works.” Include the broker, paper or live environment, product and time window, along with the error text where appropriate.

Use the designated support channel for any account-specific reference. Redact screenshots so they contain only what is needed. Do not paste API secrets, passwords, recovery codes or other credentials into a general contact message.

If the issue concerns an actual position or working order, check it at the broker. A reply from support is not itself evidence that an order has been cancelled or a holding sold. Confirm the broker state after any corrective action, especially if you are also making manual changes.

What SquaredQ support can see and do

The documented administrative workflow includes customer and subscription records, cloud-instance state, Reader and Gateway status, relevant NAV and freshness information, and operational history. The team can diagnose failures, restart services, retry or recommission infrastructure, and access the customer desktop for support and maintenance.

These capabilities explain why the security overview does not describe the execution environment as inaccessible to administrators. Broker custody and administrative access are different matters. Knowing both is part of understanding the service.

Those capabilities also do not establish a guaranteed response time or continuous human oversight. Check the current support arrangements and service terms for the actual commitment. This article makes no 24/7 support or service-level promise that is absent from those arrangements.

A handoff should leave you knowing the next step

When an incident is resolved, identify what changed, what you need to verify and whether execution remains disarmed. A repaired connection does not necessarily mean trading has restarted. In SquaredQ’s documented workflow, a latched risk stop requires the appropriate user action before reactivation.

Before that action, review the account’s current holdings and orders, then the products, allocations and risk settings you intend to use. A stale configuration should not become live merely because a technical fault was fixed. The MyAlgo guide keeps this distinction visible.

SquaredQ addresses the ownership question through a defined technical support role, documented controls and an accessible help centre. Automation can reduce repetitive work. A clear division of responsibilities helps you keep that convenience without losing track of the account behind it.