Whitmore.

AI Transaction Coordinator

Cora.

Powered by Whitmore

Nothing falls through the cracks between offer accepted and keys handed over.

Cora is a transaction coordinator who never loses track of a file. From the moment a deal goes under contract to the day keys change hands, she watches every date across Follow Up Boss and Lone Wolf, chases every outstanding signature, keeps every party informed, and makes sure nothing slips. She works in English and Spanish, she is on duty every day, and she never sends anything to a client, lender, or attorney without your approval.

Cora, your AI transaction coordinator
Meet Cora

She works behind the scenes, in your name

Your clients experience you, better organized than ever. Cora does the coordinating; you stay the face of every file. She reads your systems freely so she always knows where every file stands, and she works the schedule, the follow-ups, and the paperwork the way a great transaction coordinator would.

You stay in control of everything that leaves the building. Any time Cora wants to send an email, update a contract date, or start a signature request, she prepares it and sends it to your phone as an approval card. You read it, tap Approve, and only then does it go out. Nothing reaches a client or another party without your yes.

The Systems She Plugs Into

Your tools, connected

Cora works inside the systems you already use. She does not replace them, and she does not ask you to move your data anywhere. You connect each one once, and from then on she can see what you see.

Follow Up Boss

CRM

Your CRM and workflow brain. Cora reads your contacts, deals, deal stages, tasks, notes, and email templates here. This is where she sees which tasks are due, which contract dates are approaching, and who has gone quiet.

How it connects: a secure sign-in from Whitmore. You authorize it once, the same way you would connect any trusted app to your account. You can disconnect at any time.

Lone Wolf

Transactions & E-Sign

TransactionDesk and Authentisign, where your transactions, documents, and signatures live. Cora reads transaction dates, watches documents arrive, tracks who has signed and who has not, and can prepare signature packets for you to send.

How it connects: you connect your own Lone Wolf account to Whitmore and authorize access. Until that is switched on, Cora runs fully on Follow Up Boss (see Getting Started).

@

One thing worth knowing about email.Follow Up Boss does not allow any outside program to send email through it. So Cora drafts her emails, you approve them, and they go out from your own Gmail, in your name. Follow Up Boss automatically files each one on the right client's timeline, so your CRM history stays complete.

What She Can Do In Each System

Every tool, and who decides

Here is the complete list of what Cora can do in your systems. Green means she can look things up on her own, which is how she keeps watch. Amber means she prepares the action and asks you first, every time.

Contacts, deals, tasks, and templates

See your deals and their key datesClosing, due diligence, earnest money, walkthrough, possession
Reads on her own
See the full picture of one transactionThe deal, its people, open tasks, and recent notes in one look
Reads on her own
Look up a contactProfile, relationships, and recent communication history
Reads on her own
Check tasks due today or coming upThe backbone of her morning brief
Reads on her own
Check who has gone quietLast call, text, email, or note for anyone on a file
Reads on her own
Fill in one of your email templatesYour wording, with names and dates filled in correctly
Reads on her own
Learn your account's setupYour stages, pipelines, custom fields, and templates, so she speaks your language
Reads on her own
Add or complete a taskHousekeeping inside your own account, visible to your team
On her own · internal
Add a note to a timelineRecords what she did and why, so there is always a paper trail
On her own · internal
Add a contact (lender, attorney, inspector)Checks for duplicates first
On her own · internal
Update a deal's dates or detailsDate corrections are routine; moving a deal's stage asks you first because your own automations may fire
Asks you first
Start one of your Follow Up Boss automationsBecause automations send real email and texts to real people
Asks you first
Send an email (via your Gmail)Drafted by Cora, sent in your name, filed to the FUB timeline automatically
Asks you first

TransactionDesk transactions and documents, Authentisign signatures

