Skip to content
This site is under construction. Content, screenshots, and workflows may change at any time.

Fluent Support channel

The Fluent Support channel brings your bot’s knowledge to your WordPress support desk. The FluentChat connector plugin uses it to “Generate support answers from the Fluent Support plugin in WordPress.”

Open Bot > Channels > Fluent Support. The page has three sections: WordPress connection, Instructions, and Actions.

Before you start

  • You need bot edit access to create, rotate, or revoke the credential and to turn the channel on: Owner, Team Admin, or Bot Admin. Other roles see “Bot edit access is needed to manage this connection.”
  • Your WordPress site needs the Fluent Support plugin and the FluentChat connector plugin.
  • The site must be connected through the WordPress integration, and that connection must be enabled. It can belong to this bot or another bot in the same team.

Connect Fluent Support

  1. Create the credential. Under WordPress connection, select Create connection. The new credential appears once: “Copy this credential now. It cannot be shown again.”

  2. Copy it. Select Copy credential, or Show credential to see it, then select Done. The section now shows Active credential ending in and the last four characters.

  3. Turn the channel on. In Bot > Channels, turn on the Fluent Support availability switch. Creating the credential doesn’t turn the channel on.

  4. Paste it in WordPress. The app says: “In WordPress, open FluentChat → Integrations → FluentSupport, then paste it under Support agent assistant.” Then verify it in the connector.

The channel must be on before the connector can verify: “This credential is for this bot only. Enable the Fluent Support channel from Channels before verifying it in the WordPress connector.”

WordPress connection

State or controlWhat it means
No active credentialNo credential exists. Select Create connection to make one.
Active credential ending inA credential exists. Only its last four characters are shown.
Rotate credentialCreates a new credential. “The current credential stops working immediately. You must update WordPress with the new one.” Select Confirm rotation to continue.
Revoke credentialRemoves the credential. “WordPress will stop receiving drafts, summaries, history, and ratings through this credential. Existing conversations are kept.” Select Confirm revocation to continue.

This credential is not a team API key. It starts with fci_, works only for this bot, and authorizes only the Fluent Support channel.

Instructions

With Use global instructions on, Fluent Support answers follow the bot’s global instructions. Turn it off to write instructions only for your support desk, such as tone or sign-off rules. See Instructions.

Actions

The Actions section sets which configured actions this channel can use. Knowledge search is always available.

Only actions that work without a website visitor appear here: Web search, FluentCart, and custom actions that read from an API. The Fluent Support tickets action works on website channels, not here.

Limitations

  • The credential works for one bot. Each bot that serves Fluent Support needs its own credential.
  • The credential is shown only once. If you lose it, rotate it and paste the new one into WordPress.
  • Rotating or revoking takes effect immediately. WordPress stops working with the old credential until you paste a new one.
  • Creating or rotating a credential doesn’t change availability. Turn the channel on in Bot > Channels.

Troubleshooting

The WordPress connector can’t verify the credential

Possible cause: The Fluent Support channel is disabled, the site’s WordPress connection is disabled or not connected, or the site is connected to a bot in another team.

Solution: Turn on Fluent Support availability in Bot > Channels. Check that Bot > Integrations > WordPress shows Connected for a bot in the same team, then verify again.

Could not load the credential. Check your bot access and reload.

Possible cause: Your account can’t read this bot’s credential status, or the request failed.

Solution: Select Reload credential status. If it keeps failing, ask a team admin to check your access to this bot.

Next steps