Topic: Syspro Torque

Syspro Torque is an AI platform that automates the work that falls between your systems. It does two things from one place:

• Automation: Workflows that run on their own, triggered by a schedule, an incoming message, or a file arriving. No one has to press a button.
• Sidekick : A conversational agent you can ask in plain language to look something up, pull a report, or carry out a task on your behalf.

Sidekick, managed agents, and workflows are three parts of Syspro Torque that do different jobs. Managed agents monitor, analyse, and recommend, and workflows execute. Both are grounded in the customer's live ERP data and the rules extracted from their own documents, and neither acts outside what its operator is already permitted to do in Syspro.

Sidekick is how everyone reaches the managed agents and workflows. The user asks questions in plain language and Sidekick answers, or brings in whichever managed agent that is required. They never know which specialist exists or which system holds the answer. Approvals, and anything else that needs a person, land bank in the same conversation.

In Syspro, this needs no integration work. From Syspro 8 2026 R1 and later, users on the Syspro Web UI (Avanti) reach Syspro Torque through Sidekick embedded in the product.

Managed agent	Workflow
A configured AI agent built for a specific business role. Each managed agent has a defined system prompt, behaviour instructions, capability layers, and guardrails that scope it to the business objects and data it is allowed to access. Managed agents can be called directly by a user or delegated to by Sidekick.	A predetermined, repeatable sequence of steps that Torque executes automatically. Workflows are more structured and deterministic than managed agents. Each step is defined and maps to a visual graph. They are built by Torque Builder or configured manually, and can be triggered by a user, a file arriving in a watched folder, a schedule, a webhook, or an FTP event.
Managed agents are grounded in the customer's operation, therefore reasons over their live ERP data and the rules extracted from their own policy documents, never a general-purpose model guessing.	Workflows run on-premises on the Syspro Torque Executor , inside the customer's network, reaching anything that server can reach.
An agent can only ever act within the access its operator already has in Syspro.	It can started by a schedule, a file arriving, a webhook, an inbound message, or an agent that determines it is needed.
Managed agents improves when you give it more rules and context to work from, without ever training a model on your data.	When an approval step is required it stops the run and routes the decision back into the approver's Sidekick chat to respond before continuing.
	Every step, input, and outcome is recorded, and actioned inside the ERP rather than a separate analytics tool.
Managed agents are built by an user with an Editor role, by describing it to Torque-Builder in plain language.	Workflows are built by an user with an Editor role, by describing the process to to Torque-Builder in plain language.
Managed agents are reached via Sidekick . Sidekick delegates to it, or open it directly as its own chat.	Workflows are triggered, or called by an agent mid-conversation.

The thinking happens in our cloud. The touching of your data happens on you server, through a service you install (Syspro Torque Executor ) and can switch off.

• The conversation runs in the Syspro Torque cloud. Sidekick and every Managed Agent reason in Syspro's Azure tenancy, in the customer's assigned region. Conversation content is processed by our AI provider under terms that exclude it form model training.

• The work runs on the customer's server. Every database query, business object call and workflow step executes on the Syspro Torque Executor .

• Nothing is copied, replicated or synced. Syspro Torque does not bulk-export databases and does not fetch data no tasks has asked for. What leaves the network is the scope of the work the customer asked for, and nothing else.

• Outbound only - no inbound ports. The Syspro Torque Executor initiates every connection itself, out over HTTPS and AMQP-TLS. No inbound firewall openings, no exposed endpoint. Its only listener is a setup page bound to localhost on that server.

No. You describe what you want in plain English, and the Syspro Torque Builder drafts the workflow or Managed Agent for you. Business users work through Sidekick and the visual builder; your IT team handles the one-time setup of connections and the on-premises Syspro Torque Executor .

Manufacturers and distributors who lose time to manual data movement, one-off lookups, and approvals and notifications that someone has to trigger by hand. If your systems don't talk to each other, Syspro Torque is the layer that connects them.

A short onboarding: your Syspro Torque tenant is created, your IT team installs the on-premises Syspro Torque Executor (a guided, one-time setup), and you connect Syspro Torque to your systems - typically your Syspro business objects and any relevant SQL databases. From there you invite your team and start building.

Install the Syspro Torque Executor on a Windows server inside your network that can reach your Syspro application server and SQL Server, and has outbound HTTPS access to the Syspro Torque cloud.