See all your transactionsStatus, type, and what changed recently
Reads on her own
Open one transaction in fullMilestone dates, the people on it, and every document
Reads on her own
Read a documentPull a contract or amendment to check its terms
Reads on her own
Browse your form libraryThe blank NC forms available to attach to a file
Reads on her own
Check a signature request's progressWho has signed, who has not, and the full audit trail
Reads on her own
Collect the final signed documentsSigned PDF plus certificate of completion, filed safely
Reads on her own
Hand you a direct linkOne tap from your phone into the exact transaction in TransactionDesk
Reads on her own
Create a new transactionWhen a deal goes under contract
Asks you first
Update transaction datesThe card shows exactly which dates change, from what, to what
Asks you first
Add or update a person on a transactionBuyer, seller, lender, closing attorney, and so on
Asks you first
Upload a documentFile an executed amendment or report to the transaction
Asks you first
Attach a form to a transactionPull the right blank form so it fills from the transaction's details
Asks you first
Prepare a signature packetDocuments, signers, and signing order assembled as a draft. Nothing is sent yet
Asks you first
Send a signature requestA separate approval. The card shows exactly what goes out and to whom
Asks you first
Remind a signerA nudge to someone sitting on a signature
Asks you first
Cancel a signature requestVoid a packet that is no longer needed
Asks you first

What Cora deliberately cannot do: she has no ability to delete transactions, documents, or contacts in any system. Ever.

Her Training

Skills: what she knows how to do

Tools are what Cora can do. Skills are what she knows: the trained procedures of a great transaction coordinator, written down and repeatable. Tap any skill to read her actual working brief.

New file intake: "we're under contract"Turning an accepted offer into a fully set-up file

When a deal goes under contract, Cora sets the file up end to end. She reads the executed contract, pulls out every date that matters, and pays special attention to the effective date, because in North Carolina it is the date the last signature was communicated back, and getting it wrong shifts every deadline on the file.

  • Confirms or creates the transaction record and matches it to the deal in Follow Up Boss, so both systems point at the same file.
  • Builds the roster: buyer, seller, both agents, lender, and closing attorney (this is North Carolina, so an attorney closes, not a title company).
  • Flags contract defects early: a missing initial or an undated signature is the number one thing that voids a file.
  • Finishes with a proposed timeline for your approval: "here is the schedule I read from the contract." You confirm it before anything else happens.
The date engine: working backward from closingEvery deadline derived, checked, and rechecked

The heart of the whole product. From the contract's two anchor dates, Cora derives the full working schedule: some dates count forward from the effective date (due diligence fee, earnest money deposit, loan application), and the rest count backward from closing (final walkthrough, closing disclosure, clear-to-close target, appraisal).

  • She knows which rules are law and cannot bend: the federal three business day closing disclosure window, and North Carolina's 5:00 PM due diligence deadline.
  • She knows which are convention, and which are your team's own standards, which you can change any time.
  • Every date on the schedule carries its reason, so when you ask "why is this due Tuesday?" she can tell you exactly.
  • When an amendment moves a date, she recalculates the whole schedule and shows you what changed.
The watchdog: nothing falls through the cracksDaily sweep of every file against its schedule

Every day, Cora walks every active file against its schedule. Anything coming due gets attention before it becomes a problem. Hard legal deadlines get louder treatment, earlier, than routine dates.

  • She knows the chase ladder: the lender is the most-chased party on any file (application confirmed, appraisal back, conditions cleared, clear to close).
  • Every file gets touched every day. Silence on a file is itself a finding, not a comfort.
  • Reminder drafts come to you batched: one approval card per file per day, never five separate pings.
  • When someone has ignored two nudges, she stops nudging and escalates to you.
Milestone emails, in your voiceYour templates, the right dates, English or Spanish

Cora drafts the standard communications of a transaction from your own templates: the introduction email to all parties, weekly check-ins, milestone reminders, and closing week logistics. She fills in names and dates from the live file, not from memory.

  • Every draft goes to your approval card before it is sent. You can edit it right on the card.
  • She writes naturally in English and Spanish, and remembers which language each client prefers.
  • Sent emails file automatically to the client's Follow Up Boss timeline, and she logs a note cross-referencing what was sent and why.
  • She knows North Carolina's two-step ending: settlement is the signing, closing is when the attorney records and funds move, and keys come at recording. Her client emails set expectations correctly so closing day has no surprises.
