No. Patients communicate via SMS, so there are no downloads, logins, or portals. This keeps engagement high, especially for older patients or less tech-savvy populations.

PostSurgy is an agentic care coordination layer for procedural practices that automates readiness, follow-up, and logistics while escalating exceptions using clinic-defined guardrails.

PostSurgy is built around coordinated agents and escalation, not just campaigns. Routine questions and workflows follow your approved pathways, and exceptions are routed to the right role with structured context.

Guardrails are the rules your clinic defines for what the agent can answer, what requires coordinator review, and what must escalate to a clinician. Guardrails can vary by procedure type and time period (pre-procedure vs recovery).

When a patient response matches your escalation criteria. Escalations include context such as timeline, the patient’s responses, and the triggering pathway, so clinicians can act quickly without digging through message history.

Yes. The default flow supports patient and coordinator coordination, and clinicians can be pulled into the same conversation when escalation requires clinical review or a decision.

PostSurgy automates procedure readiness, follow-up, and internal logistics across the patient journey. Common workflows include prep instructions and confirmations, recovery check-ins, education, follow-up scheduling nudges, and logistics tasking such as insurance approval tracking and missing requirements.

Most practices can launch an initial procedure workflow in 2 to 4 weeks, depending on procedure complexity, message review cycles, and your escalation policy. We typically start with one high-volume procedure and expand from there.

Yes. You can start from proven templates or customize content, timing, tone, and pathways by procedure. No code is required.

Dashboards and reports can include engagement, check-in completion, escalations, symptom pathway trends, and workflow performance by procedure and time window.

PostSurgy is hosted on AWS using HIPAA-eligible services and supports HIPAA-aligned safeguards. BAA is available. Data is encrypted in transit and at rest, and access is protected with audit trail, role-based access, and MFA.

Patients can opt out at any time. Practices can also define fallback instructions for opt-out scenarios (for example, call the clinic for questions).

No. PostSurgy is designed for procedure coordination and follow-up, not emergency response. Patient messages should include clear instructions for urgent or emergency symptoms based on your clinic’s policy.

Yes. PostSurgy supports any language, and the agent adapts to each patient’s preferred language. Practices can configure language preferences up front, and workflows, education, and check-ins will follow that preference throughout the procedure journey.

PostSurgy works well for small to mid-sized clinics and outpatient centers, and can scale across multiple procedures and sites with consistent guardrails and templates.