Mic not working again

General
1

Let me investigate the agent and its recent history right away.

Let me look for Athalie Merchant’s conversation specifically and check the deployment setup.

Good news — I found what happened. Here’s the full picture:

What Went Wrong for Athalie

User: 2273411112@members.act-bold.com — this matches the timing and pattern of Athalie’s complaint.

Two separate problems:

1. :studio_microphone: Voice recording bug (the main complaint) In session 896716bb at 9:02 AM, the user literally wrote:

“look i’m trying my best to work here but the stop button keeps disappearing if i record”

The mic button’s stop control disappears mid-recording, leaving users stranded. This is a platform-level UI issue with the voice-to-text feature — not something in the agent’s config itself.

2. :warning: Empty assistant responses (early sessions) In sessions 3785314d (8:01 AM) and 91726c9c (8:47 AM), the assistant returned completely empty responses. The action tool (user_identity_mapper) started but never completed — you can see it stalled mid-load in the message parts. This is triggered on every first message of a new conversation.

What happened next:

Once she pushed through and typed (despite the frustration), the agent DID work — she had a 40-message conversation by 9:10 AM that ran just fine.

What You Can Do Right Now

  1. Reach out to Athalie and let her know:

    • The mic button has a bug that makes the stop control disappear — she should type her responses for now
    • If the agent ever doesn’t respond, start a fresh conversation and type the first message instead of recording

  2. The user_identity_mapper action is stalling on first messages occasionally — worth checking if that action is healthy. Would you like me to look at it?

  3. The voice-to-text UI bug would need to be flagged to Pickaxe support, as it’s a platform-level issue outside what we can fix in the agent settings.

Want me to check the user_identity_mapper action to see if something is broken there?

2

Hi @actbold,

Thanks for sending this over to us. It seems like you’ve contacted us previously about a similar issue. After looking through those emails, it looks like it was resolved by removing the introductions from the agent. If possible, can you try doing this to see if it fixes your issue? If this doesn’t work, it would be helpful to know what browser your user is using as well as allowing me to have access to where your embed is located. If you want to keep this info private, you can send over an email to us at info@pickaxeproject.com, and I can reply there!