# SetSlots Button payload not working as expected

**URL:** <https://forum.rasa.com/t/setslots-button-payload-not-working-as-expected/64099>\
**Category:** Rasa CALM\
**Created:** [October 23, 2024, 7:33am UTC](https://forum.rasa.com/t/setslots-button-payload-not-working-as-expected/64099 "2024-10-23T07:33:54Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![msr](https://avatars.discourse-cdn.com/v4/letter/m/d9b06d/32.png) [@msr](https://forum.rasa.com/u/msr)\
**Post date:** [October 23, 2024, 7:33am UTC](https://forum.rasa.com/t/setslots-button-payload-not-working-as-expected/64099/1 "2024-10-23T07:33:54Z")

</div>

Hello, I am working on a small demo bot for a presentation and I am having issues with button payloads. I am using a form to fill some slots and /affirm and /deny as payloads work fine for setting the boolean slots using “from\_intent” as mapping, but with some other slots I have issues.

```auto
slots:
  mitarbeiter:
    type: categorical
    values:
    - low
    - mid
    - high
    mappings:
    - type: custom

responses:
  utter_ask_nis2_check_form_mitarbeiter:
  - text: Wie viele Mitarbeiter arbeiten in Ihrem Unternehmen?
    buttons:
    - title: Unter 50
      payload: /SetSlots(mitarbeiter=low)
    - title: 50 bis 250
      payload: /SetSlots(mitarbeiter=mid)
    - title: 250 oder mehr
      payload: /SetSlots(mitarbeiter=high)

```

I am testing the behavior using interactive training and at the point I select one of these options, instead of setting the slot it shows my message as ‘mitarbeiter=mid)’ and classifies it as an intent (affirm in this case), which triggers a fallback and breaks the form. Am I misunderstanding how this is supposed to work? Or did I forget something? Rasa-Pro Version: 3.10.7

---

_[View the full topic](https://forum.rasa.com/t/setslots-button-payload-not-working-as-expected/64099)._