Skip to main content
Use update_user_details when a customer gives or corrects their name in a GoHighLevel-connected conversation. This updates the linked contact; changing a name in an assistant’s reply does not update the record.

​
Set up the update

  1. Open the assistant’s Tool Kit → Tools & APIs and add update_user_details.
  2. Tell the assistant to ask for missing identity, use the customer’s spelling, and save corrections before booking or sending a message that depends on those details.
  3. Save your changes. For a live voice test, Publish before calling. Use a test contact with a recognizable starting name.
  4. Ask the assistant to change the name. Open the contact in GHL and check the saved first and last name.
The tool accepts these name fields. Use one alias for each value you intend to change; an empty answer does not erase a saved name. For every other supported contact field, see the complete contact field reference.

​
Check difficult cases

Test a corrected spelling, a name with punctuation, and a customer who supplies only one name. The prompt should ask for clarification when necessary instead of fabricating a surname. If you also change an email address or phone number that belongs to another GHL contact, GHL may merge the records. Check the surviving contact before concluding the update was lost.

​
If the update fails

  • Contact context is missing: resolve the contact identity in the conversation before attempting another contact action.
  • GHL authorization failed: repair the account connection.
  • Some fields update but others do not: inspect the returned field-validation error and check each saved field. Do not replace rejected email or phone values with invented ones.
  • The assistant says it changed the name but the record did not change: check whether the tool ran and whether it returned success.
See platform tools for the reference and automatic extraction for mapping custom fields.