Getting a house from accepted offer to keys runs on email and calendar invites between four companies. An AI transaction coordinator needs an identity all four of them can reach.
Once an offer is accepted, closing a house is a scheduling job. There is an inspection to book before the contingency window shuts, an appraisal to chase, disclosures to send to the other side, a lender to keep updated, a walkthrough to move when the loan slips, and a closing date that every one of those hangs off. Those dates are written into the purchase agreement, so missing one can cost a buyer their deposit or give either side a way out.
In most brokerages, that work belongs to a transaction coordinator, who handles it from a mailbox and a calendar, between a lender, a title officer, an appraiser, and the realtor on the other side, none of whom work at the same company or use the same software. So an agent built to take it on has to do both: write to people, and put the results on a calendar it can move when the deal does.
Borrowing a coordinator’s seat
The coordinator’s account is where the job already lives, so that is where the agent usually starts. Everything it sends and books now goes out under the coordinator’s name, so the inspector, the lender, and the title officer are all dealing with a single person who can leave. When the coordinator moves to another brokerage, IT hands the mailbox to whoever takes over, but the agent was signed in as someone who no longer works there. It stops mid-file on every deal at once, and the deadlines keep running.
The other attempt is to run the whole deal inside the transaction platform and invite everyone in. The people who work at the brokerage will log in. The appraiser, the HOA manager, and a processor at the lender have their own systems and no reason to learn yours, so they reply by email and keep their own calendars, and when the closing date moves, somebody is retyping it into four of them.
Put the two side by side, and they are the same problem. Everyone on a closing has an address: the realtor, the coordinator, the inspector, the lender’s processor. The agent coordinating it is the only participant without one, so its mail and its appointments have been living scattered across everyone else’s.
Nylas Agent Accounts give the transaction coordinator agent an identity of its own, like closing@yourbrokerage.com, one account holding both the mailbox and the calendar, created through the Nylas API with a single call to POST /v3/connect/custom. Which deadline matters and when to escalate stays in your application, and advising the client stays with the realtor. What Nylas runs is the identity the agent writes and books from.
A closing that moves
Say a house goes under contract on Monday. The agent emails the buyer, the lender, the title company, and the seller’s realtor from one address, and from then on, every reply about that deal comes back to the same place, on the same thread.
Booking the inspection is where the calendar starts doing the work. The agent offers times from its own calendar, and when the inspector picks one, it creates the event through the Events API. The invite lands in the inspector’s Outlook the way any meeting does, via standard iCalendar, and the acceptance comes back as a status on the event rather than as another email for someone to read. Invitations arrive the other way too. When the title company sends its own invite for the signing, the event lands on the agent’s calendar, and the agent accepts it like any other attendee, so the title company gets its confirmation without anyone at the brokerage having to watch an inbox. The inspection report comes back attached to a reply, and the agent reads it from the message it arrived in.
Then the lender needs two more days. Because the agent’s mailbox and calendar are the same account, the email asking for the extension and the appointment it affects are visible to the same identity. And because the agent organized that appointment, it can move it. It updates the event, and the corrected invitation goes to every participant, wherever each of them keeps their calendar. The final walkthrough was booked for the day before closing, so that moves too. One email came in and four calendars changed.
What a brokerage checks first
The agent’s mail lands in the middle of the largest purchase of most people’s lives. Three things have to be true before a brokerage lets it near a client.
The first is deliverability. If a deadline notice ends up in spam, the buyer can miss the date, and nobody finds out until it is too late. An Agent Account sends from the brokerage’s own domain, on infrastructure Nylas has run for more than a decade.
The second is that a person can step in. A coordinator opens the mailbox in Outlook over IMAP and reads the file, and a reply sent from there sits on the same thread as everything the agent sent. The mailbox holds the correspondence while the deal is live, and their transaction system stays the file of record.
The third is compliance, as closing mail carries a buyer’s finances and personal details. Agent Accounts carry Nylas’s compliance posture on every plan, from the free tier up: SOC 2 Type II, HIPAA, ISO 27001, ISO 27701. When a brokerage’s review asks who is holding this mailbox and to what standard, that is the answer.
If Nylas is in your stack, this part is already built. An Agent Account is another grant: provisioning returns the same shape, and the Messages, Threads, Attachments, and Events endpoints work against it exactly as they do today. If your product already syncs realtor mailboxes and coordinator calendars, adding an agent identity is one more call to an API you have already integrated and already had reviewed.
The agent books appointments in a brokerage’s name, and the name is what makes them land. A lender’s assistant does not accept an invitation from a domain they do not recognize, and an inspector does not add it to their calendar. So each brokerage verifies its domain once during onboarding, and after that your application can create accounts on it whenever a new file opens. Each brokerage maintains its own policies and sending reputation, and a busy month at one brokerage stays inside that brokerage’s domain.
The free tier includes three Agent Accounts, enough to run the whole loop end to end before paying anything. The Full Platform plan starts at fifteen dollars a month and scales with usage. Provision the account, hand it a file, and let it carry the closing from accepted offer to signing day without dropping a date.
Sign up (or sign in if you already have an account) to create your first Agent Account. The scheduling agent recipe walks through the propose, book, and reschedule loop this runs on.
Read more from our Agent Accounts vertical series:
Email and Contacts API 
Calendar API & Scheduler 
Notetaker API 
Agent Accounts 
Sales & CRM 
Recruiting & ATS 
Healthcare
Financial
Legal
Real Estate
Education
Field Services
Docs
SDKs
Guides
Integrations
API status
Changelog
Support
Enterprise
