Start in Settings → Integrations and open the connection. QR Rx shows the last visit received, the last visit processed, anything still processing, and any failed deliveries. Do not create a second connection while troubleshooting. The existing private link is tied to the clinic and location.
1. Read the connection status
- Waiting for first test visit: setup exists, but QR Rx has not processed a real completed visit yet.
- Live and receiving: at least one completed visit has passed the full workflow.
- Processing: QR Rx received the visit and is still working on it. Refresh after a minute.
- Needs attention: a delivery exhausted its automatic retries or the vendor credentials failed.
2. Run the five-minute checks
- Confirm the appointment was completed or checked out, not merely booked, changed, or cancelled.
- Confirm it happened at the location attached to this connection.
- Check that the patient has the contact information needed for your chosen delivery channel.
- Open Care Feed and look for an unmatched service or another item needing review.
- Compare the test time with Last received. This tells you whether the vendor reached QR Rx.
3. Retry failed deliveries safely
If the connection shows failed deliveries, fix the problem named underLatest issue, then click Retry failed. QR Rx keeps the original event identity, so retrying the same visit cannot create a second draft.
Do not ask staff to recreate the patient or appointment.
Retry the delivery first. Recreating records can produce a genuinely new vendor event and make the situation harder to untangle.
4. Check the vendor side
- Vagaro: open Settings → APIs & Webhooks, confirm the Appointments webhook is active, and verify the selected location.
- Mangomint: ask authenticated chat support to confirm the Sale completed webhook is active for the approved locations.
- Zenoti: check Configuration → Integrations → Webhooks and its failure log. Repeated failures can cause a webhook to be deactivated.
5. Contact QR Rx if it still does not arrive
Send the clinic name, location, connection name, vendor, and approximate test time through QR Rx support. Never include patient information, API keys, client secrets, or webhook secrets.