CRW ride texts: check in, chat, and finish

Riders

Download or print this guide (PDF)

Save 573-279-2739 as CRW Ride Text.

When you arrive

Text HERE from the phone listed on your CRW registration. Read the reply. If more than one ride appears, choose yours, then text HERE again.

On an ordinary ride without separate chat groups, HERE connects you to the main ride chat. Give chat setup a moment after the check-in reply.

If your ride has groups, text GROUPS, then JOIN and the number you want, such as JOIN 2. Once you join, your ordinary texts go to that group.

Talk to the ride

Text normally, for example:

• "Waiting at the next turn."
• "Flat at mile 12 by the church. Could someone stop?"
• "Anyone joining us for coffee?"

Main ride chat reaches riders who have checked in and connected their phones to CRW SMS, until they finish or leave the ride. If you join a route or pace group, ordinary texts go to that group instead. Large rides and centuries use smaller groups for rider conversations; riders do not have a default all-event chat.

Nobody is guaranteed to see a text immediately. If you need a response and do not get one, contact the leader or another rider directly.

When should I use ALERT?

On a small ride, you can also use ALERT if you are lost, dropped, or have a mechanical and want to notify the ride. For example: ALERT dropped near the church at mile 12; can someone contact me? Read the reply and send YES ALERT to confirm. Ordinary chat works without ALERT. Neither option guarantees an immediate response.

Use ALERT for an important message that needs to reach across the ride's groups, such as a road hazard, route change, or severe weather.

Example: ALERT road closed at mile 18; follow the signed detour

Read the confirmation and reply YES ALERT to send. ALERT reaches eligible checked-in riders across the ride, plus active crew covering that event. It does not call emergency services.

Emergency: call 911. The CRW number is not an emergency line. Call, do not text.

When you finish

Text FINISH before heading home, then answer the feedback question.

Leaving early? Text LEAVE RIDE. It records your departure. If you need help, tell someone directly rather than using LEAVE RIDE as a help request.

LEAVE GROUP leaves a chat group. On ordinary rides, your texts return to main ride chat; on large rides, choose another group before chatting again.

STOP unsubscribes you from all CRW SMS, including crew requests.

If check-in does not work

Find the ride leader. They can check your registration and check you in through Wild Apricot.

A leader can check you in manually to record attendance. That alone does not connect your phone to SMS or put you in a chat group. Check that your registration has the phone you are using. Once SMS recognizes your checked-in registration, text GROUPS, then JOIN plus the displayed number. If your phone is still unrecognized, arrange direct contact with the leader or another rider.

If SMS does not recognize your phone, ask the organizer how to contact support volunteers directly. Do not rely on manual check-in to connect you to text support. Read any support reply; if your request is not confirmed or nobody responds, use the direct contact plan.

Supported events

Your organizer will tell you whether volunteer text support is available.

To request it, text #SUPPORT with your location and problem:

#SUPPORT mile 42 near the church, broken chain

Read the reply and check the event name. Crew receive your message and callback number. They may call or text you directly.

After you open support, your ordinary texts go to support. Text RESOLVED when you are done, or GROUP to return to normal ride-chat handling. This changes where your texts go; it does not tell crew that help has arrived or that you no longer need them. Tell the person helping you directly.

SUPPORT shows instructions; it does not open a request or confirm staffing. Ordinary words such as "flat" or "lost" do not open a support request.

If you cannot text, call the CRW number and follow the voicemail instructions. It is a recording. If support is unavailable or nobody responds, contact the leader or another rider directly.

For an emergency, call 911.

Also handy

• MY RIDES: see your rides and, when available, where ordinary texts will go.
• MENU: see options. SAFETY: get the CRW safety page.
• All commands: full command reference.

Back to guide choices

Ride leaders: basic guide

Download or print this guide (PDF)

CRW SMS number: 573-279-2739

On a small ride without planned groups, text HERE, then send ordinary texts to ride chat. They reach checked-in riders connected to CRW SMS until those riders finish or leave. With a chosen route or pace group, ordinary texts go to that group instead. Large rides and centuries have no default all-rider chat.

This guide covers an ordinary ride, which is most rides. Supported events, centuries, and planned groups are in the advanced guide. Want one page to print? Use the one-pager.

The one rule

Hurt or in danger: call 911. Call, do not text. The CRW number is not an emergency line. Nobody reads texts to it live.

Good, better, even better