Signature packets, assembled rightThe right form, every signer, the right order

Mid-transaction paperwork is where files stall: amendments, repair agreements, due diligence extensions, notices. Cora assembles the packet so all you do is check it and approve.

  • She picks the correct NC form for the situation and attaches it so it fills from the transaction's own details.
  • She checks signer completeness (spouses and entities included) and sets the signing order correctly.
  • She keeps an eye on who signs last, because that signature sets the new effective date.
  • Assembling the packet and sending it are two separate approvals. The send card shows you exactly which documents, which signers, in what order.
Signature chasing, to completionFrom "sent" to "signed, filed, and reflected everywhere"

Sending a signature request is the easy half. Cora watches every outstanding packet and closes the loop.

  • She checks progress daily and drafts a reminder for anyone stalled about 48 hours, for your approval.
  • When everyone has signed, she collects the signed PDF and the certificate of completion and files them to the transaction.
  • If the signed document changed terms (an amendment moved closing, say), she recalculates the schedule and shows you the new timeline.
  • Completed documents queue automatically for the compliance checklist.
Compliance gaps, caught earlyYour checklist versus what is actually on file

Commission gets released when the compliance file is complete, so Cora treats compliance as a running task, not a closing day scramble.

  • She knows your market center's required document checklist and compares it against what actually exists on the file.
  • She flags gaps as they appear: an unsigned amendment, a missing disclosure, an initial page that never came back.
  • As documents are executed, she keeps a ready-ordered set so the compliance upload is a formality, done within days of each signing rather than piled up after closing.
Your playbook, rememberedYour standard work becomes her standard work

This is the quiet superpower. You know exactly how you like each step of a transaction handled. Cora learns it once and applies it every time.

  • Your instructions for each task ("when due diligence ends, here is the exact next-steps list") live in her playbook, in your words. You can read and edit them any time.
  • Your preferred vendors (inspectors, contractors), your template choices, and how each attorney or lender likes to be communicated with all accumulate here.
  • Every file she runs makes the playbook a little sharper. It is your standard work, made executable.
Her Standing Assignments

The jobs, and their instructions

Jobs are the standing assignments Cora runs on a schedule or when something happens. Each one comes with default instructions, shown below exactly as you will see them. They are written in plain English and they are yours to edit. Change the wording, change the rules, and Cora follows the new version from the next run.

Every morning · 7:00 AMStarts day one

Morning Brief

One message that replaces the morning scramble: where every file stands, before your first coffee.

Default instructions You can edit these
Every morning at 7, go through every active file and send me one brief that covers: where each file stands against its schedule, any task due today or in the next 3 days, any signature request still waiting and on whom, anything that changed since yesterday (a date moved, a document arrived, a stage changed), and who we are currently waiting on for each file. Lead with anything urgent. Keep it short enough to read on my phone.

Lands in your approval queue: nothing. The brief is a report, not an action. Anything in it that needs a send shows up as its own approval card.

Every day · middayStarts day one

Transaction Sweep

The "nothing falls through the cracks" patrol. This is the job that replaces worry.

Default instructions You can edit these
Once a day, sweep every active transaction. If the due date for a task is less than 3 days away, prepare the follow-up email to the responsible party and send it to me for approval. For hard legal deadlines (the due diligence deadline and the closing disclosure window), start earlier: 5 days out, and raise the urgency each day. Batch everything for one file into a single approval card per day. If someone has not responded to two reminders, stop reminding and flag them to me directly.

Lands in your approval queue: one card per filewith that file's drafted reminders, ready to approve, edit, or decline.

When a deal goes under contractStarts day one

New File Intake

The moment a deal moves to under contract, the file sets itself up.