• Put it close to Syspro and SQL Server on the same LAN segment where possible.

  The Syspro Torque Executor communicates with those systems constantly; low-latency local access matters.

• Use a dedicated or lightly-loaded server. The Syspro Torque Executor is an always-on background service. It can share a server with other workloads, but size RAM accordingly.

• Co-location with Syspro or SQL is allowed but not required.

  The only hard requirement is network reach-ability to those systems and outbound HTTPS to the cloud. A separate integration or utility server works equally well.

• Multiple sites: install more than one Syspro Torque Executor and use tags to route specific connections to specific Syspro Torque Executor s.

  For example:

  , There could be one Syspro Torque Executor per plant or region. The cloud distributes work across Syspro Torque Executor s that share a tag .

There are five capability areas, all from the same platform:

Capability	What it means for you
Build Your Own	Managed Agents and automations shaped to your roles and processes, not generic templates.
Teaching Syspro Torque Your Business	Give an agent your context and rules so it applies them automatically.
Conversational Access	Ask questions of your own data in plain language and get answers back.
Run & Integrate	Unattended workflows that connect your systems and run without supervision.
Insight on Demand	Live tables and charts rendered right inside a conversation.

Your data is stored in Syspro's Azure tenancy in your assigned region. The AI models themselves are a separate matter: agent conversations are currently processed by Anthropic's API, and Microsoft Azure AI is used for supporting functions such as document and schema indexing. Conversation content is therefore sent outside Azure to a third-party AI provider.

Yes, and it is isolated by design at three independent layers:

• Database: Every customer's records are separated by tenant-level filtering enforced at the data layer, so one customer's queries can only ever see their own data.
• Messaging: Each customer gets a dedicated message-broker virtual host with its own credentials. Cross-customer message flow is impossible at the infrastructure level, not just in application code.
• Encryption: Each customer's secrets are protected with per-tenant encryption keys.
Customer-managed encryption keys (BYOK) are not supported at this stage, and keys are not shared across regions.

Sysprodoes not train models on your data. Syspro Torque runs on leading enterprise AI providers (currently Microsoft Azure and Anthropic), and our AI providers' terms exclude customer data from model training. Because this rests on our AI providers' contractual terms, ask your account team or the SysproAI enablement team for the current, written data-handling commitment before you rely on it in your own compliance review.

Syspro Torque 's AI runs on leading enterprise AI providers — currently Microsoft Azure and Anthropic. When an agent answers a question, the content of that conversation is sent to the AI provider to work out which action to take. Where a task requires the agent to reason over data retrieved from your systems — for example, summarizing an order book or explaining an exception — that data forms part of the conversation content and is sent to the AI provider as well. Our AI providers' terms exclude this content from model training..

Access to customer conversation data is tightly controlled. Every access goes through a single audited gateway that applies PII redaction and consent controls, and every access is written to tamper-evident records. Emergency ("break-glass") access is time-limited, requires a documented reason, raises an immediate alert to Syspro platform operations team, and enters an independently reviewed queue. No Syspro employee has open, unlogged access to your conversations.

Data at rest is protected by Azure-managed database encryption plus an envelope-encryption scheme for secrets and credentials, with the master keys held in a hardened key vault. Traffic between your browser, the Syspro Torque Executor , and the Syspro Torque cloud is encrypted in transit. Your IT team can find the connectivity specifics in the Syspro Torque System Requirements document.

Yes. Syspro Torque supports exporting your tenant's data and erasing it on request, in line with data-protection obligations. Erasure operates at the level of your whole tenant. For a specific data-subject request or a formal export, contact your account team so it can be handled correctly.

Syspro maintains a security and compliance program. For current certifications, their scope, and formal security documentation, request the latest security pack from your account team or the Syspro AI enablement team - certifications and their coverage change over time, so we prefer to point you to the authoritative source rather than restate it here.

Syspro Torque is built so the AI doesn't answer from memory. The AI's job is to choose the right action and fill in its parameters - it does not invent the numbers. The actual figures come from live queries against your own Syspro and SQL data, executed deterministically in an isolated environment. The same request against the same data gives you the same result.

Yes. Every answer can be traced to the exact business object or query it called and the data that came back. Syspro Torque records the AI's reasoning steps and tool calls so you can open a response and see what it actually did, rather than taking the answer on faith.

