AI Strategy

Real Estate Agent Offboarding: Transfer CRM Work and Revoke Access

Offboard a real estate agent with a verified CRM handoff: preserve history, assign tasks and appointments, check inbound routing, and remove remaining access.

By REN AI Editorial Team ·

A brokerage operations manager and team lead reviewing a work handover worksheet beside a laptop and desk phone

An agent can leave the brokerage while their leads, appointments and scheduled workflows remain active. Removing a login is only part of the change. The brokerage also needs to establish who may take over the work, what history must remain, where new inquiries arrive and how connected access actually ends.

How should a brokerage offboard an agent without abandoning leads?

Name an authorized operator and approved successor, inventory active work and connected access, and set a documented cutoff. Transfer permitted responsibilities, preserve required history, and verify appointments, inbound routing and queued messages separately. Remove access through each relevant system, then record observed results and unresolved exceptions. If access is compromised, follow the incident process immediately rather than delaying containment for a routine handoff.

Checked October 17, 2026: This is an editorial operations checklist, not legal advice or a universal CRM procedure. Brokerage agreements, client instructions, transaction status, local rules and retention obligations determine what may be transferred or retained. A technical assignment does not decide who owns a client relationship. Resolve those questions with the responsible broker and qualified advisers.

Why is offboarding different from deleting contacts or migrating a CRM?

For this guide, agent offboarding means ending one person's authorized access while maintaining approved responsibility for the work that remains. The CRM stays in place. This is not an instruction to export the database, merge people, erase a former agent's activity or transfer clients automatically.

The CRM governance guide covers ongoing field definitions and permissions. Offboarding applies those decisions to a specific departure. Keep three outcomes separate: the former user's access ends; permitted work reaches a named successor; required records remain available to authorized people. A pass on one outcome does not establish the other two.

What can change when a CRM user is removed?

Follow Up Boss's user-deletion guide illustrates why the operator must inspect more than lead ownership. In that product, an owner or admin deletes the user and selects the agent who receives the leads. Manually created tasks and action-plan tasks are reassigned to the selected agent. Notes, call logs, texts and shared emails remain on lead profiles.

The same guide documents important exceptions:

  • Appointments remain, but the newly assigned agent is not automatically added. Reassigned leads do not prove the successor can see and handle every appointment.
  • Scheduled emails from the deleted user do not send. A successor must review the planned communication rather than assume it transferred.
  • Shared email and text templates created by that agent are deleted. A Smart List must be shared before deletion to remain. Review assets that the team relies on before the routine change.
  • Access and history are different. The guide says deleted-user CRM/mobile access is revoked and attached API keys become invalid; retained lead history is not retained user access.

These are Follow Up Boss-specific behaviors, not REN AI specifications or promises about another CRM. Ask each vendor what its remove, deactivate, suspend and delete controls actually do. Do not substitute one action for another based on its label.

A six-check departure runbook for brokerage operators

The following process is a REN AI editorial recommendation. For a routine planned departure, prepare the continuity handoff before the cutoff and coordinate it with access removal. In a suspected compromise or unauthorized-access case, the incident owner should contain access promptly and arrange a controlled continuity response in parallel.

  1. Authorize the scope and cutoff. Record the departing user's identifier, approved operator, effective time and who may approve reassignment. Identify active client matters, team-owned inquiries and disputed or restricted records separately. Route unresolved authority questions to the broker; do not let an AI summary decide them.
  2. Inventory work, not just contacts. List active leads, open tasks, appointments, deals, collaborator access, shared inboxes, phone numbers, routing rules, templates and queued communications. Record the system that controls each item. A calendar event mentioned in a CRM note may still require a separate calendar change.
  3. Prepare and accept the permitted handoff. Name a successor for each responsibility, preserve the original activity attribution and verify that the successor can see the required records. Check client-facing sender details and appointment participation. A person appearing in an owner field is not evidence that they accepted the task or received its deadline.
  4. Review connected workflows and inbound channels. Check where replies, forms, calls and texts go after the cutoff. Inspect agent-specific sending accounts, calendars and integration credentials. Hold affected AI-assisted actions when ownership, permission or routing is unresolved; do not pause unrelated work merely because it shares the same platform.
  5. Remove access through the relevant controls. Follow each provider's supported procedure for the CRM user, mobile access, identity account, sessions and connected grants. Identify user-bound API keys and separately governed shared credentials. Do not blindly revoke a company-wide connection that other authorized users still need; arrange an approved replacement or narrower change.
  6. Verify and close exceptions. Use authorized admin evidence and isolated tests where appropriate. Confirm the successor's task and appointment access, the monitored inbound destination and the affected workflows' approved state. Record access-change results, remaining limitations and follow-up owners. Do not use a former employee's credentials or send a test to a real client.

The broker-led onboarding plan addresses the successor's training and competence, not just access. After the handover, use ongoing workflow exception monitoring to catch missed replies and unowned work. A departure closeout is a specific change record, not a replacement for ongoing supervision.

