Keep the first message narrow
Start with who you are, what page or issue you are writing about, why it matters, and the safest way to respond.
Contact and collaboration
Send a focused message without exposing private records.
Use contact for media, collaboration, verified source suggestions, record-accuracy resource leads, support-group leads, patient thanks, correction concerns, community safety ideas, and responsible partnerships. Keep the first note short and do not use ordinary email for emergencies, medical advice, legal advice, urgent care decisions, or private case handling.
Contact guide
Start hereRead privacy policySend a useful message without oversharing.
A first contact should explain the reason for reaching out, the general issue, and the type of response needed without attaching records or exposing sensitive identifiers.
Best first route
Send less, not more
Keep the first message focused. Do not send full records, prescription numbers, or private account details.
Good reasons to contact
Pain Care Rights can use responsible leads and collaboration ideas that strengthen the mission without exposing private patient information.
- Official agency, board, insurer, pharmacy board, representative, or patient-rights source links.
- Correction requests for outdated, unclear, or poorly routed site content.
- Media, advocacy, support-group, or public education collaboration.
- Community safety, moderation, concierge, and contact-routing suggestions.
- Mission-aligned resource ideas for patients and caregivers.
What not to send
Do not send emergencies, urgent medical decisions, full records, prescription numbers, account numbers, screenshots with private identifiers, or requests for individualized diagnosis, treatment, legal advice, or case handling.
How to make the message useful
A strong first message is short: the page or issue involved, what you noticed, why it matters, the public source if there is one, and the safest way to follow up.
Contact route check
Choose the safest contact path before sharing anything private.
Pain Care Rights keeps contact simple on purpose. Use the public tools for patient packets, use contact for focused source or collaboration notes, and keep sensitive records out of ordinary email.
I do not know where to start
Use the tool navigator or the small site guide first. They route you to the right public page without collecting private details.
Find the right toolI found a source, link, or wording concern
Send the page, the issue, and the public source that should be reviewed. Keep the message factual and narrow.
Use contactI want to help the work responsibly
Review what stays free, what support may fund, and why patients should never feel pressured for basic help.
Review supportWhat this contact flow does not do
These limits protect patients from oversharing and keep the site honest: contact is for focused notes, not emergency help, private case review, or guaranteed outcomes.
- No emergency monitoring or urgent medical handling.
- No private case review through ordinary email.
- No hidden form submission, stored message, or account requirement.
- No promise of a response, result, medication access, legal outcome, or official action.
Contact router
Send a useful lead, not a private file.
Contact should help improve the site, connect credible resources, or point to a safer path. The first message should be short enough to review and safe enough that the sender is not exposing sensitive health details by accident.
Source or correction lead
Best for a broken link, outdated source, unclear page wording, official contact lead, or a claim that needs stronger grounding.
Include: Page URL, public source link, state if relevant, and the exact issue to review.
Use contact optionsSupport group or advocacy lead
Best for credible support groups, patient organizations, advocacy allies, media leads, or professionals who may help strengthen the resource library.
Include: Name, public website, who it helps, and why it appears trustworthy.
Check directory standardsPersonal issue needing a packet first
Best when the message is really about a record problem, pharmacy barrier, care delay, appointment concern, or complaint route.
Include: Build the private packet first, then send only a limited summary if contact is still needed.
Choose a tool firstFirst-message rules
A careful first message protects the sender and makes it easier to tell whether the issue belongs in contact, an advocacy packet, or a formal route outside this website.
- Use one subject and one reason for contact.
- Send links instead of screenshots when possible.
- Do not send full medical records, prescription labels, account numbers, claim numbers, or urgent medical facts.
- Do not expect the contact page to provide emergency help, case management, legal advice, medical advice, or guaranteed response.
Privacy-first contact
Contact without exposing unnecessary medical details.
This page is for media requests, credible resource leads, correction concerns, support-group leads, and mission notes. Keep the first message focused and avoid sending full records, prescription numbers, account numbers, or urgent medical requests through email.
Media, interview, or collaboration inquiry
For interviews, podcast requests, advocacy partnerships, or public education opportunities connected to chronic pain, medication access, medical dismissal, dysautonomia, TBI symptoms, or patient documentation.
What to include: Include who you are, the deadline if there is one, the topic, and the safest way to respond. Do not send private medical records in the first message.
Open email draftAdvocacy resource or agency lead
For credible state agencies, medical boards, pharmacy boards, insurance departments, appeal resources, patient-rights guides, or public resources that may help patients find the right official route.
What to include: Send the official link, the state or jurisdiction, what the resource helps with, and why it appears reliable. Avoid screenshots when a direct source link is available.
Open email draftCorrection, source, or clarity concern
For outdated links, unclear wording, questionable claims, missing context, or anything that could weaken the site’s accuracy, trust, or usefulness for patients and caregivers.
What to include: Name the page, describe the concern, and include the source you believe needs review. Keep it factual so the issue can be checked quickly.
Open email draftPatient thanks, support group, or mission note
For brief encouragement, support-group leads, patient community ideas, or mission-aligned suggestions that do not require case handling or private medical review.
What to include: Share the short message, public link, or collaboration idea. Leave out private records, prescription details, account numbers, and urgent medical facts.
Open email draftContact helper safeguards
A contact helper should feel like a calm front desk, not another demand.
The safest helper is small, quiet, and route-focused. It should help visitors find the right page or contact lane without pretending to be medical care, legal advice, emergency help, or live staff.
I need help finding the right page
The active guide lets visitors type a short issue or tap a topic, then routes them to the right starting page without collecting private information or pretending to be live chat.
I am media or press
Media requests should funnel into a focused message with topic, outlet, deadline, contact details, and the safest public-facing summary.
I want to thank or encourage the mission
A patient or caregiver should be able to send a short thank-you without feeling asked to submit private medical details.
I want to collaborate
Advocates, attorneys, clinicians, support-group leaders, and resource owners should be routed into a structured collaboration note.
Rules that keep the guide from feeling annoying
A support guide should reduce confusion, not add another distraction. It should be polite, small, dismissible, and clear about what it can and cannot do.
- Do not open automatically or interrupt reading.
- Do not repeat the same greeting on every page view.
- Do not present the guide as a clinician, attorney, emergency service, or live support team.
- Do not ask for full records, prescription numbers, account numbers, or private screenshots in the widget.
- Do not send email until the user reviews the message and intentionally sends it.
- Keep any contact message review-first: the visitor should see what is being shared and choose whether to send it.
Contact stays review-first
Contact language should keep the visitor in control: choose the reason, write a narrow note, remove private records, review the exact wording, and understand that contact does not guarantee a reply or result.
The right guide should help without hovering.
The site guide should stay simple: typed issue, topic chips, and route buttons. Contact pages should protect privacy, avoid pressure, and keep every sensitive step review-first.
Protect private details before sending.
Read the privacy policy and disclaimer before sending anything that could identify a patient, provider, pharmacy, insurer, or case.