> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assistable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Save a customer address

> Collect and confirm an address, then verify it on the connected contact.

Use **Update User Details** to save an address during a conversation. You do not need a separate BuildShip workflow or a custom `save_address` endpoint for the connected GoHighLevel contact workflow.

## Before you start

Use an assistant with access to the platform tool, a working GoHighLevel connection, and a conversation linked to the correct contact. See [Save contact details](/v3/guides/workflows/save-contact-details) for setup and identity checks.

## Collect and save the address

1. Open the assistant's **Tool Kit → Tools & APIs** and add **Update User Details** (`update_user_details`).

2. In the assistant's instructions, specify the address components your business needs: street and unit, city, state or region, postal code, and country.

3. Ask the assistant to repeat the address for confirmation before saving. For example:

   > Ask for the service address, including apartment or unit, city, state, postal code, and country. Confirm it with the customer, then save it using Update User Details. If saving fails, say that it needs follow-up; do not claim the address was updated.

4. Save and publish the assistant.

5. Test with an address you can recognize on a dedicated test contact.

For a custom integration, use the field names your tool defines. The native contact update handler accepts all of these address fields:

| Value | Accepted parameter names |
| - | - |
| Street and unit | `address1`, `address` |
| City | `city` |
| State or region | `state` |
| Postal code | `postalCode`, `postal_code`, `zip`, `zipCode`, `zip_code` |
| Country | `country` |

Give only the components to change. Empty values are skipped. A standalone parameter named `street` is not a supported street-address field. See the [complete contact field reference](/v3/guides/workflows/save-contact-details#supported-contact-fields) for non-address fields.

## Verify it works

Open the correct contact in GoHighLevel and inspect each address component. Confirm that the unit number was preserved and the postal code was not placed in the city or state field.

Saving an address does not validate deliverability, calculate travel distance, or confirm that the customer is inside your service area. Add those checks separately if your workflow needs them.

## Troubleshooting

If nothing changed, inspect the tool result and the account's GoHighLevel connection. If only part of the address saved, compare the supplied parameter names with the tool's fields. If the address belongs to the wrong contact, stop the workflow and correct the conversation's contact association before retrying.

[Platform tools](/v3/platform-tools) · [Save contact details](/v3/guides/workflows/save-contact-details)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.