Askleadbind.orgOpen LeadBind →
LeadBind Docs

Invite your team

Seats, roles, and the calendar gap that quietly breaks new reps.

Seats, roles, and who can see what. Open Team in the app.

Roles

Owner or manager. Runs the org. Sees every rep's leads, calls, and bookings. Configures accounts, creates snapshots, and manages managed clients.

Rep. Works their own leads. Sees their own pipeline, their own calls, their own calendar.

The split is deliberate: a rep should not be browsing another rep's book, and a manager should not have to ask permission to see the board.

Adding someone

Seats are billed per seat with no minimum, so a team of one rep is a real configuration rather than a workaround. Add the second seat when you hire, not before.

Invite them by email from Team. They set their own password, or sign in with Google or Apple if you have that enabled.

Before they take a single call, three things need to be theirs and not yours:

  1. Their availability: their real hours, not a copy of yours. This is the one people skip, and it is why a rep gets booked while they are asleep.
  2. Their calendar: connected by them, to their own Google account.
  3. Their number or caller ID: so a callback reaches the person who called.

Teams

An agency with more than one team leader needs more than one floor. A team is a named slice of your org with a lead of its own.

What a team lead sees. Their own reps and nobody else's. The roster, the leaderboard, coaching, floor callbacks, the door map, and the end of day recap all narrow to their team. Lead distribution narrows too: a round robin from a team lead reaches their own reps only.

What the owner sees. Everything, as before. The owner is the only person who can create a team, rename it, name its lead, or delete it. Filter chips on the Team page narrow the owner's view to one team when they want it.

Who can move reps. The owner, on any team. A team lead, on their own team. Naming the lead stays with the owner on purpose, because a lead who could appoint the next lead could hand themselves a second team.

If you never create a team, nothing changes. A flat org behaves exactly as it did before teams existed: every manager sees the whole floor. The same is true for a manager you have not put in charge of a team, and for a rep you have not placed on one.

Deleting a team does not delete anyone. The reps on it go back to no team, with their leads, their numbers, and their history untouched.

The leaderboard

Ranked by bookings, over today, 7 days, 30 days, or 90 days. Every rep can see it, not just managers. A rep on a team competes against their own team; everyone else sees the whole org. A rep does not see teammates' contact info or full pipeline through it, only names, avatars, and where everyone stands. Solo accounts with no org see nothing here; the leaderboard only exists once there is a team to rank.

Floor callbacks

Every callback your reps promised in the next 24 hours, on the Team page, grouped by rep. Managers and owners only.

A callback is the one appointment a rep sets for themselves, and it is the one nobody else can see until it is missed. This is where you see it before that. Anything whose time has already passed is still listed and marked past due, rather than disappearing the moment it is late.

Reps see their own version of the same list on Home. See Follow-up sequences.

Coaching

What the call grader heard on your team's calls, per rep, over the last 7 or 30 days. It is a separate tab on the Team page.

Full detail: Coaching your reps.

The end of day recap

Owners and managers get one message at the end of each day with what the floor produced: dials, connects, bookings, sales, and knocks, for the team and then per rep, busiest first. A team lead gets their own team's numbers, named for the team. The owner gets the org.

Two things worth knowing. Only reps who did something appear, because a roster of zeros is the part of a digest nobody reads. And on a day where the whole team did nothing, nothing is sent. A message saying a team made no calls on a Saturday is noise, so there is no message.

It follows your notification settings like everything else, so it reaches you wherever you already read LeadBind.

What a manager should watch

Not activity. Outcomes.

  • Connect rate per rep. Low across everyone is a list problem. Low for one rep is a timing or approach problem.
  • Booking rate per rep. The number that turns into money. See Dashboard.
  • Leads sitting untouched. The most expensive thing on the board.

A connected assistant answers this better than a filter does: "Which reps have leads that went cold this week?"

A trap worth naming

Calendar connections are per person. A rep who never connects theirs is invisible to the booking engine, so LeadBind will happily book them on top of whatever is already in their day. It looks like a scheduling bug and it is an onboarding gap.

Check every new rep has connected their calendar before you give them leads.

Was this page helpful?
NextLead routing →