Keep in mind there may be a delay between when someone becomes active or recently active and when they're shown as active or recently active. What does a green dot mean for Facebook Pages? Facebook Pages that have been online recently, or have a record of being quick and responsive in their replies to messages on Facebook, Messenger, or WhatsApp will have a. Was this helpful? Related Articles.
You can choose which friends see you as online, block any contact or log out and receive any sent messages in your Messages inbox.
Facebook removed the idle symbol in Facebook chat, so you won't be shown as idle when you aren't in the Facebook window. Facebook used to display a blue half-moon symbol to let users know that a person on the contact list was logged into chat but away from Facebook.
As of late , however, that functionality was removed. Now users with green circles are available, users with mobile phone icons can be reached on mobile devices and those with no sign next to their names can be reached through Facebook messages, which can be sent through the chat window.
The contact list on Facebook is split into two parts. The first part, the top list, shows friends you've recently interacted with or friends that you interact with on a regular basis. As soon as the user clicks on a post back CTA owned by app A, the thread ownership will go back to app A. It will always have a secondary role. A: Yes, agent using Facebook Page Inbox will be able to send a message to the user when the user is engaged with the automation app.
After the message is sent the thread control is passed to the Facebook Page Inbox if the admin responds to the user inquiry from the Main folder.
The API will return null if the thread is in Idle mode. A: Welcome message set on the ad will take precedence over Icebreakers set on the page. People will see the welcome message set on the ad once they click the ad. A: Icebreakers are set at the page level. When a M. For businesses who want their users to enter the ad experience vs. Docs Tools Support. Messenger Platform. Handover Protocol Developers who want to use Handover Protocol or have been using Previous version of Handover Protocol must refer to the recent improvements and behaviors we have introduced to Handover Protocol.
Using the Handover Protocol To familiarize yourself with Handover protocol, we have summarized the key actions you could take. Subscribe apps to your page Retrieving the list of non-primary receiver apps Only the Facebook app with the Primary Receiver app role may retrieve the list of all messaging apps connected to the page.
If a Primary app is configured, by default all new threads will be sent to the Primary Receiver app. Pass metadata between apps There may be scenarios where apps may need to pass additional data to other apps connected to the page without passing or taking thread control. Field would not be present. If the caller is a non-primary app, the app Id will have their value if the thread is owned by them, else it would be null If the thread is in idle mode the app Id would always be null in the response.
The expiration field would only be included if the thread is not in idle mode i. Key Handover Protocol behaviors Exclusive Mode Whenever an app is in control of the thread, no other app would be able to interject the conversation by sending messages to the thread.
The following scenarios are when you should expect a thread to be in idle mode or non-controlled mode: When Primary app is not set, all threads start in idle mode. After thread ownership expiration default expiration time is 24 hours of inactivity after an app takes control The controlling app explicitly releases their ownership If a Primary app is set and a user messages a page when thread is idle, then the Primary app gets the control of the thread.
Human Agent Tag Apps with Human Agent tag permission will be able to interject the conversation the user might be having with another app. This is done since app A is configured to handle that postback unlike app B which may error out. If thread is in idle mode, thread will remain idle.
If thread is owned by app A, thread will remain with app A. Otherwise any apps can set page level menu. Also in case a user taps a menu item on a menu that was set by another app, thread control will pass to that app that set the menu in the first place. If thread is in idle mode, the thread will not pass, it will only happen when thread is owned by an app Same as Postback CTA behavior above.
Default Behavior Without utilizing Handover Protocol By default, if no app takes control of the thread all subscribed apps may respond at any given time. Handover Protocol API availability based on app type The following is a summary of the available actions for Primary and other apps.
Migration Guide If you already use handover protocol today, here is a summary of the changes you need to account for given the improvements we are introducing to Handover protocol. Roles are optional to enable HOP. Brand can choose to assign an app as primary if needed. Entry points Always default to primary app. Any entry point can be associated with an app. CTM to start with. Facebook Page Inbox Marking conversations Done releases thread to Primary app Transferring conversation from Done to Inbox would request control from Primary app Marking Done releases thread to Primary app if it is set, else releases to idle mode Transferring to Inbox would take thread control from any app Secondary app powers Cannot pass control to another secondary app Not applicable since there are no secondary apps.
All events would be sent on standby channel for non-controlling apps. Use Cases Use case 1: A business wants to use an automated experience for simple FAQs but wants to transfer the customer to a live support agent for complex inquiries. By default, all thread ownership will go to the automation app.
Live agent app should not interfere with the automation flow unless thread control is passed. If the live agent needs to interject the conversation, leverage Request Thread Control API to notify the automation app that they want to interject the thread. Once live agent app has completed the conversation, pass back thread control to the automation app. If the live agent app needs more time to handle user enquires, leverage the Extend Thread Control API to extend thread ownership.
Optionally, you can leverage the Pass Metadata API to pass any metadata between apps without changing thread ownership. This will release the thread control to primary app if any or set as idle mode.
Setup the ads via ads manager by following the Handover Protocol for ads that click to Messenger guide. Ensure that the live agent app respect the thread ownership logic. Ensure correct implementation of webhooks received from standby channel. When an escalation to a live agent is needed, the automation app can use pass thread control to the live agent app.
Best Practices We recommend automated experiences to be set as the primary receiver app and any live agent app to be the non-primary app. Do not interject or interrupt if you do not have control. What Are "Idle" Friends on Facebook? By Lara Webster. Chat Feature "Idle" status refers only to friends in regard to the social networking site's chat feature. Time Frame Friends are considered idle on Facebook when they have been completely inactive on the site for 10 minutes or longer.
Symbols An idle friend is represented by a light gray half moon next to her name in your list of friends in chat. Receiving Messages While an idle Facebook friend is not actively on the site, because she is still online, your messages will pop up on his computer screen.
0コメント