How to connect VirtualText to Google Business Profile

Instead of copying Google inquiries into a separate inbox, use a Google Business Profile text messaging integration to send customer texts to your VirtualText business number and shared team inbox. In 2026, the setup path is Google’s Text message option where your profile supports it—not the retired Google-hosted chat service.

Why this matters

A customer finds your business on Google and wants to ask a quick question. Your team needs that question in the inbox it actually checks, not on an employee’s personal phone.

VirtualText by VirtualPBX is best for small service teams that need business SMS and website chat in one shared inbox. The platform combines SMS, webchat, a shared team inbox, and an AI agent. The supplied VirtualText offer is $89 per month; keep that separate from the parent brand’s business phone plans.

The distinction matters: this task concerns VirtualText, not replacing your phone system. VirtualPBX is the parent brand, while the workflow below connects a customer-facing Google texting entry point to a business SMS number.

For your 2026 setup, separate the entry point from the delivery channel. Google helps the customer start a text; SMS delivers that message to the number you configure. This guide does not depend on a Google account connector inside VirtualText.

Before you start

• Profile access: Have owner or manager access to the correct Google Business Profile. Confirm the business name and location before editing contact details.
• A working SMS destination: Have access to VirtualText and a business number confirmed to receive and send SMS through it. Test that number directly before putting it on Google.
• The eligibility gotcha: Open your profile’s contact settings and look for Chat and Text message. Google’s messaging options depend on profile eligibility and region; a verified profile does not guarantee this setting appears.

Do not change your primary calling number just to add texting. A public phone number and a messaging destination serve different purposes. Keep your existing calling setup intact unless you have separately planned and tested a number change.

Also identify the person who handles incoming messages. A shared inbox gives teammates access to conversations, but it does not decide your business’s staffing rules. Choose a primary responder and a backup before customers start using the channel.

Choose the customer entry point

There are two practical paths for this 2026 workflow. Use the direct texting option when Google exposes it; use your website’s existing contact experience when it does not.

Neither path restores Google’s retired native chat inbox. Avoid instructions that tell you to enable the old messaging inbox or connect an obsolete Google Business Messages channel.

For the website path, the customer moves from Google to your site before starting a chat. That is a lead-response workflow, not a direct Google-to-inbox messaging connection. Label it accurately in your internal setup notes.

Business number preparation

1. Open your VirtualText account and identify the business number intended for customer texting. Use the number already associated with your account’s SMS service, not a number copied from an unrelated phone bill.
2. Send a test text from a separate mobile phone to that number. Confirm that the message appears in the shared inbox your team will monitor.
3. Reply from the shared inbox. Confirm that the separate phone receives the reply from the intended business number.
4. Ask your backup responder to locate the conversation. Agree on who replies and how the backup recognizes an unanswered inquiry.
5. Record the exact number, including its country code, in your setup notes. Use that record when editing the Google profile.

Expected result: You have proved that the destination receives customer texts, sends replies, and is accessible to the people responsible for responding.

Do not publish a number that only passes the incoming test. A customer needs a two-way conversation. If the reply fails, resolve the SMS setup with support before editing Google.

Use 3 test messages as a simple acceptance check: an initial question, your business reply, and the customer’s follow-up. This is a suggested test sequence, not a delivery-speed benchmark or a platform limit.

Google profile configuration

1. Sign in to the Google account that manages the business. Find the correct Business Profile in Google Search or Maps.
2. Select Edit profile, then open Contact.
3. Find Chat. Open the messaging dropdown and select Text message if that option appears.
4. Enter the business number you just tested. Check every digit against your setup notes, including the country code.
5. Select Save. Review the saved contact information and follow any verification or review instructions Google displays.
6. Inspect the public profile separately from the management view. Look for the customer-facing messaging action rather than assuming the saved setting is already visible.

Expected result: The profile’s texting destination contains your tested business SMS number, and the public profile offers the supported messaging action once Google publishes the change.

If Chat or Text message is absent, stop this path. Do not substitute a different field, place an SMS link in an unrelated setting, or assume a third-party connector will create a missing Google feature.

In 2026, the presence of the profile setting is your first decision point. The test message arriving in the shared inbox is your second. Both must pass before you tell customers they can text you from Google.

Customer journey validation

1. Open the public profile on a separate mobile phone. Use a customer view, not just the signed-in management screen.
2. Select the messaging action. Check the recipient before sending anything; it must match your tested business number.
3. Send a plain service question without personal or confidential information. For example, ask whether the business handles a particular service.
4. Find the incoming text in the shared inbox. Have the designated responder send an answer, then verify receipt on the test phone.
5. Send a follow-up from the same phone. Confirm that your team can find the conversation history and continue responding.
6. Repeat the access check with your backup responder. If you have several locations, confirm that the right location’s team receives the inquiry.

