Hi Vapi team — running into a reproducible issue. Assistant: Bob — BCF (Assistant ID: 4056f7f9-b32f-4949-a1d3-56c5...) Setup: Assistant was created by cloning another assistant (Maddox) Has 4 SMS-type tools attached: send_intake_form_sms, send_renee_contact_sms, send_amber_contact_sms, notify_renee_of_caller All tools have valid From Phone Number (an imported Twilio number with SMS enabled), Message Body presets, and {{customer.number}} as To Phone Number Twilio number is imported with SMS Enabled: true Tools appear in the assistant's Tools tab as attached Assistant has been re-published multiple times Problem: During calls, the assistant verbally states: "I don't actually have a SMS tool available to me right now." It never attempts to fire any of the SMS tools. The Logs tab inside the call shows NO tool call attempts. However, when I had transfer_call_tool attached (a transferCall-type tool that also came in from the clone), the assistant DID fire that one successfully during the same kind of call. What I've tried: Simplified all SMS tool descriptions Added explicit "you have SMS tools, use them" instructions in the system prompt Removed transfer_call_tool to eliminate cross-contamination Re-published the assistant after each change Confirmed in the Vapi Messages logs that the system prompt is being delivered correctly Reference call IDs (most recent failures): 019e...e803 (May 29, 13:32 MDT) The transfer-tool-fires call from the same session Question: Is there a known issue with SMS-type tools failing to register in runtime when the assistant was created by cloning? Is there a workaround? Thanks, Todd Schreier

This sounds more like a runtime/tool-registration issue than a prompt issue, especially since the transfer tool is being recognized and executed. One thing I'd check is whether those SMS tools are actually being exposed in the assistant payload at runtime after cloning. if you create a brand-new assistant (not cloned) and attach the same SMS tools, do they fire correctly? @ToddFather

this one is cloned at least framework wise. There is a disconnect between what I have set up in vapi and having the bot recognize it. Here is what I get,"I appreciate you confirming that, but I should be upfront with you. The SMS tools I have are set up to send to the number you're calling from. I'm not able to manually enter a different number on my end. The easiest workaround would be to have whoever needs the intake form call us directly, and I'll send it straight to them. Or if you're calling from a different number than the one you wanted sent to. That's the simplest path. Would either of those work for you?"

Hey, Thanks for reaching out. Could you please share the Assistant ID and the Call ID so that I can investigate the issue further? Kind regards, Akash