Sparkforge Agent Platform Settings Inside the CRM

By Sparkforge Support Team ·Last reviewed May 3, 2026

From within Sparkforge, configure the Agent Platform with user permissions, an Agent Bypass tag, a Send-to-Agent tag, and the Send to Agent Platform workflow action. The send-to tag wins if both bypass and send-to are configured.

You can manage parts of the Sparkforge Agent Platform from inside the Sparkforge CRM itself. These settings handle who can configure the platform, which conversations bypass it, and which conversations get pushed in.

User Permissions for Agent Service

Users who edit FAQs or configure the Agent Platform at the sub-account level need the Agent Service permission enabled.

Open Agency Settings > Team.
Click Edit User next to the user.
Scroll to User permissions.
Toggle Agent Service on.

Once granted, the Agent Service tab appears in sub-account settings for that user.

Agent Bypass Tag

Use a bypass tag when some conversations should never enter the Agent Platform.

Create the tag under Settings > Tags.
Open Sub-Account Settings > Agent Service and select that tag as the Agent Bypass tag.

Every new inbound conversation is checked for the bypass tag. If the contact has it, the message is not forwarded to the Agent Platform. If the conversation is already inside the platform, the next time an agent opens it, it's removed from the queue with the disposition Bypass tag assigned.

Send to Agent Tag

Use a send-to tag when only specific conversations should enter the platform.

Create the tag.
Open Sub-Account Settings > Agent Service and configure it as the Send to Agent tag.
Use a workflow to apply the tag to qualifying contacts.

Only new inbound conversations with the tag are sent in. If you tag a contact and want them to enter the platform without waiting for an inbound message, use the Send to Agent Platform workflow action instead.

What Happens If Both Tags Are Configured

If you accidentally set both an Agent Bypass tag and a Send to Agent tag, the system honors the Send to Agent tag. This is intentional — it errs on the side of routing conversations in rather than dropping them.

Send to Agent Platform Workflow Action

The Send to Agent Platform action pushes a contact into the connected Agent Platform account immediately, regardless of whether they've sent an inbound message. Add it to any workflow whose contacts you want the agent team to nurture.

Frequently Asked Questions

How do I expose the Agent Service tab in sub-account settings?

Toggle Agent Service on under the user's permissions in Agency Settings > Team. Once enabled, the tab appears in sub-account settings for that user.

What does the Agent Bypass tag do?

It blocks tagged contacts from entering the Agent Platform. New inbound conversations stay out, and existing in-platform conversations are removed from the queue with the Bypass tag assigned disposition.

Send-to tag vs send-to workflow action — what's the difference?

The tag only sends a contact in when they next send an inbound message. The workflow action pushes them in immediately, even without an inbound message.

What if I set both bypass and send-to tags on the same contact?

The system honors the Send to Agent tag. The contact enters the platform rather than getting dropped silently.