[Feature New API] Voice AI Custom Action Resume API

[i-am-rad]

🌟 Describe the Feature

We need a way to pause execution with live voice AI calls. Then when our custom action responds we call a special resume API similar to the workflow resume api action.

🚀 Justification

Currently voice AI times out in 2 to 3 seconds. This means it's really only used for short outbound saving of data into custom fields or fast responses. Other leading voice AI tech like VAPI will play keyboard click sounds while it waits on you to asynchronously await a response.

📝 Suggestions

A) Have one option to wait up to X amount of seconds for our API to respond to the original request. 15 seconds is probably the max a customer would be patient to wait.

B) Let us respond 200 to wait on us. Then a new API to resume voice AI conversation with our response. You play keyboard clacking sounds or other filler noise while it processes.

For failures of custom actions give us a consistent way to respond. Right now the system just errors out and says "something went wrong" which is terrible.

Product Area

conversations-ai

🧠 Additional Context

Subaccount ID: VUc1GSivMC6X6ODs8NRd

Ticket #3803897

[github-actions]

✅ Issue processed successfully!

Your issue has been reviewed and assigned to the appropriate team.

[mitul-highlevel]

Dear Customer,

We’ve reviewed your feature request and determined that this functionality is not currently supported, and we will not be able to provide it in the near future.

We discussed your request in detail and noted that other competitors/providers also do not offer an API to resume a call.

Currently, our updated agents have a 2-minute timeout for actions, which should be sufficient to complete most processes. If the processing takes longer than that, we recommend handling it asynchronously on your side so that the agent can continue the conversation without interruption.

Looking ahead, we do plan to introduce an async action trigger, where the agent will not wait for the response but will continue the conversation. This feature will be integrated into the Action CRUD operation, allowing you to configure whether an action should run in sync or async mode.

For now, we are closing this request, as we do not plan to provide a resume API call.

Best regards,
GHL