How to move client chats off personal phones

Imagine a five-person remodeling company. The owner gave her cell number to the first fifty customers. Two project managers text clients from their own phones, and the estimator uses WhatsApp on his. It works, mostly. Then the estimator leaves for another job. Three active quotes and a year of photos, measurements and “can you also look at the deck?” messages leave with him.

This guide is for teams in that situation. It walks through moving customer conversations from personal phones to business numbers the team shares, in a way customers barely notice.

Why move conversations off personal phones

Personal phones are a natural place to start. They become a problem as the team grows:

• The business doesn’t own the relationship. When an employee leaves, their customer conversations and contacts go with them.
• Nobody else can see the thread. If a rep is sick, on vacation or with another customer, a new message just waits.
• There’s no record. Quotes, promises and photos sit in chat history that the business can’t search or back up.
• Compliance is harder. Opt-outs, consent and quiet hours are tracked in each person’s head, if at all. Our overview of US business texting compliance explains why that matters.
• Staff never get off work. Customers learn they can reach someone directly at 10 p.m. on a Sunday.
• Mixed personal and business data. Customer photos sit next to family photos, and personal chats sit next to client chats on a device the business doesn’t manage.

The goal is a shared business number (or a few) where conversations belong to the business, each thread has a clear owner, and history stays when people change roles.

Step 1: Inventory every number customers use

Start by listing every number and channel customers use to reach your team today. Ask each team member to fill in a row, and be clear that this isn’t about blame.

For each number, also note where it appears publicly: website, Google listing, vehicle wraps, business cards, invoices, quote templates, email signatures and social profiles. You’ll need that list later.

Step 2: Decide your target setup

Most small teams end up with one of these patterns:

Whatever you pick, the important part isn’t the number. It’s that conversations land in a place where the team can see them and ownership is clear. A unified inbox that combines your channels, plus simple conversation assignment rules, does that job.

Step 3: Port an existing number or get a new one

For each number in your inventory, decide whether to keep it (by porting it to a business provider) or replace it.

Porting in general terms

Porting moves an existing phone number from one carrier or provider to another. In the US, you generally can port a number you control, and the process typically involves:

1. Confirming the new provider can accept the number for the use you need (for example, business texting).
2. Getting the current account details: account number, PIN or passcode and the name and address on the account.
3. Submitting a port request through the new provider, often with a letter of authorization and a recent bill.
4. Waiting for the port to complete, which can take from days to a few weeks depending on the carriers and number type.

Things to check before porting:

• Who legally controls the number? If it’s on an employee’s personal plan, it’s their number. You can ask them to transfer it, but you can’t port it without their account authorization. Get any agreement in writing.
• Texting may need separate setup. A ported number isn’t automatically ready for business texting. Plan for 10DLC registration or toll-free verification, which can take time on its own.
• WhatsApp is separate from the carrier. Moving the number’s carrier doesn’t move a WhatsApp account. If a number is used for WhatsApp, check how to move it to a business account; our WhatsApp guide covers the app and the Business Platform.
• Don’t cancel the old service first. Canceling before the port completes can release the number.

When a new number is better

A new number is often the cleaner choice when:

• The number belongs to an employee who wants to keep it
• The number is mixed heavily with personal use
• The number is on a plan that’s hard to port
• Few customers know it, and it doesn’t appear on printed materials

If you go with a new number, choose one with a local area code your customers recognize, and register it for business texting before you announce it.

Step 4: Tell customers

Customers should hear about the change from the person they already know, in plain language. Send the announcement from the old number, then follow up from the new number so they can save it.

Announcement from the old number:

Hi Dana, it’s Marcus from Brightline Remodeling. We’re moving all project messages to our team number, (555) 010-0100, so someone can always answer, even when I’m on site. I’m still your project manager. Please text that number from now on. I’ll send a hello from it today so you can save it.

First message from the new number:

Hi Dana, this is Brightline Remodeling’s team line. Marcus is still your project manager, and he’ll see your messages here. Save this number as “Brightline Remodeling.” Reply STOP if you don’t want texts from this number.

For customers you haven’t spoken to in a long time, you may not need to send anything. Update your public listings, and let the old number’s auto-reply handle anyone who reaches out.

Sending an announcement to many people at once is outbound messaging. Make sure it fits your consent and texting rules, and send it from properly registered numbers.

