STL Cookbook

SMS Scenarios (Consumer)

Summary of consumer-facing SMS scenario codes, trigger conditions, and send timing.

Reset password

  • Scenario code: access_passcode_reset
  • Trigger: staff resets a user password in Console, or a user resets password in the App
  • Send timing: immediately after the action completes

Room passcode notification (grant)

  • Scenario code: access_room_grant
  • Trigger: staff grants access to a user in Console
  • Send timing: immediately after authorization completes

Verification code

  • Scenario code: auth_user_login_verification
  • Trigger: user requests a login verification code in the App, website, etc.
  • Send timing: immediately after the request

Temporary login credentials

  • Scenario code: auth_user_onetime_credential
  • Trigger: staff sends temporary login credentials in Console for a user without the App
  • Send timing: immediately after the action completes

Check-out reminder

  • Scenario code: crs_reservation_checkout_reminder
  • Trigger: every day at 11:45, the system sends to primary occupants who should check out today but have not, with no linked follow-on reservation; if departure time is changed after 11:45, it triggers again
  • Send timing: immediately after trigger

Sublet created

  • Scenario code: crs_reservation_rerent_create
  • Trigger: staff creates a sublet in Console or a user creates one in Guest App
  • Send timing: immediately after successful creation

Sublet cancelled

  • Scenario code: crs_reservation_rerent_cancel
  • Trigger: staff cancels a sublet in Console or a user cancels one in Guest App
  • Send timing: immediately after successful cancellation

Sublet date changed

  • Scenario code: crs_reservation_rerent_date_set
  • Trigger: staff changes sublet dates in Console or a user changes them in Guest App
  • Send timing: immediately after successful update

Sublet ending reminder

  • Scenario code: crs_reservation_rerent_period_ending
  • Trigger: after night audit on the sublet end date
  • Send timing: sent immediately to the primary occupant

Sublet started

  • Scenario code: crs_reservation_rerent_start
  • Trigger: staff starts a sublet in Console or a user starts one in Guest App
  • Send timing: immediately after the action completes

Sublet successful

  • Scenario code: crs_reservation_rerent_success
  • Trigger: a hotel reservation is assigned to the sublet room and night audit has passed
  • Send timing: automatically sent to the primary occupant at 9:00 on the day after check-in

Sublet starting soon

  • Scenario code: crs_reservation_rerent_come
  • Trigger: automatically triggered at 20:00 on the day before the sublet start date
  • Send timing: sent immediately to the primary occupant

Long-stay invoice payment reminder

  • Scenario code: finance_new_invoice_emit
  • Trigger: staff submits an e-contract in Console, or manually generates an invoice with notification enabled
  • Send timing: immediately after trigger

Contract pending signature

  • Scenario code: finance_esign_tenant_contract_sign
  • Trigger: staff submits an e-contract in Console
  • Send timing: immediately after submission

Room lock reminder

  • Scenario code: finance_reservation_countdown_lock
  • Trigger: the next rent invoice remains unpaid before the due date
  • Send timing: automatically sent to the primary occupant at 8:00 on the due date

Lost and found notification

  • Scenario code: wo_lost_found_notify_to_customer
  • Trigger: a lost-and-found work order is created and linked to a reservation
  • Send timing: sent immediately to the primary occupant of that reservation

None

On this page