LevSMS Status - 2026-05-13

Purpose: current pickup note after Sam reported Twilio is finally OK/connected.

New report from Sam

On 2026-05-13, Sam reported: Twilio is connected / LevSMS is OK to work.

I searched the connected Gmail for recent Twilio approval/A2P campaign messages and did not find a clear approval email. Treat the Twilio approval/connection as Sam-reported, console-visible, not email-verified in this workspace until we record the exact console status.

Last verified local state

• Public site source: levsms-site/
• Public domain previously recorded as live: https://levsms.com/
• Public number on site: (516) 585-2323
• Support email: support@levsms.com
• Netlify project: levsms
• Netlify site ID: fe444885-3be5-40f8-bd67-a92904ec7c03
• Prior failed campaign SID: CMea45a10d77cf4b659889d9920048a7d5
• Prior messaging service SID: MGdd479ee0d71bf93570d1c8706b003d81
• Prior brand SID: BN96a162f44f4e4df3fc2ed654e95cfebd

Important gap

No production LevSMS SMS router code was found in the workspace outside documentation and the static compliance site.

Current buildable next step is not more compliance copy. It is the actual minimal command router:

1. Create/confirm a Google Sheet backend for LevSMS.
2. Add tabs: INBOUND_LOG, OUTBOUND_LOG, CONTACTS, COMMANDS, APPROVED_RESPONSES, SETTINGS.
3. Build Apps Script doPost(e) for Twilio inbound webhook.
4. Implement only safe MVP commands first: MENU, HELP, STOP, START, MINYAN, ZMANIM.
5. Store Twilio secrets in Apps Script Properties, never in git.
6. Set Twilio Messaging webhook to the deployed Apps Script Web App URL.
7. Test from Sam's phone:
   - MENU
   - HELP
   - STOP
   - START
   - an unknown command

Local scaffold created:

• levsms-router-apps-script/Code.js
• levsms-router-apps-script/README.md
• levsms-router-apps-script/appsscript.json
• levsms-router-apps-script/DEPLOY_CHECKLIST.md
• levsms-router-apps-script/TWILIO_CONSOLE_CAPTURE.md
• levsms-router-apps-script/sheet-template/

This version returns a TwiML body directly to Twilio for inbound replies, so the first live test does not require storing the Twilio auth token.

Important Apps Script note: Google's current ContentService.MimeType enum does not include XML, so Code.js serves the TwiML body as TEXT. If Twilio rejects because it requires strict text/xml, move the same router logic to Cloudflare Worker or Netlify Function.

Ops portal briefing created:

• outputs/2026-05-13_16-20_action_levsms-router-go-live.html

Google Drive native Sheet creation/upload attempt returned 403 Forbidden; reconnect Drive with create/upload permissions before asking Codex to create the backend Sheet directly.

What to capture from Twilio console

Needed to update docs from "reported connected" to "verified":

1. Current A2P Brand name and status.
2. Current A2P Campaign status.
3. Current Messaging Service SID and linked sender number.
4. Webhook URL configured for inbound messages, if any.
5. Whether outbound SMS to Sam's phone succeeds.

Current recommendation

Build the smallest production-safe Apps Script router now, backed by a manually approved APPROVED_RESPONSES tab. Keep AI/schedule extraction out of live SMS until manual responses work end-to-end.