workflow · how to

Configure CTA defaults

Follow the configure cta defaults workflow in Slack.

Goal

Build reusable call-to-action snippets and set default CTA behavior for the active brand, campaigns, and pillars so Create and publish flows resolve the right link or text snippet.

When to use this

Use this workflow when you want a shared CTA library for your brand, need to mark a default snippet for Create, or must set campaign- or pillar-level CTA defaults. CTA library entries are brand-scoped unless you open organization-level config forms.

Before you begin

Confirm these prerequisites:

  • An active brand is selected.
  • You have brand management access and admin permission. The CTA Settings hub entry enforces both before the editor opens.

Without an active brand or admin permission, the CTA library and config editor do not open.

Steps

Open CTA settings

  1. Type /social, choose Settings, then open CTA Snippets under Links & Distribution.
  2. You can also open the CTA library from Create when adding a CTA to a draft.
  3. For domain-level CTA config (separate from the snippet library), open the CTA config list and form from Settings when you need scope-wide defaults.

The Settings hub CTA card routes to the editor and library entry surfaces. If you opened Create first, the library shows snippets for the active brand only.

Add a CTA snippet

  1. In the CTA library, choose Add CTA.
  2. Pick the snippet type: link or text snippet.
  3. Fill required fields such as label, URL, or body text. Invalid URLs are blocked on submit.
  4. Submit to save. The library list refreshes with the new entry.

The add flow moves from type selection into the link or snippet submit form for the variant you picked.

Edit, default, or remove snippets

Use the library overflow menu on each row:

  • Edit opens the edit modal with current values.
  • Set default marks the snippet Create should pre-select where applicable.
  • Delete removes unused snippets. Entries referenced by active settings may show a conflict message instead of deleting.

Overflow actions follow separate branches for edit, toggle default, and delete.

Configure CTA defaults beyond the library

CTA Snippets manages reusable snippets and brand-level library defaults.

To set campaign or pillar defaults:

  1. Edit that campaign or pillar from brand or Plan settings.
  2. Choose its default CTA link or snippet.

Platform-scope CTA overrides are not exposed in the Slack settings UI today. Use brand, campaign, or pillar scope for defaults you can manage in Slack.

For domain-level CTA config (inheritance across scopes), use the CTA config form from the config form suite. That form edits CTA domain settings at org, brand, or other offered scopes. Read Configuration inheritance before stacking overrides.

Snippet library changes and domain config changes are separate surfaces. Update both only when you need library entries and scope-wide defaults.

Confirm it worked

Check these signals after you save:

  • Open Create, add a CTA to a draft, and confirm your new or updated snippet appears in the library.
  • If you set a default snippet, Create pre-selects it where applicable.
  • Published posts use the resolved CTA for that item’s scope.
  • Delete and edit actions complete without conflict errors unless the snippet is still referenced.

Terminal save states include saved, active, or skipped depending on the action.

Troubleshooting

CTA settings do not open

Confirm an active brand is selected and you have admin permission. Switch brands in App Home if needed.

URL rejected on submit

Use a valid URL format for link snippets. Fix the field shown in the modal error.

Delete blocked with a conflict message

The snippet is referenced by active settings. Clear the reference or choose a replacement default before deleting.

Published post uses an unexpected CTA

A narrower scope override may win. Check campaign, pillar, and brand defaults against Configuration inheritance.

Config change does not appear

If you edited domain-level CTA config, see Configuration change is not applied. Cache and inheritance can delay visible changes for a few minutes.

You need domain details

See the Config domains reference.