Fluent Support tickets
The Fluent Support action lets your bot help customers with their own support tickets on your WordPress site. Signed-in customers can see their tickets and, with their confirmation, create, reply to, close or reopen them.
Open Bot > Actions > Action library > Fluent Support.
Best for: customers who want to check or update their tickets without leaving the chat.
Common requests:
- “What’s the status of my ticket?”
- “Open a ticket about my license not activating.”
- “Reply to my last ticket and say the fix worked.”
Before you start
- You need the Owner, Team Admin or Bot Admin role.
- This bot’s WordPress integration must be set up and enabled. See WordPress integration.
- Fluent Support must be installed on the connected WordPress site.
- The Fluent Support tickets action must be available on your FluentChat account. It’s off by default in FluentChat’s configuration; if you can’t enable it after a successful check, contact FluentChat through Feedback.
- In WordPress, allow access under FluentChat → Integrations → Fluent Support.
- Customers must be signed in to your WordPress site. Ticket access comes only from their signed-in WordPress account.
Add the Fluent Support action
-
Open the template. In Action library, select Fluent Support, then Start customizing.
-
Name the action. In General, enter an Action name and review When to use.
-
Check access. In Fluent Support access, select Check access. When it succeeds, the editor says “Support access verified. Review the permissions below.”
-
Choose permissions. Under Customer permissions, select what customers may do. Then select at least one mailbox under Support mailboxes and, optionally, categories under Support products. Select Save and continue.
-
Choose channels. Turn on the website channels that may use the action, then select Save, or Save & enable.
-
Enable the action. Turn on Enable action if you didn’t use Save & enable.
Settings
| Setting | What it does |
|---|---|
| Action name | The name the bot uses to call this action. Use 3–64 characters. Spaces become underscores. |
| When to use | Tells the bot how to help with tickets. The default tells it to read only authorized public ticket conversations and never claim a change without a confirmed result. Select Reset to restore it. |
| Check access | Reads what WordPress allows. “Checking access does not create a customer or a ticket.” |
| Customer permissions | The operations customers may use. An operation that WordPress doesn’t support shows Unavailable in WordPress. Select at least one. |
| Support mailboxes | The mailboxes the bot can read and create tickets in. Select at least one, up to 50. Uncategorised tickets in selected mailboxes are included. |
| Support products | Optional. Product categories defined in Fluent Support, up to 50. |
Customer permissions
| Permission | What customers can do |
|---|---|
| List own tickets | See a list of their own tickets. |
| Read own public conversations | Read the public replies on one of their tickets. |
| Create tickets with confirmation | Create a ticket from a draft the bot prepares and the customer reviews. |
| Reply to own tickets | Add a reply. Replying to a closed ticket reopens it, and the card says so. |
| Close own tickets | Close a ticket when the issue is resolved. |
| Reopen own tickets | Reopen a closed ticket. |
| Rate eligible agent responses | Like or dislike an agent’s reply, when the support configuration allows it. |
What the customer sees
- Reading tickets: The bot answers from the customer’s current tickets and refers to them by ticket number.
- Creating a ticket: The bot asks about the problem, then prepares a draft with a subject and description based on what the customer said. The chat shows a review card with Submit ticket. Nothing is sent until the customer selects it.
- Changing a ticket: Replies, closing, reopening and feedback each show a card with Send reply, Close ticket, Reopen ticket or Save feedback. Typing “yes” isn’t a confirmation.
- Not signed in: The bot asks the customer to sign in on your WordPress site, and shares your support portal link when one is available.
If an outcome is unknown, the card offers Check status. While a new ticket’s outcome is unknown, the bot doesn’t prepare another ticket for the same issue.
Channel compatibility
| Channel | Supported |
|---|---|
| Chat bubble | Yes |
| Help page | Yes |
| Center stage | Yes |
| API | No |
| Fluent Support | No |
Limitations
- No ticket attachments in the chat. Customers can’t add files to tickets from the chat. The bot can share the ticket’s portal link so they can continue there.
- Own tickets only. Customers see only their own tickets and only public replies.
- Signed-in customers only. An email address or code typed in the chat isn’t proof of account ownership.
- Every change needs the customer’s confirmation.
- Not live chat. To connect a visitor with an agent in FluentChat, use the Live chat action.
Troubleshooting
Support setup can be saved. Customer tools will be available after integration verification.
Possible cause: Your support integration hasn’t been verified for customer tools yet.
Solution: Save the setup. You can enable the action once verification is complete and Check access shows the permissions as available.
Allow access in WordPress under FluentChat → Integrations → Fluent Support, then check access here.
Possible cause: The connector hasn’t allowed Fluent Support access for FluentChat.
Solution: Allow access in WordPress, then select Check access again.
No allowed mailbox options. Check permissions in WordPress.
Possible cause: The connector allows no mailboxes.
Solution: Allow at least one mailbox in WordPress, then select Check access.