> [!NOTE]
> Choose whether to manage agents with the Business Communications [Developer
> Console](https://business-communications.cloud.google.com?utm_source=/business-communications/business-messages/guides/how-to/launch/locations&utm_medium=devsite&utm_campaign=business-messages) or [API](https://developers.google.com/business-communications/business-messages/reference/business-communications/rest). <button value="console" default="">Developer Console</button> <button value="api">API</button>

After you [verify
locations](https://developers.google.com/business-communications/business-messages/guides/how-to/verify)
and [launch the associated
agent](https://developers.google.com/business-communications/business-messages/guides/how-to/launch/agents),
it's time to launch locations. When you launch a location, you enable users to
have conversations with that location.

> [!CAUTION]
> **Caution:** After locations have been verified and associated with your Business Messages agent, only launch locations that you have permission to enable messaging for.

To edit allowed location entry points after verification,

contact us. (You must first [sign
in]() with a Business Messages Google account. To register for an account, see
[Register with Business
Messages](https://developers.google.com/business-communications/business-messages/guides/how-to/register).)


### Pre-launch checklist

Before you launch your location, use the following checklist to catch any issues
that might appear during the launch process.

| Location configuration |
|---|
| **Location verification** **Required.** Verification that the location belongs to the brand that the agent represents. See [Verify agents and locations](https://developers.google.com/business-communications/business-messages/guides/how-to/verify). |
| **Location-specific greeting** **Optional.** The welcome message and optional conversation starters that are unique to a location. Overrides the [agent-level greeting](https://developers.google.com/business-communications/business-messages/guides/how-to/agents/begin-conversation?method=api#agent-_and_location-level_settings). See [Begin the conversation](https://developers.google.com/business-communications/business-messages/guides/how-to/agents/begin-conversation). |
| **Location-specific offline message** **Optional.** A message that displays when a user starts a conversation outside of an agent's operating hours for that specific location. Overrides the agent-level offline message. See [Begin the conversation](https://developers.google.com/business-communications/business-messages/guides/how-to/agents/begin-conversation). |

| Infrastructure readiness |
|---|
| **Message routing is complete** **Required.** Your infrastructure is ready to route location-specific messages to a live agent or automation capable of responding to such messages. |

| Conversation readiness |
|---|
| **Live agents are available** **Required.** Live agents are ready to respond to user messages as soon as the location launches. |
| **Automation is complete and available** **Recommended.** Any automation you've developed or integrated with is complete and ready to handle user messages as soon as the location launches. |

## Supported entry points

Locations support [`LOCATION` entry
points](https://developers.google.com/business-communications/business-messages/guides/concepts/entry-point#location).

You need to [specify entry
points](https://developers.google.com/business-communications/business-messages/guides/how-to/locations#update-entry-points)
for each location before you verify or launch the location.

## Launch a verified location

When you launch a verified location, the location is available to users within a
few hours. Messages from users in conversations with locations include the
locations' `placeId`. See [Receive
messages](https://developers.google.com/business-communications/business-messages/guides/how-to/message/receive).

You should be ready to route messages based on `placeId` and respond to user
messages before you launch a location.

> [!CAUTION]
> **Caution:** If your agent doesn't meet minimum [performance
> thresholds](https://developers.google.com/business-communications/business-messages/guides/qa/metrics#performance), your agent may be suspended.

To launch a location,

1. Open the [Business Communications Developer
   Console](https://business-communications.cloud.google.com?utm_source=/business-communications/business-messages/guides/how-to/launch/locations&utm_medium=devsite&utm_campaign=business-messages) and sign in with your Business Messages Google account.
2. Choose your agent.
3. In the left navigation, click **Launch**.
4. In the **Verified locations** section, choose the locations you want to launch, then click **Launch**.

## Unlaunch a location

If you need to cancel a location launch or unlaunch a live location, you can
mark the location as unlaunched. If the location was in a pending launch state,
this cancels the location launch. If the location was launched, this removes the
location from all configured entry points.

To unlaunch a location,

1. Open the [Business Communications Developer
   Console](https://business-communications.cloud.google.com?utm_source=/business-communications/business-messages/guides/how-to/launch/locations&utm_medium=devsite&utm_campaign=business-messages) and sign in with your Business Messages Google account.
2. Choose your agent.
3. In the left navigation, click **Launch**.
4. In the **Verified locations** section, choose the locations you want to unlaunch, then click **Unlaunch**.
5. Enter "UNLAUNCH", then click **Unlaunch**.

## Next steps

Now that your locations are launched, users can start conversations on the
locations' configured entry points. Identify and review the
[metrics](https://developers.google.com/business-communications/business-messages/guides/how-to/qa/metrics) you
can use to measure your agent and locations' success.