Clients not autopopulating

Hi Diana! Sorry about that, This is a known issue and it’s because the conversion of messages to the new type is not done running yet.

You’ll experience it in the following scenario: Replies to old messages (pre-selective communication) in old projects, until the migration is done.

Note that you won’t experience issues in the following cases:

• If you start a new message instead of replying, this will work, and the client will auto- populate
• if you reply to a message that was sent post-selective, it’s also supposed to work

in the meantime (until the migration is done) - the solution is just to add manually, but it won’t be like that for long.

Not sure if this is intended, but when an AI drafts a response for us, it does not auto populate the recipients name - FYI. 

Oooh, @Diana - The Finer Points Thank you for flagging! I’ll bring this to the AI team. 

@Diana - The Finer Points Follow up questions from the team
During which stage of the project does this happen?
What is the project history and which ai feature is it?

​​​@Elinor Shulman 

I was following up with an inquiry and used the AI composer. That project only had inquiry and one discovery call scheduled.

Thanks Diana!

The team is exploring how to get this working! We’ll let you know when there is an update :)