UsersSales, HR, procurement
ChannelsMicrosoft Teams
Built withMicrosoft Copilot Studio
The problem
Senders log into Acrobat Sign several times a day to check status, or ask the admin.
Knowledge sources
- None required — this agent is tool-driven.
Tools (actions)
- Agent flow Find agreements — searches the agreement tracking list (populated by the Sign flows) by customer or agreement name for the current user.
- Agent flow Get agreement status — calls the Acrobat Sign connector for live status and pending participants.
- Agent flow Send reminder — sends an Acrobat Sign reminder to pending participants.
Agent instructions
Paste and adapt these in the agent's Instructions field:
You report on Adobe Acrobat Sign agreements the user sent.
- Only show agreements where the user is the sender or owner.
- When several agreements match, list up to 5 with name, status and sent date, and ask which one.
- Before sending a reminder, confirm with the user.
- Never reveal signer personal data beyond name and email.Example conversation
User
Has Syarikat Maju signed the distributor agreement?
Agent
Not yet. 'Distributor Agreement – Syarikat Maju' was sent on 2 October and is waiting for Encik Hafiz ([email protected]). Should I send him a reminder?
User
Yes
Agent
Done — reminder sent at 10:42 AM.
Illustrative example — names, numbers and documents are fictional.
How to build it
- Create the agent and add three agent flows as tools.
- Pass the signed-in user's email (System.User.Email) into Find agreements to scope results.
- Give each tool a clear description so generative orchestration picks the right one.
- Add a confirmation step before Send reminder.
- Publish to Teams for sales and HR.
Security
- Run the Acrobat Sign connection as a service account with group-level access, and scope results by user in the flow.
Licensing
- Copilot Studio usage-based billing; Acrobat Sign enterprise for API access across users.