People · departments · accountability
Teams, Departments, and Organization
Give every conversation a clear home and every teammate a clear role. Organize people, departments, and business numbers while keeping customer context and accountability visible.
Read the full explanationIllustrative example · not live controls or data
Customer conversation
Fictional example · shared context
Alex Rivera
Illustrative teammate · assigned owner
Clear ownership. Context that stays with the work.
Seven parts of a thoughtful team structure
Agent roles
Make responsibility easier to see.
Define permissions around each person's responsibilities, from replying to assigned conversations to overseeing teams and campaigns. Role-based access keeps sensitive data and actions limited; no role overrides customer consent.
Illustrative example · not live controls or data
Responsibility shapes access
Role names are examples only
Agent
Work with assigned conversations
Supervisor
Support team oversight
Administrator
Manage organizational setup
Compliance Officer
Review relevant activity
Illustrative role concepts—not a verified list of account controls or permissions. A role does not override customer consent.
Agent skills and languages
Put the right context near the conversation.
Tag agents with skills and languages to match conversations with appropriate expertise. Halo can assist with knowledge-grounded drafts, while teammates review suggested replies before sending.
Illustrative example · not live controls or data
A more informed handoff
Illustrative matching context
A customer asks a detailed billing question.
Matching helps find an appropriate person; it does not promise automatic translation.
Department management
Give each kind of work a place.
Organize Sales, Support, or Billing into departmental queues. Claim and transfer conversations without losing context, with department-level visibility keeping campaigns and automations relevant to each team's work.
Illustrative example · not live controls or data
Work has a clear home
Illustrative department map
Sales
Team · example
Support
Team · example
Billing
Team · example
Field service
Team · example
A conversation can move from one department to another without losing its history.
Department phone-number assignment
Keep the familiar number in the picture.
Assign local, verified toll-free, or compatible existing business numbers to departments. Each team works from the appropriate line while managers retain shared visibility.
Illustrative example · not live controls or data
A recognizable way in
Illustrative number-to-team map
Main business line
Support · example assignment
Local business line
Regional sales · example assignment
Number examples show organization concepts, not a live routing or provisioning screen.
Multiple locations or business units
Local teams, with the wider picture.
Give regional offices, franchise locations, or business units their own teams and numbers. Organization-wide analytics bring their activity together while local teams retain their working context.
Illustrative example · not live controls or data
Distinct teams, shared view
Illustrative organization structure
Northstar Group
Organization-wide visibility · example
Harbor location
Own team · own context
Cedar location
Own team · own context
Keep local work distinct while retaining a broader organizational view.
Audit history
Leave a clear trail of changes.
An organizational audit trail can show when a change happened and who made it, helping teams review role, department, routing, or security changes with useful context.
Illustrative example · not live controls or data
Changes with context
Illustrative audit history
Role updated
Jordan Kim · Administrator
Example timestamp · 10:42 AM
Team assignment changed
Riley Park · Supervisor
Example timestamp · 10:42 AM
Number routing reviewed
Jordan Kim · Administrator
Example timestamp · 10:42 AM
A useful trail shows who changed what and when; this example makes no compliance guarantee.
Integration and security setup
Keep access aligned with approval.
Control who can access customer data, update approved knowledge, and create campaigns. Role-based permissions and managed credentials keep access tied to authorized people and applications.
Illustrative example · not live controls or data
Approved access, clear boundaries
Illustrative access concepts
Authorized people
Access aligned to assigned responsibility
Approved knowledge
Changes limited to people with approval
Campaign creation
Audience and sending access considered
Enterprise access concepts
SSO and API keys are examples of concepts, not confirmation of named providers or available integrations.
Human review here refers to Halo reply suggestions; it does not imply Auto-Pilot is disabled.
Structure for shared messaging
Keep the team visible. Keep the customer in context.
Give people and conversations a clearer place to belong as your messaging work grows.
Examples illustrate organizational concepts, not account controls.