No. A single headline number doesn't tell you much about your workflows on your data. The stronger guarantee is architectural: answers are grounded in live queries against your own systems, and every answer is traceable to its source. .

Automations can include an approval or preview step, so a person confirms before anything is committed. previewing a batch of changes before they are applied.

Syspro Torque runs on leading enterprise AI models from Microsoft Azure and Anthropic. The platform is model-flexible — Sysproselects and manages the approved models centrally, so you benefit from improvements without having to manage model choices yourself.

Torque-Builder is the engine room where automation is built, and Sidekick is where you drive them once they exist.

Environments	Description
Sidekick	Sidekick is the place you use Syspro Torque day-to-day. You ask it something in plain language and it either answers directly or pulls in a specialist managed agent behind the scenes and brings the results back in one reply. It runs workflows on your behalf, answers questions, opens results, and delegates to specialists. All users with a Viewer role have access to it. Sidekick is personal to you and keeps context within a conversation, so you can ask follow-up questions without repeating yourself. Your conversation history is saved, and you can reopen an earlier chat at any time. Sidekick does not build things directly, however it will however point you to Torque-Builder if required.
Torque Builder	Torque-Builder is the authoring tool, the place where you create things. You describe a managed agent or a workflow in plain language and the builder constructs it, asks clarifying questions, and proposes capabilities for you to review and apply. Only users with an Editor role have access to it.

• Open the Help Assistant (Torque Helper) from anywhere in the platform by clicking on the question mark icon. It slides open from the side, so it does not disrupt your current chat.

  A persistent help tool available in the top-right corner of the Torque platform at any time. It answers questions about how Torque works by drawing on ingested Torque guides, Sidekick knowledge, and Syspro 8 business object schemas. It is distinct from Sidekick and does not execute tasks.

• Ask a how to question, for example, "How do I configure a SQL connection to Syspro?".

• Follow the returned steps and tips. Use previous chats in the panel to revisit earlier answers.

Syspro Torque and AI Assistant are both Syspro AI offerings, but they sit in different places, serve different purposes, and fall under different commercial models.

AI Assistant is the original AI tool set built into the product and sits within the ERP and subscription, while Syspro Torque is a fundamentally different offering, a separate cloud platform.

Syspro Torque is a cloud-first, no-code platform embedded in Syspro that understands your business data, business objects, and workflows. Its guided library of pre-built AI Assistants and AI agents, together with powerful tools for creating and deploying custom AI solutions, enables organizations to automate tasks, accelerate decision-making, and augment day-to-day operations with consistent, context-aware AI.

The Syspro Torque widget brings AI directly into the Syspro Web UI (Avanti), giving users seamless access to intelligent assistants, agents, and insights within the context of their daily tasks, making AI a natural extension of the Syspro experience.

Where AI Assistant works inside Syspro, Syspro Torque sits across the systems you run, connecting Syspro, SQL databases, file systems, and external services, and moving work between them.

• Ensure you have a valid tenant and user account.

• Ensure you entered the correct password (use Forget password on the sign-in page if you do not have it).

When you see the Session expired - attempting re-authentication message, Syspro Torque is trying to restore your session automatically.

• Wait a few seconds and let it complete, then refresh the page.

• If you are not signed back in, sign out of and sign in again with your email and password.

• If the page is still blank or shows an error after signing in, clear cookies for the domain only, then sign in manually.

Syspro Administrators creates the tenant on the customer's behalf. The tenant and its first tenant administrator (TenantAdmin) are created together.

• To add users to your tenant, go to Admin > Members.

  Within the Syspro Torque Admin portal you can add users under Admin > Platform > Users or within Syspro Torque you can add users under Admin > Members.
  In Syspro Torque , users and members refer to the same thing - they're interchangeable terms for people who have been invited to and have access to your tenant.
  
  Only TenantAdmin's can create and manage users.

• For each person, enter their email, and optional display name, and a starting role.

• Choose one of the required role:.

  • • Viewer — read-only access

  • • Editor — can build and modify workflows and Managed Agents

  • • Manager — Editor access, plus managing teams, assigning resource permissions, sharing connections, and seeing execution history across the tenant

  • • Tenant Admin — full access, including inviting and managing users

• Roles are cumulative and each includes everything below it.

