Google Business Profile

On the Google side sits a verified Google Business Profile: one listing per physical location, held under a business account, carrying the name, category, address, hours, photos, attributes, the review stream, the question-and-answer section, local posts, and the messaging feature that lets a searcher start a chat straight from the map or search results. Access is granted per location or per location group, with roles that determine whether a connected tool may read, reply or edit.

On the AppBO side sit the conversation inbox, the contact record, the reputation or reviews area, and workflows that can request a review after a job is completed and respond when one arrives. Connected, a message from someone looking at the map appears in the same inbox as an SMS, and a new one-star review becomes an internal alert and a task rather than something somebody notices two weeks later.

The point of wiring this up is that local search is where intent is highest and patience is lowest. Someone messaging a profile is usually comparing two or three nearby businesses right now, and the one who answers first wins the job. Reviews are the other half: the volume and recency of reviews feed local ranking, and a systematic request-and-respond loop built into the workflow that already knows when a job finished is far more reliable than asking staff to remember.

1. Confirm the profile is verified. An unverified listing cannot be managed by a connected tool, and verification can require a postcard, a video call or a document check depending on the business type: start it well before you need the integration.
2. Confirm ownership. The business should hold the primary owner role on its own Google account, with the agency or manager added as a manager rather than the other way round. A profile owned by a former contractor is a problem to solve now, not later.
3. Check the Google account you will connect has the right role on every location you intend to manage. A manager can usually reply to reviews and messages; editing some profile fields may need owner access. Verify what your role permits before assuming the integration is broken.
4. Tidy the profile before connecting: correct categories, accurate hours including holiday hours, a service area if relevant, and a phone number that rings somewhere answered. The integration surfaces what is there; it does not fix it.
5. Decide which phone number appears on the profile. Using a platform-provisioned number lets you attribute calls from local search, but changing the primary number on an established profile can briefly affect ranking signals, so consider using a secondary number or accept the trade-off deliberately.
6. In the sub-account, open the integrations area and start the Google Business Profile connection.
7. Complete Google's OAuth consent screen signed in as the account that holds access to the locations. Read the permissions on the dialog itself rather than assuming scope names.
8. Select the locations to manage. A multi-location business must select each one, or map each location to the sub-account that handles it; one sub-account per location is the cleaner pattern for an agency.
9. Enable messaging on the profile and confirm it is switched on for the locations you selected. Messaging has its own setting in Google's interface and can be disabled per location.
10. Set a welcome message and the response-time expectation. Google surfaces responsiveness to searchers, and an unanswered chat is visible in a way an unanswered email is not.
11. Configure where messages land: which inbox, which users are notified, and what happens outside business hours.
12. Import the existing reviews if the platform offers it, so your reputation view starts complete rather than from today.
13. Build the review-request workflow. Trigger it on the event that genuinely means the work is done (an appointment marked complete, an invoice paid, a pipeline stage reached) and send a short message with the direct review link. Respect a cool-down so the same contact is never asked twice.
14. Build the review-response workflow: notify the owner on any new review, raise a task for anything below a threshold you choose, and keep a short library of reply drafts for the common cases.
15. Verify messaging: from a personal Google account, message the profile from search or maps, confirm it arrives in the inbox attached to a contact, and reply from the platform to confirm the reply reaches the sender.
16. Verify reviews: confirm existing reviews are visible in the platform, then confirm a reply posted from the platform appears publicly on the profile.
17. Verify the request link by sending yourself a review request and checking the link opens the correct location's review dialog.
18. Document which Google account authorized the connection, which locations are mapped to which sub-accounts, and who holds owner rights on the profile.

Google to the platform

• Inbound messages from searchers, with the sender's display name and Google-scoped identifier, creating or attaching to a contact.
• New reviews, with star rating, review text, reviewer display name and timestamp.
• Edits and deletions of existing reviews, where surfaced.
• Existing review history at connection time, where the platform imports it.
• The list of locations the connected account can manage, with their names and identifiers.
• Questions posted to the profile's question-and-answer section, where the platform supports that stream.

Platform to Google

• Replies to messages, sent from the inbox into the searcher's chat.
• Public replies to reviews, posted as the business owner.
• Local posts and offers, where the platform offers publishing.
• Profile field updates such as hours or description, where the connected role permits and the platform exposes them.
• Photos uploaded to the listing, where supported.

What does not move

• The reviewer's email address or phone number. Google provides a display name only, so a review cannot be matched to a contact with certainty.
• Star ratings as a writable value. You cannot change, hide or remove a review through any integration; you may only reply or flag it in Google's own interface.
• Search ranking, impressions and the insights Google reports on its own dashboard, beyond anything the platform explicitly pulls.
• Reviews from other platforms. A third-party review site is a separate integration.
• Verification status and the verification process itself.
• Google Ads data. Local search performance is not ad performance, and the two integrations are separate.
• Call logs for calls placed from the profile, unless the profile's number is a platform number, which is the whole reason to consider using one.

