optlo.com<\/a>.<\/p>\n\nExternal services<\/h3>\n\n
This plugin connects your website to Optlo, a hosted customer support service operated by Optlo. It is required for the plugin to do anything: the chat interface itself is served by Optlo, not by your site.<\/p>\n\n
What is sent, and when<\/strong><\/p>\n\nOn every page where the messenger is enabled, the visitor's browser loads a script from https:\/\/optlo.com\/embed\/v1\/<your workspace ID><\/code> and opens a connection to Optlo. This happens for every visitor to those pages, including visitors who never open the chat.<\/p>\n\nOptlo receives, as a normal consequence of the visitor's browser making that request: the page address the messenger is loaded on, the visitor IP address, the browser user agent, and a cookie Optlo sets to recognise a returning visitor across page loads. Anything a visitor types into the messenger is sent to Optlo so it can be answered.<\/p>\n\n
If you turn on \"Identify signed-in users\"<\/strong><\/p>\n\nThis setting is off by default. When it is on, the browser of each signed-in WordPress user fetches a short-lived token from your own site and passes it to the messenger, which sends it to Optlo. The token carries that user's WordPress user ID, email address, display name, username, first role, registration date, this site's host name, and avatar URL if avatars are enabled and the URL is https. Optlo uses it to attach the conversation to that user in your Optlo inbox. Visitors who are not signed in, and users in roles you exclude, are not identified. The optlo_user_claims<\/code> filter lets a developer change or remove any of these fields, or add organizations the user belongs to.<\/p>\n\nBeyond that, this plugin sends nothing else. It does not transmit your posts, site content, or the accounts of users who are not signed in.<\/p>\n\n
The plugin also sets one cookie of its own on your site, named optlo_signed_in<\/code>, for signed-in users only. It holds the fixed value 1<\/code>, identifies nobody, and only tells the browser that it is worth asking your site for a token. It is set when someone signs in and removed when they sign out. Visitors who are not signed in never receive it, so it does not affect page caching for them. It is never sent to Optlo.<\/p>\n\nTerms and privacy<\/strong><\/p>\n\n\n- Terms of service: https:\/\/optlo.com\/terms<\/li>\n
- Privacy policy: https:\/\/optlo.com\/privacy<\/li>\n<\/ul>\n\n\n
\n- Install and activate the plugin.<\/li>\n
- In your Optlo dashboard, go to Settings, Workspace, Profile and copy the workspace ID.<\/li>\n
- In WordPress, go to Settings, Optlo, paste the workspace ID and save.<\/li>\n
- Visit your site. The chat launcher appears in the corner.<\/li>\n<\/ol>\n\n\n
\nThe messenger is not showing up<\/h3><\/dt>\nCheck Settings, Optlo for a notice explaining why. The two common causes are that WordPress reports this site as something other than production, or that the site address changed since the workspace ID was saved.<\/p><\/dd>\n
I moved my site to a new domain<\/h3><\/dt>\nSettings, Optlo shows a notice that the site was connected under its old address. If you moved the site, click \"This site moved here\" and the messenger loads again. If you are looking at a copy of another site, click \"Disconnect\" instead, so conversations from the copy do not reach your live inbox.<\/p><\/dd>\n
Why does it refuse to load on my staging site?<\/h3><\/dt>\nStaging sites are normally created by copying the production database, which copies your workspace ID with it. Without this check, test conversations from a staging site would arrive in your live inbox. Untick \"Only load on production\" under Settings, Optlo if you want it there.<\/p>\n\n
Note that a database copy also carries the private key this site signs identity tokens with, protected by the security keys in wp-config.php. Anyone who holds both a copy of the database and those keys can sign tokens as your users. If you hand a copy to someone who should not have that power, generate a new key from Settings, Optlo afterwards.<\/p><\/dd>\n
Can I open the chat from a button or link?<\/h3><\/dt>\nYes. Use the [optlo]<\/code> shortcode, or the \"Optlo chat button\" block. Both accept a label and an opening message.<\/p><\/dd>\nCan developers change what is sent about a user?<\/h3><\/dt>\nYes. The optlo_user_claims<\/code> filter receives the user payload before it is signed. It can change or remove any field, add attributes, or add up to ten organizations, each with an id<\/code>, a name<\/code> and optional attrs<\/code>, which Optlo shows alongside the user. Anything Optlo would reject is dropped rather than failing the whole payload. The optlo_should_load<\/code> filter can suppress the messenger entirely for a request.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.3<\/h4>\n\n\n- Added the plugin's page on optlo.com to the plugin header. No functional changes.<\/li>\n<\/ul>\n\n
1.0.2<\/h4>\n\n\n- The messenger script is added as soon as the page is parsed instead of after every image has loaded, so it appears sooner on slow pages.<\/li>\n
- A signed-in user's identity is no longer lost when the token arrives after the messenger has started.<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Renamed to \u201cOptlo \u2013 AI Customer Support, Live Chat & Chatbot\u201d. No functional changes.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- First release.<\/li>\n<\/ul>","raw_excerpt":"Deploy AI support agents on your WordPress site. Adds the Optlo messenger to your pages in a couple of clicks.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/367125","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=367125"}],"author":[{"embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/optlo"}],"wp:attachment":[{"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=367125"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=367125"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=367125"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=367125"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=367125"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=367125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}