Start with the right file
Give your AI the transaction identifier from the accepted file. Have it show the property and represented side before it prepares the update. This prevents two deals with similar addresses from getting mixed together.
Use an agent token from the portal's AI Agent page and the documentation supplied there. The agent API limits reads to the deals available to that agent account. Keep the token in the connection's credential settings and out of any update you share.
Read the working record with a defined time window
Ask for the transaction status and the related tasks. Retrieve the recorded calendar dates for the period you want to discuss. Use explicit dates and a time zone so 'next week' has a clear meaning.
The agent documentation makes task and calendar access read-only. If you find a wrong date or task, ask the coordinator to check it. Don't have the AI assume that a permission to submit a transaction also lets it edit the coordinator's working calendar.
A prompt to adapt
Draft a transaction status update for my review.
Transaction identifier: {{accepted file ID}}
Reporting window and time zone: {{start, end, and zone}}
Intended recipient: {{agent or client}}
Use my Unicorn TC agent connection to read the transaction record and its associated tasks and calendar. Confirm the property before summarizing. State when you retrieved the records.
Separate confirmed completions from pending requests. Include upcoming recorded dates and the open items that need attention. Keep a source reference for each status or date. Mark conflicts and missing information as questions for the coordinator.
For a client draft, include only information appropriate for that recipient. Return an unsent draft. Wait for my review before any delivery.Describe the status you found
In a fictional example, the record says 'appraisal requested.' Your update should preserve that status. You haven't established that the appraisal happened or that a lender cleared a condition.
Treat a blank date the same way. It gives you a question to resolve. It doesn't establish that the event is unnecessary or complete. Ask the coordinator for the missing information before the client relies on the update.
Review the client version separately
Keep a copy of the reviewed update with its retrieval time. If a record changes after you prepare it, refresh the affected detail. A recurring calendar reminder can prompt you to run the workflow, but this guide doesn't claim that a scheduled integration is already installed.
- Check the property and the reporting period against the accepted file.
- Confirm the status of any item that affects the next client conversation.
- Remove internal notes or information the intended recipient should not receive.
- Approve the final wording and destination before sending through your normal communication process.
Use the service agreement for expectations
This directory uses a supplied rate of $399 per single-side transaction. Unicorn TC's public Full Service Plus page lists $499 per file. Confirm the applicable service and communication scope with the team.
Use the update to make your next conversation easier to prepare. Keep the responsible agent and broker in charge of transaction decisions.
Sources and review notes
Product information and starting prices checked October 17, 2026. These guides use documented product information and suggested workflows. We have not tested these connections for the directory. Unicorn TC's supplied directory rate is $399/transaction. Its public Full Service Plus page lists $499 per file. Confirm the service and rate for your file. Provider plans, coverage, and permissions can change.