On a small ride without planned groups, text HERE, then send ordinary texts to ride chat. They reach checked-in riders connected to CRW SMS until those riders finish or leave. With a chosen route or pace group, ordinary texts go to that group instead. Large rides and centuries have no default all-rider chat.

Say this at check-in (about 90 seconds)

Please save 573-279-2739 as CRW Ride Text and text HERE now. If the reply asks you to see a leader, come find me.

Once connected, text normally to reach ride chat: waiting at a turn, lost, dropped, a flat, or coffee after the ride. If we use groups, text GROUPS and join our group, number __.

You can also use ALERT to notify the ride, then reply YES ALERT when asked. If you need an answer and nobody responds, call me at __ or speak to another rider.

For an emergency, call 911. Before heading home, text FINISH and answer the feedback question. Leaving early? Text LEAVE RIDE.

On a small ride, you can also use ALERT if you are lost, dropped, or have a mechanical and want to notify the ride. For example: ALERT dropped near the church at mile 12; can someone contact me? Read the reply and send YES ALERT to confirm. Ordinary chat works without ALERT. Neither option guarantees an immediate response.

During the ride

A leader can check you in manually to record attendance. That alone does not connect your phone to SMS or put you in a chat group. Check that your registration has the phone you are using. Once SMS recognizes your checked-in registration, text GROUPS, then JOIN plus the displayed number. If your phone is still unrecognized, arrange direct contact with the leader or another rider.

If SMS does not recognize your phone, ask the organizer how to contact support volunteers directly. Do not rely on manual check-in to connect you to text support. Read any support reply; if your request is not confirmed or nobody responds, use the direct contact plan.

• ROSTER: who has checked in. ROSTER OUT: who is still on the road.
• ALERT message: a short safety note to checked-in riders. SMS asks you to confirm; reply YES ALERT. Limit: 3 per phone every 2 minutes. ALERT does not call 911 or get medical help.
• Plain text from you goes to the ride chat for checked-in riders. If the ride has planned groups and you have joined one, it goes only to that group.

At the end

Invite every rider to text FINISH. A rider who never does is treated as done two hours after the ride's end time. Riders who head off early can text LEAVE RIDE. It only records the departure, and most riders who leave are simply done, so do not treat it as a sign of trouble.

When it does not work

Nothing you do today goes away.

More

All commands: cheat sheet. Why we built it: the guides index.

Back to guide choices

Ride leaders: printable one-pager

Download or print this guide (PDF)

On a small ride without planned groups, text HERE, then send ordinary texts to ride chat. They reach checked-in riders connected to CRW SMS until those riders finish or leave. With a chosen route or pace group, ordinary texts go to that group instead. Large rides and centuries have no default all-rider chat.

Emergency or anyone in danger: CALL 911. Call, do not text. The CRW number is not an emergency line. Nobody answers it live.

Say this at check-in (about 90 seconds)

Please save 573-279-2739 as CRW Ride Text and text HERE now. If the reply asks you to see a leader, come find me.

Once connected, text normally to reach ride chat: waiting at a turn, lost, dropped, a flat, or coffee after the ride. If we use groups, text GROUPS and join our group, number __.

You can also use ALERT to notify the ride, then reply YES ALERT when asked. If you need an answer and nobody responds, call me at __ or speak to another rider.

For an emergency, call 911. Before heading home, text FINISH and answer the feedback question. Leaving early? Text LEAVE RIDE.

On a small ride, you can also use ALERT if you are lost, dropped, or have a mechanical and want to notify the ride. For example: ALERT dropped near the church at mile 12; can someone contact me? Read the reply and send YES ALERT to confirm. Ordinary chat works without ALERT. Neither option guarantees an immediate response.

What riders should do

During the ride

A leader can check you in manually to record attendance. That alone does not connect your phone to SMS or put you in a chat group. Check that your registration has the phone you are using. Once SMS recognizes your checked-in registration, text GROUPS, then JOIN plus the displayed number. If your phone is still unrecognized, arrange direct contact with the leader or another rider.

If SMS does not recognize your phone, ask the organizer how to contact support volunteers directly. Do not rely on manual check-in to connect you to text support. Read any support reply; if your request is not confirmed or nobody responds, use the direct contact plan.

• ROSTER shows who checked in. ROSTER OUT shows who is still on the road.
• ALERT message asks you to confirm. Reply YES ALERT. Limit: 3 per phone every 2 minutes.
• No reply, wrong phone, balance owed, or forgot phone: use Wild Apricot Admin.
• Support requests go to CREW volunteers, not to you, unless you joined CREW.

