Connect and test Twilio SMS

Save Twilio in the settings screen used by GymCore’s sending client, send one test to an authorized staff phone, and verify it in Twilio.

Access and dependencies

• Use a WordPress administrator with manage_options and a Twilio account owner.
• Complete sender registration and obtain an Account SID, Auth Token, and either a Messaging Service SID or Twilio phone number.
• Put an authorized E.164-format billing phone on the administrator’s own user profile for the test.
• GymCore Admin > Integrations > Twilio SMS is not sufficient for launch: its current Test Connection checks only that Account SID, Auth Token, and From Number (E.164) are non-empty. The runtime sending client uses the settings below.

Exact steps

Safe stop: Save the approved sender configuration, but stop before Send test SMS until the current user’s billing phone, consent, test cost, and Twilio account are confirmed.

1. Open GymCore Admin > GymCore Settings, then select SMS.

2. Enter Twilio Account SID and Twilio auth token. The token is encrypted after saving; leave the masked value unchanged unless rotating it.

3. Enter Twilio messaging service SID or Twilio phone number. A Messaging Service SID is optional but takes precedence when both are set; a phone number must use E.164 format.

4. Set Rate limit from 1 to 10 messages per contact per hour. The default is 1.

5. Save the settings before testing.

   Expected: The SMS section reloads with saved non-secret values and a masked auth token. No message has been sent yet.

6. Select Send test SMS. This action sends a one-line Twilio test to the current user’s billing phone.

   Expected: GymCore displays Test SMS sent. and Twilio records one message SID. If the user has no billing phone, GymCore says so instead of choosing another member.

7. Verify the final result in Twilio: open the message log and compare sender, recipient, body, time, and final delivery status with the current WordPress user’s billing phone.

   Expected: The Twilio log and WordPress profile agree. A GymCore success notice without a matching Twilio message is not final verification.

8. If the site also uses the Twilio SMS integration card, connect it only after the SMS settings test passes. Its event listener can send fixed messages for rank_promoted, badge_earned, subscription_created, and subscription_cancelled to the member’s gym_phone value.

Effects, reversal, and consent

The test sends a real SMS and may incur a Twilio charge; it cannot be recalled. The runtime retries once only for Twilio HTTP 429 or 503 responses. Keep the default rate limit unless the messaging owner approves more. Sender registration, consent, quiet hours, opt-out handling, and retention remain the gym’s responsibility. Rotate the Auth Token in Twilio immediately if it is exposed, then replace the saved token.

Owner handoff: Give the administrator the Twilio message SID, redacted sender/recipient, GymCore event, and timestamp. Do not send the Auth Token or full message content in a general support channel.

If the test fails

• Save settings before sending a test: save the SMS section, then retry once.
• No billing phone is set: add an approved phone to the testing administrator’s own billing profile; do not borrow a member’s number.
• Twilio credentials are not configured: confirm Account SID, token, and at least one sender setting in the SMS section—not only the Integrations card.
• Twilio rejects the request: use the Twilio error and message log to check sender registration, destination format, balance, and regional permissions.

Related guides

• Credentials Webhooks
• Integrations API
• Scheduled Jobs Automation