All topics
How it works / Transactions

Keeping everyone updated

Lender, title, the other side, your client. Beverly writes the update each one needs and queues it for you to send.

In testingBuilt, and running in our own testing environment. It is switched off for customer accounts, so you cannot use it yet. The Transaction Assistant is built and runs against real contracts in our own testing environment. It is switched off for customer accounts, so you cannot use it today, and Beverly says so plainly if you ask for it rather than pretending to do it. It is on this site because it is close, not because it is available. The updates on this page are email and text. Beverly phoning the people on a file, and your own clients, is in testing on our own test account only, and each has its own row on the phone calls page. Either way Beverly never reaches a party on a file without you approving the exact words first.

Being the switchboard is most of the job and none of the value. Beverly writes what each party needs to hear, in your voice, and puts it in front of you. You read it, you send it.

Who gets written to, and about what
PartyTypical message Beverly drafts
Your clientWhere the file is, what happens next, what you need from them.
The lenderWhat is outstanding, and what date it is against.
Title or escrowWhat has been sent, what is still missing.
The other agentAnything the two sides have to agree on the timing of.
Asking for a text instead of an emailSay "text the lender on 128 Oak Street about the appraisal" and Beverly writes a text to the phone number on that person's line of the file, in the same words the email chase uses, and leaves it on the file with your other drafts. If there is no number on the file, Beverly says so and offers to write it as an email instead. One limit worth knowing: a text waits on the file rather than in the one click approvals list, which is built for email, so nothing about it moves until you act on it there.
Who Beverly can reach unprompted, which is only youBeverly can tell you a file needs you, over the same channel you already use for lead alerts. There is no path by which Beverly contacts a lender, an escrow officer or your client without you approving the exact words first. That is a structural property of how it is built, not a setting.
What Beverly will not write at allWire and funds mechanics, repair credit negotiation, legal advice including relaying someone else's counsel, a change to a contract deadline, a promise about the closing date, and accepting or rejecting terms. These are caught before the draft exists, not filtered afterwards.
When someone on the file tells Beverly not to contact somebodyBeverly works for you, not for the other people on the deal. If a party texts "don't contact me", Beverly stops texting them, as anyone would. If they ask Beverly not to contact somebody else, such as "don't contact my sellers directly", Beverly does not simply obey and does not ignore it. The request goes on the file for you to decide, and Beverly drafts a reply naming exactly whom it understood, "Sounds good, just confirming I won't contact Jane and Mark Smith directly", so they can correct a wrong reading. The reply waits for your approval like every other message. Beverly only treats a request as being about somebody else when it is very sure; otherwise it is handled as the sender asking to stop.
Walkthrough coming
One update, four parties, four different messages

The same event turns into the right message for each person, and the agent approves each one. Planned length: 90 seconds. We would rather leave the space marked than fill it with something staged, so this is a slot and not a video yet.

Checked against the product on 11 September 2026. What the labels mean

Language