AI outbound calls
From recipients to call results. Shared actions with feature-specific inputs and evidence.
Task sequences
Compare shared actions across features in the sequence catalog.
Related guidance
AI can call customers first to confirm bookings or explain schedule changes. It uses your call instructions and Entity facts, and can collect responses when a form is connected. Marketing calls are outside this feature’s scope.
From customer selection to dialing
Narrow the customer list and select the rows to contact. Choose a phone template, then preview the number and instructions. Actual dialing begins when you submit the send after reviewing those inputs.
These are the same basic actions used for messaging. A separate customer-selection method is unnecessary. The chosen template kind and linked account determine the transport.
For first-time use, finish phone account and template preparation, then make a test call. The procedure explains the inputs and checks for each action in order.
Distinguish request processing from answering
A processed request does not guarantee an answered call. Check the call’s response and ending state after delivery history, and answer the test phone to verify the actual guidance.
This final check is the additional action that distinguishes calls from messaging. For failures or cancellation requests, inspect call states and retry criteria. Establish how the existing attempt ended before placing another call.