Skip to content
nofeb

Solutions / Real-estate closing

Document chasing for closings

For real-estate, mortgage and title operations

A closing is a checklist that lives in email: disclosures, signed forms, inspection reports, each from a different party. Most of it is routine chasing, and some of it must be handled by a person.

The problem

Every transaction involves buyers, sellers, lenders and agents on different threads. Documents arrive as attachments with inconsistent names, and exceptions need a person without losing the context.

How it runs on nofeb

  1. Create a pod per brokerage or client and an inbox per transaction, so each file's mail and keys stay separate.
  2. Give each human agent a forwarding address into the transaction inbox. Their own mailbox forwards the closing mail byte for byte, only from the addresses you allow, and the Gmail or Outlook forwarding-confirmation code shows up on the address so setup takes one step.
  3. Label messages with keywords, keep the document checklist on the thread as typed metadata, and read attachments through their extracted text while the originals stay filed byte-exact.
  4. Put each document's deadline in follow_up_at; when it passes, a thread.due event wakes the agent to chase it.
  5. Book the walkthrough and the signing from the transaction inbox's calendar: find a slot inside working hours that is free on every inbox involved, and the booking creates the event and emails the invitations. Replies from the parties update it automatically.
  6. Anything addressed to a buyer or seller is a draft the agent writes and a person sends, or a send held for approval.
  7. When a deal goes sideways, the escrow officer takes the thread over in the webmail, with the checklist in the metadata panel and the agent's activity on the timeline, and hands it back when it is routine again.
  8. Keep closed files for as long as your regulator requires with a retention policy per pod, and put a legal hold on a transaction under dispute.

Where nofeb stops

  • nofeb is not an e-signature or transaction-management system.

Status of everything this relies on

CapabilityWhat it doesStatus
Pods Sub-tenants inside one organization: one per end customer, created idempotently from your own customer id. Shipped
Unlimited inboxes Create as many inboxes as the work needs, with a generated or chosen address and an idempotent client reference. Shipped
Attachment text Attachments are listed with their extracted text and can be downloaded byte-exact. Shipped
Typed metadata on messages, threads and inboxes Merge-patch keys onto a message, a thread or an inbox, and declare a key's type so every write to it is validated. Shipped
Folders, keywords and labels Folder roles with unread counts, plus keywords such as seen, flagged or your own labels. Shipped
Human approval of held sends A held send waits with status awaiting_approval until a human approves or rejects it; both steps emit events. The approval queue lists every held send with its recipients (each marked if new to the conversation), the reasons it was held and who submitted it. Approving needs the separate send:approve scope, which keys from agent self-signup never hold, so an agent cannot approve its own send. Shipped
Follow-up timers Set follow_up_at on a thread and, when that time passes, a thread.due event carrying the thread's metadata goes to your webhooks and the event feed, so agents need no scheduler of their own. Shipped
Forward to an agent Per-person forwarding addresses that bring someone's own mail into their agent's inbox byte for byte, accepting only mail traceable to the senders you allow. Gmail and Outlook forwarding-confirmation codes and links are recognised and surfaced, and each address can be rotated or revoked. Shipped
Calendar per inbox A calendar on every inbox: events with recurrence and time zones, invitations, updates, cancellations and replies by email, auto-accept rules, free/busy, availability and booking that sends the invitations, MCP tools for scheduling, and CalDAV and JMAP Calendars for standard clients. Invitations an agent sends follow its inbox's autonomy tier. Shipped
Drafts Agents write drafts that a person edits and sends, over the API, MCP, JMAP, IMAP and the webmail. It is the documented path for draft-only inboxes: sending a draft needs the approval permission agents do not hold. Shipped
Take a thread over from the agent A person takes a thread over; until they hand it back, the agent's sends on that thread are held for approval or refused, and an event records who is driving. Works over the API, MCP, JMAP and the webmail. Shipped
Webmail for the humans in the loop A full webmail and calendar on the same mailboxes the agents use, with an agent-activity timeline, the approval queue, a per-thread driver lock and a metadata panel, signed in through the same accounts as the console. It opens with hosted access. Shipped
Retention policies and legal holds Delete messages older than a number of days, or move them to Trash or Archive, per organization, pod, inbox or folder, keeping flagged mail by default, with a dry run that shows what a policy would do. A legal hold blocks every deletion in its scope, including expiry and inbox deletion. Shipped