---
title: Manually Stop Engagement
description: "The `Taalk_Success` field in Taalk's AI-driven campaign management system allows businesses to define custom success conditions for stopping customer engagement. By setting `\"Taalk_Success\": true` via API, users can ensure contacts are only marked as successfully reached when external business criteria, such as payment completion or appointment confirmation, are met."
---

[Skip to content](https://knowledge.taalk.ai/understanding-taalk-success-engagement-stop-condition-in-campaign-dialer-strategy#main-content)

Open main navigation

Close main navigation

 How can we help you today?

- There are no suggestions because the search field is empty.

1. [Taalk Academy](https://knowledge.taalk.ai/?hsLang=en)
2. [Contact Center](https://knowledge.taalk.ai/contact-center?hsLang=en)
3. [Campaign](https://knowledge.taalk.ai/contact-center?hsLang=en#campaign)

July 28, 2025

# Manually Stop Engagement

## This article is best for: 🟦 Developers or IT Admin

### **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 **"Taalk Engagement Methods"** section in the Campaign Setting.

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_Success` to `true`**, 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:

![IMG_0123](https://knowledge.taalk.ai/hs-fs/hubfs/IMG_0123.jpeg?width=670&height=760&name=IMG_0123.jpeg)

---

### **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.

 

- [Getting Started](https://knowledge.taalk.ai/getting-started?hsLang=en#main-content)
  
  
  
  
  
    - [Platform 101](https://knowledge.taalk.ai/getting-started?hsLang=en#platform-101)
    - [Campaign 101](https://knowledge.taalk.ai/getting-started?hsLang=en#campaign-101)
    - [AI Workforce](https://knowledge.taalk.ai/getting-started?hsLang=en#ai-workforce)
    - [Operator Force](https://knowledge.taalk.ai/getting-started?hsLang=en#operator-force)
    - [Billing 101](https://knowledge.taalk.ai/getting-started?hsLang=en#billing-101)
    - [Compliance 101](https://knowledge.taalk.ai/getting-started?hsLang=en#compliance-101)
- [AI Force](https://knowledge.taalk.ai/ai-force?hsLang=en#main-content)
  
  
  
  
  
    - [Agent Behavior](https://knowledge.taalk.ai/ai-force?hsLang=en#agent-behavior)
    - [Objective and Scripts](https://knowledge.taalk.ai/ai-force?hsLang=en#objective-and-scripts)
    - [Agent Call Flow and Transfers](https://knowledge.taalk.ai/ai-force?hsLang=en#agent-call-flow-and-transfers)
    - [Agent Knowledge](https://knowledge.taalk.ai/ai-force?hsLang=en#agent-knowledge)
    - [Agent Multichannel Playbooks](https://knowledge.taalk.ai/ai-force?hsLang=en#agent-multichannel-playbooks)
    - [Agent Plugins](https://knowledge.taalk.ai/ai-force?hsLang=en#agent-plugins)
    - [Best Practices](https://knowledge.taalk.ai/ai-force?hsLang=en#best-practices)
    - [Templates](https://knowledge.taalk.ai/ai-force?hsLang=en#templates)
- [Operator Force](https://knowledge.taalk.ai/operator-force?hsLang=en#main-content)
  
  
  
  
  
    - [Operator](https://knowledge.taalk.ai/operator-force?hsLang=en#operator)
    - [Admin](https://knowledge.taalk.ai/operator-force?hsLang=en#admin)
- [Contact Center](https://knowledge.taalk.ai/contact-center?hsLang=en#main-content)
  
  
  
  
  
    - [Campaign](https://knowledge.taalk.ai/contact-center?hsLang=en#campaign)
    - [Taalk Dialer](https://knowledge.taalk.ai/contact-center?hsLang=en#taalk-dialer)
    - [Metrics & Reporting](https://knowledge.taalk.ai/contact-center?hsLang=en#metrics-reporting)
    - [Templates](https://knowledge.taalk.ai/contact-center?hsLang=en#templates)
    - [Best Practices](https://knowledge.taalk.ai/contact-center?hsLang=en#best-practices)
- [Automation](https://knowledge.taalk.ai/automation?hsLang=en#main-content)
  
  
  
  
  
    - [OpenAPI](https://knowledge.taalk.ai/automation?hsLang=en#openapi)
    - [Native Integration](https://knowledge.taalk.ai/automation?hsLang=en#native-integration)
- [Compliances](https://knowledge.taalk.ai/compliances?hsLang=en#main-content)
  
  
  
  
  
    - [Company DNC](https://knowledge.taalk.ai/compliances?hsLang=en#company-dnc)
    - [TCPA](https://knowledge.taalk.ai/compliances?hsLang=en#tcpa)
    - [Best Practices](https://knowledge.taalk.ai/compliances?hsLang=en#best-practices)
    - [Teleco Trust](https://knowledge.taalk.ai/compliances?hsLang=en#teleco-trust)
- [Product Updates](https://knowledge.taalk.ai/product-updates?hsLang=en#main-content)
  
  
  
  
  
    - [W9-2025](https://knowledge.taalk.ai/product-updates?hsLang=en#w9-2025)
    - [W8-2025](https://knowledge.taalk.ai/product-updates?hsLang=en#w8-2025)
    - [W10-2025](https://knowledge.taalk.ai/product-updates?hsLang=en#w10-2025)
    - [W11-2025](https://knowledge.taalk.ai/product-updates?hsLang=en#w11-2025)
    - [W12-2025](https://knowledge.taalk.ai/product-updates?hsLang=en#w12-2025)
    - [W13-2025](https://knowledge.taalk.ai/product-updates?hsLang=en#w13-2025)
    - [W14-2025](https://knowledge.taalk.ai/product-updates?hsLang=en#w14-2025)
    - [W15-2025](https://knowledge.taalk.ai/product-updates?hsLang=en#w15-2025)
    - [W16-2025](https://knowledge.taalk.ai/product-updates?hsLang=en#w16-2025)

[![Taalk](https://knowledge.taalk.ai/hs-fs/hubfs/logo%20taalk.png?width=60&height=60&name=logo%20taalk.png "Taalk")](https://knowledge.taalk.ai/?hsLang=en)

[mailto:success@taalk.ai](mailto:success@taalk.ai) <https://www.linkedin.com/company/taalkai>

Copyright © 2025 Taalk LLC