Safe notices delivery - Revision history

GlaznahGassner at 17:47, 9 March 2019

2019-03-09T17:47:16Z

← Older revision		Revision as of 17:47, 9 March 2019
Line 1:		Line 1:
	How to ensure your notices delivery?		How to ensure your notices delivery?

-	1. Make sure that your attachments are '''copy+trans'''.	+	# Make sure that your attachments are '''copy+trans'''.
-	2. Make sure your bot is within [[Message Limits\|Linden Messaging Limits]].	+	# Make sure your bot is within [[Message Limits\|Linden Messaging Limits]].
-	3. Don't send notices too fast. [[Notices without spam\|Let SmartBots do delays]].	+	# Don't send notices too fast. [[Notices without spam\|Let SmartBots do delays]].

	== Verify notices delivery ==		== Verify notices delivery ==
Line 9:		Line 9:
	Whenever you create periodic or one-time notices, you can view their delivery stats.		Whenever you create periodic or one-time notices, you can view their delivery stats.

-	[[Image:Delivery_Stats2.png\|link=\|center\|]]	+	[[Image:Delivery_Stats2.png\|link=\|center\|frame]]

-	Check this page to make sure your notice is not considered s	+	Check this page to make sure your notice is not considered spam: [[Notices without spam]]

	[[Category: Group Notices Service]]		[[Category: Group Notices Service]]
	__NOTOC__		__NOTOC__

GlaznahGassner at 17:46, 9 March 2019

2019-03-09T17:46:43Z

← Older revision		Revision as of 17:46, 9 March 2019
Line 1:		Line 1:
-	~~== General Information ==~~	+	How to ensure your notices delivery?

-	~~As of January 30th, 2014 - Linden Labs restricted every Scripted Agent (otherwise known as bots) with messaging limits~~. ~~Every~~ bot is ~~restricted with 5,000 messages daily. More information on messaging limits are available~~ [[Message Limits\|~~here~~]]	+	1. Make sure that your attachments are '''copy+trans'''.
		+	2. Make sure your bot is within [[Message Limits\|Linden Messaging Limits]].
		+	3. Don't send notices too fast. [[Notices without spam\|Let SmartBots do delays]].

