Until now, anything that touched a lead could rename them. A returning prospect who typed "Sam" on a second booking overwrote the "Samantha Ladwig" your first call recorded, and a contact renamed in your CRM overwrote whatever they had told you themselves. Across the accounts we measured, 60 names got shorter or wrong this way.
From now on the name a person gives you is settled the moment they complete a booking. Your booking forms, a second booking, and your HubSpot or GoHighLevel sync can still fill in a name that is missing, but none of them can replace one that is already there. Changing it is now something a person does: an edit you make yourself, an update through the API, or a CSV import.
One exception, so it does not surprise you: if you sync with Close, its contact updates can still change the name, because your sync recipe includes the name field unless you removed it. Take "Full name" out of that recipe and Close will keep its own version alongside yours instead of overwriting it.
Your CRM's version of the name is not thrown away — it is kept alongside, and shown on the call record when the two differ, so you can see that HubSpot or GoHighLevel disagrees without Aura silently picking a side.
When the CRM is right and Aura is wrong, you now fix it directly: open the call and click the pencil next to the lead's name. That edit always wins, and it is recorded in your audit trail.
August 2026
Lead scoring and lead routing are live
Every booking is now graded A to D the moment the form is submitted, using the answers your booking questions already collect: current revenue, target revenue, ability to invest, and whether you are talking to the decision maker.
Routing then sends each booking to the closer most likely to close it. Aura routes on how good the lead is and on who actually closes, without hiding anyone's availability, so you never lose a booking to a full calendar.
Grades show up everywhere the lead does: the Slack alert, the pipeline card, and the call record your closer opens before the call.