• Does anyone know why this is?
• Should I be seeing the delivery receipts mentioned in the resource center? I am not right now, and this seems odd.

• Does anyone know why this is?
• Should I be seeing the delivery receipts mentioned in the resource center? I am not right now, and this seems odd.

• Does anyone know why this is?
• Should I be seeing the delivery receipts mentioned in the resource center? I am not right now, and this seems odd.

@Peter Stoltenberg
​I believe this documentation page was trying to help identify failure delivery receipts, more than anything. But i can see how in it's current state, it can cause confusion. As it does show some other non failure statuses on it too (queued, sent, etc), but not all. We will look at adding the missing ones, thanks for bringing it up.
As for received message status you saw, this is there to represent inbound messages to Genesys Cloud, so this would not exactly be considered a delivery receipt in the intended nature of the definition. You should only see this status on the customer purpose on the Genesys Cloud Conversation (inbound messages). And would be the only status you see for those messages. If the message didn't come to us (no delivery; due to carrier failure for instance) then it wouldn't exist on the Conversation at all. We couldn't represent the message with a delivery receipt, as it wouldn't exist. That's why received is the only status for those messages.
For outbound messages like from a campaign purpose, then you should see some of the various delivery receipts listed on that page, including delivery-success. Which is not listed on that page yet, as you said. And also possibly some delivery-failed statuses, which would also contain an errorInfo object on the Conversation representing some of the reasons why the message failed (which are listed on that page), using errorPayload field on the Conversation.

Hope this helps,
Greg

• Does anyone know why this is?
• Should I be seeing the delivery receipts mentioned in the resource center? I am not right now, and this seems odd.

Thanks, Greg.

That is helpful!

Do you know if there will be specific Digital Campaign reports? My org currently has the BETA for the New Campaign Performance Views, which looks great for Voice calls, but maybe not as applicable to the Digital pieces. Do you know?

Thanks,

@Peter Stoltenberg
​I believe this documentation page was trying to help identify failure delivery receipts, more than anything. But i can see how in it's current state, it can cause confusion. As it does show some other non failure statuses on it too (queued, sent, etc), but not all. We will look at adding the missing ones, thanks for bringing it up.
As for received message status you saw, this is there to represent inbound messages to Genesys Cloud, so this would not exactly be considered a delivery receipt in the intended nature of the definition. You should only see this status on the customer purpose on the Genesys Cloud Conversation (inbound messages). And would be the only status you see for those messages. If the message didn't come to us (no delivery; due to carrier failure for instance) then it wouldn't exist on the Conversation at all. We couldn't represent the message with a delivery receipt, as it wouldn't exist. That's why received is the only status for those messages.
For outbound messages like from a campaign purpose, then you should see some of the various delivery receipts listed on that page, including delivery-success. Which is not listed on that page yet, as you said. And also possibly some delivery-failed statuses, which would also contain an errorInfo object on the Conversation representing some of the reasons why the message failed (which are listed on that page), using errorPayload field on the Conversation.

Hope this helps,
Greg

• Does anyone know why this is?
• Should I be seeing the delivery receipts mentioned in the resource center? I am not right now, and this seems odd.

Hi Peter, the campaign performance views support digital media types, but we're also in the process of building a Campaign Interactions view and export as well as Campaign Attempt History export. We're continuing to advance our campaign reporting and would love to hear more about what you're looking for in digital campaign reporting specifically.

Thanks, Greg.

That is helpful!

Do you know if there will be specific Digital Campaign reports? My org currently has the BETA for the New Campaign Performance Views, which looks great for Voice calls, but maybe not as applicable to the Digital pieces. Do you know?

Thanks,

@Peter Stoltenberg
​I believe this documentation page was trying to help identify failure delivery receipts, more than anything. But i can see how in it's current state, it can cause confusion. As it does show some other non failure statuses on it too (queued, sent, etc), but not all. We will look at adding the missing ones, thanks for bringing it up.
As for received message status you saw, this is there to represent inbound messages to Genesys Cloud, so this would not exactly be considered a delivery receipt in the intended nature of the definition. You should only see this status on the customer purpose on the Genesys Cloud Conversation (inbound messages). And would be the only status you see for those messages. If the message didn't come to us (no delivery; due to carrier failure for instance) then it wouldn't exist on the Conversation at all. We couldn't represent the message with a delivery receipt, as it wouldn't exist. That's why received is the only status for those messages.
For outbound messages like from a campaign purpose, then you should see some of the various delivery receipts listed on that page, including delivery-success. Which is not listed on that page yet, as you said. And also possibly some delivery-failed statuses, which would also contain an errorInfo object on the Conversation representing some of the reasons why the message failed (which are listed on that page), using errorPayload field on the Conversation.

Hope this helps,
Greg

• Does anyone know why this is?
• Should I be seeing the delivery receipts mentioned in the resource center? I am not right now, and this seems odd.

