WordPress customer context
WordPress customer context shows agents details about a visitor from your connected WordPress site, right next to the conversation. Agents start with what your site knows instead of asking the visitor to repeat it.
Open Conversations in the team sidebar, select a conversation, and look for the WordPress section in the visitor panel. See Live chat inbox.
Before you start
- The bot needs an enabled, connected WordPress integration.
- The visitor needs an email address on the conversation. Without one, the section doesn’t appear.
- You need permission to view the conversation in the inbox.
How a customer is matched
When an agent opens a conversation, FluentChat sends the visitor’s email address to the connector plugin on your WordPress site. The connector looks for a matching customer and returns their details. If nothing matches, the section says “No matching customer on your WordPress site.”
The connector plugin on your site decides which details it returns. FluentChat shows them as labeled fields and tables. Long tables show how many more rows exist, such as ”+ 3 more”.
Check where the email came from
Every result has a badge that tells agents how much to trust the match:
| Badge | What it means |
|---|---|
| Verified identity | The visitor’s identity was verified, for example through identity verification or a WordPress sign-in the connector recognizes. |
| Self-reported email | The visitor typed this email. It isn’t proof of who they are. |
When the section is hidden
The WordPress section appears only when there’s something to show. It’s hidden when:
- The bot has no WordPress connection, or the connection is Disabled.
- The connected site hasn’t finished connecting.
- The visitor has no email address.
Privacy and access
- Details appear only to agents. The WordPress section is part of the agent’s visitor panel in the inbox. Visitors don’t see it in the chat.
- Anyone who can view the conversation can see its details. Review your team’s roles before connecting a site with sensitive customer data.
- Lookups are cached. A successful lookup is reused for up to 15 minutes, so changes on your site can take that long to appear.
- Turning off the connection stops lookups. In Bot > Integrations, turn off the WordPress connection to stop sending visitor emails to your site.
Troubleshooting
Could not load customer details.
Possible cause: FluentChat couldn’t reach your WordPress site, or the connector returned an error.
Solution: Select Retry. If it keeps failing, check the connection status in Bot > Integrations. See WordPress integration.
No matching customer on your WordPress site.
Possible cause: Your WordPress site has no customer with the visitor’s email address.
Solution: Check the visitor’s email in the visitor panel. If the customer changed their email on your site recently, wait up to 15 minutes for the cached result to expire.