Sprint 166 expands how Vsimple helps teams use AI across sales and operations. vAI can now work with record tables, linked records, images, and more complex inputs. The sprint also adds project management flexibility and improvements across integrations, security, performance, and administration.

These changes support connected workflows. Teams can spend less time collecting information, transferring data, and coordinating the next step manually.

Sprint 166 at a glance

vAI works with more operational data

Operational work rarely stays inside one field or record. An order may include several line items. A customer request may depend on linked records, email history, documents, images, or information from another system.

Sprint 166 expands vAI’s ability to use that surrounding information.

Data can map directly into record tables

vAI Inboxes can now map incoming data directly into record tables. This expands the existing ability to populate individual record fields.

The update supports workflows that contain multiple line items or structured sets of information. For example, during AI order intake, vAI can capture the products, quantities, or other details that belong in an order table instead of leaving someone to transfer each item manually.

A typical workflow can include:

1. An order or other business document arrives through an inbox.

2. vAI identifies the information in the input.

3. vAI maps individual values into record fields.

4. vAI maps grouped or repeated information into a record table.

5. The resulting record can move to the next review, approval, or fulfillment step.

This helps teams organize data earlier in the process. It also gives AI Agents more structured information to use when coordinating work from quote through order and billing.

Linked records add context to analysis

vAI can now use linked-record context when it analyzes a record or executes a prompt. This allows an Agent to consider related information instead of treating each record as an isolated item.

For example, an order intake workflow may need to account for:

• Other orders connected to the same customer

• Customer preferences stored in a related record

• Historical information that affects the next step

• Related records that provide missing context for an Agent’s analysis

This supports workflows such as reviewing a customer’s order history before determining how to process a new request. It can also help an Agent account for special customer preferences during order intake analysis.

The current update focuses on using existing relationships. Vsimple is continuing to expand the functionality so vAI can create links and linked records as part of its work.

Image and attachment processing handles less structured input

Operational information does not always arrive as clean, structured data. Teams may receive documents, screenshots, images, attachments, purchase orders, or other files that require review before someone can enter the information into a system.

Sprint 166 improves vAI’s image processing capabilities. Agents can use more information from visual inputs and help turn it into data that teams can act on.

This supports workflows such as:

• Extracting information from an image or document attached to an incoming request

• Reviewing a screenshot before routing work

• Using purchase-order details during order intake

• Identifying missing information before a request moves forward

• Combining extracted information with records already stored in Vsimple

The update extends vAI’s ability to work across the inputs that teams already receive.

Autonomous actions are more reliable

As vAI performs more work independently, consistent action execution becomes essential. Sprint 166 resolves several autonomous action errors identified through system logs.

The fixes improve the reliability of vAI as it executes actions across workflows. Depending on the workflow, an Agent can help analyze incoming information, populate records, use related records, and move work toward the next operational step.

These updates improve the foundation for Agents that handle real work while keeping teams involved in review and approval processes where needed.

More flexible project management workflows

Sprint 166 adds the ability to show linked child objects or tasks across multiple link sections.

A child task, project, or related object may need to appear in more than one context. For example, a task may relate to a project and also need to appear through another connected record or workstream.

This update gives teams more control over how related work is organized and displayed. It supports project management workflows while also helping teams manage connected sales, service, and operational processes.

Teams can use these relationships to:

• View related tasks from the contexts where they are needed

• Connect project work to operational records

• Organize interconnected processes without forcing every relationship into one rigid structure

• Give different teams visibility into the same related work

The result is a clearer view of how tasks, projects, and records connect.

Platform, integration, and administration updates

Sprint 166 also includes updates that improve platform performance, configuration, troubleshooting, and everyday navigation.

Longer-running processes

Vsimple upgraded its Cloudflare infrastructure to increase timeout limits. Longer Power BI queries and complex vAI prompts can now run successfully when processing takes more than two minutes.

This gives teams more room to run processes that require additional time to query data or analyze complex inputs.

Integration creation

Updates to integration creation and configuration make it easier to set up connected workflows. This supports teams that connect Vsimple with the systems they already use across sales, operations, reporting, and communication.

Load testing

Vsimple modernized its load-test coverage. Expanded testing helps the team identify performance issues and assess platform reliability as usage grows.

Outlook error messages

Improved error formatting makes Outlook integration issues easier to understand. Clearer messages help administrators identify the source of a problem and take the appropriate troubleshooting step.

Kanban performance

Updates to Kanban view requests improve performance behind the scenes. Teams can continue using Kanban views to track work while Vsimple handles those requests more efficiently.

