In development · Early access waitlist open
AI is changing how work gets done. Understand what’s happening.
Connect your AI agents and workflows to Trovis. See the steps they take, the tools they use, and how work passes between agents, people, and systems. Get AI-powered explanations of what happened and what needs your attention.
Inside the agent. Across the workflow. Throughout your business.
You’re on the early-access list.
We’ll reach out as access opens. Tell us what you’d connect so we can better understand your team’s needs.
Thanks. Your details are saved, and we’ll be in touch as early access opens.
Inside the agent’s work
Handle return request · Order #1042
- Agent action
- Tool or system event
- Human handoff
Step 1Request received from customer inbox
- Source
- Customer inbox
- Event
- New email
- Subject
- “Return request for order #1042”
- From
- customer@example.com (sample)
- Next recorded step
- Support agent
Step 2Support agent retrieved the order
- Tool call
- Order system · get_order
- Input
- order_id: 1042
- Output
- 1 item · delivered 9 days ago
- Result
- Success
Step 3Support agent checked the return policy
- Tool call
- Knowledge base · search
- Input
- “return policy, delivered items”
- Output
- “Returns accepted within 30 days of delivery”
- Result
- Success
Step 4Support agent drafted a response
- Output
- Reply draft with return instructions
- Length
- 142 words
- Result
- Draft ready to send
Step 5Email tool attempted delivery
- Tool
- Email service
- Action
- Send customer response
- Recipient
- customer@example.com (sample)
- Attempt
- 1 of 2
Step 6Delivery failed
- Tool
- Email service
- Action
- Send customer response
- Result
- Failed
- Recorded error
- Authentication expired
- Attempt
- 1 of 2
- Next recorded step
- Automatic retry
Step 7Retry failed
- Tool
- Email service
- Action
- Send customer response
- Result
- Failed
- Recorded error
- Authentication expired
- Attempts
- 2
- Next recorded destination
- Support review queue
Step 8Case routed to the support team for review
- Handoff
- Support agent → Support team
- Destination
- Support review queue
- Recorded reason
- “Delivery failed after 2 attempts”
- Status
- Waiting for review
Inside the agent’s work
Set up new account · Northwind Co.
- Agent action
- Tool or system event
- Human handoff
Step 1Onboarding record created in the CRM
- Source
- CRM
- Event
- Deal moved to Closed won
- Record
- Northwind Co. (sample)
- Next recorded step
- Onboarding agent
Step 2Onboarding agent prepared the workspace
- Tool call
- Account platform · create_workspace
- Input
- plan: Team · seats: 12
- Output
- Workspace drafted, not yet active
- Result
- Success
Step 3Approval requested from the account manager
- Handoff
- Onboarding agent → Priya (account manager)
- Channel
- Team chat
- Status
- Waiting for approval
Step 4Priya approved the setup
- Recorded by
- Account platform
- Decision
- Approved
- Waited
- 22 minutes
- Next recorded step
- Account activation
Step 5Account activated
- Event
- Workspace activated
- Result
- Success
- Welcome email
- Sent to the customer’s admin
Inside the agent’s work
Weekly sales report · Week 42
- Agent action
- Tool or system event
- Human handoff
Step 1Report agent queried the data warehouse
- Tool call
- Data warehouse · run_query
- Input
- Sales by region, last 7 days
- Output
- 4 regions · 1 table
- Result
- Success
Step 2Report agent drafted the report
- Output
- Draft in shared docs
- Length
- 2 pages · 3 charts
- Result
- Draft ready
Step 3Draft sent for review
- Handoff
- Report agent → Reviewer
- Channel
- Shared docs
- Status
- Waiting for review
Step 4Reviewer approved the draft
- Recorded by
- Shared docs
- Decision
- Approved with 2 edits
- Waited
- 29 hours 34 minutes
- Next recorded step
- Send report
Step 5Report emailed to the sales team
- Tool
- Email service
- Action
- Send report
- Result
- Delivered
The response was prepared, but the customer never received it.
The support agent retrieved the order, checked the return policy, and drafted a reply. Both delivery attempts failed because the email connection had expired. The case was routed to the support team for review.
- What failed
- Email delivery
- What it affected
- Customer response
- Where the work went next
- Support review queue
Supporting evidence
Onboarding finished end to end.
The onboarding agent prepared the workspace, Priya approved it 22 minutes later, and the account platform recorded the activation. Nothing here needs attention.
- Outcome
- Account active
- Longest wait
- Approval, 22 minutes
- Needs attention
- Nothing
Supporting evidence
The report went out Tuesday afternoon instead of Monday.
The report agent finished the draft at 8:20 AM Monday. It then waited for review until Tuesday afternoon, so the delay in this run happened at the review step, not in the agent.
- What happened
- Delivered a day late
- Where the time went
- Review handoff
- Needs attention
- Review timing
Supporting evidence
More work is happening.
Less of it is in view.
-
“Where did that actually happen?”
Agent runs live in one platform, messages in another, outcomes in your business tools. The story of one piece of work is scattered.
-
“The agent finished. Is the work done?”
An agent completing its step doesn’t mean the customer, order, or process moved forward.
-
“Where do I need to step in?”
You need to know where to intervene without reconstructing every journey by hand.
Connect the work.
See the whole journey.
-
1
Connect
Bring activity from your agents, workflows, and business tools into Trovis.
-
2
Understand
Follow recorded steps, tool calls, outcomes, and handoffs in one connected view.
-
3
Stay informed
Get explanations of what happened, where work stopped, and what needs your attention.
Ways to connect today
- Add a few lines to a Python agent. The Trovis SDK records agents built with supported frameworks, such as the OpenAI Agents SDK and the Claude Agent SDK.
- Send OpenTelemetry traces. Custom agents and tools that already emit OpenTelemetry can send their traces to Trovis.
- Install a plugin on a supported agent platform, such as OpenClaw.
- Connect supported business tools, starting with Stripe, HubSpot, and Shopify, to see the work they record.
Not every platform is supported yet. Tell us which agents and workflows you use when you request access.
See inside the AI.
Understand the work around it.
-
Level 1
Across your AI work
See connected workflows, participating agents, recent runs, and work needing attention.
-
Level 2
Inside each run
Inspect recorded steps, tool calls, available inputs and outputs, failures, and retries.
-
Level 3
Beyond the agent
Follow work into the next agent, person, or system and understand whether the process continued.
Spot what keeps happening, not just what happened once.
Trovis looks across many runs to surface recurring behavior, alongside explaining a single failure.
“Which AI work keeps coming back to people?”
Refund replies from the support agent are often corrected before they’re sent.
Support leads edited 11 of 24 refund drafts this week, usually changing the amount. The edits began the week the refund policy was updated, so it’s worth checking whether the agent is using the current policy.
- Help desk11 of 24 refund drafts edited before sending
- Help deskMost edits change the refund amount
- DocsRefund policy updated the same week the edits began
Understand the work today.
Make it work better tomorrow.
-
Initial focus
Understand
Understand connected work and surface what needs attention.
-
Longer-term vision
Improve
Suggest better workflows and help optimize operations.
-
Longer-term vision
Act
Carry out approved fixes, including repairs to agents.
Build the next chapter of work with us.
We’re looking for teams already putting AI to work. Our first teams will help shape Trovis around real agents, real workflows, and the questions that matter in their businesses.
For teams invited into early access
-
Get in before public launch
An opportunity to use Trovis with your team as early access opens.
-
Connect a real workflow
Work directly with us to connect an initial supported agent workflow and explore the activity behind it.
-
Have a direct line to the founder
Share feedback and help inform the integrations and capabilities we prioritize.
Be one of the first teams inside Trovis.
Request early access to understand how work moves across your agents, people, and tools. Help shape Trovis around the work your team is doing.
You’re on the early-access list.
We’ll reach out as access opens. Tell us what you’d connect so we can better understand your team’s needs.
Thanks. Your details are saved, and we’ll be in touch as early access opens.
What to expect
- What does requesting early access mean?
- You’ll join the list of teams interested in trying Trovis before public launch. We’ll contact teams as supported connections and onboarding become available.
- Will I get access immediately?
- Not yet. Trovis is in development, and submitting a request does not provide immediate access.
- What should I have ready?
- An example of work your team is already doing with AI, and the agents or tools involved. You don’t need to connect anything to join the list.