Full detail: ride leader guide.

Back to guide choices

Ride leaders: advanced guide

Download or print this guide (PDF)

For supported events, centuries and other large rides, and planned groups. Read the basic guide first. Most weekly rides do not need this page.

Which one am I leading?

Supported events

Confirm the named event and current coverage with the organizer and volunteers before promising text support. SUPPORT, HELP SUPPORT and RIDE HELP show instructions; they do not open a request or confirm anyone is responding. CREW can show the current event and coverage status. An open time window does not prove someone is actively responding. Volunteers join with CREW, select the event, then YES CREW. Opening starts 24 hours of coverage; joining later does not extend it.

• Riders text #SUPPORT with a location and a problem. It goes to the crew, not to you, unless you joined the crew yourself.
• A rider who cannot text can call the CRW number and leave a voicemail. That is a recording, not a person, and it is transcribed and texted to the crew.
• Once a rider sends #SUPPORT, their texts go to support, not ride chat, with no timer, until they text RESOLVED or GROUP.
• The crew expiring, closing, or emptying does not end a rider's request.

The supported-event script

Read parts 1 and 2 of the basic script, then this instead of part 3:

"This ride has support crew. For a flat, a mechanical, or if you're lost, text #SUPPORT, then where you are and what's wrong, like #SUPPORT mile 42 by the church, broken chain. A text that just says 'help' won't ask the crew for help. A crew member may text or call you back. Once you text support, your texts go to support, not ride chat, until you text RESOLVED. If you can't text, call this number and leave a voicemail. That is a recording, not a person. Urgent means 911."

Large rides and centuries

• Check-in opens 3 hours before the start and closes 3 hours after. An ordinary ride is 2 hours each way.
• A long ride stays active until about two hours after its end time, so riders still out late keep their ride context.
• There is no default all-event chat. Use ALERT for urgent news and groups for smaller conversations.
• A verified leader who has checked in and is in the main chat can send event-wide chat. Once you join a route or pace group, your ordinary texts go only to that group, so the other routes do not see them. To reach every route, use ALERT.

Groups

Plan them before the ride so check-in can suggest the right one.

• GROUP PLAN: open planning for a ride you lead.
• GROUP ADD 50 mi / 16-18 / 8:30: add a group. Distance and pace help check-in suggest it.
• GROUP COPY LAST, then YES COPY GROUPS: copy names from the last clean recurring ride.
• Riders: GROUPS lists them, JOIN 2 joins group 2, HERE G2 checks in and joins at once.

Roster filters

ROSTER NOTIN shows riders not checked in. ROSTER SHORT, MEDIUM, LONG, or 75+ filters by distance (under 30, 30-49, 50-74, 75 and up). ROSTER ROUTE 30-49 and ROSTER PACE 16-18 take ranges. ROSTER ? shows help. Distances come from the ride description.

More than one leader

Leaders and co-leaders on a ride share the same roster and tools: READY opens the leader hub, and ROSTER REFRESH or READY REFRESH refreshes a stale roster. CALL OFF RIDE is leader-only. CLONE copies a ride and needs global Ride Leader membership.

Full command list: cheat sheet.

Back to guide choices

Crew volunteers

Download or print this guide (PDF)

For supported events only. Most rides have no crew on the text line.

You are a volunteer who covers the text support line for a CRW event: the person who gets a rider's "broken chain at mile 42" and decides whether to call them back. You do not need to be a CRW member or a registered rider. You need a phone that can text.

CRW SMS number: 573-279-2739

Emergencies are not handled by text. Anyone hurt or in danger calls 911. If a request describes an injury or danger, tell the rider to call 911. Every support message ends with "Emergency: call 911."

What you are signing up for

• Riders text #SUPPORT with a location and problem. It goes to everyone on the crew.
• Riders who cannot text can call the CRW number and leave a voicemail. It is transcribed and texted to the crew.
• You also receive event-wide ALERT messages.
• CLAIM is optional. A request can be sent without a claim; delivery and help are not guaranteed.

There is one shared crew at a time, tied to one event.

Join the crew

From your own phone, text the CRW number:

1. Text CREW.
2. If no crew is open, you see up to five public events from CRW's event list. Reply with your event's number, or text CREW <event-id>. If a crew is already open, you see its event and when it ends.
3. Check the event name, then text YES CREW.

Opening a crew starts 24 hours of coverage. The confirmation shows when it ends, in Eastern time. Others join by texting CREW. Joining later does not extend it.