• Click Add Member to send the invitation. If the person already has a Syspro Torque account they are added directly, if not, Syspro Torque creates the account and emails a one-time setup link (valid for seven days).

  Within Syspro Torque , under Admin > Members, there is no resend invitation button. If a welcome email does not arrive, confirm the address and check spam, if needed, remove and re-add the member to trigger a fresh email.

• The invitee select Set up your account, sets a password, and sign in on the Home Dashboard (https://torque.sysprocloud.com)

• TenantAdmin's can adjust users later from the same page, change a role from the Roles drop-down, deactivate (platform wide), remove (from the current tenant), or set per-category domain permissions.

You install the Syspro Torque Executor to link Syspro Torque cloud to your on-premises systems. It runs as a Windows service on a server inside your network. Until a Syspro Torque Executor is online, workflows and managed agents cannot reach any on-premises data. TheSyspro Torque Executor connects outbound only and opens no inbound ports.

To set up the Syspro Torque Executor , you must first create a registration token:

• Go to Admin > Infrastructure > Executors and click +Create Token.

• Give the Executor an identifiable name (for example, warehouse-executor-01).

• Add one or more comma-separated tags. Tags are optional for a single Executor, but drive tag-based routing once a tenant has more than one.

• Click Create Token.

  The registration token is valid for one hour after it is generated, so coordinate the install so it does not expire.

Next, install and register the Syspro Torque Executor :

• From the Create Token screen, choose an install method.

  • Manual install: Click Download installer and save TorqueExecutorSetup.exe to the server.

    Run the downloaded installer as a local administrator. It installs the Syspro Torque Executor service to C:\Program Files\SYSPRO\Torque Executor\, sets the local UI port, and installs .NET 10 if missing, then registers and starts the Syspro Torque Executor service.

    The installer installs the .NET 10 ASP.NET Core hosting Bundle (about 80 mb) if it is not already present, downloading it from Microsoft at install time. Internet access on the server is required only for that download.

    When the manual installer finishes, choose to go and register the Syspro Torque Executor .

    Open the Syspro Torque Executor UI in your browser (for example, http://localhost:5210/), copy the registration token, and paste it in, and select Register Executor.

  • Quick install: Click Copy script.

    Paste it into an elevated PowerShell window. It downloads the installer, verifies its SHA-256-hash, sets the token, installs, and registers in one step.

  Recommended Syspro Torque Executor placement: a dedicated or lightly loaded host on the same LAN segment as Syspro and SQL Server, patched and hardened to your ERP standard.
  Executors are not updated automatically. New functionality are added with each Syspro Torque Executor release. To update your current installer, go to Admin > Executors > Download installer. It upgrades in place and keep existing configuration and cloud region. New functionality will only be active after you reinstalled it.

• After registering your Executor, you will have to restart the Syspro Torque Executor service (TorqueExecutor) again to establish a connection to your local host or Windows server (depending on where you have installed the Executor)

• Go back to Syspro Torque Admin > Executors and confirm the Executor shows Online within about 60 seconds.

  If the Syspro Torque Executor does not show Online, restart the Syspro Torque Executor service (in services.msc, or run Restart-Service -Name "TorqueExecutor" - Force as Administrator) and allow one or two minutes for it to reconnect.
  From the Executor entry you can later re-register, download the installer, restart, or revoke it. Revoking deletes the token and requires re-registration.

• Once your Syspro Torque Executor has been installed and registered you can start configuring connections.

You create a connection to link Syspro Torque to the system(s) it must work with. Various connections can be created. You must create the connection first, then configure its credentials per environment.

You require a TenantAdmin or Editor role.

Rules are re-usable business-logic checks that live in your tenant and run at runtime. You create them once in the Rules catalog, and a workflow or managed agent applies them when it actually runs. A workflow calls them through a validation step, and an agent through a rule set layer. Rules are part of what your automation does every time it executes.

• Go to Build > Create > Rules

• Two options exist to add rules:

  Extract rules from a document by uploading a document using the attachment button.

  • The Rules Agent will review and propose rules in the chat. It will display all the rules in the chat, state what rule type is chosen, and (for SQL rules) which database table it verified against.

  • Confirm, edit, or reject each rule. The agent will save confirmed rules to the catalog immediately.

  Describe a rule in plain language using the chat mode.

  • The Rules Agent picks the appropriate rule type, writes the rule logic, and (for SQL rules) verifies the required database table and columns before saving.

• Rules will appear in the right-hand catalog pane.

  You do not need to specify rule types, table names, or field names. The agent discovers these from your connected databases. Only describe the business intent.

• Some rules might be flagged for review (indicated by a review indicator) as they couldn't be fully verified. The Rules Agent will tell you why and what to action.

• To view a rule's full definition, click on the rule in the right-hand catalog pane under Rule Catalog. You might need to collapse Insights first in order to see all the rules.

  Toggle the Active button to deactivate (soft-delete) the rule without removing it from the audit trail. Use Delete only when you want to remove it permanently.
  Rules are grouped by Rule Sets. You can create additional rule sets to organize rules by domain, source document, or workflow.

The Knowledge Base gives your Managed Agents a structured understanding of your organization, your industry, the challenges your business solves, how your team works, and how Syspro Torque integrates with your systems. When a Managed Agent answers a question or takes an action, it can draw on this context to give more relevant, grounded responses.

The Knowledge Base has two parts:

Structured sections describe who your organisation is and how it operates — your industry, the problems your business solves, how your teams work, and how Syspro Torque fits your systems. Your administrators maintain these, and every Managed Agent in your tenant can draw on them.

Knowledge collections hold documents you upload (.txt and .pdf). Each document is indexed so Managed Agents can search it and cite it when answering, and each shows its processing status. Bind a collection to a specific Managed Agent with a Knowledge Base capability layer to control which agents see which documents.

• Go to Build > Knowledge

• Update the structured sections that describe your organization.

  Be specific. For example, 'We manufacture precision automotive parts and serve Tier 1 OEM suppliers in Europe. The more context you provide, the more relevant the Managed Agent's responses will be.

A Managed Agent is a purpose-built AI that answers questions, runs actions, and automates tasks within a defined scope.

There are two ways to start building a managed agent:

• Use the Torque-Builder (Build > Torgue builder) and describe the managed agent you want. Torque-Builder creates it for you and takes you to the managed agent builder page.

• Go to Build > Managed Agents. Create a named shell, and describe its capabilities in the chat panel.

A workflow is an automated multi-step process that runs on your on-premises systems, querying databases, calling business objects, sending notifications, waiting for approvals, and more. Workflows run on the Syspro Torque Executor , not in the cloud, so they can reach any system where theSyspro Torque Executor was installed.

There are two ways to start building a workflow:

• Use the Torque-Builder (Build > Torgue builder) and describe the workflow you want. Torque-Builder creates it for you and takes you to the workflow builder page. This approach is faster if you know your workflow.

• Go to Build > Workflows. Create a named workflow, and describe the process in the chat panel docked on its builder page.

Rules can be attached to a Workflow or Managed Agent.

TenantAdmins and Editors can test what was built. Sidekick is the orchestrator users chat to. It answers their questions directly or delegates to a specialist managed agent and returns the results.

• Test a managed agent from Build > Managed Agents > Open Chat.

• Test a workflow from Build > Workflows > Run, and inspect each step under Monitor > Executions.

  • Where a workflow includes an approval step, confirm it behaves as intended.

    In Sidekick , an approval required card appears inline for the user to Approve or Deny before anything commits.

• Set a trigger under Connect > Triggers. You can also add a trigger by asking Torque-Builder in plain language. (For example, 'run this every night at 8pm' or 'run this when a file lands in the order folder')

  • Schedules run on a cron or fixed interval cadence with a timezone.

  • Webhooks give an inbound URL or send outbound notifications.

  • File polling watches a folder and runs a workflow when a matching file appears.

  Sidekick has no Planning Mode. Planning Mode only lives on the builder. Sidekick is personal to you and keeps context within a conversation, so you can ask follow-up questions without repeating yourself.

A trigger is what starts a workflow or a managed agent task automatically, so it runs without someone starting it by hand. For example, instead of opening a workflow and run it, you attach a trigger that fires it when a condition is met.

Syspro Torque has four trigger types, and any workflow can also be run manually or started from an API call:.

• • Schedule — runs a workflow or Managed Agent on a timer.

• • Webhook — an inbound URL an external system calls to start a workflow, or an outbound call Torque makes when something happens, such as a workflow completing or failing.

• • File polling — watches a folder on your network and runs a workflow when a matching file appears.

• • FTP/SFTP contract — polls a remote FTP, SFTP, FTPS or SCP location, runs a workflow when a matching file arrives, and can deliver files back.

  Add FTP contracts wherever the Connect area is enumerated.

Automates the full order capture and posting process, from document receipt to confirmed sales order in Syspro.

You: Either upload the purchase order PDF using Sidekick , or place it in a monitored folder configured to trigger the workflow.

Syspro Torque : Reads the PDF, extracts order lines, checks stock availability for each line, and presents any shortage for resolution before posting the confirmed sales order to Syspro.

Structures the shortage resolution decision as a governed, auditable step within the order processing workflow.

You: Review the options presented when a shortage is detected, and select whether to substitute with an alternative item or place the line on back order.

Syspro Torque : Identifies lines that cannot be fulfilled from available stock, presents configured substitutes where available, and pauses at a human intervention point. Once a decision is confirmed, Syspro Torque applies it and continues processing the order.

Adds an automated market intelligence check to the order processing workflow before an order is confirmed.

You: No additional input is required. The check runs automatically as part of order processing.

Syspro Torque : Queries current market pricing data for the items on the order, compares them against the prices being applied, and flags any lines that fall outside the configured acceptable range.

Automates replenishment calculation and requisition creation, ensuring purchasing decisions are based on accurate, current data.

You: Trigger the workflow for a stock code or range of stock codes, or configure it to run on a schedule.

Syspro Torque : Calculates the required replenishment quantity using average daily demand, safety stock levels, economic batch quantity, due date, and unit cost, then raises a purchase requisition in Syspro with the calculated values populated.

Provides a consolidated approval interface for requisitions, replacing Syspro's standard one-at-a-time approval process.

You: Open the requisition approval agent, review the batch of pending requisitions, and approve or reject items before confirming.

Syspro Torque : Retrieves all requisitions pending your approval, presents them in a consolidated view, and posts the approved and rejected decisions back to Syspro on confirmation.

Automates bank statement ingestion and review, with a mandatory human approval step before any posting occurs in Syspro.

You: Place PDF bank statements in the monitored folder, then review and confirm the transactions Syspro Torque presents before posting proceeds.

Syspro Torque : Detects new PDF files in the configured folder, extracts transaction data, checks for duplicates against existing cash book entries, and presents the transactions for review. On confirmation, posts the approved transactions as cash book deposits in Syspro.

Makes compliance checks available on demand, combining your Syspro data with codified compliance knowledge to produce a structured findings report.

You: Initiate the compliance check through Sidekick and specify the scope, i.e. period, entities, or accounts to include.

Syspro Torque : Queries the relevant Syspro data, applies segregation-of-duty rules and aged balance thresholds, identifies control weaknesses, and produces a structured report with findings and a remediation plan, citing the specific rule breached for each item.

Enables conversational querying of financial statement data, with the ability to drill into the detail behind any figure without running additional reports.

You: Ask Sidekick or the configured financial agent a question about a specific line, period, or variance in your income statement, in plain English.

Syspro Torque : Queries the connected Syspro and SQL data, resolves the question against GL dimensions and transaction detail, and returns a structured answer with the supporting figures.

Produces a live operational dashboard from a plain-language description, without any development effort.

You: Describe the metrics you want to track. Optionally, provide a screenshot or sketch of the layout you have in mind.

Syspro Torque : Builds a live dashboard card connected to your Syspro and SQL data, presenting the specified metrics and refreshing them in real time.

Automates the execution and delivery of recurring reports, ensuring they run reliably on a defined schedule without manual initiation.

You: Define the report content, intended recipients, and delivery schedule when configuring the workflow.

Syspro Torque : Runs the workflow at the configured interval, queries the relevant data, formats the report, and delivers it to the specified recipients.

Automates the comparison of documents against current Syspro business object schemas, surfacing discrepancies before they cause downstream issues.

You: Place the documents to be checked in the monitored folder, or trigger the workflow manually for a specific set of files.

Syspro Torque : Reads the documents, compares their content against the current Syspro business object schemas in the knowledge base, identifies fields or descriptions that no longer match, and produces a prioritized report of discrepancies.

Enables authorized users to ask data questions in plain English and receive accurate answers, without needing to know the schema or run a query manually.

You: Ask Sidekick or a configured Managed Agent a question about your data in plain English.

Syspro Torque : Translates the question into a structured query, executes it against the connected Syspro or SQL database within the agent's configured access permissions, and returns the result in a readable format.