Your team, each with their part.
Invite people, give each a role and the access it needs, and let work find the right team.
Invited, placed, described.
Invite by email, a whole group at once.
Type several email addresses, pick a role and, if you want, a team, and send. Each person gets an invitation.
A role for each person.
Every person has a role, such as owner, admin or operator, and the list shows who has joined and who is still pending.
Put people in teams.
Group operators into teams, such as Support, and add members to each.
Work reaches the team its description names.
Say in a sentence what each team handles. Felesh hands work to the right team based on each team's description.
From an invite to a team.
Five steps, in this order.
- 1 Invite
Invite your people.
Their email addresses, a role, and a team if you want one.
- 2 Pending
See who has not joined.
Invited people show as Pending. Resend the invitation, or revoke it.
- 3 Roles
Owner, admin or operator.
Each person has one role. An invitation cannot make someone an owner.
- 4 Team
Group them.
Create a team and add members to it.
- 5 Describe
Say what work should reach it.
One sentence on what the team handles. A team without a description gets no work from Felesh.
Where this does the most.
Sarah starts on Monday and should handle questions about orders. You invite her as an operator on the Support team, whose description says it covers orders and deliveries.
Invited · OperatorSee the playbook →Two new agents join, and a Front desk team has no description yet. The team list says Felesh can't send it work until you describe it. One sentence fixes that.
Team · needs a descriptionSee the playbook →Alex has not accepted the invitation yet. He shows as Pending. Resend the invite, or revoke it if it went to the wrong address.
Pending · resend or revokeSee the playbook →What the team page does not do.
And what happens instead.
- It does notIt does not make an invited person an owner.InsteadAn invitation gives an operator or an admin role. Ownership stays with you.
- It does notIt does not tailor permissions person by person.InsteadEach person has one of the roles that come with Felesh.
- It does notIt does not route every chat to a team.InsteadWork finds a team by its description. A team with no description receives none.
- It does notIt does not watch what people do.InsteadThe list shows who is on the team, their role and whether they have joined.
Which roles are there?
Owner, admin, operator and member. You invite people as an operator or an admin. In the panel, plans, billing, automations and boards are visible to the owner only.
Can I invite several people at once?
Yes. Type several email addresses, choose a role and a team, and send. People who are already members are counted as such rather than invited twice.
What does a team description do?
It tells Felesh what that team handles, so work can be handed to the right one. A team with no description cannot be sent work.
Can I add someone to a team later?
Yes. Open the team and add a member at any time.
Can I ask Felesh in chat to invite someone?
No. Invitations and teams are managed on the Operators and teams page.
Hand it the work. Keep the decisions.
Hand Felesh the work you've been carrying?14 days free, no card. Everything that needs your call still waits for your yes.