# Version 2.2.5 TextBee Inbound Reply Fix

This patch improves inbound TextBee reply handling.

## Why

If SMS_PROVIDER=textbee, outbound texts come from the Android/TextBee SIM number, not the Telnyx number.
Customer replies also go back to that TextBee SIM number.

If TextBee inbound webhooks are not configured or the payload shape is different than expected, the app receives no reply or cannot parse sender/message.

## What changed

- Robust TextBee inbound parser supports flat and nested payloads:
  - webhookEvent / event / type / event_type
  - sender / from / fromNumber / phoneNumber / phone / msisdn
  - message / body / text / content / messageBody
  - data.payload nesting
  - messages[] nesting
- More detailed SMS webhook logs:
  - [Incoming SMS received]
  - [Incoming SMS has no text/body]
  - Incoming SMS missing sender/from field
- Adds TextBee API check endpoint:
  GET /admin/api/textbee/received

## Required TextBee setup

TextBee dashboard webhook:

URL:
https://demo.recovermissedcall.com/sms/incoming

Event:
Message Received / MESSAGE_RECEIVED

Method:
POST

TEXTBEE_VALIDATE_SIGNATURE=false until confirmed working.