Roles and permissions
Know which HoneyFalcon actions belong to agents and firm admins.
Give each teammate the right operating surface while preserving company control and a clear final safety net for leads that complete the normal route without acceptance.
Why it matters
Clear roles help agents focus on selling while firm admins manage the rules that affect the whole company. The designated buffer is an additional routing responsibility, not a separate access role, so the team can protect unaccepted opportunities without creating a second operating structure.
See it in HoneyFalcon
Step 1 of 2: member role, account, profile, eligibility, and buffer badges.
Step 2 of 2: Available as buffer control in the member editor.
Roles that keep work clear
Agent
An eligible Agent can receive lead offers, accept or reject them, work accepted leads, search records visible to that account, and review personal activity and results.
This focused surface keeps urgent decisions and owned work close together without exposing company-wide configuration.
Firm admin
A Firm admin manages members, invitations, allocation, tags, business hours, costs, templates, intake keys, CRM connectors, the company profile, and subscription.
Admin access does not automatically make someone the terminal buffer. A firm-admin account can participate in normal lead work when its account, profile, and lead eligibility are active.
Pausing a member affects future allocation
Turning off the account, allocation profile, or lead eligibility removes that member from new automatic offers. Existing leads and history are not deleted or automatically reassigned.
Designated buffer
Buffer is an extra routing responsibility that can be assigned to one eligible company member. The same person remains an Agent or Firm admin and can still participate in normal routing when eligible.
After the regular path has no recipient left, the active designated buffer is the first terminal-rescue choice. When no eligible buffer is designated, HoneyFalcon uses the eligible firm-admin fallback.
Manual assignment remains an admin decision
A Firm admin can assign a lead manually to an active teammate in the same company. Preferred or Hard tag matching does not choose or block that explicit administrative destination, while the assignment flow keeps its normal protections.
Company boundaries stay enforced
Access remains company-scoped. A member cannot use an identifier or copied URL from another company to read or modify that company's records.
A practical staffing scenario
A small team can keep most members as Agents, give one operations lead Firm admin access, and designate one reliable teammate as buffer. The admin configures the process, agents focus on offers and follow-up, and the buffer adds final coverage without being removed from ordinary distribution.
The result is less ambiguity over who can change rules, who should act next, and who receives the last rescue opportunity.
Choose the buffer for operational availability, not as a substitute for correct roles or healthy routing. The buffer acts only after the normal path has run its course.
Roles are configured well when
- Agents can complete daily lead work without access to company-wide settings.
- Firm admins can configure the company and intervene manually when needed.
- Exactly one eligible member is marked Buffer when terminal rescue needs a designated recipient.
- Standard members remain available for normal routing according to their active and eligibility settings.
- Pausing a member changes future allocation without rewriting existing lead ownership or history.