Skip to content
Eliza Agent Platform

Eliza Agent Platform Settings within the CRM

The Eliza Agent Platform can be used to some extent from within the CRM; some of its configurations allow users to access it from within the CRM. This Article covers details of those Eliza settings within the CRM.

2 min read491 words5 explained imagesUpdated Wed, 24 May, 2023 at 1:50 PM
View as markdownOpen in ClaudeOpen in ChatGPT
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
On this page
  1. Eliza Settings inside the CRM
  2. User Permission setting for Eliza
  3. Eliza By-pass tag
  4. Send to Eliza Tag
  5. Send to Eliza Agent Platform Action in GHL Customer Care Workflow

The Eliza Agent Platform can be used to some extent from within the CRM; some of its configurations allow users to access it from within the CRM. This Article covers details of those Eliza settings within the CRM.

Covered in this Article

Eliza Settings inside the CRM

User Permission setting for Eliza

Eliza By-pass tag

Send to Eliza Tag

Send to Eliza Agent Platform Action in GHL Customer Care Workflow

Related Articles
Eliza Agent Platform Introduction and FAQs 

Eliza Agent Platform Settings

Eliza Agent Platform Search Tools

Eliza Agent Platform Dashboard

Eliza Agent Platform Conversations


Eliza Settings inside the CRM

Eliza Settings inside the CRM (video 1) Open in a new tab

User Permission setting for Eliza

Users who will edit FAQs and set up Eliza on the subaccount level need Eliza Service enabled in Agency Settings> Team> Edit User> User permissions.

User Permission setting for Eliza (image 1 of 5) What this shows Users who will edit FAQs and set up Eliza on the subaccount level need Eliza Service enabled in Agency Settings> Team> Edit User> User permissions. What this shows Illustrates the "User Permission setting for Eliza" section of "Eliza Agent Platform Settings within the CRM". This screenshot appears in the "User Permission setting for Eliza" section of "Eliza Agent Platform Settings within the CRM". The text alongside this image reads: Users who will edit FAQs and set up Eliza on the subaccount level need Eliza Service enabled in Agency Settings> Team> Edit User> User permissions. The navigation path used here is Agency Settings > Team > Edit User > User. Immediately after, the guide continues: To add the Eliza Service tab in the sub-account settings, You need to go to the user permissions and toggle the Eliza Service tab to grant access to that user. Once the access is granted, the Eliza Service tab will show up in the…. Path: Agency Settings > Team > Edit User > UserImage 1 of 5 What this coversUsers who will edit FAQs and set up Eliza on the subaccount level need Eliza Service enabled in Agency Settings> Team> Edit User> User permissions.
Buttons and menus referenced Please Note
Next stepTo add the Eliza Service tab in the sub-account settings, You need to go to the user permissions and toggle the Eliza Service tab to grant access to that user. Once the access is granted, the Eliza Service tab will show up in the sub-account settings for you.

Please Note

To add the Eliza Service tab in the sub-account settings, You need to go to the user permissions and toggle the Eliza Service tab to grant access to that user. Once the access is granted, the Eliza Service tab will show up in the sub-account settings for you.
User Permission setting for Eliza (image 2 of 5) What this shows Users who will edit FAQs and set up Eliza on the subaccount level need Eliza Service enabled in Agency Settings> Team> Edit User> User permissions. What this shows Illustrates the "User Permission setting for Eliza" section of "Eliza Agent Platform Settings within the CRM". This screenshot appears in the "User Permission setting for Eliza" section of "Eliza Agent Platform Settings within the CRM". The text alongside this image reads: Users who will edit FAQs and set up Eliza on the subaccount level need Eliza Service enabled in Agency Settings> Team> Edit User> User permissions. The navigation path used here is Agency Settings > Team > Edit User > User. Immediately after, the guide continues: In cases where you don't want to let some conversations come into the Eliza Agent Platform, use the Eliza bypass tag. Path: Agency Settings > Team > Edit User > UserImage 2 of 5 What this coversUsers who will edit FAQs and set up Eliza on the subaccount level need Eliza Service enabled in Agency Settings> Team> Edit User> User permissions.
Buttons and menus referenced Please Note
Next stepIn cases where you don't want to let some conversations come into the Eliza Agent Platform, use the Eliza bypass tag.

Eliza By-pass tag

In cases where you don't want to let some conversations come into the Eliza Agent Platform, use the Eliza bypass tag.

