K

Personas for Team Roles and Shared Lines

How to use Phound personas for team-based communication and shared phone lines.

Personas for Team Roles and Shared Lines

Phound personas are not limited to individuals. Teams and small businesses can use them to create role-based phone lines that belong to a function rather than a single person. A "Customer Support" persona, a "Sales" persona, or an "On-Call" persona gives your team a stable, recognizable phone number that stays the same regardless of who is behind it on any given day.

This guide covers how to set up personas for team roles, manage shared lines across multiple team members, and hand off responsibility smoothly.

Why Use Personas for Teams?

In a small business, phone numbers often get tied to individual employees. The support line is Sarah's cell phone. The sales number is Mike's personal line. This works until Sarah goes on vacation or Mike leaves the company, and suddenly customers cannot reach anyone.

Persona-based team lines solve this by decoupling the phone number from the person:

  • Continuity. The number stays active even when individual team members change. Customers never need to learn a new number.
  • Professional image. Callers hear a department-appropriate voicemail greeting instead of a personal one.
  • Accountability. Call logs and message histories are attached to the role, not the person, making it easy to review what happened and when.
  • Clean handoffs. When someone finishes their shift or leaves the team, the persona transfers seamlessly to the next person.

Setting Up a Team Persona

Creating a team persona follows the same steps as creating any persona in Phound. If you need a refresher, see How to Create a New Persona. Below are recommendations specific to team and role-based use.

Naming the Persona

Name the persona after the role or department, not the individual. Good examples:

  • Customer Support
  • Sales Team
  • On-Call Tech
  • Front Desk
  • Billing Department

This makes it clear to anyone using the persona what it represents, and the caller ID displays the role name rather than a person's name.

Choosing a Number

For team personas, consider these number strategies:

  • Local numbers work well for businesses that serve a specific geographic area. Customers see a familiar area code.
  • Toll-free numbers suit businesses with a national presence and give a polished, established impression.
  • Vanity numbers (like 1-800-HELP-NOW) are memorable for customer-facing roles, though availability varies.

See Choosing a Phone Number for more guidance on selecting the right type.

Recording the Voicemail Greeting

Team voicemail greetings should reference the role, not a specific person:

  • "You have reached the customer support line for Acme Co. Our team is currently unavailable, but please leave a message and we will return your call within two hours."
  • "Thank you for calling Acme Co. Sales. All of our representatives are assisting other customers. Please leave your name and number and someone will get back to you shortly."

Avoid including a specific person's name in the greeting. When team members rotate, you do not want to re-record the voicemail every time.

Tip: Use Phound's text-to-speech feature for team voicemail greetings. It provides a consistent, neutral voice that does not change when team members rotate, and you can update the script instantly without needing someone to record a new message.

Common Team Persona Setups

Support Line Persona

A support line persona is one of the most common team setups. Here is a typical configuration:

Setting Recommended Value
Persona Name Customer Support
Number Type Toll-free or local
Voicemail Greeting Reference "support team," include expected response time
Business Hours Match your support hours (e.g., Mon-Fri 8 a.m. - 6 p.m.)
Auto-Response "Thanks for reaching out. A support team member will respond within 2 hours during business hours."

With this setup, customers have a single number to call or text for help. Whoever is on support duty that day logs into the persona and handles incoming communications.

Sales Persona

A sales persona helps your sales team present a unified front:

Setting Recommended Value
Persona Name Acme Sales
Number Type Toll-free for national reach
Voicemail Greeting Energetic but professional, mention callback timeframe
Business Hours Extended hours if your sales team works evenings
Auto-Response "Hi! Thanks for your interest in Acme. A member of our sales team will be in touch shortly."

Tip: Enable SMS on your sales persona so prospects can text their inquiries. Many people prefer texting over calling, especially for initial inquiries. This small addition can increase your lead capture rate. For more on messaging features, see Auto-Responses.

On-Call Persona

For teams that provide after-hours or emergency coverage, an on-call persona keeps the responsibility movable:

Setting Recommended Value
Persona Name On-Call Tech
Number Type Local
Voicemail Greeting "You have reached the on-call technician. Please leave a detailed message including your name and the nature of the issue."
Business Hours Disabled (always active during on-call shifts)
Auto-Response Disabled (on-call should answer live)

The on-call persona gets handed from one team member to the next at the end of each shift. The phone number never changes, so anyone who has it always reaches whoever is currently on duty.

How Shared Lines Work in Phound

A shared line in Phound is a persona that multiple team members can access and operate under. When a persona is shared, the team member who is currently active on it handles all incoming calls and texts through that persona's number. Here is how it works in practice.

Accessing a Shared Persona

