TautivaHelp

Customers

Manage tags, consent, and communication preferences

Tags group contacts. Consent records which communications a customer has agreed to receive.

- CS / Agent, CRM Admin, Marketing# 5, 8 minutes #Last checked October 13, 2026.
Supplies record: Some actions depend on role and data conditions, and have not been tested by saving / sending data. Use this as a check guide, instead of proof of transaction testing.

Before you start

Log in to the correct workspace and have the necessary permissions according to your role.

Step-by-step instructions

Follow these steps in order. You can keep this guide open while working in another Tautiva tab.

  1. Open Customers and select the customer you want to check.

  2. Check the Customer 360 and look for the TAGS and Communication consent sections.

  3. Use the available tag settings only if you have the right to change them.

  4. Before a Campaign, read the customer's communication permission status, including objections or opt-outs.

  5. Do not change the consent status based on assumptions; use evidence and company policies.

  6. Ensure the tags used in filters or segmentation match the communication goals.

Open the page in Tautiva

PRACTICAL EXAMPLE

Example from daily work

Example: 'Corporate customer' is a segmentation tag; permission to receive WhatsApp promotions must still be recorded separately.

This is a fictional training example. No real customer data was used.

Expected result

Actions are understood and results can be checked on the workspace page. For data changes, only perform them according to the Standard Operating Procedure (SOP).

Important notes

  • No consent record does not mean the customer automatically agrees to promotional messages.
  • Tags for services and marketing permissions are two different things.

If something goes wrong

  • Tag not available: check profile change permissions.
  • Customer not included in the Campaign segment: check tags, consent, and other eligibility criteria.

This guide describes the interface reviewed on 13 October 2026. Documentation testing did not send real messages, invite users, process payments, or modify real customer records.