One transaction, worked in one place
Most agents keep the client in one tool, the conversation in another, and the paperwork in a third. The same address and the same names get typed into each, and the status of the file lives in the agent's head.
With the connection on, the transaction is where the agent works: the client, the messages, the tasks and the documents. The forms and the brokerage's review stay in Lone Wolf, and Raven keeps the two in step.
Forms from your Transact libraries
From the transaction's checklist, the agent picks a form from the libraries your brokerage licenses in Transact. Raven adds it to the matching Transact transaction, which it keeps in step with the transaction's property, parties and dates, and brings the filled PDF back onto the checklist item it belongs to.
- Your brokerage's own Transact forms libraries, browsed from the checklist
- Forms come back filled from the transaction's details
- Client agreements can be filled from the client's record before there is a property
- The filled PDF lands on the checklist item it satisfies
Signatures through Authentisign
The agent sends a form for signature in Authentisign without leaving the transaction. When every signer has finished, the executed copy comes back as an ordinary document on the transaction, ready to send to the broker.
- Started from the transaction's own documents and parties
- The executed copy returns to the transaction on its own
- Signing progress shows on the transaction while it is out
Send to Broker delivers into Transact
Set the Broker System to Lone Wolf Transact in Brokerage Settings, and every agent's Send to Broker delivers the finished document into the brokerage's Transact account. Your broker keeps reviewing where they review today, and Raven records what was sent, when, and where.
- One button for the agent, whatever system the broker reviews in
- Each delivery recorded on the transaction
- A document the broker sends back is reopened in one click, with both events kept
Getting connected
Your broker or office admin requests the connection from Brokerage Settings, Integrations; a solo agent requests it from Settings. Raven sends the request to Lone Wolf, Lone Wolf sends your broker its authorization form, and once it is approved Raven connects the account. Agents are matched to their Transact users by email.
- Requested from inside Raven, no technical setup on your side
- Your broker authorizes the connection with Lone Wolf
- Agents matched to their Transact users by email
What Raven adds around it
Lone Wolf keeps the forms and the file. Raven adds the rest of the business around the same transaction: the client relationship and pipeline, email and text in one thread per client, a shared Room for the other parties, and EVE, which reads the transaction and prepares the next step for the agent to approve.
- CRM and pipeline on the same record as the transaction
- Email, text and calls in one thread per client
- A shared Room for the client, co-op agent, lender and title
- EVE preparing updates and follow-ups for approval
What connects to Lone Wolf
Each connection carries the same status word everywhere Raven states it. Status as of October 2026.
Lone Wolf Transact
LiveMirrors a transaction and its documents into the agent's Transact account, browses the brokerage's forms libraries, attaches a form and pulls the filled PDF back into the transaction.
Authentisign
LiveDispatches a signing to Authentisign from the transaction and pulls the executed copy back as an ordinary document when every signer finishes.
TransactionDesk
Built, awaiting partner accessMirrors a transaction and its documents into the brokerage's TransactionDesk account and delivers a finished document there when the agent sends it to the broker.
zipForm
Built, awaiting partner accessMirrors a transaction and its documents into the agent's zipForm account; a signed-document return leg is not available on zipForm's API.
- Live:
- Connect it from Settings and it works today.
- Built, awaiting partner access:
- Raven's side is finished. It turns on the day the partner grants API access; until then it shows as awaiting access in Settings.
Lone Wolf, Transact, TransactionDesk, zipForm, Authentisign are trademarks of their owners and are named here for identification.
Frequently asked questions
Do we have to stop using Lone Wolf?
No. Your forms libraries, Authentisign and the Transact file your broker reviews stay in Lone Wolf. Raven connects to them so agents work the transaction in Raven and the paperwork lands where it always has.
Which Lone Wolf products does Raven connect to?
Transact for forms and the transaction file, Authentisign for signing, plus TransactionDesk and zipForm. Status today: Live: Lone Wolf Transact, Authentisign. Built, awaiting partner access: TransactionDesk, zipForm.
Who sets up the connection?
Your broker or office admin requests it from Brokerage Settings, Integrations. A solo agent requests it from Settings. Lone Wolf sends your broker its authorization form, and Raven finishes the connection once it is approved.
Does Raven copy our forms library?
No. The libraries stay in your brokerage's Transact account and Raven reads them from there. Only the forms an agent fills for a transaction are stored on that transaction.
Does the broker still review in Transact?
Yes, when the Broker System is set to Lone Wolf Transact. The agent presses Send to Broker in Raven and the document is delivered to Transact, where the broker reviews it.