Hi Maisey,

Sure! I would think we would want:

• Successful Delivery
• Failed Delivery
• Opt Out Count (how many STOPs we received)
• Response Rate (customers sent a message back to the outbound SMS)
  • Question: I don't know what technology is available to identify "opened messages versus Unread Messages versus when a customer clicked a link". This would be great information, if we could have it.
• Maybe some additionl Performance metrics for Queue/Agent statistics like ASA, Bot Performance Metrics, or even Flow Outcome Aggregate reporting.

These are all things I think would make sense!

Hi Peter, the campaign performance views support digital media types, but we're also in the process of building a Campaign Interactions view and export as well as Campaign Attempt History export. We're continuing to advance our campaign reporting and would love to hear more about what you're looking for in digital campaign reporting specifically.

Thanks, Greg.

That is helpful!

Do you know if there will be specific Digital Campaign reports? My org currently has the BETA for the New Campaign Performance Views, which looks great for Voice calls, but maybe not as applicable to the Digital pieces. Do you know?

Thanks,

@Peter Stoltenberg
​I believe this documentation page was trying to help identify failure delivery receipts, more than anything. But i can see how in it's current state, it can cause confusion. As it does show some other non failure statuses on it too (queued, sent, etc), but not all. We will look at adding the missing ones, thanks for bringing it up.
As for received message status you saw, this is there to represent inbound messages to Genesys Cloud, so this would not exactly be considered a delivery receipt in the intended nature of the definition. You should only see this status on the customer purpose on the Genesys Cloud Conversation (inbound messages). And would be the only status you see for those messages. If the message didn't come to us (no delivery; due to carrier failure for instance) then it wouldn't exist on the Conversation at all. We couldn't represent the message with a delivery receipt, as it wouldn't exist. That's why received is the only status for those messages.
For outbound messages like from a campaign purpose, then you should see some of the various delivery receipts listed on that page, including delivery-success. Which is not listed on that page yet, as you said. And also possibly some delivery-failed statuses, which would also contain an errorInfo object on the Conversation representing some of the reasons why the message failed (which are listed on that page), using errorPayload field on the Conversation.

Hope this helps,
Greg

• Does anyone know why this is?
• Should I be seeing the delivery receipts mentioned in the resource center? I am not right now, and this seems odd.

Thank you, Peter, this is very helpful! I've passed this along to my product manager. 

Hi Maisey,

Sure! I would think we would want:

• Successful Delivery
• Failed Delivery
• Opt Out Count (how many STOPs we received)
• Response Rate (customers sent a message back to the outbound SMS)
  • Question: I don't know what technology is available to identify "opened messages versus Unread Messages versus when a customer clicked a link". This would be great information, if we could have it.
• Maybe some additionl Performance metrics for Queue/Agent statistics like ASA, Bot Performance Metrics, or even Flow Outcome Aggregate reporting.

These are all things I think would make sense!

Hi Peter, the campaign performance views support digital media types, but we're also in the process of building a Campaign Interactions view and export as well as Campaign Attempt History export. We're continuing to advance our campaign reporting and would love to hear more about what you're looking for in digital campaign reporting specifically.

Thanks, Greg.

That is helpful!

Do you know if there will be specific Digital Campaign reports? My org currently has the BETA for the New Campaign Performance Views, which looks great for Voice calls, but maybe not as applicable to the Digital pieces. Do you know?

Thanks,

@Peter Stoltenberg
​I believe this documentation page was trying to help identify failure delivery receipts, more than anything. But i can see how in it's current state, it can cause confusion. As it does show some other non failure statuses on it too (queued, sent, etc), but not all. We will look at adding the missing ones, thanks for bringing it up.
As for received message status you saw, this is there to represent inbound messages to Genesys Cloud, so this would not exactly be considered a delivery receipt in the intended nature of the definition. You should only see this status on the customer purpose on the Genesys Cloud Conversation (inbound messages). And would be the only status you see for those messages. If the message didn't come to us (no delivery; due to carrier failure for instance) then it wouldn't exist on the Conversation at all. We couldn't represent the message with a delivery receipt, as it wouldn't exist. That's why received is the only status for those messages.
For outbound messages like from a campaign purpose, then you should see some of the various delivery receipts listed on that page, including delivery-success. Which is not listed on that page yet, as you said. And also possibly some delivery-failed statuses, which would also contain an errorInfo object on the Conversation representing some of the reasons why the message failed (which are listed on that page), using errorPayload field on the Conversation.

Hope this helps,
Greg

• Does anyone know why this is?
• Should I be seeing the delivery receipts mentioned in the resource center? I am not right now, and this seems odd.

Hi Maisey,

Is there a specific idea on the idea portal for our conversation above? If not, I can create one. Just want to make sure this is accounted for :)

Thanks,
Peter

Thank you, Peter, this is very helpful! I've passed this along to my product manager. 

Hi Maisey,

