Set up and govern Cabby

Connect Cabby with explicit data controls

CAB Settings → AI & integrations → AI Agent Setup

Complete the setup in order. Cabby remains unavailable to end users until the organization is registered, the connection succeeds, the Agent is activated, and the user has the required permission set.

Complete AI Agent Setup

1. Accept Terms and Choose AI Data Processing Mode. Select Review Terms, choose the processing mode, select I have read and accept the terms, and confirm. Afterward, the action reads View or Change Terms.
2. Assign Agent Permission Set. Select Select Users and assign Campaign Audience Builder Agent User. This step appears only when the current admin can assign permission sets; otherwise assign it from Salesforce Setup.
3. Create Credentials. Select Create Credentials to create the Named Credential infrastructure.
4. Enable Named Credential. Open the generated Salesforce Setup page and select Enable for Callouts.
5. Register with CAB Agent. Select Register to create organization-specific Agent credentials. Regenerate Credentials replaces them when rotation is required.
6. Test Connection. Select Test Connection and resolve any Named Credential, permission, or registration problem before continuing.
7. Enable Metadata Statistics. Select Enqueue Job. This starts an initial collection and schedules the nightly job. Use Unschedule to stop future collections.
8. Activate Agent. Select Activate. The setup card then offers Deactivate instead.

Required permissions

Give setup administrators the Campaign Audience Builder Admin permission set. Do not assign that administrative access to ordinary Cabby users.

Give end users Campaign Audience Builder Agent User. It includes Use Segmentation Agent and the access needed by Cabby surfaces. The assignment flow also creates CAB_ExternalServices_Credential for external credential access; teams that deploy metadata through source control should retrieve and commit that generated permission set.

Choose the AI data processing mode

AI Data Processing Mode is part of accepting the Agent terms:

Choice	Processing boundary
Enforce EU data residency and processing	Keeps AI model and embedding requests on Google Cloud Platform infrastructure in the EU. Capacity can be more constrained, so responses, feature availability, or access to newly released models can arrive later.
Optimize availability and performance	Uses Google Cloud Platform’s global AI endpoint to improve availability and reduce capacity errors. Google may process requests outside the EU/EEA.

The selected mode is attached to Agent requests rather than inferred from the current user’s location.

Changing mode deactivates Cabby

Changing the AI data processing mode changes the applicable data processing terms. The Agent will be deactivated until setup is completed again. Review the new terms, repeat the affected setup steps, test the connection, and activate Cabby again.

Keep metadata statistics current

Enable Metadata Statistics schedules a nightly schema analysis and runs the first collection immediately. Cabby receives accessible and filterable schema facts such as record counts, field population rates, and which fields are indexed. It does not receive raw field values from this job.

Keeping the job active helps Cabby prefer fields that exist, contain data, and are suitable for filtering. Unschedule stops future collections; Enqueue Job enables them again.

Control Cabby data access

Under Cabby data access, the page states Changes in this panel apply immediately. These controls are not part of the page’s ordinary Save/Cancel batch.

Cabby always uses organization metadata, audience configurations, Campaign metadata, and aggregate schema statistics. Individual Salesforce record values are not sent unless a user types them into a prompt or filter.

Outcome data

Give Cabby access to outcome data is off by default. When enabled, CAB sends aggregate checkpoint statistics—such as counts added, responded, and converted—plus outcome-definition names. It does not send individual names, record IDs, individual records, or member lists.

Enabling may require accepting the current Agent terms. Turning the control off stops new sharing and deletes the stored outcome statistics. If cleanup is incomplete, use Retry deletion before enabling it again. See Let Cabby help define and explain outcomes.

Geolocation filtering

Under Enable Geolocation Filtering, turn on Allow Cabby to resolve locations via Google Maps only when the organization uses populated Address or Geolocation fields.

When enabled, location names that users type in prompts—for example, “contacts near Berlin”—are sent to the Google Maps Geocoding API to resolve coordinates. No Salesforce record data is included in those requests. Users can then ask Cabby for proximity filters; manual coordinate-based filtering remains available as described in Filter by location.

Set organization instructions and response mode

Under Agent Settings:

• Add organization terminology, data-model conventions, and durable preferences under Custom Agent Instructions in the Instructions field. The limit is 32,768 characters. These edits are staged until you select the page-level Save; Cancel discards them.
• When the edition exposes Response Mode, choose Fast or Thinking. Treat this as a managed response preference, not as a promise of a particular underlying model. CAB can use the same model for both choices and can change routing as models evolve.

Control Campaign context

Cabby’s Create with Cabby flow always receives standard Campaign context: Name, Type, Description, Start Date, End Date, Status, Parent Campaign name, Number of Contacts, and Number of Leads.

Add approved custom fields

Salesforce Setup → Object Manager → Campaign → Field Sets → Agent Campaign Context

Add only custom Campaign fields that are safe to send to the Agent. The field set’s guidance is explicit: fields must be free of PII, PHI, and confidential data. CAB ignores unsupported field types, including identifiers, references, encrypted strings, Base64 values, addresses, and locations.

A field set is a data allowlist

Do not add a field merely because it would improve a suggestion. Treat every field in Agent Campaign Context as approved for transmission to the configured Google Cloud processing boundary.

Deactivate or erase GCP data

Select Deactivate in the final setup step to revoke the organization’s Agent credentials. Reactivation requires a new registration.

The confirmation offers Also erase all data from Google Cloud Platform:

Choice	What happens
Leave the checkbox clear and select Deactivate	Credentials are revoked, but the organization’s stored GCP Agent data is retained.
Select the checkbox and choose Deactivate & Erase Data	CAB also requests deletion of the organization’s conversations, configurations, Campaign context, cached Agent data, job and usage records, and stored outcome data from GCP.

Erasure is scoped to Google Cloud Platform

This option does not delete Salesforce audiences, Campaigns, runs, or Salesforce-side CAB records. Apply the organization’s Salesforce retention and deletion policy separately.

Troubleshoot Cabby

Message or symptom	What to do
You don’t have permission to manage CAB Agent administrative settings. Ask your Salesforce administrator to assign the ‘Campaign Audience Builder Admin’ permission.	Assign Campaign Audience Builder Admin to the setup administrator.
You don’t have permission to use the CAB Segmentation Agent. Ask your admin to assign the ‘Campaign Audience Builder Agent User’ permission set.	Assign Campaign Audience Builder Agent User to the user.
The agent backend has been updated. Please upgrade the Campaign Audience Builder package to the latest version to continue.	Upgrade the Campaign Audience Builder package to the latest version.
This conversation’s data has expired. Start a new message to continue.	Start a new message.
The agent couldn’t process that request. Please rephrase and try again.	Rephrase the request and try again.
The agent couldn’t complete the task within the allowed number of steps. Try a more specific prompt.	Use a narrower, more specific prompt.
The agent stopped responding and the turn was ended. Please try again.	Retry the turn.
Your organization has reached its daily agent budget. Please try again tomorrow.	Wait for the next daily budget period. This organization budget is separate from monthly conversation allowances; there is no documented numeric allowance in this message.
You have used all agent conversations for this month. Conversations reset at the beginning of each month.	Existing conversations remain usable, but users cannot start another until the beginning-of-month reset.

If Test Connection fails without one of these messages, confirm that Enable for Callouts was completed, the organization is registered, and the current credentials have not been regenerated or revoked since the Named Credential was configured.