-	==~~= How it works with notices ===~~	+	== Verify notices delivery ==
-		+
-	~~For example, when you are sending one notice to a group with 3,000 members, your bot will have 2,000 messages remaining. So each member of the group counts as '''one individual message'''~~	+
-		+
-	~~== Using Shared Bots ==~~	+
-		+
-	~~System Bots are managing your groups when using our [[Group Services\|Separate Group Services]] for L$ 79/week. When you are using shared bots, you also share bots messaging with other customers.~~	+
-		+
-	* You should be fine by sending 2-3 notices daily.	+
-	* Calculate how many notices you can send based on number of members your group has	+
-	* They can successfully deliver notices while being used by '''less customers'''([http://mysmartbots.com/en/contacts.html Contact us] to find out which bot is being used less)	+
-		+
-	~~== Using Personal Bots ==~~	+
-		+
-	~~Personal Bots are your alternative avatars that you can host with SmartBots. More information for Personal Bots is available [[Personal_Bots\|by this link]]~~	+
-		+
-	* Personal Bots have their own messaging limits. (No sharing)	+
-	* You should be fine with sending more notices than shared bots	+
-	* Calculate how many notices you can send based on number of members your group has	+
-	* '''You can also use QubicBot for no limits''': [[QubicBot Interface\|More information here]]	+
-		+
-	~~== Reliable~~ notices delivery ==	+

	Whenever you create periodic or one-time notices, you can view their delivery stats.		Whenever you create periodic or one-time notices, you can view their delivery stats.

	[[Image:Delivery_Stats2.png\|link=\|center\|]]		[[Image:Delivery_Stats2.png\|link=\|center\|]]
		+
		+	Check this page to make sure your notice is not considered s

	[[Category: Group Notices Service]]		[[Category: Group Notices Service]]
	__NOTOC__		__NOTOC__

QuincyJohnes at 10:30, 29 January 2017

2017-01-29T10:30:16Z

← Older revision		Revision as of 10:30, 29 January 2017
Line 1:		Line 1:
-	Second Life servers may restrict the amount of notices delivered to a group. The actual limits are not known and seems to vary from group to group. Some precautions will help you to increase the success of your notice delivery.	+	== General Information ==

-	~~== Official~~ limits ==	+	As of January 30th, 2014 - Linden Labs restricted every Scripted Agent (otherwise known as bots) with messaging limits. Every bot is restricted with 5,000 messages daily. More information on messaging limits are available [[Message Limits\|here]]

-	~~The only official~~ notices ~~limit is 2500 notices per avatar.~~	+	=== How it works with notices ===

-	~~== Experimental results ==~~	+	For example, when you are sending one notice to a group with 3,000 members, your bot will have 2,000 messages remaining. So each member of the group counts as '''one individual message'''

-	The official limits seems very optimistic, but sometimes you may be faced with more strict limitations applied by SL. Your notice may get silently discarded: usually this happens after 20 repetitive notices (nevertheless, usually you can send 30 or even 42 simultaneous notices without being capped).	+	== Using Shared Bots ==

-	~~=== Mysterious error message ===~~	+	System Bots are managing your groups when using our [[Group Services\|Separate Group Services]] for L$ 79/week. When you are using shared bots, you also share bots messaging with other customers.

-	~~Under some rare circumstances you may get the following system message after~~ sending ~~a notice~~:	+	* You should be fine by sending 2-3 notices daily.
		+	* Calculate how many notices you can send based on number of members your group has
		+	* They can successfully deliver notices while being used by '''less customers'''([http://mysmartbots.com/en/contacts.html Contact us] to find out which bot is being used less)

-	~~''"Failed to send group notice. It has been too soon since the last group notice has been sent. Please try again after a few minutes."''~~	+	== Using Personal Bots ==

-	~~We've faced this message while sending 10 or more repetitive messages to the '''same group'''~~. ~~After receiving~~ this ~~message you should stop sending all notices. SL unblocks your avatar in about 10 minutes after the last notice.~~	+	Personal Bots are your alternative avatars that you can host with SmartBots. More information for Personal Bots is available [[Personal_Bots\|by this link]]

-	~~'''As of 06/2013, SL support staff does not know any details about this error message~~.~~'''~~	+	* Personal Bots have their own messaging limits. (No sharing)
-		+	* You should be fine with sending more notices than shared bots
-	* ~~It seems that a 30 second delay helps to avoid this message. Lower delays' impact varies from group to group.~~	+	* Calculate how many notices you can send based on number of members your group has
-	* ~~It does not matter~~ how ~~much~~ notices your ~~avatar~~ has ~~sent before. We've received this message while using an avatar which was offline for several months.~~	+	* '''You can also use QubicBot for no limits''': [[QubicBot Interface\|More information here]]
-	* ~~SL viewer version does not matter (Phoenix, SL Viewer, SmartBots engine, Pikkubot). We~~'~~ve seen this message after sending 10 messages using the native SL Viewer.~~	+

	== Reliable notices delivery ==		== Reliable notices delivery ==

-	~~The best way to ensure reliable~~ delivery ~~is to add a delay after each notice~~.	+	Whenever you create periodic or one-time notices, you can view their delivery stats.

-	~~SmartBots periodic notices delivery engine allows you setting custom delay when you send notices to multiple groups (10+)~~.	+	[[Image:Delivery_Stats2.png\|link=\|center\|]]

	[[Category: Group Notices Service]]		[[Category: Group Notices Service]]
	__NOTOC__		__NOTOC__

Chevonn Edelmann at 00:20, 27 June 2013

2013-06-27T00:20:44Z

← Older revision		Revision as of 00:20, 27 June 2013
Line 28:		Line 28:

	SmartBots periodic notices delivery engine allows you setting custom delay when you send notices to multiple groups (10+).		SmartBots periodic notices delivery engine allows you setting custom delay when you send notices to multiple groups (10+).
		+
		+	[[Category: Group Notices Service]]
	__NOTOC__		__NOTOC__

Chevonn Edelmann at 22:16, 26 June 2013

2013-06-26T22:16:37Z

← Older revision		Revision as of 22:16, 26 June 2013
Line 1:		Line 1:
-	Second Life servers may restrict the amount of notices delivered to a group. The actual limits are not known and seems to vary from group to group. Some precautions will help to increase your delivery ~~success~~.	+	Second Life servers may restrict the amount of notices delivered to a group. The actual limits are not known and seems to vary from group to group. Some precautions will help you to increase the success of your notice delivery.

	== Official limits ==		== Official limits ==

-	The only official notices limit is 2500 notices per ~~by single~~ avatar.	+	The only official notices limit is 2500 notices per avatar.

	== Experimental results ==		== Experimental results ==
Line 13:		Line 13:
	Under some rare circumstances you may get the following system message after sending a notice:		Under some rare circumstances you may get the following system message after sending a notice:

-	''"Failed to send group notice. It has been too soon since the ~~kast~~ group notice has been sent. Please try again after a few minutes."''	+	''"Failed to send group notice. It has been too soon since the last group notice has been sent. Please try again after a few minutes."''

-	We've faced this message while sending 10 ~~and~~ more repetitive messages to the '''same group'''. After receiving this message you should stop sending all notices. SL unblocks your avatar in about 10 minutes after the last notice.	+	We've faced this message while sending 10 or more repetitive messages to the '''same group'''. After receiving this message you should stop sending all notices. SL unblocks your avatar in about 10 minutes after the last notice.

	'''As of 06/2013, SL support staff does not know any details about this error message.'''		'''As of 06/2013, SL support staff does not know any details about this error message.'''

Chevonn Edelmann at 08:51, 26 June 2013

2013-06-26T08:51:42Z

GlaznahGassner at 17:27, 21 June 2013

2013-06-21T17:27:06Z

← Older revision		Revision as of 17:27, 21 June 2013
Line 7:		Line 7:
	== Experimental results ==		== Experimental results ==

-	The official limits ~~are~~ very optimistic, but sometimes you may face with more strict limitations applied by SL. Your notice may get silently discarded, usually this happens after 20 repetitive notices (nevertheless, usually you can send 30 or even 42 simultaneous notices without being capped).	+	The official limits seems very optimistic, but sometimes you may face with more strict limitations applied by SL. Your notice may get silently discarded: usually this happens after 20 repetitive notices (nevertheless, usually you can send 30 or even 42 simultaneous notices without being capped).

	=== Mysterious error message ===		=== Mysterious error message ===
Line 15:		Line 15:
	''"Failed to send group notice. It has been too soon since another group notice has been sent. Please try again after a few minutes."''		''"Failed to send group notice. It has been too soon since another group notice has been sent. Please try again after a few minutes."''

-	We've faced this message while sending 10 and more repetitive messages to the same group. After receiving this message you should stop sending any notices. SL unblocks your avatar in about 10 minutes after a last notice.	+	We've faced this message while sending 10 and more repetitive messages to the '''same group'''. After receiving this message you should stop sending any notices. SL unblocks your avatar in about 10 minutes after a last notice.

	'''As of 06/2013, SL support staff does not know any details about this error message.'''		'''As of 06/2013, SL support staff does not know any details about this error message.'''

-	It seems that 30 seconds delay helps to avoid this message. Lower delays' impact varies.	+	* It seems that 30 seconds delay helps to avoid this message. Lower delays' impact varies from group to group.
		+	* It does not matter how much notices your avatar has sent before. We've received this message while using avatar which was offline for several months.
		+	* SL viewer version does not matter (Phoenix, SL Viewer, SmartBots engine, Pikkubot). We've seen this message after sending 10 messages using native SL Viewer.

	== Reliable notices delivery ==		== Reliable notices delivery ==

GlaznahGassner at 17:19, 21 June 2013

2013-06-21T17:19:04Z

← Older revision		Revision as of 17:19, 21 June 2013
Line 26:		Line 26:

	SmartBots periodic notices delivery engine allows you setting custom delay when you send notices to multiple groups (10+).		SmartBots periodic notices delivery engine allows you setting custom delay when you send notices to multiple groups (10+).
		+	__NOTOC__

GlaznahGassner: Created page with "Second Life servers may restrict the amount of notices delivered to the group. The actual limits are not known and seems to vary from group to group. Some precautions will help t..."

2013-06-21T17:18:52Z

Created page with "Second Life servers may restrict the amount of notices delivered to the group. The actual limits are not known and seems to vary from group to group. Some precautions will help t..."

New page

Second Life servers may restrict the amount of notices delivered to the group. The actual limits are not known and seems to vary from group to group. Some precautions will help to increase your delivery success.

== Official limits ==

The only official notices limit is 2500 notices per by single avatar.

== Experimental results ==

The official limits are very optimistic, but sometimes you may face with more strict limitations applied by SL. Your notice may get silently discarded, usually this happens after 20 repetitive notices (nevertheless, usually you can send 30 or even 42 simultaneous notices without being capped).

=== Mysterious error message ===

Under some rare circumstances you may get the following system message after sending a notice:

''"Failed to send group notice. It has been too soon since another group notice has been sent. Please try again after a few minutes."''

We've faced this message while sending 10 and more repetitive messages to the same group. After receiving this message you should stop sending any notices. SL unblocks your avatar in about 10 minutes after a last notice.

'''As of 06/2013, SL support staff does not know any details about this error message.'''

It seems that 30 seconds delay helps to avoid this message. Lower delays' impact varies.

== Reliable notices delivery ==

The best way to ensure the reliable delivery is to add a delay after each notice.

SmartBots periodic notices delivery engine allows you setting custom delay when you send notices to multiple groups (10+).

← Older revision		Revision as of 08:51, 26 June 2013
Line 1:		Line 1:
-	Second Life servers may restrict the amount of notices delivered to ~~the~~ group. The actual limits are not known and seems to vary from group to group. Some precautions will help to increase your delivery success.	+	Second Life servers may restrict the amount of notices delivered to a group. The actual limits are not known and seems to vary from group to group. Some precautions will help to increase your delivery success.

	== Official limits ==		== Official limits ==
Line 7:		Line 7:
	== Experimental results ==		== Experimental results ==

-	The official limits seems very optimistic, but sometimes you may ~~face~~ with more strict limitations applied by SL. Your notice may get silently discarded: usually this happens after 20 repetitive notices (nevertheless, usually you can send 30 or even 42 simultaneous notices without being capped).	+	The official limits seems very optimistic, but sometimes you may be faced with more strict limitations applied by SL. Your notice may get silently discarded: usually this happens after 20 repetitive notices (nevertheless, usually you can send 30 or even 42 simultaneous notices without being capped).

	=== Mysterious error message ===		=== Mysterious error message ===
Line 13:		Line 13:
	Under some rare circumstances you may get the following system message after sending a notice:		Under some rare circumstances you may get the following system message after sending a notice:

-	''"Failed to send group notice. It has been too soon since ~~another~~ group notice has been sent. Please try again after a few minutes."''	+	''"Failed to send group notice. It has been too soon since the kast group notice has been sent. Please try again after a few minutes."''

-	We've faced this message while sending 10 and more repetitive messages to the '''same group'''. After receiving this message you should stop sending ~~any~~ notices. SL unblocks your avatar in about 10 minutes after a last notice.	+	We've faced this message while sending 10 and more repetitive messages to the '''same group'''. After receiving this message you should stop sending all notices. SL unblocks your avatar in about 10 minutes after the last notice.

	'''As of 06/2013, SL support staff does not know any details about this error message.'''		'''As of 06/2013, SL support staff does not know any details about this error message.'''

-	* It seems that 30 ~~seconds~~ delay helps to avoid this message. Lower delays' impact varies from group to group.	+	* It seems that a 30 second delay helps to avoid this message. Lower delays' impact varies from group to group.
-	* It does not matter how much notices your avatar has sent before. We've received this message while using avatar which was offline for several months.	+	* It does not matter how much notices your avatar has sent before. We've received this message while using an avatar which was offline for several months.
-	* SL viewer version does not matter (Phoenix, SL Viewer, SmartBots engine, Pikkubot). We've seen this message after sending 10 messages using native SL Viewer.	+	* SL viewer version does not matter (Phoenix, SL Viewer, SmartBots engine, Pikkubot). We've seen this message after sending 10 messages using the native SL Viewer.

	== Reliable notices delivery ==		== Reliable notices delivery ==

-	The best way to ensure ~~the~~ reliable delivery is to add a delay after each notice.	+	The best way to ensure reliable delivery is to add a delay after each notice.

	SmartBots periodic notices delivery engine allows you setting custom delay when you send notices to multiple groups (10+).		SmartBots periodic notices delivery engine allows you setting custom delay when you send notices to multiple groups (10+).
	__NOTOC__		__NOTOC__