Sure! I would think we would want:

• Successful Delivery
• Failed Delivery
• Opt Out Count (how many STOPs we received)
• Response Rate (customers sent a message back to the outbound SMS)
  • Question: I don't know what technology is available to identify "opened messages versus Unread Messages versus when a customer clicked a link". This would be great information, if we could have it.
• Maybe some additionl Performance metrics for Queue/Agent statistics like ASA, Bot Performance Metrics, or even Flow Outcome Aggregate reporting.

These are all things I think would make sense!

Hi Peter, the campaign performance views support digital media types, but we're also in the process of building a Campaign Interactions view and export as well as Campaign Attempt History export. We're continuing to advance our campaign reporting and would love to hear more about what you're looking for in digital campaign reporting specifically.

Thanks, Greg.

That is helpful!

Do you know if there will be specific Digital Campaign reports? My org currently has the BETA for the New Campaign Performance Views, which looks great for Voice calls, but maybe not as applicable to the Digital pieces. Do you know?

Thanks,

@Peter Stoltenberg
​I believe this documentation page was trying to help identify failure delivery receipts, more than anything. But i can see how in it's current state, it can cause confusion. As it does show some other non failure statuses on it too (queued, sent, etc), but not all. We will look at adding the missing ones, thanks for bringing it up.
As for received message status you saw, this is there to represent inbound messages to Genesys Cloud, so this would not exactly be considered a delivery receipt in the intended nature of the definition. You should only see this status on the customer purpose on the Genesys Cloud Conversation (inbound messages). And would be the only status you see for those messages. If the message didn't come to us (no delivery; due to carrier failure for instance) then it wouldn't exist on the Conversation at all. We couldn't represent the message with a delivery receipt, as it wouldn't exist. That's why received is the only status for those messages.
For outbound messages like from a campaign purpose, then you should see some of the various delivery receipts listed on that page, including delivery-success. Which is not listed on that page yet, as you said. And also possibly some delivery-failed statuses, which would also contain an errorInfo object on the Conversation representing some of the reasons why the message failed (which are listed on that page), using errorPayload field on the Conversation.

Hope this helps,
Greg

• Does anyone know why this is?
• Should I be seeing the delivery receipts mentioned in the resource center? I am not right now, and this seems odd.

Hi Peter, I shared the information with my PM, but an Idea is always a great idea, so others can vote on it as well!

Thanks,

Hi Maisey,

Is there a specific idea on the idea portal for our conversation above? If not, I can create one. Just want to make sure this is accounted for :)

Thanks,
Peter

Thank you, Peter, this is very helpful! I've passed this along to my product manager. 

Hi Maisey,

Sure! I would think we would want:

• Successful Delivery
• Failed Delivery
• Opt Out Count (how many STOPs we received)
• Response Rate (customers sent a message back to the outbound SMS)
  • Question: I don't know what technology is available to identify "opened messages versus Unread Messages versus when a customer clicked a link". This would be great information, if we could have it.
• Maybe some additionl Performance metrics for Queue/Agent statistics like ASA, Bot Performance Metrics, or even Flow Outcome Aggregate reporting.

These are all things I think would make sense!

Hi Peter, the campaign performance views support digital media types, but we're also in the process of building a Campaign Interactions view and export as well as Campaign Attempt History export. We're continuing to advance our campaign reporting and would love to hear more about what you're looking for in digital campaign reporting specifically.

Thanks, Greg.

That is helpful!

Do you know if there will be specific Digital Campaign reports? My org currently has the BETA for the New Campaign Performance Views, which looks great for Voice calls, but maybe not as applicable to the Digital pieces. Do you know?

Thanks,

@Peter Stoltenberg
​I believe this documentation page was trying to help identify failure delivery receipts, more than anything. But i can see how in it's current state, it can cause confusion. As it does show some other non failure statuses on it too (queued, sent, etc), but not all. We will look at adding the missing ones, thanks for bringing it up.
As for received message status you saw, this is there to represent inbound messages to Genesys Cloud, so this would not exactly be considered a delivery receipt in the intended nature of the definition. You should only see this status on the customer purpose on the Genesys Cloud Conversation (inbound messages). And would be the only status you see for those messages. If the message didn't come to us (no delivery; due to carrier failure for instance) then it wouldn't exist on the Conversation at all. We couldn't represent the message with a delivery receipt, as it wouldn't exist. That's why received is the only status for those messages.
For outbound messages like from a campaign purpose, then you should see some of the various delivery receipts listed on that page, including delivery-success. Which is not listed on that page yet, as you said. And also possibly some delivery-failed statuses, which would also contain an errorInfo object on the Conversation representing some of the reasons why the message failed (which are listed on that page), using errorPayload field on the Conversation.

Hope this helps,
Greg

• Does anyone know why this is?
• Should I be seeing the delivery receipts mentioned in the resource center? I am not right now, and this seems odd.