Choosing the Right Roles

Nekst works differently than most transaction tools: instead of assigning tasks and messages directly to specific people, you assign them to a Role — Buyer, Lender, Transaction Coordinator, Listing Agent, and so on. When you launch a transaction, you link a real person to each Role, and that person becomes the recipient of any task or message routed to that Role.

This is a deliberate design choice. It lets you build a workflow once and reuse it across every deal — with whichever team members, service providers, or transaction parties happen to be involved this time. You don't rebuild the workflow per client, and you don't have to re-route every task when your team changes.

Roles in Nekst apply in two contexts:

• Transaction Parties — the external people involved in a transaction: the Buyer, Seller, Lender, Title Representative, Inspector, Buyer's Attorney, and so on.
• Team Members — the people who work on your business: an Assistant, Transaction Coordinator, Listing Specialist, and so on.

You customize your own list of Roles so they match how you actually run your business. Nekst comes with a default set, and you can rename, remove, or add to them as needed.

Where Roles are used

Roles show up in three places across Nekst. Seeing each one helps explain why the role-based approach pays off:

Adding parties to a transaction. When you create a new transaction, you add the people involved by Role. Rather than just typing their names, you tell Nekst "this person is the Lender" or "this person is the Buyer's Attorney." That assignment is what later lets Nekst route the right message or task to the right person on this specific deal.

Choosing recipients for Email and SMS in Workflows. When you build an Email or SMS task inside a Workflow, you don't pick a specific person to send it to — you pick the Role that should receive the message. The actual recipient is filled in at launch time, based on who you assigned to that Role on the transaction.

Assigning tasks to team members (Pro accounts only). On a Team Pro account, tasks in a Workflow can be assigned by Role as well. When the workflow launches, the task lands on the to-do list of whichever team member is filling that Role on this transaction. Change who's filling the Role and the task automatically reassigns.

Here's an example of setting an Email task to send to a specific Role inside a Workflow:

Managing Roles

Your list of Roles lives in your account settings. To open it:

1. Go to Settings → Setup → Custom Roles.
2. From there, you can add new Roles, rename existing ones, or remove Roles you don't use.

When you create a new transaction (or open an existing one), you assign actual people to those Roles using the Transaction Parties section of the transaction page.

Team Pro tip: assign tasks by Role when you build a Workflow rather than by specific person. That way, when you launch a new transaction and assign your team members to each Role, every task tied to a Role automatically lands on the right person's plate — even if your team has changed since you built the workflow.

Best practice: decide your Roles before building your first Workflow

Take a few minutes upfront to decide which Roles fit your business. This pays off because every Workflow you build, every email template you write, and every task you create is going to reference those Roles. Getting the list right at the start means you won't have to revisit existing Workflows later when you realize you needed a Role you didn't define.

Add or edit your Roles in Settings → Setup → Custom Roles, then start building.

Pre-loaded Roles

These come with Nekst. You can keep, rename, or remove any of them. Most users start by reviewing this list and removing what doesn't apply to their business before they add anything new:

System Roles (can't be removed)

A few Roles are built into Nekst and you can't delete them, because they're tied to how transactions get created and shared:

• Editor — can edit a transaction's details but doesn't have a formal external role. Nekst automatically assigns this to the person who creates a transaction, unless another Role is selected for them.
• Viewer — can see a transaction and view its tasks and details, but can't edit anything.
• Manager — reserved for the account owner. Gives full access to every transaction in the account regardless of who created it.

Common confusion: what do you call the agents?

Whatever you decide to call the agents in your transactions, be consistent. The exact label doesn't matter as much as picking one and using it everywhere — because every SmartTag, task assignment, and report references the Role name you choose.

Agent representing the Buyer: Real Estate Agent · Co-op Agent · Buyer's Agent · Selling Agent · something else

Agent representing the Seller: Real Estate Agent · Co-op Agent · Listing Agent · Seller's Agent · something else

Updated on: 06/11/2026