Default instructions You can edit these
When a deal moves to under contract (or a new transaction appears in Lone Wolf), run intake on it: read the contract, pull out every date, build the full working schedule, set up the parties, and send me the proposed timeline as an approval card. Once I approve the timeline, create the tasks on the file and draft the introduction email to all parties (attorney, agents, lender) with the key terms and a request to confirm receipt.

Lands in your approval queue: the proposed timeline first, then the introduction email to all parties.

Every FridayStarts day one

Weekly Status Report

The weekly check-in great TCs are known for, generated instead of remembered.

Default instructions You can edit these
Every Friday, write a status update for each active file: what was completed this week, what is coming next week, and anything waiting on someone. Prepare one version for me, and a client-friendly version for each client in their preferred language. Send the client versions to me for approval before anything goes out.

Lands in your approval queue: each client-facing status email, one card per file.

When signatures are outstandingOnce Lone Wolf is connected

Signing Chase

Every signature packet followed to completion, filed, and reflected everywhere.

Default instructions You can edit these
Check every outstanding signature request daily. If a signer has had it more than 2 days, draft a reminder for my approval. When a packet completes, collect the signed documents and the certificate, file them to the transaction, and if the signed document changed any dates, recalculate the schedule and show me what moved.

Lands in your approval queue: signer reminders, and a revised timeline whenever a signed document moves dates.

Weekly, and after each signingOnce Lone Wolf is connected

Compliance Gap Report

The compliance file stays closing-ready the whole way, so commission is never waiting on paperwork.

Default instructions You can edit these
Compare each active file against our compliance checklist. Whenever a required document is missing, unsigned, or incomplete, add it to the file's gap list and include it in the morning brief. Keep the completed documents in checklist order so the upload to Command is ready whenever we are.

Lands in your approval queue: nothing directly. Gaps surface in the morning brief; any chase email they trigger arrives as a normal approval card.

This list grows with you. As Cora earns trust on these six, we keep adding assignments: closing gift reminders, post-closing follow-ups, utility transfer checklists, whatever your process calls for. You will always see each new job and its instructions before it runs.

How She Remembers

A working memory you can read

Cora keeps organized, readable notes, and you can open them any time. No black box: if she knows it, you can see it.

One notebook per transaction

Every file gets its own notebook: the full date schedule with the reason behind each date, the roster of parties, the open items list, and a chase log of who was nudged when and whether they responded. This is what the morning brief reads first.

Your playbook

Your standard work, in your words: how each task should be handled, which template goes with which milestone, your team's date rules. You can read and edit it any time, and Cora follows the current version.

People and preferences

Which clients prefer Spanish. Which lender answers texts but not emails. Your go-to inspectors and contractors. The small knowledge a great TC carries in their head, kept where it never gets lost.

What changed overnight

Cora checks your systems for changes many times a day and keeps a running “what changed” digest per file: a date moved, a document arrived, a stage changed. Yesterday's changes are always one question away.

Your playbook stays yours.Cora never rewrites your playbook on her own. When she notices a pattern worth adding (“we always order the survey the same week”), she suggests it to you as a card. You decide what becomes standard work.

How We Start

Day one, and what comes next

Day One

Cora starts on Follow Up Boss alone. The morning brief, the daily sweep, new file intake, and the weekly status report all run on your FUB deals, dates, and tasks from the first day. Nothing waits on Lone Wolf.

Next

Lone Wolf switches on when access is confirmed. Then transaction dates and documents come straight from TransactionDesk, and the signature work lights up: packet assembly, signing chase, and the compliance gap report.

Later

The assignment list keeps growing. Once the core is running on real files, we extend into whatever your process needs next, one job at a time, each one approved by you before it runs.

?

What we need from you to begin: your Follow Up Boss connection, a copy of your TC email templates, your task-by-task instructions for the playbook (a working session covers it), and confirmation of which Lone Wolf product your market center provides.

Send a brief.

Tell us what you want to be true. We'll come back the same day with a sketch.

Start a brief