What runs underneath
What runs underneath.
Terriv runs as four narrow jobs writing to one shared record, with a person in front of every decision. This page describes that architecture. It is the intended shape of the software, not an account of software that is running.
Nothing described on this page runs.
The four jobs
Four jobs. Narrow mandates.
Each job is scoped to one thing, and each is designed to write to the same record, so no part of the system acts on its own and no output is hidden from review. None of the four exists today.
- Lead intake Classifies an inquiry and puts it in front of the right person with the context that arrived with it. Inputs: website forms, lead inboxes and the portals the brokerage connects. Output: a routed lead with its source attached.
- Transaction file Takes the dates and required items out of executed documents and holds them against a timeline. Inputs: transaction documents and file activity. Output: proposed dates, missing-item notes, and the clause each one came from.
- Communication Summarizes what clients and parties have said across the channels a brokerage authorizes, and attaches each summary to the file it belongs to. Nothing leaves the brokerage: the output is for internal review only.
- Broker view Reads across the other three and orders what leadership should look at first.
After hours
After 6 PM, the work does not stop arriving.
Terriv puts what comes in overnight into one queue instead of six inboxes: new leads, missed calls, client questions, offer activity, document activity, and anything on a transaction that cannot wait. Each item carries its source, its contact, an owner and a priority.
| Item | Source | Contact | Owner | Priority |
|---|---|---|---|---|
| New leadWants to see 963 Larkspur Way this weekend | Website form | T. Calloway | Sarah Mitchell | High |
| Missed callVoicemail about the listing at 27 Quarry Ln | Business line | R. Onishi | D. Okafor | High |
| Client questionAsks when the inspection response on 412 Alder Ct is due | Connected inbox | L. Ferreira | J. Paz | Routine |
| Offer activityRevised terms circulated on 88 Fernwood Dr | Connected inbox | P. Stanton | R. Whitfield | High |
| Document activityTitle documents received on 1248 Walnut Street | Transaction file | Harborline Title | Sarah Mitchell | Routine |
| Urgent transaction issueMortgage commitment deadline approaching on 1248 Walnut Street | Transaction file | Sarah Mitchell | M. Ellison (Broker) | Urgent |
Leadership and each agent open one briefing in the morning: what came in overnight, what changed, and what needs a decision first.
What arrives in email becomes routed work.
Terriv reads the inboxes a brokerage authorizes, identifies what each message is, and ties it to the property or transaction it belongs to. No inbox connector exists.
What is read
Agent accounts opted in under broker policy, shared mailboxes, and lead inboxes. Nothing else, and nothing outside the accounts a broker has named in writing.
Email, calendar and transaction systems are switched on per brokerage under written terms.
Who decides that
The broker would configure which accounts are connected and who sees what, and access is designed to follow the same role-based controls as the rest of the product.
- New leads Classified and routed with the context that came with them.
- Client threads Connected to the file they belong to, rather than sitting in one person's inbox.
- Property addresses Matched to a transaction or a listing where the match is unambiguous.
- Documents Filed against the transaction record with the message they arrived on.
- Deadlines Proposed against the timeline for a person to confirm. A proposed date is not a tracked date.
- Questions Given an owner, so a question does not sit unanswered because nobody claimed it.
- Follow-ups Turned into tasks against the file, not into messages to anyone.
- Urgent items Raised for review rather than answered. Nothing is replied to on the brokerage's behalf.
Phone
What a call on the business line would have to become.
Calls to a brokerage carry leads, questions and problems, and they arrive with no file attached. Terriv turns each one into routed, reviewable work. The sequence below is the intended one, end to end.
- Call receivedA call arrives on the brokerage business line.
- Answered, or recorded and transcribedWhichever the brokerage configures, under its own recording policy and state law.
- Caller intent identifiedBuyer, seller, existing client, vendor, or something urgent.
- Lead and property capturedName, number, address, and what was asked for.
- Conversation summarizedA few reviewable lines, with the transcript behind them.
- Urgency assignedSo the morning starts in the right order rather than in arrival order.
- Routed to an ownerUnder the brokerage's routing rules, not ours.
- Task createdAgainst the file, with the context attached to it.
- Morning summary deliveredTo leadership and to the agent who owns the item.
This would apply only to brokerage-authorized business phone systems, configured by the broker, and never to a personal line.
What stays with your team
Agents propose. People decide.
Every job on this page is designed to organize, draft and flag. None of them would commit the brokerage to anything, and none of them is a substitute for your own file review.
- Proposals A classification, a summary or a date stays a proposal until a person accepts it. A proposed date is not a tracked date.
- Sources Every summary carries the message or document it came from, so the person reviewing it can check the claim instead of trusting it.
- Clients Nothing reaches a client from Terriv. Client communication stays where it is today.
- Access Which systems are connected and who sees what is set by the broker, and broker-level controls stay with the broker.