Does disabling identity access end every connected session?

A disabled company login is not proof that every application session has ended. Microsoft Entra's access-revocation guidance distinguishes blocking new sign-ins and revoking refresh tokens from existing access tokens and sessions issued by an application. Microsoft states that Entra cannot directly revoke an application-issued session token. Check the application's own deprovisioning and session controls as well as identity changes.

That limitation describes Microsoft Entra's role; it does not contradict Follow Up Boss's documented deletion behavior or establish a universal waiting period. The useful question is: which authority issued this credential or session, and which control can invalidate it? Have the responsible administrator document the applicable answer.

Google Account Help separately explains reviewing and removing third-party access to Google Account data. Removing that grant is not a CRM ownership transfer or evidence that an external provider erased information it already received. Distinguish user-level grants, organization-managed access and the vendor account itself; use the authorized administrator rather than asking a departing agent to share a personal password.

How do you avoid abandoning an inbound number or reply channel?

Follow Up Boss's phone-number guide documents supported changes between team members, team inboxes and company number assignments. Its user-deletion guide separately describes temporary routing for a removed user's number. Do not confuse a temporary forwarding state with a permanent, monitored destination or apply a deadline from a different number-management procedure.

Record the actual number, current route, approved replacement destination, responsible monitor and any provider deadline. Check whether voice calls and texts follow the same route in the chosen setup. Confirm the destination through a vendor-supported preview or authorized internal test; this article does not establish that any particular provider supports a routing preview.

Use the same discipline for email replies, booking links and website forms. A website can still advertise the departed agent's details after CRM reassignment. The operator should identify and resolve affected entry points within their authority. Do not change a public profile owned by another business merely because an agent departed.

A fictional handover: leads moved, but the appointment did not

Illustrative same-platform scenario—not a REN AI customer result or product demonstration: a brokerage authorizes Jordan to succeed a departing agent on one active buyer inquiry. The CRM records the new owner and preserves the prior conversation. Jordan's first check finds that the separate calendar still lists only the former agent. The team marks the appointment handoff incomplete and asks the authorized calendar owner to correct participation.

A connected follow-up workflow also refers to the former agent's calendar and reply destination. The operator holds that affected workflow, records the approved replacement settings and checks them without contacting the buyer. Only after Jordan accepts the next action and the responsible operator approves the verified configuration does the workflow return to its permitted state. The example shows why a contact reassignment should not be reported as a completed handover.

What should the closeout record prove?

Keep a protected record containing the object or workflow identifier, former responsible user, approved successor, relevant system, cutoff time, expected outcome, observed evidence, reviewer and exception status. Record what was verified and what remains unknown. Do not place passwords, reusable tokens or unnecessary client information in the checklist.

An unresolved calendar, an unmonitored inbox or an application session that has not been addressed should have a named owner and explicit disposition. Do not close the record merely because the former user vanished from a team list. Applicable retention and incident requirements come from the actual agreements, rules and professional review, not a universal retention period in this guide.

Where does REN AI fit?

The REN AI platform overview and AI Workforce service description provide context for evaluating lead-response, follow-up and business workflows. This guide does not claim REN AI automates agent offboarding, revokes identity credentials, transfers phone numbers, retains every CRM object or implements the provider-specific controls above. Verify supported behavior and ownership responsibilities in the actual configuration.

You can start a free REN AI account to explore the current offer and bring a fictional handover scenario to a workflow discussion. Review REN AI customer experiences as context, not proof that your departure process is complete or secure.

Frequently asked questions

Does deleting an agent from a CRM delete their lead history?

The answer depends on the product and action. Follow Up Boss documents that notes, call logs, texts and shared emails remain on lead profiles when a user is deleted, while other objects have different outcomes. Do not assume another CRM behaves the same way. Review the current vendor documentation and brokerage retention requirements before changing access or records.

Does disabling a company login end every CRM or connected-app session?

Not necessarily. Microsoft Entra distinguishes blocking new sign-ins and revoking refresh tokens from existing access tokens and application-issued sessions. Entra cannot directly revoke a session token issued by an application. Check the identity provider and each connected application's own access controls, and retain evidence of the relevant changes rather than treating one disabled-login screen as complete offboarding.

Can AI keep following up after the assigned agent leaves?

Do not continue merely because the automation is still running. A responsible operator should verify the permitted workflow, current human owner, reply destination, calendar, sending identity and escalation path. Hold affected actions when those dependencies are unresolved. A new assignment does not create client-transfer authority or communication consent; the brokerage must approve the actual handover and restart.

Sources and methodology

Sources checked October 17, 2026. Provider documentation supports only the named products and controls. The six-check runbook, closeout record and fictional scenario are REN AI editorial recommendations, not a vendor certification, legal ownership decision or measured outcome. No live account deletion, access revocation or client-message test was performed for this article.