Agents that do the routine work, within your rules.
An agent is a job you set up once and SourceLace runs for you: every weekday morning, two days before each QBR in your calendar, or as soon as something happens in a connected system. It reads your systems with its owner's access, then writes a summary, drafts emails and documents, or proposes changes for a person to approve.
Agents are in Preview: new, offered for pilots and provided as is, and shaped with early customers.
From answers to action.
QBR preparation
Two days before each QBR with Corvanta on the account owner's calendar, build the deck from CRM, ERP and support data and leave it for review.
Escalation drafts
Draft the escalation email to the account team with Corvanta's open orders, renewal date and recent cases, ready to send.
Account health updates
Recalculate the account's health score, propose the update, and open a follow-up task for the customer success manager.
Start from a template, or describe the job.
Pick a ready-made template, use one your organization wrote, or describe what you want in a few sentences and SourceLace drafts the agent for you to check. Nothing runs until you save it and turn it on, and you can try a dry run first.
Ready-made templates
For sales, customer success, support, RevOps, finance, HR and supply chain: pipeline reviews, meeting briefs, renewal reminders, overdue invoice reminders, new hire onboarding, late purchase orders and more.
When it runs
On a schedule, before meetings on the owner's calendar, when something happens in a connected system, such as a new priority 1 case, or when another system or agent starts it.
What it may do
Only the systems and actions listed for it, within the limits your plan and admins set. Each run stops at its step, record or credit limit.
Runs you can read
Every run shows what the agent read, what it made and what it proposed, with failures explained.
Your SourceLace agents work with everyone else's agents.
Your other systems can start a SourceLace agent, agents on other platforms can hand it work, and it can ask theirs for help. One SourceLace agent reaches all your connected systems, under the same rules however it is started.
Started when something happens
A secure webhook starts an agent from the systems you already run: a Salesforce Flow, SAP business events through SAP Event Mesh, or an integration platform such as MuleSoft. For example, when a priority 1 case is created.
Other agents hand it work
Agents on platforms that support the open A2A standard, and AI apps over MCP, can give a SourceLace agent a job. It runs signed in as the person it works for, with their access and never more.
It asks other agents too
A SourceLace agent can ask for help only from agents your admins allow. Your data protection rules apply to what it shares, and by default a person approves before any data leaves.
Governed where you govern agents
Because SourceLace uses open standards, integration platforms with agent governance can register SourceLace agents and govern them alongside the rest of your agents.
For example
- When a P1 case is created in Salesforce, a Corvanta escalation agent pulls the account's open SAP orders, drafts the customer email for the account owner and posts a summary for approval.started by a Salesforce Flow (Preview) · Salesforce + SAP · the email is a draft and the post waits for approval
The same rules, however it starts
- The person's own permissions. A run started by another system or agent reads and writes as the person it works for, never as the caller.
- Shadow mode applies. An agent in shadow mode never changes, drafts or posts anything, whoever starts it.
- Approvals only in SourceLace. Another agent can't approve a change. A person approves it in SourceLace.
- One audit trail. Every run is in the audit trail with what it read, made and proposed, however it started.
Agents earn trust before they act on their own.
Shadow mode Preview
The agent runs exactly when it would for real, with real data, but never changes, drafts or posts anything. You review what it would have done, then press Go live.
Trust ramp Preview
Admins can require a minimum number of days in shadow, then a period after go-live in which a person approves every change and message the agent makes.
Approvals
Record changes and Slack or Teams posts wait for a person's approval, with every field's current and new value, unless an admin lets that one action run by itself.
One agent, run for each person as themselves.
Instead of everyone building their own copy, one person shares an agent and others subscribe. Each time it is due, it runs once for each subscriber, with their own sign-ins and their own access, never the owner's.
- Your own answers. The owner can ask each subscriber a few questions, such as their accounts or region, which shape only their runs.
- Whole groups. An admin can subscribe a group, so the agent runs for each member.
- Safe changes. If an edit lets the agent read a new system or write something new, each subscriber's runs pause until they accept the new version.
- Co-owners and hand-over. Name co-owners, hand an agent to a colleague, and keep it running for its subscribers when the owner leaves.
The same Trust Layer as a person asking.
- Never more access than their owner. An agent reads and writes as its owner, through the same access by group, change switches and audit trail. If the owner loses access, their agents pause and say why.
- Data is data, not instructions. If a record or email asks the agent to do something else, it is refused: an agent can only use its listed systems and actions.
- No email is sent. Email actions create drafts for a person to review and send.
- Data protection applies. Hidden fields never reach the AI, and masked values reach it only as placeholders.
- A stop switch. Admins see every agent in the organization and can pause, stop or delete any of them. Every run and approval is in the audit trail.
Run agents inside your own network.
Keep building and managing agents in the SourceLace app, and let the runs happen on a runner in your own cloud account or data center. Turned on per organization, on request.
- Your data stays with you. What the agent read, its results, drafts and changes waiting for approval, everyone's sign-ins to your systems and your own AI key stay in your network.
- No inbound port. The runner connects out over HTTPS only.
- Status, not data. SourceLace sees each run's status, steps and counts, so you can manage agents in one place.