During your shift

A support request looks like this:

CRW ride support
<event name>

Rider: <name>
Phone: <rider's full phone number>
Message: mile 42 near the church, broken chain
CLAIM - optional, tell rider you can follow up
Emergency: call 911.

A voicemail request shows Call back: and a Transcript:. The transcript is automatic and can be wrong, so call back to confirm.

To take a request: text CLAIM. The rider is told you can follow up, and the first claim wins. Then call or text the rider at the phone number shown. If it is an emergency, tell them to call 911. Claiming is a courtesy, not a lock: if you cannot follow through, tell the rest of the crew yourself.

Crew commands

Keeping coverage going

• Coverage ends 24 hours after it opened or was last renewed. About an hour before, active crew get a warning text (sent between 6 AM and 10 PM Eastern): "CRW support for [event] closes at [time]. Reply KEEP CREW for another 24 hours, or CLOSE CREW if support is finished."
• KEEP CREW cannot revive an expired crew. After it ends, someone starts a new one with CREW.
• If you are the last one to leave, support is unstaffed. A new #SUPPORT text or call is told no crew is available, and to call 911 in an emergency.
• Before CLOSE CREW, hand off anything you claimed. If you are just done for the day and others are covering, use LEAVE CREW.

The rider's side of a request

A rider's request has no timer. It stays open until they text RESOLVED or GROUP, and until then their texts go to support, not ride chat. The crew expiring or emptying does not close it, and if nobody is left their next update is told it could not be delivered. When you finish helping, tell the rider to text RESOLVED. Ending it does not notify you.

Questions

A request can be sent without a claim. That does not prove someone saw it or is helping. If you can help, call or text the displayed rider number directly. Otherwise, contact another volunteer or the organizer directly. Do not assume silence means the request is covered. STOP ends all CRW SMS. LEAVE CREW ends only your crew participation.

I want to stop all CRW texts. Reply STOP. That unsubscribes you from all CRW SMS, including crew requests. To stop covering one event, use LEAVE CREW.

Commands in full: cheat sheet.

Back to guide choices

Crew scenarios

Download scenario one-pager (PDF)

573-279-2739 · crw.org/sms

Join your event. Text CREW. Check the event name, then reply YES CREW. If no crew is open, choose the event first. The confirmation shows when coverage ends. Joining later does not extend it.

A rider needs help. Read the location, problem, and callback number. If you can follow up, optionally text CLAIM and read the reply. Then call or text the rider's displayed number directly. CLAIM tells the rider you can follow up; it does not place the callback for you. Ordinary replies to the CRW number are not replies to the rider.

Someone else claimed. The first claim is recorded. If the reply names another volunteer, coordinate directly before arranging duplicate help.

Nobody has claimed. The request can still be sent to crew without a claim. That does not prove someone has seen it or is helping. If you can help, contact the rider. If you cannot, contact another volunteer or the event organizer directly. Do not assume silence means the request is covered.

CLAIM cannot identify the request. Use the rider's displayed callback number and coordinate directly. Do not keep guessing which request a bare CLAIM will select.

You cannot continue helping. Tell the rider. Arrange a direct handoff with another volunteer and confirm that they have taken over.

A voicemail arrives. Read the callback number and transcription. Call the rider to confirm the details; automatic transcriptions can be wrong. CLAIM does not assign a voicemail callback.

The problem is resolved. Tell the rider to text RESOLVED. Ask them to tell you directly when they no longer need help. RESOLVED does not send crew a completion notice. GROUP also ends support messaging and returns to normal chat handling.

Your shift ends. LEAVE CREW stops your crew messages while others remain. Hand off unfinished requests first. KEEP CREW extends current coverage to 24 hours from now. CLOSE CREW, then YES CLOSE CREW, ends coverage for everyone. An expired crew must be opened again with CREW. STOP stops all CRW SMS.

Emergency. Anyone hurt or in danger should call 911. The CRW number is not an emergency line.

Administrators

Download or print this guide (PDF)

For CRW staff and Wild Apricot admins. Engineers who deploy or debug the system should use the operations runbook.

CRW SMS number: 573-279-2739

What this is

CRW SMS is the ride-day layer on top of Wild Apricot. Riders text the number to check in, say they finished, and give feedback. Leaders text it to see who is here and to reach the whole ride. Wild Apricot stays the source of truth for members, events, registrations, waivers, and payments. SMS cannot waive a bill or override a registration.

