Introduction
In Taalk’s AI-driven customer engagement platform, campaigns define the strategy for contacting customers through voice, SMS, and email. A crucial aspect of campaign management is determining when the system should stop engaging a contact. This is controlled by the Engagement Stop Condition, a setting found under the "Audience Engagement Mode" section in the Campaign Dialer Strategy.
One key stop condition is the Taalk_Success field, which allows businesses to dynamically control when a contact is considered successfully reached, even when success criteria occur outside of Taalk’s system.
Understanding Taalk_Success and Its Role in Campaigns
The Taalk_Success field is a reserved field that enables users to mark a contact as successfully reached. When this flag is set to true, Taalk will automatically stop further engagement with that contact within the given campaign.
Why Use Taalk_Success?
In some scenarios, the default stop conditions (e.g., answered call, transferred call, or URL opened) may not fully represent success for a specific business process. The Taalk_Success flag provides greater flexibility by allowing external systems or human intervention to define success.
For example:
- If a debt collection campaign is running, Taalk may consider a call transferred to a live agent as a success. However, for the business, success only happens when the customer pays the bill.
- In this case, Taalk would continue calling the customer until an external system sets
Taalk_Successtotrue, indicating the bill has been paid.
How to Set Taalk_Success via API
Users can programmatically mark a contact as successful using Taalk’s API by sending a POST request.
Example API Request
curl --location 'https://api.taalk.ai/api/campaign2s/{campaign_id}/contacts/{phone_number}' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer ********' \
--data '{
"Taalk_Success": true
}'
If the contact was modified, the response will let you know of the change:
{
"payload": {
"modified": 1
}
}
Example Usage:
Mark contact 7047058647 as successfully reached in campaign 6791043299aeedfec27f85d5:
curl --location 'https://api.taalk.ai/api/campaign2s/6791043299aeedfec27f85d5/contacts/7047058647' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer ********' \
--data '{
"Taalk_Success": true
}'
Once this request is processed, Taalk will stop contacting this customer for the given campaign.
Note: in W12-2025 we also enabled manual set of the Taalk_success in the contact tab for each campaign:
Use Cases for Taalk_Success
| Scenario | Default Stop Condition | Business Success Condition | Solution |
|---|---|---|---|
| Debt Collection | Call is transferred to a live agent | Customer makes a payment | External system sets "Taalk_Success": true after payment confirmation |
| Appointment Booking | Call is answered | Customer completes online booking | Booking system updates "Taalk_Success": true when appointment is confirmed |
| Lead Generation | Call is answered and a survey is completed | Lead signs a contract | CRM updates "Taalk_Success": true upon contract submission |
Conclusion
The Taalk_Success field gives businesses precise control over when a contact should be considered successfully reached within a campaign. This flexibility ensures that engagement stops only when a true business outcome is achieved, rather than relying solely on predefined system conditions.
By integrating Taalk’s API, businesses can seamlessly update success conditions based on external events, optimizing engagement and improving operational efficiency.