Teams Integration doesn't recognize Buttons

Ggg So i've integrated teams with voiceflow and i have the buttons pop up correctly,...

T

Tico | Voiceflow Assistant•7/4/24, 4:42 PM

In Voiceflow, buttons can be configured to trigger specific events or paths in your flow. Here's how you can set up and manage buttons:

Button Configuration

Each button should be defined with a unique name and a request type. For example:

buttons: [
  { name: 'Button A', request: { type: 'eventA', payload: 'example' } },
  { name: 'Button B', request: { type: 'eventB', payload: 'another-example' } }
]

buttons: [
  { name: 'Button A', request: { type: 'eventA', payload: 'example' } },
  { name: 'Button B', request: { type: 'eventB', payload: 'another-example' } }
]

buttons: [
  { name: 'Button A', request: { type: 'eventA', payload: 'example' } },
  { name: 'Button B', request: { type: 'eventB', payload: 'another-example' } }
]

buttons: [
  { name: 'Button A', request: { type: 'eventA', payload: 'example' } },
  { name: 'Button B', request: { type: 'eventB', payload: 'another-example' } }
]

When a button is clicked, it sends a request payload to the runtime.

Listen Functionality

You can define a 'listen' command to respond to button clicks. For instance, clicking 'Button A' can trigger a function step to leave from a specific path.

No Match Configuration

In cases where the user input doesn't match any button payloads, you can define a 'No Match' path. This can be set to reprompt your users or configure a fallback path.

Testing

You can test the button functionality in the Voiceflow Prototype Tool to ensure that the buttons are working as expected.

Advanced Features

Buttons can also be integrated into carousels and cards, which can trigger the 'listen' functionality.

Here is an example of how you might configure a button with a payload:

trace: {
  type: 'choice',
  payload: {
    buttons: [
      { name: 'Button A', request: { type: 'eventA', payload: 'example' } },
      { name: 'Button B', request: { type: 'eventB', payload: 'another-example' } }
    ]
  }
}

trace: {
  type: 'choice',
  payload: {
    buttons: [
      { name: 'Button A', request: { type: 'eventA', payload: 'example' } },
      { name: 'Button B', request: { type: 'eventB', payload: 'another-example' } }
    ]
  }
}

trace: {
  type: 'choice',
  payload: {
    buttons: [
      { name: 'Button A', request: { type: 'eventA', payload: 'example' } },
      { name: 'Button B', request: { type: 'eventB', payload: 'another-example' } }
    ]
  }
}

trace: {
  type: 'choice',
  payload: {
    buttons: [
      { name: 'Button A', request: { type: 'eventA', payload: 'example' } },
      { name: 'Button B', request: { type: 'eventB', payload: 'another-example' } }
    ]
  }
}

For more detailed information, you can refer to the following resources:

F

faint-whiteOP•7/4/24, 4:49 PM

Thanks Tico, anyway here is a image of teams chat, it's in different langauge but it doesn't matter, i tried clicking 'Pracovný inzerát' and i've tried simple names without the signs of my langauge and it didn't help. Also here is a short part from teams which get's sent to voiceflow

_activity: {
    text: 'Pracovný inzerát',
    textFormat: 'plain',
    type: 'message',

_activity: {
    text: 'Pracovný inzerát',
    textFormat: 'plain',
    type: 'message',

_activity: {
    text: 'Pracovný inzerát',
    textFormat: 'plain',
    type: 'message',

_activity: {
    text: 'Pracovný inzerát',
    textFormat: 'plain',
    type: 'message',

F

faint-whiteOP•7/4/24, 4:50 PM

so i think voiceflow should be able to recognize it and i'm not sure where the problem is