It is not an emergency line. Nobody reads texts to it live. Every rider-facing message says to call 911 in an emergency. Do not promote the number as a way to reach CRW in a crisis.

What to keep right in Wild Apricot

SMS is only as accurate as these records.

• Rider phone numbers. Riders are recognized by the phone on their profile. The most common ride-day failure is a rider texting from a different phone.
• Leader and co-leader assignments on each event, set before ride day. Leader tools are tied to the specific ride.
• Event description with route distance. Roster filters read it. SMS does not guess a distance from the event title.
• Event end time. Set a real end time on each event. An unfinished check-in stays active until two hours after the event end. With no end time on the event, it lapses 24 hours after the start instead, so a long ride or century needs its true end time to stay active until the last rider is in.
• Waivers and payments. SMS blocks check-in while Wild Apricot shows an unpaid balance. Fix it in Wild Apricot.

Check-in windows

Ordinary ride: 2 hours before the start through 2 hours after. Century or large ride: 3 hours each way.

Ride-day help

A leader can check you in manually to record attendance. That alone does not connect your phone to SMS or put you in a chat group. Check that your registration has the phone you are using. Once SMS recognizes your checked-in registration, text GROUPS, then JOIN plus the displayed number. If your phone is still unrecognized, arrange direct contact with the leader or another rider.

If SMS does not recognize your phone, ask the organizer how to contact support volunteers directly. Do not rely on manual check-in to connect you to text support. Read any support reply; if your request is not confirmed or nobody responds, use the direct contact plan.

Manual check-in in the Wild Apricot Admin app covers anything SMS cannot.

Supported events

Confirm the named event and current coverage with the organizer and volunteers before promising text support. SUPPORT, HELP SUPPORT and RIDE HELP show instructions; they do not open a request or confirm anyone is responding. CREW can show the current event and coverage status. An open time window does not prove someone is actively responding. Volunteers join with CREW, select the event, then YES CREW. Opening starts 24 hours of coverage; joining later does not extend it.

Keep the emergency wording consistent

Anything you publish should say the same thing as the guides index: hurt or in danger, call 911; the CRW number is not an emergency line. The website safety page source is in `docs/site-pages`.

Privacy basics

Riders opt in by texting the number; STOP unsubscribes them. Ride chat and alerts go to checked-in riders who opted in. A support request shows the crew the rider's name and full phone number. SMS activity is logged for operations.

When something looks wrong

Source versus live

Before offering text support, organizers must confirm the current release state and the named event's volunteer coverage. See the existing operations runbook for release checks.

Back to guide choices

Full command reference

Download full command reference (PDF)

573-279-2739 · crw.org/sms

Send one command per text and read its reply. For an emergency, call 911. The CRW number is not an emergency line.

Start here

Register or change plans

From RIDES, choose a ride and follow the prompts.

• YES or JOIN: confirm the ride you just selected.
• I AGREE: accept a waiver after reviewing the link and being prompted.
• UNREGISTER: start removing yourself from a ride; follow the confirmation.
• If payment is due, use the payment link. After payment clears, text HERE again.
• If several rides appear during check-in, choose yours, then text HERE again. Choosing a ride alone does not check you in.
• Type FINISH or LEAVE RIDE explicitly. A bare menu number is not a substitute for these commands.

Chat and groups

On an ordinary ride without planned groups, HERE connects you to main ride chat. Give chat setup a moment after the check-in reply, then send ordinary messages without a command. Main chat reaches checked-in riders who have connected their phones to CRW SMS and have not finished or left early.

When groups are offered, choose one before using its chat. Once you join, your ordinary texts go to that group. Large rides and centuries use smaller groups for rider conversations rather than a default all-event chat. Verified event leaders who are checked in and in main chat can send ordinary event-wide chat; after joining a smaller group, their ordinary texts go to that group instead.

If check-in succeeds but joining the group does not, use GROUPS and JOIN plus the displayed number. Older forms NEW GROUP name and JOIN G1 remain accepted in the verified source. Bare JOIN needs the context of a ride-selection or group-selection prompt.

Nobody is guaranteed to read a text immediately. If you need an answer and do not get one, contact the leader or another rider directly.

Important ride-wide messages

• ALERT message: send an important message across your ride's groups to eligible checked-in riders, plus active crew covering that event.
• YES ALERT: send the alert after reviewing its confirmation.
• ALERT GROUP 2 message: send a safety note to group 2 immediately, without a separate confirmation. Check the group number and text first.