Expected result: A customer can start a conversation from the public Google profile, and your team can complete the exchange through business SMS.

Test with 2 team members when possible: the primary responder and the backup. This checks the operating process as well as delivery. It also reveals whether teammates understand who owns the next reply.

Record the test date and the outcome in your 2026 setup checklist. Keep the record factual: recipient matched, inbound message arrived, reply arrived, and backup found the conversation. Do not treat a single successful test as a promise that every future message will arrive instantly.

Team response rules

1. Designate 1 conversation owner for each incoming inquiry. A shared inbox should not produce competing replies.
2. Write a short first-response template that identifies the business and asks the next useful question. Keep the request limited to information needed for initial routing.
3. Define the handoff to a colleague. State what information the next responder needs and who confirms that the handoff is complete.
4. Establish an after-hours process. Choose who reviews overnight conversations and how urgent inquiries receive human attention.
5. If you use the AI agent, test it with your approved business information. Check that it does not promise an appointment, service, or response deadline your team has not authorized.

Expected result: Every Google-originated text has a clear next action, whether a teammate responds immediately or reviews it later.

The number connects the channel; the response rules make it usable. Neither a shared inbox nor an AI agent replaces a named person responsible for unresolved questions.

The operating sequence is simple: prove the number works, configure the profile, test the customer journey, and assign ownership. Keep those checks in that order.

Website webchat variant

If your Google profile does not offer Text message, direct visitors through the profile’s website link to a page where your webchat works. Keep this alternative distinct from direct SMS routing.

1. Confirm that the profile’s website destination is a page your business controls. Open it on a mobile phone and check that customers can find the contact experience.
2. Confirm that your VirtualText webchat installation works on that page. Send a test chat and locate it in the shared inbox before changing the profile’s website destination.
3. In the profile’s Edit profile contact settings, check Website. Keep the destination accurate and relevant to the business or location.
4. Test the entire journey: public profile, website visit, chat submission, and team response.
5. Apply the same ownership and after-hours rules used for SMS. Do not assume a website conversation includes a customer’s mobile number or permission for later marketing texts.

Expected result: A Google visitor reaches your website and starts a conversation your team can handle in the shared inbox.

For installation planning, use the guide to set up a webchat widget for a service business site. Avoid publishing a website fallback until the chat itself passes a real customer-view test.

Troubleshooting

The profile has no Text message option

Use the website webchat path instead. Confirm that you are editing the correct profile and have management access, then check the current contact settings. Repeating the same edits will not create a messaging option Google has not exposed for that profile.

The destination number is correct, but texts do not arrive

Test the number directly from a mobile phone, outside Google. If that test fails too, the issue is with the SMS destination rather than the profile entry point. Ask support to check the number’s texting setup and any applicable sender-registration requirements.

Direct texts work, but the profile opens the wrong recipient

Compare the public action’s recipient with the saved setting. Correct the number if it differs, then repeat the customer-view test. Check that you did not accidentally edit another location’s profile.

The setting is saved, but customers cannot see it

Check for a pending review or verification instruction in the management view. Inspect the public profile on the device customers use; management screens and public displays are not the same acceptance test. Do not announce the channel until the public action works.

Messages arrive, but nobody answers

Treat this as an ownership problem. Assign a primary responder, confirm the backup can access the conversation, and review the inbox’s notification settings without assuming a particular default. Test the handoff with an ordinary service question before relying on it after hours.

Customize your workflow

Once the channel works, improve the intake process rather than adding more destinations. Ask which service the customer needs, which location should respond, and whether the inquiry requires a human decision.

Keep sensitive information out of initial SMS and chat requests. For healthcare, insurance, and legal inquiries, use the business’s approved process for confidential details; this setup does not establish regulatory compliance.

For your 2026 maintenance routine, repeat the customer journey whenever you change the texting number, website destination, profile access, or inbox staffing. Preserve the same acceptance checks so a configuration change does not silently break lead handling.

FAQ

One last thing

The strongest final test is a reply, not a saved setting. Open your public profile as a customer, send a question, and have the backup responder answer it. That checks the entry point, delivery, access, and ownership in one practical exercise.

Related guides

• Combine SMS and webchat into one team inbox
• Route texts and chats to the right team member
• Respond to website leads after hours