How to set up custom actions for pt appointment reminder …

You need a few things in place before you build the no-show action. Walk through the checklist first – skipping a step almost always causes the action to fail silently.

• A Chatref agent trained on your clinic’s operating details (hours, services, scheduling policies). This keeps the agent’s responses grounded in your practice.
• Admin access to the agent’s custom actions screen. In the Chatref dashboard, open your agent, then go to Custom Actions.
• A webhook URL or email API endpoint where you want the no-show notification to land. For example, your practice management system’s intake endpoint, a Slack channel for the front desk, or an email service like Postmark or SendGrid.
• If you want the reminder to reach the patient directly (SMS, WhatsApp, email), make sure you’ve already connected those channels under the agent’s omnichannel settings. That is a separate setup step – chatref won’t deliver messages on a channel you haven’t configured.
• A clear idea of the information you need from the patient. At minimum: patient name, appointment date/time, and a way to contact them back (phone or email). A brief reason for the no-show is helpful for follow-up but adds friction, so start minimal.

For Physical Therapy Clinics, your appointment data might live in a system like WebPT or Prompt, and your front desk may already use a Slack channel for real-time alerts. The custom action can push a formatted notification into either system so the team sees it right away.

The goal is one custom action that fires when a no-show scenario is detected, collects the right details, and triggers your notification. Build it once, then iterate.

1. Create a new custom action. In your agent’s Custom Actions tab, click Add Action. Give it a clear internal name like Record No-Show and Send Reminder.
2. Set a trigger description. In the When to trigger field, write a natural-language instruction that helps the agent recognise a no-show. For example:

   “Patient says they missed or will miss today’s appointment, or mentions no-show, missed visit, forgot appointment.” This prevents the action from firing on unrelated scheduling questions.

3. Define the fields the agent must collect. Under Collect these details, add fields for:
   • patient_name (string, required)
   • appointment_date (date or string, required)
   • appointment_time (optional, but helpful)
   • contact_method (select: phone, email, SMS – use the channel the patient prefers)
   • contact_value (the actual phone number or email)
   • reason (optional, free-text) Make only the first three required. The rest can be filled if the patient volunteers them, and the agent won’t stall the conversation.
4. Configure the action endpoint. Under Action to perform, choose Send HTTP request and paste your webhook URL. Chatref will POST the collected fields as a JSON payload. A minimal example payload looks like:

   {
     "patient_name": "Jane Doe",
     "appointment_date": "2026-07-10",
     "appointment_time": "14:00",
     "contact_method": "email",
     "contact_value": "jane@example.com",
     "reason": "Car trouble"
   }
   

   You can map these to your notification system’s expected format. If your webhook requires an API key, add it as a Custom header – e.g., Authorization: Bearer your_token.
5. Optionally, set a follow-up message for the patient. In the Response to patient box, put something like:
   “I’ve noted the no-show for your appointment on {appointment_date}. I’ll send a reminder to help you reschedule – keep an eye on your {contact_method}.” This closes the loop while your back-end handles the actual delivery.

If you have omnichannel configured, the same action can trigger a message on the patient’s preferred channel. For example, if they ask for a text reminder, your webhook can call Twilio or your clinic’s SMS provider, and the agent confirms the text is on its way. The custom action is just the trigger; you own the delivery logic.

After saving the action, test it with a conversation that looks like a real no-show. Open your agent’s playground and type something like:

“I missed my 2 pm PT appointment – can you help?”

The agent should ask for your name and appointment date (or confirm from the conversation context), then present the fields one by one. Once it collects enough, you’ll see the “action triggered” confirmation and the patient response. Check your webhook logs to confirm the payload arrived correctly. If the reminder is supposed to land in your front desk’s Slack, verify the message posted.

Test a few variations: a patient who knows the date but not the time; a patient who gives a phone number instead of email; a patient who doesn’t want a reminder at all. The action should gracefully degrade – if required fields are missing, the agent should ask again instead of failing silently.

The action never fires. Usually the trigger description is too narrow. Add more synonyms (missed session, cancel, running late) and test again. Also confirm the agent can see the custom action – check the action’s visibility settings are set to the agent you’re testing.

The webhook receives the wrong data. Field names in the payload must match exactly what your endpoint expects. If your endpoint wants patientName but you named the field patient_name, the data will be there but ignored. Rename the field in the action’s settings or adjust your receiving script.

Patients don’t get the reminder message. This is almost always a channel configuration gap. Confirm the omnichannel channel (email, SMS, WhatsApp) is connected and verified in your agent’s channel settings, and that the delivery provider (Twilio, SendGrid, etc.) is online. Test the channel separately by sending a manual message to the same address from the agent’s inbox.

The front desk doesn’t see the no-show in the EHR. Custom actions only send data; they don’t write back into your electronic health record. You’ll need a small middleware step – for example, a Zapier or Make.com workflow that receives the webhook and creates a note in WebPT or Prompt. Chatref can trigger that middleware but can’t integrate natively with every practice management system out of the box.

What causes pt appointment reminder no show problems for Physical Therapy Clinics?

Most no-shows happen because patients forget the appointment or don’t see the reminder in time. Clinics often rely on a single reminder method (one text 24 hours ahead) that patients miss. Operational friction – like a front desk too busy to call every patient – turns a minor scheduling gap into a lost revenue slot. An automated, multi-channel follow-up the moment a no-show is reported catches the patient while the topic is top of mind.

How do I improve pt appointment reminder no show for Physical Therapy Clinics?

Make it immediate and personalised. When a patient reports a missed appointment, collect their preferred contact channel and send a reminder right there in the conversation. Using Chatref’s custom actions, you can push that information to a workflow that fires a text, email, or WhatsApp message with rescheduling instructions. Pair this with omnichannel so the patient gets the follow-up on the channel they actually use, not just a generic email they may never open.