Skip to content
  • There are no suggestions because the search field is empty.

Company DNC Sync Across Single or Multiple Workspaces - Plugin

Automatically Push DNC Updates to Current and Other Taalk Workspaces

Taalk provides a simple way to synchronize Company DNC updates across multiple workspaces using a post-engagement webhook. No matter if you have one Workspace or like some organizations run multiple Taalk workspaces—often for separate brands, teams, or campaign groups. When a consumer requests to be added to your Do-Not-Call list, that request often needs to be honored across all associated workspaces, not just the workspace that handled the call.

What This Feature Does

When the AI completes an engagement, a workflow can automatically send the caller’s phone number to a list of other workspaces’ Company DNC lists.

This ensures:

  • A single Do-Not-Call request is respected everywhere.

  • No workspace continues calling a consumer who opted out.

  • Compliance is consistent across accounts and sub-brands.

Install this from the Taalk Marketplace:

- Single Workspace DNC Sync

- Multiple Workspace DNC Sync

How It Works

You configure a webhook action inside a Post-Engagement Processing workflow.

The workflow sends the consumer’s phone number to the DNC API endpoint that supports multi-workspace updates.

The API route for multiple workspace looks like this:

/api/dnc/local/<workspace1>%2C<workspace2>%2C<workspace3>

  • Workspaces are listed in order.

  • They must be separated by commas.

  • Commas are URL-encoded as %2C.

The webhook then PATCHes the consumer’s number into the DNC lists for all specified workspaces.

The API route for a single workspace is: 

/api/dnc/local

 

Example Setup

Method: PATCH

Send Data To:

/api/dnc/local/workspace1%2Cworkspace2

Data Sent to Webhook:

{
  "<contact.localPhone>": true
}

In this example:

  • The system automatically writes the phone number into workspace1 and workspace2 Company DNC lists.

  • The value true flags this number as blocked.

Workspace Naming Requirements

Use the exact Taalk workspace names, all lowercase, with no spaces.

If your workspaces are:

  • workspace1

  • workspace2

  • workspace3

Then your endpoint becomes:

/api/dnc/local/workspace1%2workspace2%2Cworkspace3

When This Should Be Used

Use multi-workspace Company DNC Sync when:

  • You operate multiple Taalk workspaces under the same brand.

  • You need centralized Do-Not-Call handling.

  • You run parallel campaigns across different business units.

  • You want a guarantee that any DNC request is honored globally.

Notes

  • This feature controls Company DNC, not FTC DNC.

  • Sync applies only to the workspaces listed in the API path.

  • The workflow typically runs during Post-Engagement Processing for reliability.

 

 

 

If you want, I can also write an internal CSM training guide, add screenshots with captions, or create a Marketplace description for this DNC Sync tool.