const { init } = require ( "@holler2660/console-text") ;
init({ apiKey: "ct_live_<key removed>", debug: true });
console.text("Error detected!");
% node test.js
[console.text] SDK initialized successfully
[console.text] Alert sent: { id: 'zzmfq6eltuqica32krircrql', delivered: true, rateLimited: false }
Thanks for the detailed debug output! This confirms what we suspected, the message is being accepted by Twilio but it might be filtered by T-Mobile before reaching your handset.
Can you try sending "Error Detected" one more time just to confirm it's consistently filtered (not a one-time glitch)?
If it fails again, then:
1. The immediate problem: "Error Detected" is likely triggering T-Mobile's spam filter. Try a more specific message like "[YourApp] Error in payment processor at 3:42 PM", generic error messages get filtered heavily. Let me know if that gets through.
2. Our misleading status: You're right - showing "delivered: true" when it just means "accepted by carrier" is confusing. We're working on:
- Clearer status terminology ("accepted" vs "delivered")
- Webhook integration to track actual handset delivery
- Guidance on avoiding carrier filtering
Tried changing to "Hey Jeremy1026: Error in payment processor at 3:42 PM", same status with no delivery to my phone number, ID: jz44a46jjpx7vjpzsa9c0soc.
I used to work with Twilio pretty heavily at a SaaS, I left as they started to crack down on SMS. One of my last projects was developing an in-app front-end to submit the regulatory paperwork to get higher delivery rates for SMS. I know it was a huge pain, sounds like it still is.