Task
A piece of work with an owner and next action. Use it when someone needs to do something.
Realtors and coordinators
Use this guide to start the day, work a lead, update a client, request a file, invite someone into Journey, and bring in a partner for one piece of work.
01 / First session
Your exact menu depends on your role. A realtor usually sees Today, Clients, Inbox, Lead Inbox, Reports, and Settings. Coordinators may see fewer areas.
Use the password you created from your invitation. If you cannot remember it, choose Forgot password from the sign-in page.
Check the upper-left product name and the account shown in the upper-right. Stop if you are in the wrong team workspace.
Today is the daily operating page. It gathers client tasks, overdue items, messages, and document work into one ranked list.
Read the client name, stage, owner, due information, and suggested action before changing anything.

02 / Today
Do Next is ranked for action. Filters narrow the queue; they do not delete work.
Check the item type, client, current stage, owner, and due state. Open the item when you need the full client context.
Call, reply, review, upload, or update the client as the item requests. Do not mark an item done merely to clear the list.
Add the useful result, assign the right owner, and set the next follow-up when the relationship still needs attention.
Work the next item until the remaining list reflects what truly needs attention.

Use the field labeled for internal notes when a comment should stay with the realty team. Client-facing messages should contain only what the client is meant to read.
03 / Clients
Clients contains the relationship profile, current work, documents, messages, and timeline. Use search when you know the person; use filters when you need a group such as active buyers or items with no next step.

Confirm the person and household before editing. Similar names can belong to different relationships.
Check the stage, owner, open work, and most recent activity before calling or messaging.
Tasks holds assigned work, Documents holds requests and files, Messages holds scoped conversations, and Timeline keeps the activity history.
Before closing the client record, make sure responsibility and timing are understandable to the next teammate.

04 / Lead Inbox
Lead Inbox is for people who may need contact but are not yet active clients. A high place in the list is a reason to review the person, not an instruction to contact them automatically.
Use New or Follow-ups when you need a short list. Check whether someone else already owns the item.
Review timing, plan, area, budget, message, and any uncertainty shown. Do not assume every field is complete or current.
Claim and contact when the context supports it, set a later reminder when timing is not right, or hide the item when it should not be worked.
Use a short factual note. If the person becomes an active client, carry the context into the client record instead of starting again.

05 / Journey invitation
Journey is the client-facing plan. Internal notes and restricted documents do not belong in the client view.
Confirm the email address with the client before sending anything.
Make sure the current stage, next action, responsibility, and requested items are accurate and written in plain language.
Send the invitation through the client access area. Do not copy an invitation created for another person.
They will create or connect their Journey account, open Home, and see the plan your team shared.

Verify the address, ask the client to check spam or junk, and resend from the client access area. Create a fresh invitation if the old link expired.
06 / Tasks and documents
Use a task when someone must do something. Use a document request when a specific file must be supplied or reviewed. Keep the two linked when the task cannot finish without the file.
A piece of work with an owner and next action. Use it when someone needs to do something.
A request for a specific file or review. Explain why it is needed and who is waiting.
A client-visible update or question attached to the relevant work.
Team-only context that should not appear in the client's Journey view.
Create the work where it belongs so the client and the next teammate can understand the reason.
Use a title such as “Upload pre-approval letter,” not “Send documents.” Add a due date only when it is real.
Confirm whether the client, a teammate, or an invited partner should act, and keep internal commentary in an internal note.
Move the request to the state that is true now. Explain what must change if the file is incomplete or belongs to another request.

Never ask a client to send a password or full account credential. Use the specific secure request supplied by the workspace for sensitive files.
07 / Partner invitation
A partner invitation should contain only the task, request, document, message thread, or status item the partner needs to handle.
Start from the task or request, not from a broad client export.
Select only the work the partner needs. Review the access summary before sending.
Send the secure invitation to the individual who will complete the work.
Review the returned update, finish the request, and revoke access that is no longer needed.

Share the public partner guide so the invited person knows what the link will show.
08 / Daily habit
09 / Troubleshooting