Keep alerts brief; the message is limited to 260 characters. The system limits alert starts to three per phone and event in two minutes. An alert does not call emergency services. A send confirmation does not prove that everyone received or read the message.

Volunteer support

Your organizer will tell you whether volunteer text support is available. Confirm the named event and current coverage with the organizer and volunteers; an open coverage window does not guarantee someone is responding.

While support is open, ordinary texts go to support. Ordinary words such as "flat" or "lost" do not open a request by themselves. If crew become unavailable, this does not automatically return your texts to ride chat. Read any error reply and contact a person directly. The request has no automatic timeout; an explicit exit is required.

If you cannot text, call the number and follow the voicemail instructions. It is a recording. For an emergency, call 911.

Crew volunteers

Only one event's shared crew is open at a time. Opening starts 24 hours of coverage; joining later does not extend it. An expired crew must be opened again with CREW. A new crew does not automatically include previous volunteers. Event size, tags, or a leader assignment do not sign up volunteers. Volunteers need not be members or registered riders.

The first claim is recorded. Coordinate directly if another volunteer claimed, no one has claimed, or CLAIM cannot identify the intended request. A claim is optional and does not place a callback, promise help, or prove delivery. Ordinary replies to CRW are not direct replies to the rider. For voicemail, call the displayed callback number and confirm the transcription; CLAIM does not assign that callback.

Crew may receive a warning before coverage ends. Renew before expiry if needed; do not assume a missed warning extends coverage. Older requests stay with their original crew rather than transferring to a new event's volunteers.

Ride leaders

Choose your ride through MY RIDES before using its leader tools. Leader and co-leader tools apply to the specific ride assigned to you in Wild Apricot.

Find riders by distance or pace

• ROSTER SHORT: under 30 miles.
• ROSTER MEDIUM: 30-49 miles.
• ROSTER LONG: 50-74 miles.
• ROSTER 75+: 75 miles or more.
• ROSTER DISTANCE SHORT, ROSTER DISTANCE MEDIUM, ROSTER DISTANCE LONG, or ROSTER DISTANCE 75+: the same distance categories.
• ROSTER ROUTE 62, ROSTER DISTANCE 62, or ROSTER 62 MI: the category containing 62 miles.
• ROSTER ROUTE 30-49: a distance range.
• ROSTER ROUTE 30 AND 50: either listed distance.
• ROSTER PACE 16: a pace.
• ROSTER PACE 16-18: a pace range.
• ROSTER PACE 16 AND 18: either pace.
• ROSTER PACE CASUAL or ROSTER PACE INTERMEDIATE: a pace label.

Distances come from the ride description. Riders whose choices are unclear may appear under "Distance not set." With no route distance in the description, distance filters match no riders. Use a word such as PACE or ROUTE with a number; bare ROSTER 16 shows help. Within a group, names are alphabetical when nobody has checked in; after check-in begins, status comes first, then names.

Plan groups

• GROUP PLAN: choose an upcoming ride you lead.
• GROUP PLAN event-id: open a particular ride.
• GROUP ADD route / pace / start: add a group, for example GROUP ADD 50 mi / 16-18 / 8:30 or GROUP ADD Amy 33@15-16.
• GROUP RENAME 3 new name: rename empty planned group 3.
• GROUP REMOVE 3: remove empty planned group 3.
• GROUP COPY LAST, then YES COPY GROUPS: copy group names from the previous matching ride.

Use group numbers from the displayed planning list. Copying a ride can carry its planned group names into planning for the new draft.

Other useful commands

• FEEDBACK GREAT, FEEDBACK OKAY, FEEDBACK PROBLEM: give quick ride feedback.
• SAFETY: get the safety page.
• MEDIA: get photo/video-sharing information.

If something does not work

Read the reply and follow its next step. If check-in cannot be confirmed, find the ride leader. A leader can check you in manually to record attendance. That alone does not connect your phone to SMS or put you in a chat group. Check that your registration has the phone you are using. Once SMS recognizes your checked-in registration, text GROUPS, then JOIN plus the displayed number. If your phone is still unrecognized, arrange direct contact with the leader or another rider.

If SMS does not recognize your phone, ask the organizer how to contact support volunteers directly. Do not rely on manual check-in to connect you to text support. Read any support reply; if your request is not confirmed or nobody responds, use the direct contact plan.

If SMS says an action may have completed, ask for help checking it before repeating it. For payment or registration problems, use Wild Apricot or ask staff; SMS cannot waive a bill.

Emergency: call 911.

Back to guide choices