Phound's team features allow an account administrator to grant persona access to specific team members. Once granted:

  1. The team member opens the Phound app and sees the shared persona in their persona switcher bar alongside their personal personas.
  2. Tapping the shared persona makes it active. Incoming calls and texts to that persona's number now ring on their device.
  3. Outgoing calls and texts sent while the persona is active use the persona's number and display its caller ID.

Multiple People, Same Persona

When multiple team members have access to the same persona, Phound handles routing based on which members are currently active:

  • One active member: All calls and texts go to that person.
  • Multiple active members: Phound rings all active members simultaneously. The first to answer takes the call. Text messages appear in all active members' inboxes, but only the first reply is sent (others see that the message has been handled).
  • No active members: Calls go to voicemail. Texts trigger the auto-response if one is configured.

Warning: If multiple team members are active on a shared persona and both attempt to reply to the same text message, only the first reply is delivered. The second member will see a notification that the message has already been answered. Coordinate with your team to avoid duplicate responses, especially during busy periods.

Handing Off Personas Between Team Members

One of the biggest advantages of team personas is the smooth handoff. When a shift ends or a team member goes on leave, the persona moves to the next person without any disruption to customers.

Shift-Based Handoff

For teams that operate in shifts (morning and afternoon support, for example):

  1. The outgoing team member opens the shared persona and taps Go Inactive (or simply switches to their personal persona).
  2. The incoming team member opens the shared persona and taps Go Active.
  3. All new calls and texts now route to the incoming member.

The handoff is instant. There is no downtime, no number change, and no customer impact.

Long-Term Handoff

When a team member leaves the company or moves to a different role:

  1. The account administrator opens Team Settings > Personas > [Persona Name] > Members.
  2. Remove the departing member from the persona's access list.
  3. Add the replacement member.
  4. The new member will see the persona appear in their switcher bar the next time they open the app.

All conversation history stays with the persona, giving the new team member full context on past interactions.

Tip: When handing off a persona to a new team member, have them review the persona's recent call log and message threads before going active. This helps them understand ongoing conversations and avoid asking customers to repeat themselves. See Exporting Call History if you need to share records outside of Phound.

Managing Team Persona Settings

Who Can Change Settings?

By default, only the account administrator can modify a shared persona's settings (name, number, voicemail greeting, business hours, etc.). Team members who have access to the persona can use it to make and receive calls but cannot alter its configuration.

If you want to allow certain team members to manage settings, the administrator can grant Persona Admin permission on a per-persona basis:

  1. Go to Team Settings > Personas > [Persona Name] > Permissions.
  2. Select the team member and toggle Persona Admin on.
  3. That member can now edit the persona's settings in addition to using it.

Reviewing Call and Message History

Because all activity on a shared persona is tied to the persona itself (not to individual team members), administrators and persona admins can review the full history at any time:

  • Call log: Shows every incoming and outgoing call, including duration, time, and which team member handled it.
  • Message threads: All text conversations are visible to anyone with access to the persona. This provides transparency and helps with quality assurance.
  • Export: Call logs and message histories can be exported as CSV files for record-keeping or compliance purposes. See Exporting Call History.

Best Practices for Team Personas

  1. Name personas after roles, not people. "Customer Support" is better than "Sarah's Support Line." Roles outlast individuals.
  2. Use text-to-speech for voicemail. It stays consistent when team members rotate and can be updated in seconds.
  3. Set clear handoff procedures. Document when and how team members should go active and inactive on shared personas. Even a simple "go active at 9 a.m., go inactive at 5 p.m." rule prevents gaps in coverage.
  4. Limit persona access. Only grant access to team members who need it. Fewer active users on a shared persona means fewer coordination issues.
  5. Enable auto-responses for gaps. If there is any risk of a period where no one is active on a shared persona, configure an auto-response so callers are not left in silence. See Auto-Responses.
  6. Review logs regularly. Use the shared persona's call and message logs to monitor response times, identify busy periods, and ensure quality.

Warning: Avoid giving every team member permanent active status on a shared persona. Simultaneous ringing across many devices creates confusion and increases the chance of dropped or duplicated responses. Designate specific active members per shift instead.

Plan Requirements for Team Features

Team persona features, including shared access, multi-member routing, and shared phone numbers, are available on Phound's Business plan at $18 per user per month (billed annually). If you are currently on the Basic (free) or Pro ($9.99/user/month) plan and want to use shared personas and team lines, visit Plans and Pricing to explore your upgrade options.


Still need help?

If you have questions about setting up team personas or managing shared lines, our support team is here for you. Visit Contact Support to get in touch by chat, email, or phone.

Was this helpful?

Still need help?

If you couldn't find what you were looking for, our support team is ready to assist. Contact Phound Support and we'll get back to you as soon as possible.