35

Twilio SMS Notifications (v8.2)

5 test cases · 31 verification points
UAT-35.1

Phone Number Setup & OTP Verification

High
Precondition: Twilio env vars configured (TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, TWILIO_PHONE_NUMBER)

Steps

  1. Navigate to Settings > Notifications
  2. Enter a mobile phone number
  3. Click Send Verification Code
  4. Enter the 6-digit OTP received via SMS
  5. Click Verify

Verify (7 checks)

  • Phone input field accepts international format
  • OTP SMS delivered within 30 seconds
  • Correct 6-digit code verifies successfully
  • Incorrect code shows error message
  • Phone number saved and visible in settings after verification
  • SmsLog record created for the OTP send event
  • Splunk log shows phone verification event
ScoreTesterDateNotes
____________
UAT-35.2

Per-Event SMS Toggle Switches

High
Precondition: Phone number verified

Steps

  1. Navigate to Settings > Notifications
  2. Toggle individual SMS events on/off
  3. Toggle "Enable All" and "Disable All"

Verify (5 checks)

  • Toggle switches visible for: OTP, Document Viewed, NDA Signed, Comments, Data Room Invitations, Contract Signing, File Uploads
  • Individual toggles save state correctly
  • "Enable All" turns all toggles on
  • "Disable All" turns all toggles off
  • Disabled events do not trigger SMS
ScoreTesterDateNotes
____________
UAT-35.3

SMS Delivery on Trigger Events

High
Precondition: Phone verified, relevant event toggles enabled

Steps

  1. Trigger each enabled event type
  2. Verify SMS receipt for each

Verify (7 checks)

  • Document viewed → SMS received with document title and viewer email
  • NDA signed → SMS received with signer name
  • Comment added → SMS received with comment excerpt
  • Data room invitation → SMS received with invitee email
  • Contract fully signed → SMS received with contract title (UAT-36.1)
  • File uploaded via request → SMS received with filename
  • All SMS events logged to SmsLog table with Twilio SID
ScoreTesterDateNotes
____________
UAT-35.4

SMS History Audit Log

Medium
Precondition: At least 3 SMS events triggered

Steps

  1. Navigate to Settings > SMS History

Verify (5 checks)

  • Paginated table shows SMS history
  • Each row shows: event type, status (delivered/failed), masked phone, timestamp, Twilio SID
  • Event filter dropdown works
  • Failed SMS shown with error message
  • Phone number is masked (e.g., +1 ***-***-1234)
ScoreTesterDateNotes
____________
UAT-35.5

SMS — Owner Alert on Contract Signing

Critical
Precondition: Contract owner has verified phone, contract_signed SMS toggle enabled (see UAT-36.1)

Steps

  1. Create a new contract as the owner
  2. Sign as provider
  3. Send to client via email
  4. Open the signing portal as client and complete signing
  5. Check owner's phone within 60 seconds
  6. Check SmsLog in Supabase or Settings > SMS History

Verify (7 checks)

  • SMS delivered to owner's verified phone number within 60 seconds of client signing
  • SMS body contains the contract title or reference identifier
  • SMS is only triggered on full execution — not when provider signs alone
  • SMS is not sent if owner's contract_signed toggle is disabled
  • SmsLog record created with event_type="contract_signed", status="delivered", twilio_sid populated
  • Splunk log shows SMS dispatch event with contract ID
  • SMS History page in Settings shows the event with correct masked phone and timestamp
ScoreTesterDateNotes
____________
← Module 34: Multi-Upload & Mobile PDF Viewer (v8.2)Module 36: SMS Contract Alert & Invite-Only Landing (v8.2.3) →