91803 text message: who sends it?

Match the text to a Ro visit you already started.

The public 91803 sample says to finish an online visit and see treatment options. That only makes sense if you recently began a Ro intake, visit, or checkout flow.

Open Ro yourself before you use any 91803 link.

Type ro.co or use the app or saved login path you already use. A short code can prompt you, but it should not be the first place you decide to trust a medical or payment flow.

Read a treatment-savings line as marketing copy.

The observed sample says you may be eligible to save on treatment. That is a promo-style nudge, not proof that the sender owns the code or that a discount is waiting for you.

Use STOP only for a marketing-style Ro thread.

The sample includes Reply STOP to opt out, which fits an advertising or reminder text. STOP should end texts. It should not lead to a new form asking for your date of birth, card, or account password.

Keep the message inside the narrow pattern shown here.

The known 91803 example is short, Ro-branded, and points back to an online visit. It does not ask you to describe symptoms in the text thread or send documents by reply.

Do not tap domains that add words around Ro.

Fake examples would be ro-secure-care.com, ro-login-visit.com, or ro.co.visit-id.com. The shape matters: the real brand appears, but the registered domain is not the same as ro.co.

Do not enter card details for a fee named only in the text.

A scam version may call it a visit hold, discount lock, pharmacy release, or reactivation charge. The public 91803 sample talks about savings and finishing a visit, not paying inside a text link.

Do not send ID photos, insurance cards, or selfies by SMS reply.

A Ro-branded lure can borrow healthcare language to make document requests feel normal. The known 91803 pattern sends you toward an online visit, not a reply bubble full of identity files.

Do not answer medical screening questions in the text thread.

Watch for prompts like reply with your dosage, list your conditions, or confirm your prescription choice. The sample uses SMS as a nudge to return to a visit, not as the visit itself.

Do not trust a text that says the 91803 thread has moved.

A lookalike may arrive from a regular ten-digit number or another short code and claim Ro changed numbers for security. That claim is cheap to write and does not connect the new sender to 91803.

Do not follow shortened links in a treatment-savings text.

A link like bit.ly, tinyurl.com, or a random tracking URL hides the destination until after the tap. That is a bad fit for a message asking you to resume a healthcare account flow.

Do not treat the word verified as verification.

Phrases like verified Ro billing team, official eligibility notice, or 91803 confirmed are just text. They do not name the short-code lessee, prove the link, or show that the sender can see your Ro account.

Do not rush because the discount has a deadline.

Scam copy likes expiring eligibility, final notice, and your visit will close language because it gets taps. The safe move is slower: open your account directly and see whether the same task exists there.

Save the message before you touch it.

Keep the sender, the full wording, the link, and the time received. If money or medical data gets involved later, that screenshot is the cleanest record of what actually arrived.

Open ro.co yourself if you have a Ro account.

Do not use the text as your login path. Sign in from the address you type or the app you already use, then check whether an online visit, order, or message is waiting there.

Compare the consent language at https://ro.co/terms-of-use/.

Use it for one narrow question: does Ro describe SMS for promotions, account messages, or care-related updates. Do not use the terms page to authenticate the 91803 sender.

Text STOP if you only want the promo thread to end.

Send exactly STOP in the same thread, then stop engaging. Do not answer any follow-up that asks for a password, date of birth, card number, or document upload.

Check https://lookup.robokiller.com/p/91803/ for complaint context.

Treat it as background, not a verdict on your exact text. Shared-code history and user reports can explain why the thread feels noisy, but your account is still the source of truth.

Use your phone’s spam-report button if the account check fails.

Report the message from the device, then block the sender after you have saved the evidence. Do not assume Ro sent it unless the same task appears after you open Ro directly.