Create a tag in Settings>Tag and choose that on Sub-Account Settings >> Eliza Service as the Eliza By-pass tag. Once chosen, any new inbound conversation will be checked against this tag to see whether it has to bypass the Eliza Agent Platform. Any inbound message will NOT be forwarded to EAP if this tag is in the contact.

If this conversation is already present in Eliza, then it will be removed from the agent queue when the agent tries to navigate to that conversation. This closed conversation will have the disposition as "Bypass tag assigned"

Eliza By-pass tag (image 3 of 5) What this shows If this conversation is already present in Eliza, then it will be removed from the agent queue when the agent tries to navigate to that conversation. What this shows Illustrates the "Eliza By-pass tag" section of "Eliza Agent Platform Settings within the CRM". This screenshot appears in the "Eliza By-pass tag" section of "Eliza Agent Platform Settings within the CRM". The text alongside this image reads: If this conversation is already present in Eliza, then it will be removed from the agent queue when the agent tries to navigate to that conversation. This closed conversation will have the disposition as "Bypass tag assigned". Immediately after, the guide continues: In some situations where you don't want all the conversations to come into Eliza, but only a few. In such cases, create a tag and configure that tag as a "Send to Eliza tag on Location Settings >> Eliza Service. - Screenshot is attached…. Image 3 of 5 What this coversIf this conversation is already present in Eliza, then it will be removed from the agent queue when the agent tries to navigate to that conversation. This closed conversation will have the disposition as "Bypass tag assigned"
Buttons and menus referenced Settings>TagSettings >> Eliza ServiceEliza By-pass tag"Bypass tag assigned"
Next stepIn some situations where you don't want all the conversations to come into Eliza, but only a few. In such cases, create a tag and configure that tag as a "Send to Eliza tag on Location Settings >> Eliza Service. - Screenshot is attached below.

Send to Eliza Tag

In some situations where you don't want all the conversations to come into Eliza, but only a few. In such cases, create a tag and configure that tag as a "Send to Eliza tag on Location Settings >> Eliza Service. - Screenshot is attached below. 

Using workflows, assign this tag to those contacts whose conversations should come into Eliza. 

Send to Eliza Tag (image 4 of 5) What this shows Using workflows, assign this tag to those contacts whose conversations should come into Eliza. What this shows Illustrates the "Send to Eliza Tag" section of "Eliza Agent Platform Settings within the CRM". This screenshot appears in the "Send to Eliza Tag" section of "Eliza Agent Platform Settings within the CRM". The text alongside this image reads: Using workflows, assign this tag to those contacts whose conversations should come into Eliza. Immediately after, the guide continues: By mistake, if you configure both Eliza By pass tag and the Send to Eliza tag, then the system will only honor the Send to Eliza tag just to be safe, so conversations don't get left behind. Image 4 of 5 What this coversUsing workflows, assign this tag to those contacts whose conversations should come into Eliza. Next stepBy mistake, if you configure both Eliza By pass tag and the Send to Eliza tag, then the system will only honor the Send to Eliza tag just to be safe, so conversations don't get left behind.
 Only the new incoming conversations with this tag will be sent to Eliza. If a contact is assigned the tag and you expect it appears in Eliza even without an inbound message, use the "Send to Eliza" workflow action. For details, navigate to "2. Conversations" on the left menu in this user guide and look for the "Send to Eliza setup " section on HL and Eliza Agent Platform.

Please Note:

By mistake, if you configure both Eliza By pass tag and the Send to Eliza tag, then the system will only honor the Send to Eliza tag just to be safe, so conversations don't get left behind.

Send to Eliza Agent Platform Action in GHL Customer Care Workflow

Contacts passing this workflow action are sent to the connected Eliza Account's Contacts.

Send to Eliza Agent Platform Action in GHL Customer Care Workflow (image 5 of 5) What this shows Contacts passing this workflow action are sent to the connected Eliza Account's Contacts. What this shows Illustrates the "Send to Eliza Agent Platform Action in GHL Customer Care Workflow" section of "Eliza Agent Platform Settings within the CRM". This screenshot appears in the "Send to Eliza Agent Platform Action in GHL Customer Care Workflow" section of "Eliza Agent Platform Settings within the CRM". The text alongside this image reads: Contacts passing this workflow action are sent to the connected Eliza Account's Contacts. Image 5 of 5 What this coversContacts passing this workflow action are sent to the connected Eliza Account's Contacts.

Was this guide helpful?

Related guides