---
schema_version: "1"
id: a864964e577a63f45a1ece1880f050834a7c4b1429b284af39e38973e735fdac
title: Considerations and Limitations for Help Agent
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ai/264-0-0/help_agent_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=ai.help_agent_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 533771bf8dd96c938bdd69f4569a855b1cca2a6bb2d26f88a1918fc063fa219e
description: Review these considerations and limitations before setting up Help Agent.
products:
  - Agentforce
  - Cross Cloud
release: "264"
---
# Considerations and Limitations for Help Agent

Review these considerations and limitations before setting up Help Agent.

- You can’t use Quick Service Agent Configuration to set up Help Agent in orgs enabled with Data Cloud One.
- Help Agent comes with default permissions that enable it to do specific tasks. To give the agent access to more features, such as prompt templates, create a custom permission set that gives the agent user the access it needs. Custom permission sets that you assign to the agent user must be associated with the Einstein Agent license and Einstein Agent User profile. For a list of agent features and their required permissions, see [Best Practices for Agent Users](https://help.salesforce.com/s/articleView?id=ai.agent_user.htm&language=en_US&type=5).
- To use Quick Service Agent Configuration in a sandbox, you must [manually set up Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_setup_provision.htm&language=en_US&type=5), and then assign the Data Cloud permission sets to users.
- Before you can route escalated conversations to a rep, you must assign reps to the queue. By default, no reps are assigned to the default queue. For details, see [Escalation Path in the Conversation Lifecycle](https://help.salesforce.com/s/articleView?id=ai.help_agent_escalation.htm&release=264.0.0&type=5).
- To create a fallback support case, the customer must exist as a contact. If no contact record exists, the case isn't created. For details, see [Escalation Path in the Conversation Lifecycle](https://help.salesforce.com/s/articleView?id=ai.help_agent_escalation.htm&release=264.0.0&type=5).

#### See Also

- [Considerations for Agentforce Service Agent](https://help.salesforce.com/s/articleView?id=ai.service_agent_considerations.htm&language=en_US)
- [Best Practices for Agent User Permissions](https://help.salesforce.com/s/articleView?id=ai.agent_user.htm&language=en_US)