Scenario: a plumbing company answers a map-based inquiry, completes the job, earns a review, and handles a bad one properly.

1. The company's profile is verified and the owner holds the primary owner role. The office manager's Google account, a manager on the location, authorizes the connection.
2. Messaging is enabled on the location, with a welcome message saying the team usually replies within the hour, and the inbox is set to notify the two office staff.
3. A householder with a leaking tap searches locally, sees the profile, and taps the message button asking whether anyone can come today.
4. The message lands in the shared inbox within seconds and notifies both staff. A contact is created carrying her Google display name and the chat thread, but no phone number or email yet.
5. The office manager replies from the platform asking for a ZIP code and a phone number. The householder supplies both in the chat.
6. The staff member adds those details to the contact record, which makes the record reachable on every other channel, and books an afternoon appointment.
7. An engineer attends, fixes the tap, and marks the appointment complete on his phone.
8. A workflow triggered by the completed appointment waits two hours, then sends a text with the direct review link for that specific location, and a cool-down tag so she will not be asked again for twelve months.
9. She leaves a five-star review that evening. The review arrives in the platform, notifies the owner, and a workflow raises a quick task to reply.
10. The office manager posts a short public reply from the platform, which appears on the profile under the business name.
11. Two weeks later a different customer leaves a two-star review complaining that the engineer arrived outside the quoted window. The low-rating branch of the workflow fires: the owner is alerted immediately and a task is created with a one-hour due time.
12. The owner matches the reviewer's display name against recent jobs, finds the appointment, sees the engineer was delayed on a previous call, and replies publicly acknowledging it and offering to make it right offline.
13. She also telephones the customer, resolves it, and records the conversation as a note on the contact. The review stays as it is (nothing in the integration can remove it) but the public reply is now the first thing a future searcher reads underneath it.
14. At the end of the quarter the team compares review volume against job completions and finds a gap, traced to jobs closed without the appointment being marked complete, so the workflow trigger is widened to include the invoice-paid event.

Rate limiting

Google's Business Profile APIs carry per-project quotas, and reading reviews across many locations is the operation most likely to hit them; an agency managing dozens of listings from one connection feels this long before a single-location business does. Google publishes current quotas in its API documentation and surfaces usage in the Cloud console. The symptom is stale data rather than an error anybody sees: reviews appear hours late, which undermines the whole point of alerting on a bad one.

Retries and idempotency

Review and message events can arrive more than once, so dedupe on the review or message identifier before notifying anyone. A duplicated one-star alert at seven in the morning erodes trust in the alerting quickly. Review replies are an update rather than an insert: posting again replaces the existing reply rather than adding a second, which is forgiving, but a workflow that posts an automated reply and then a human reply will overwrite the human one. Decide which is authoritative.

Field-mapping traps

The reviewer's display name is the only identity you get, and it is often a first name, a nickname or nothing at all, so any attempt to match reviews to contacts automatically will mis-match. Treat the match as a human judgment. Review links are per location: a multi-location business that sends one link for all sites will collect every review on one listing, which is both wrong and hard to undo. Business hours have their own format and holiday hours are a separate structure, pushing hours updates without handling that distinction is how a profile ends up showing closed on a trading day.

Duplicate creation

Duplicate contacts are the norm here, because a message from search carries no email or phone. The same person may already exist as a contact from a form, and there is no reliable key to match them. The practical approach is to capture a phone number or email early in the chat, then merge. Duplicate listings are the other hazard: a business with two profiles for one location splits its reviews and its ranking, and that must be resolved in Google rather than in the platform.

Sandbox versus live

There is no sandbox. Everything you test is public: a test reply appears under a real review, and a test local post appears on a real listing. Use your own Google account as the test customer, write test replies you would be content for anyone to read, and remove test posts afterwards.

Authentication expiry

The connection depends on the authorizing Google account keeping its role on the location. It breaks when that person's access is removed, when ownership is transferred, when the password changes or the grant is revoked, and when a profile is suspended, which happens over category or name-policy issues and takes the messaging and review streams with it. Because the symptom is an absence of events, monitor for the absence: if no review or message has arrived in a period where you would expect one, check the connection before concluding business is quiet.

What commonly breaks

• Messaging left disabled on the location, so the inbox is simply never used.
• Unanswered chats, which Google reflects in the responsiveness shown to searchers.
• A single review link used across several locations.
• Review requests sent before the work is finished, because the workflow trigger fires at booking rather than completion.
• The same customer asked for a review repeatedly, with no cool-down tag.
• Automated review replies that read as automated, which does more damage than no reply.
• Incentivized or gated review requests, which breach Google's policies and risk the listing.
• A profile suspended after a name or category change made to chase ranking.
• The agency holding owner rights, leaving the client unable to reconnect after a relationship ends.
• A profile phone number swapped for a tracking number without considering the effect on an established listing's signals.