helpdashBuild the team around the work.
Invite people, create agent groups and define roles. Make access match responsibility, from an agent answering requests to the admin configuring the workspace.
Members · Agent groups · Roles · Permissions Workspaces & teams
One team. Plenty of ways to organise it.
Your products, customers and responsibilities are not all the same. Give them a structure that makes sense, with the right identity and the right access.
FFieldworkClient services
Customer supportAgent group
Alex MorganAdmin
Maya ChenAgent
Made for the work behind the answer
Keep the work connected. Keep the boundaries clear.
Give each brand its own introduction.
Configure brand identity, support sender details, signatures and portal hosts. Associate requests with the right brand so the customer sees the identity they recognise.
Multiple brands · Sender identity · Portal settingsOrganise the details that matter.
Use projects and ticket configuration to reflect your product lines. Set your workspace timezone and working calendar so the support operation follows your business hours.
Projects · Ticket configuration · Business hoursA few good
questions.
Are brands the same as separate workspaces?
No. Brands are customer-facing identities within a workspace. Separate workspaces have their own tenant context; choose the boundary that matches your operation.
Can team members have different access?
Yes. Roles and granular permissions control access to product areas and actions. Agent groups separately organise ownership and routing.
Can we use our own company identity?
Workspace and brand settings support identity details such as company name, brand colour, logo, sender name and support signature.
Part of a bigger picture.
Bring the rest of your support work along.