Step 5: Run a transition window

You won’t move everyone in a day. Plan a transition window, often a few weeks, during which the old numbers stay active but point people to the new one.

1. Set an auto-reply on old numbers where the phone or app allows it:

   Thanks for your message. Brightline Remodeling now uses (555) 010-0100 for all customer messages so the whole team can help. Please text us there.

2. Forward or copy new conversations. When a customer writes to an old number, the person who receives it moves the conversation: reply once pointing to the new number, then start the thread from the business number.

3. Update public listings in one pass: website, Google listing, social profiles, email signatures, quote and invoice templates.

4. Reprint what’s cheap to reprint, such as business cards, and schedule the rest, such as vehicle wraps.

5. Track stragglers. Keep a short list of customers who keep using old numbers, and remind them personally.

6. Set an end date. After it, old numbers stop being used for business. For employee-owned numbers, that’s the date the employee can stop responding to customers on it.

Step 6: Preserve conversation history

History is the part most teams worry about. Be honest with yourself here: chat history usually can’t be moved from a personal phone into another system in a complete, structured way. Plan for “good enough,” which normally means a mix of exports and summaries.

Export where possible

• WhatsApp: individual chats can be exported from the app (with or without media) as a text file. That’s useful as an archive, but it doesn’t become a live conversation in another system.
• SMS: phones don’t have a simple built-in SMS export for business use. Third-party backup apps exist; check their privacy terms before using them with customer data.
• Photos and documents: save project photos, measurements and signed documents to the business’s file storage, organized by customer.

Store exports somewhere the business controls, with access limited to the people who need them.

Write summary notes for active customers

For every active customer, the person who owns the relationship writes a short summary note that goes on the customer’s record in your CRM or shared system:

Summary of chats on Marcus’s phone, Jan–Oct 2026. Kitchen remodel, quote #1042 accepted Aug 12. Customer prefers texts after 5 p.m. Asked about a deck estimate for spring. Cabinet color change approved by text Sept 3 (screenshot saved to project folder). No open issues.

A good summary covers:

1. What the customer bought or is considering
2. Any commitments made in chat: prices, dates, changes
3. Preferences: best time to reach them, preferred channel
4. Open questions or follow-ups
5. Where the exported files are saved

Prioritize customers with open deals or active projects. Inactive customers can get a one-line note, or none.

Step 7: Set a policy for staff devices

Write a short policy so the change sticks. Keep it to one page. It should cover:

• Where customer conversations happen: only on business numbers and in the shared system
• Personal numbers: not given to customers; if a customer has one, redirect them politely
• Business apps on personal phones: if staff use their own phones to access business tools, say what’s allowed, how access is protected (screen lock, app login) and what happens when they leave
• Customer data: no saving customer photos or files to personal galleries or cloud accounts
• After hours: who covers messages outside business hours, and that others aren’t expected to reply
• Leaving the company: access removed on the last day; no business conversations continue from personal accounts

Talk the policy through with the team before you publish it. Explain the benefit to them: they can switch off at night, and someone else can cover when they’re out.

Step 8: Make ownership clear on the new number

Moving to a shared number without ownership rules can make things worse: now five people can see a message, and each assumes someone else will answer. Before go-live, agree on:

1. Who’s assigned new conversations, and how (by territory, by rotation or by the person on shift)
2. How existing customers stay with the person they know
3. A first-response target during business hours
4. How to hand a conversation to someone else, with an internal note explaining the context

Our article on shared inbox ownership rules has a fuller set.

Transition checklist

• Every customer-facing number listed, with owner and public locations
• Target setup chosen: one main number, numbers by team, or main plus WhatsApp
• Port or new number decided for each line; written agreement for any employee-owned number
• New numbers registered for business texting (and set up on WhatsApp if used)
• Announcement messages written and sent from old and new numbers
• Auto-replies set on old numbers
• Website, listings, signatures and templates updated
• Active customers’ history exported and summarized
• Staff device policy written and shared
• Ownership and response rules agreed
• Transition end date set and communicated

Where inChat fits

inChat is a conversation-first CRM in development for small teams. It’s designed around a shared business number: messages arrive in one unified inbox, each conversation has an owner, and history stays on the customer’s record. WhatsApp and SMS are planned launch channels. If you’re planning this kind of move, you can join early access to follow along.