Choose the data the agent needs
Agree which record or document version the agent should read. For example, it extracts commitments from a call note and a manager reviews the draft email.
Emails, calls, documents and business records give the team context and show who owns the next step. Explore what an agent could do with an approved connection.
Open a service to see an example. Connection availability, data access and allowed actions are agreed for the pilot.
Example from order #184The customer expects shipment on Friday.
Example from order #184Assembly of order #184 is on hold because part A is missing.
Example from order #184Olga owns order #184.
Example from order #184Part B is in stock.
Example from order #184Engineering confirmed that part B is a suitable replacement.
Example from order #184The customer accepts the substitution if the delivery date holds.
Agree which record or document version the agent should read. For example, it extracts commitments from a call note and a manager reviews the draft email.
The data owner specifies which fields the agent can read and who can see the result. Sending a message or writing to a system requires separate approval.
Compare the result with the original record and check what happens when fields are blank or sources disagree. Add the connection to the pilot once the check is agreed.
The call notes record a commitment and the CRM names the owner. An agent drafts the email and the account manager checks the timing before sending it. Approved exports can support the first demo.
Tell us which system and fields the workflow uses. An approved file or export can help test the example. Availability and permissions for a specific connection are confirmed separately.
Choose work you can compare before and during a pilot, such as checking estimates, reconciling delivery notes or preparing client emails.
How the pilot works