Agent Action Board

Generated: 2026-05-05

I can do now

• Maintain this launch packet.
• Build and update the static website files.
• Draft Twilio resubmission fields.
• Draft privacy/terms for counsel review.
• Draft kosher carrier outreach.
• Draft Delaware formation language.
• Draft operating agreement language.
• Draft EIN application answers.
• Build the Twilio SMS router after you choose Apps Script vs Node.
• Create a Google Sheet schema for LevSMS if Drive/Sheets access is available.
• Search connected Gmail once the correct account is attached.
• Maintain the local Apps Script router scaffold in levsms-router-apps-script/.

I need Sam/account access for

• Gmail reconnection to the mailbox with Twilio emails.
• Domain purchase.
• Delaware registered agent checkout.
• Delaware filing submission/payment.
• EIN application, because it uses SSN/responsible-party data.
• Bank account opening.
• Twilio console edits/resubmission.
• DNS changes.
• Netlify/GitHub/Cloudflare deploy if credentials are not already connected.

I need counsel/CPA confirmation for

• Whether to use Delaware LLC vs NY LLC for this exact launch.
• Whether and when NY foreign qualification is required.
• Whether to file DBAs for LevSMS and NW Pulse before launch.
• Trademark filing timing and classes.
• Privacy/terms legal sufficiency.
• COPPA/minor user process.
• School schedule data-sharing agreement.

Next agent session

Recommended command:

Codex, continue from docs/malca-yenta/launch-packet/README.md and docs/malca-yenta/launch-packet/STATUS_2026-05-13_LEVSMS.md. Twilio is reportedly connected. Verify/capture the console status, then deploy the Sheet-backed Apps Script router from levsms-router-apps-script/.

Exact next clicks

1. Open Twilio and capture Brand status, Campaign status, Messaging Service SID, linked sender number, and any inbound webhook URL.
2. If no webhook is set, leave Twilio ready and deploy the Apps Script router first.
3. Create or choose the Google Sheet backend for LevSMS.
4. Install levsms-router-apps-script/Code.js, run setupLevSmsSheet(), and deploy as a Web App.
5. Paste the Web App URL into the Twilio Messaging Service inbound webhook using POST.
6. Test MENU, HELP, STOP, START, MINYAN, and an unknown command from Sam's phone.
7. In parallel: order Harvard Business Services registered-agent service or LLC formation.
8. Finalize DELAWARE_CERTIFICATE_OF_FORMATION_DRAFT.md using Harvard RA details.
9. Sam files/pays Delaware or authorizes agent while Sam is present for payment/authentication.
10. Sam gets EIN using EIN_APPLICATION_WORKSHEET.md.
11. Later: migrate/align Twilio and website legal operator to Malca Yenta Networks LLC.

Completed on 2026-05-06

• Sam bought levsms.com.
• support@levsms.com forwarding was tested successfully.
• Netlify project levsms was created.
• Temporary live site: https://levsms.netlify.app/.
• Temporary privacy URL: https://levsms.netlify.app/privacy.html.
• Temporary terms URL: https://levsms.netlify.app/terms.html.
• Public brand was renamed everywhere in text files to LevSMS/LEVSMS.
• Local site folder was cleaned to levsms-site/.
• levsms.com and www.levsms.com were connected to Netlify.
• HTTPS is working at https://levsms.com/.
• Public site copy was reduced so Sam's full personal name is not displayed on the website.

Current blocker

Sam reported on 2026-05-13 that Twilio is connected / OK to work. The current blocker is to capture exact Twilio console status and connect the inbound webhook to a working SMS router. Gmail did not show a clean approval email in the connected mailbox.

The LLC is not formed yet. If running the pilot before formation, keep the public website branded as LevSMS and keep personal/legal details in the private Twilio account fields rather than splashing them on the public site.