Workflows

Automations & prepared work

Everre runs standing instructions on its own and stops where a decision is yours. All of it lives on the Home screen, in the card under the activity strip. At the top of the card's rail a switch reads Chat, Review and Automations: where you ask, what came back and is waiting on you, and what runs on its own. The rail and the pane change under the switch; the card stays put. On a phone the rail is folded away and the switch sits above the pane.

Chat

The assistant. The rail holds your conversation history, with + New to start another and a filter to find an old one. This is also one of the two places an automation is set up: "Every Monday morning, draft follow-ups for every contact I haven't spoken to in 30 days" becomes a standing instruction with its schedule set. The other is the editor under Automations, below.

Review

Everything Everre assembled and stopped short of sending: a document filled from a template, an email drafted for a contact, a deck built from your offering memorandum template, a rent roll extracted from a PDF, a step an automation could not carry out on its own. Items arrive from an automation, from something you asked in Chat, or from your email agent. The number on the switch is how many are waiting on you.

The heading counts what is ready and how many answers stand between you and all of it going out. Under Status in the rail you can narrow the list:

  • Needs you — items with a question only you can answer
  • Ready to send — everything is answered; it goes out when you approve it
  • Done — approved, or sent back

Open an item and its header takes the top of the pane: the title, three counts and the actions.

  • Assembled — figures Everre stands behind. Every one names its source: a deal record, a page of a document, a calculation.
  • Need you — calls Everre would not make for you. A due diligence period, a price, a name. The approve button stays disabled until every required one has an answer.
  • Left blank — fields Everre deliberately left empty, each with a reason.

The left pane shows the deliverable as it will go out, with assembled figures highlighted and open questions marked as gaps. Clicking a gap takes you to its question on the right. The right pane lists the questions, then the assembled figures with their sources, then anything left blank. The two panes scroll independently, so a long document and a long list of questions stay side by side.

The actions:

  • Open — when the item is something that already exists in Everre, such as a presentation an automation built from a template, this opens it so you can look at the real thing before deciding.
  • Send back — reject it. Nothing is sent, and the item moves to Done.
  • The approve button, labelled for what happens next: Send for signature, Send, Approve. For work that was already made, approving keeps it. For a call Everre held back, approving runs exactly what was on screen, with no re-planning in between.

The open item is in the page's address, so it can be linked to, and that is where a review notification lands.

Automations

An automation is a When and a Then: something that sets it off, and the steps that follow, in order, the same way every time. The rail lists your automations and your integration feeds, each with a status dot; pick one and the pane shows its chain, when it runs next, when it last ran, how many times it has run, the last error if there was one, and its run history. Run now runs it once without waiting; the switch pauses and resumes it; Edit opens it in the editor; + New starts one from scratch.

When

  • On a schedule — daily, weekly or monthly, at an hour in your timezone. Every Monday at 7:30, go through the pipeline and tell me what moved.
  • When a deal reaches a stage — one stage you pick, or any stage change. When a deal goes under contract, create the closing checklist.
  • When a file of a kind is uploaded — a purpose tag you pick, or any upload. When a rent roll comes in, reconcile it against the leases.
  • When a website inquiry is received — a form on one of your sites, by name, or any form. When someone asks about a listing, send them the follow-up with the OM attached.
  • When a record matches a saved view — the view's filter is scanned on a schedule, and each property, person or company runs once when it first matches, never again for the same record. Every morning, for every building that sold in the last 30 days, put a call to the new owner on my list. The database filter has a within last N days operator for exactly this.
  • When a property gets a new record — a new permit, violation, tax appeal, court listing, foreclosure or sale on any property, or on the properties in a saved view, checked on a schedule. Each record runs once, so a second permit on the same building runs again. Only records that arrived after you made the automation and happened within the last 90 days count — adding a building brings its history with it, and that is not news. Tax appeals are dated to their tax year, so set the window to a year to catch them. When a foreclosure is registered on a building in my South Side view, create a task to call the bank's agent.

Then

Up to ten steps. Six run as code, identically every time; the seventh hands work to the assistant.

  • Create a task — title, priority, due in N days, and who it is for: a named person, the deal's owner, whoever set the automation up, or nobody yet. It lands on the deal or property that set the run off.
  • Send a template — an email template, filled in for the recipient and the property, sent from your connected mailbox. The recipient is the inquiry's contact, the person that set the run off, or an address you type. Tick Attach the property's offering memorandum and the OM goes with it as a PDF. Templates can use {{inquiry.name}} and {{inquiry.email}} alongside the usual people and property variables.
  • Set a field — one custom field on a property, person or company, written the way you would write it, so a later import or enrichment leaves it alone.
  • Enrol in a sequence — puts the person into an outreach sequence. The inquiry's contact becomes a contact record the first time a step writes to them.
  • Look up data — the lookups from Enrich: the property that set the run off, or every property in a saved view. On a schedule it keeps permits, sales, tax history or owners current; on a new record or a matched view it looks up each property as it arrives. Charged like any lookup, and values go where you last sent each field.
  • Ask the assistant to… — an instruction in your own words. The assistant is told which record set the run off and works the instruction as it would in Chat; anything it wants to send, publish or delete still stops for you in Review. Reach for this where the work needs judgement — reading a closing date off a contract, finding a new owner's number — and for the other six where it does not.

A step has to make sense for its trigger, and the editor only offers what does: "the inquiry's contact" exists only on a website inquiry, and a schedule has no record of its own, so it carries assistant steps and lookups over a saved view.

Pre-approved

Sending a template and enrolling in a sequence normally stop in Review before they go out. Tick Pre-approved and they run without anyone reading them first — as long as nothing is missing. Before every pre-approved step Everre checks what it needs: the record it acts on exists, a mailbox is connected, every variable in the template filled in, the offering memorandum is there if it was asked for. Anything short of that and the step stops in Review with the reason — "No offering memorandum exists for 4645 W Belmont Ave" — and the steps after it wait. Fix what was missing and approve the item, and it sends exactly what was queued. Pre-approval covers what you saw when you set the automation up; it never extends to what the assistant decides to do inside an "Ask the assistant" step.

Run history

Under the chain, every run: when, what set it off, and whether it completed or is waiting in Review, with a link straight to the item. Three failures in a row pause the automation and tell you why; switch it back on once the cause is fixed. An organisation can have thirty automations, and a saved-view or new-record automation works through at most a hundred records per scan, taking the rest next time.

If you used stage checklists

Default tasks per pipeline stage, under Settings → CRM → Pipeline, are gone. The same thing is an automation with a "deal reaches a stage" trigger and one "Create a task" step per item — and each task now has its own assignee, due date and priority, and the one that needs reading the contract can be the assistant's.

An automation cannot create or change other automations, and an outside assistant connected through MCP cannot see them at all. Standing work is only ever set up while you are present, in Chat or in the editor.

What Everre will not do on its own

Anything irreversible or outbound — sending an email, requesting a signature, deleting a record, publishing a website — waits in Review with the exact arguments on screen, unless an automation you pre-approved is sending a template and every check passed. Approving from Review runs that call and nothing else. Work that is reversible, such as filling a template, runs first and is handed to you finished, to keep or send back.