Excel templates for vSign

Teams can now use Excel files as vSign templates. This adds flexibility for document-based workflows that rely on Excel templates.

Rearrangeable tabs

Users can reorder tabs to match the way they work. Teams can place frequently used areas in a more practical order for their daily workflows.

Who benefits from these updates

Sprint 166 is particularly relevant for teams that coordinate information across customers, orders, projects, documents, and connected systems.

Teams managing orders and customer information

Teams can use record tables for multi-line-item order intake. Linked-record context can also help teams review customer history and account preferences before an order moves to the next step.

Teams handling customer requests and documents

Teams often manage customer requests, product details, documents, and follow-up steps across several workflows. Improved image processing and related-record awareness can reduce the time spent gathering information before work is assigned or approved.

Teams coordinating projects and operational work

These teams often manage projects, tasks, documents, and customer information at the same time. Linked child objects and rearrangeable tabs provide more flexibility for organizing work across those connected areas.

Operations leaders and administrators

Operations leaders gain more visibility into related work and less manual coordination between systems. Administrators benefit from clearer Outlook errors, improved integration setup, longer-running processes, and expanded load testing.

Building AI that understands the work around it

The main theme of Sprint 166 is context. Meaningful operational automation requires more than a prompt or a single record. It depends on the tables, relationships, documents, images, and connected systems surrounding the work.

Sprint 166 expands vAI’s ability to:

• Map incoming information into fields and record tables

• Use existing linked-record relationships

• Process more information from images and attachments

• Execute autonomous actions more reliably

• Support work that takes longer to process

• Connect project and operational work across multiple contexts

For teams coordinating work from quote to order to billing, these updates can reduce manual information gathering and help the next step move forward with better context.

Vsimple is continuing to build toward AI Agents that do more than find information. They help teams organize, analyze, route, and execute operational work.

Frequently asked questions

What changed in Sprint 166, and who benefits from these changes?

Sprint 166 expands vAI’s data and workflow capabilities. The release adds record-table mapping, linked-record context, improved image processing, and more reliable autonomous actions. It also adds linked child objects across multiple project-management sections, longer-running processes, improved integrations, clearer Outlook errors, better Kanban performance, Excel support for vSign templates, and rearrangeable tabs.

Teams can benefit from these changes, especially when their work depends on orders, customer history, documents, projects, and connected systems.

How does vAI map incoming data into record tables?

vAI Inboxes can map incoming information into record fields and record tables. A table can hold repeated or grouped information, such as the multiple line items in an incoming order.

This lets vAI organize structured order details in the appropriate table instead of requiring someone to copy each item into the record manually.

How does vAI use linked records and customer history?

vAI can use information from linked records when it analyzes a record or executes a prompt. An Agent can consider related orders, customer preferences, or historical information when determining how to handle current work.

Sprint 166 supports the use of existing links. The ability to create links and linked records is still being expanded.

Can vAI process images, documents, emails, screenshots, and attachments?

Sprint 166 improves vAI’s image processing for visual inputs. vAI can work with information arriving through documents, images, screenshots, and attachments. In inbox-based workflows, teams can also process incoming operational information such as emails and purchase orders, then use the extracted details in records and follow-up steps.

What autonomous actions can vAI execute?

The release improves the reliability of autonomous actions across workflows. Depending on the configured workflow, vAI can analyze incoming information, populate records and tables, use linked-record context, and move work toward the next operational step.

Sprint 166 resolved several autonomous action errors identified through system logs. Teams can continue to use review and approval steps where their processes require human oversight.

What project-management and administration improvements shipped?

The release includes the following updates:

• Linked child objects or tasks can appear across multiple link sections.

• Integration creation and configuration are smoother.

• Outlook errors use clearer formatting.

• Kanban view requests perform more efficiently.

• Excel files can be used as vSign templates.

• Users can rearrange tabs.

• Expanded load testing supports ongoing reliability work.

• Higher timeout limits support longer Power BI queries and complex vAI prompts.

How do these changes reduce manual coordination?

The updates help teams capture information from incoming inputs, organize multiple line items, use customer and record history, and route work with more context. That reduces the need to gather details from separate records, re-enter information, or manually connect related tasks before work can proceed.

What is available now, and what is still being expanded?

The Sprint 166 updates for record-table mapping, linked-record context, improved image processing, autonomous-action reliability, linked child objects, longer-running processes, integration setup, Outlook errors, Kanban performance, Excel vSign templates, and rearrangeable tabs are included in the release.

vAI’s ability to use existing linked records is available now. The ability to create links and linked records as part of its work is still being expanded.