Learn about the fields, workflows, triggers and actions in the PatientNow Pro integration, and the EMR Appointments calendar.
Note: We also offer a PatientNow Essentials integration, which is covered in a separate help article. The two integrations share the same custom fields and pipeline logic, but differ in which statuses PatientNow sends, how orders and memberships come through, and what's needed to create a patient. See the comparison table below.
Opportunity & pipeline automation to decrease manual data entry and drive reporting efficiency
Appointment categorization for dual-pipeline practices (plastic surgery + med spa)
An EMR Appointments calendar in Aesthetix CRM that mirrors PatientNow Pro, so appointment reports match your schedule
Automate Google review collection after appointments
Automate post-appointment follow-up
Automate patient retention campaigns for specific treatment and service types
Collect data for better patient segmentation
Automated birthday campaigns
Patient lifetime value tracking from completed patient bills
Two-way sync to create patients in PatientNow Pro from Aesthetix CRM
The integration uses AX Connect, a HIPAA-compliant middleware platform that runs all integrations between Aesthetix CRM and your EMR.
Your practice must have paid API access with PatientNow, which requires a monthly integration fee of $149/month paid directly to PatientNow.
Aesthetix CRM does not collect any additional integration fee and completely sets up the integration for you.
This is a two-way sync between PatientNow Pro and Aesthetix CRM using PatientNow webhooks and Aesthetix CRM actions. Updates usually appear in Aesthetix CRM within about a minute of the change in PatientNow Pro. Cancellations take about 10 minutes (see Reschedules below).
In October 2026 we rebuilt the PatientNow Pro sync. PatientNow sends the same events as before (new patients, patient updates, appointments, completed bills and memberships), but every appointment change now goes through one update process for your practice. That process decides whether the change is real, puts it in the right order, and then updates the contact, runs your workflows and updates the EMR Appointments calendar.
For multi-location practices, we read the location from each appointment and write it to the PNOW Location custom field. If each of your locations has its own Aesthetix CRM account, each location's appointments go to that location's account.
Note: PatientNow Pro and PatientNow Essentials share the same custom fields in Aesthetix CRM. Some field names may be labeled differently between the two platforms, but they serve the same purpose.
PatientNow Pro often sends the same appointment several times, even when nothing about it has changed. We now only send a change to Aesthetix CRM when something that matters has changed:
the appointment status
the date, time or length
the provider
the appointment type
the location
Editing only an appointment's comments, reason or deposit sends nothing. This means you should no longer see the same appointment repeated in a contact's notes, or the same workflow running twice for one appointment.
If PatientNow sends an appointment's booking after that same appointment has already been checked out, cancelled or marked as a no-show, the late booking is ignored, so the contact doesn't move backward in the pipeline.
PatientNow Pro status | What happens in Aesthetix CRM |
|---|---|
Booked | Contact updated with Next Visit Date and Next Visit Service, and moved to the booked stage |
Checked In | Shows as Showed on the EMR Appointments calendar only. The contact and pipeline don't change until checkout. |
Checked Out | Contact updated with Last Visit Date and Last Visit Service, and moved to the completed stage |
Cancelled | Moved to the Cancelled / No-Show stage, about 10 minutes later (see Reschedules) |
No-Show | Moved to the Cancelled / No-Show stage |
Deleted | Shows as Invalid on the EMR Appointments calendar only. The contact and pipeline don't change. |
When you reschedule in PatientNow Pro, we recognize that the old appointment was replaced, and its cancellation or deletion isn't sent to Aesthetix CRM. A rescheduling patient doesn't drop to the Cancelled / No-Show stage, and the new booking comes through as normal.
We recognize a reschedule two ways:
The new appointment carries a link to the one it replaces.
A cancellation waits about 10 minutes before it's sent. If the same patient is booked into another appointment within 10 minutes of the cancellation (before or after it), we treat it as a reschedule and the contact stays on the new booking.
On the EMR Appointments calendar, the replaced appointment shows as Invalid, even when PatientNow sends nothing for it.
When one patient has several changes at once, we hold them for about a minute, then send them 20 seconds apart in this order: cancellations and no-shows first, then checkouts, then bookings. Bookings go in pipeline order: pre-op, post-op and follow-up visits first, then other visits, and surgery last. The contact ends on their newest booking and doesn't appear to move backward in the pipeline.
For practices that use appointment categories (plastic surgery and med spa practices).
After a checkout, cancellation or no-show, we check whether the patient has another upcoming appointment. If they do, the contact moves back to that appointment's booked stage (for example, Surgery Scheduled), and Next Visit Date and Next Visit Service show it. When there are several, a surgery comes first, then a surgical consult, then other appointments, and the soonest of those.
A change to an appointment that started more than 7 days ago updates the contact's fields and the EMR Appointments calendar, but doesn't move the pipeline or start a workflow. This stops old charts being closed out from moving patients backward.
We check the email and phone number on each PatientNow patient before writing them to Aesthetix CRM:
Placeholder emails (such as a shared "noemail" address) and invalid emails are dropped. This stops unrelated patients being merged into one contact because they share a placeholder email.
Phone numbers are formatted with the +1 country code. International numbers are kept as they are.
A patient with a valid phone number but no usable email is matched and synced by phone.
A patient with neither a usable email nor phone is not synced.
The same checks apply to patient, bill and membership updates, not only appointments.
What triggers it: Any update to a patient record in PatientNow Pro (name change, address update, etc.).
What happens:
We receive the webhook and check the email and phone number (see Email and Phone above).
We create or update the contact in Aesthetix CRM with the updated information.
No workflow is triggered. This simply keeps the contact record in sync.
Fields updated in Aesthetix CRM:
First Name, Last Name, Phone
PNOW ID
Gender
City, State, Address, Zip Code (if collected by the practice and configured)
What triggers it: A new patient is created in PatientNow Pro.
What happens:
We immediately create or update the contact in Aesthetix CRM with core contact information.
If the patient already exists in Aesthetix CRM, we simply update their existing record.
Fields updated in Aesthetix CRM:
First Name, Last Name, Email, Phone
Referral Source (if available)
PNOW ID
Gender
Important: PatientNow Pro allows you to create patients without an email or phone number. Aesthetix CRM needs at least a usable email or phone to create a contact. If neither is present, the contact will not be created in the CRM.
What triggers it: A new appointment is created in PatientNow Pro.
What happens:
We check that something has changed (see What counts as a change above).
We read the patient's details from PatientNow Pro and check their email and phone.
We look up the appointment's category from your practice's appointment types, which decides the pipeline and stage.
We update the contact in Aesthetix CRM and add them to the PatientNow Appointments Update workflow.
We add or update the appointment on your EMR Appointments calendar.
Fields updated in Aesthetix CRM:
First Name, Last Name, Email, Phone
PNOW Primary Employee (the appointment's provider)
Next Visit Service
Next Visit Date
Gender
PNOW Location (facility)
Lead Status
Appointment Category
PNOW Appointment Comments
PNOW Event Type
PNOW Last Appointment ID
PNOW Appointment Reason
Workflow actions in Aesthetix CRM:
The contact is added to the PatientNow Appointments Update workflow, which handles all pipeline movement logic (see the Appointment Categorization & Pipeline Logic section below).
A contact note is added with: appointment status, event type, appointment reason, appointment category, and appointment ID.
What triggers it: An appointment status changes in PatientNow Pro. The statuses that update the contact and pipeline are Checked Out, Cancelled, No-Show and Deleted. Checked In only updates the EMR Appointments calendar.
What happens:
The same steps as New Appointment Booked: we read the patient, check email and phone, and look up the appointment category.
All the same fields are updated, except Next Visit Service and Next Visit Date (since this is a status change, not a new booking).
On checkout, we also update Last Visit Date and Last Visit Service. Last Visit Service is the service of the appointment that was checked out.
A cancellation or deletion of an appointment that was rescheduled is not sent (see Reschedules above).
The contact is added to the same PatientNow Appointments Update workflow for pipeline movement.
What triggers it: A new patient bill is completed (payment processed) in PatientNow Pro.
What happens:
We receive the webhook, read the patient's details and check their email and phone.
We combine the bill's line items into one list (for example, "Botox, Dysport, Hydrafacial") and save it as Last Purchase.
We capture the invoice amount, invoice ID and date of birth.
We check whether this bill has already been counted. PatientNow Pro sometimes sends the same completed bill more than once, for example after the bill is edited. If the total hasn't changed, we stop here: nothing is updated and the contact isn't added to the workflow again. If the total has changed, only the difference is counted.
The contact is added to the PatientNow Order Paid workflow in Aesthetix CRM.
Fields updated in Aesthetix CRM:
Invoice Paid Amount (the amount counted for this bill: the full total the first time, then only the difference if the bill's total changes)
Last Purchase (the bill's line items)
PNOW Last Order ID
PNOW DOB (Date of Birth)
What changed in October 2026: bills used to write their line items to Last Visit Service and the selling staff member to PNOW Primary Employee. Last Visit Service now comes from the checked-out appointment, PNOW Primary Employee comes only from appointments, and the line items go to the new Last Purchase field. Last Purchase was added on October 29, 2026 and isn't backfilled: it fills in from each patient's next completed bill.
Workflow actions in Aesthetix CRM:
A contact note is added with: order total, line items (from Last Purchase), and order ID. The order total in the note is the amount counted, so after an edited bill it shows the difference, which can be negative.
The contact is added to the Birthday workflow (see Birthday Field Sync section below).
The Invoice Paid Amount is added to the Patient Lifetime Value via a math function.
The opportunity value is updated with the patient lifetime value.
What changed in November 2026: before November 2, 2026, a bill that PatientNow Pro sent more than once was added to Patient Lifetime Value each time, which could inflate lifetime value and the opportunity value. Each bill now counts once, and an edited bill counts only the change, so each bill adds its final total. Lifetime values recorded before that date aren't recalculated.
Note on surgical vs. non-surgical opportunity updates: By default, opportunity values are updated on the non-surgical pipeline. If you would like opportunity values updated on the surgical pipeline as well, this is available. Request it as part of your integration setup.
What triggers it: A new membership is created in PatientNow Pro.
What happens:
We read the patient's details, check their email and phone, and read the membership start date.
We update the contact in Aesthetix CRM with membership information.
The contact is added to the Membership Update workflow.
Fields updated in Aesthetix CRM:
PNOW Membership ID
PNOW Membership Program Name
PNOW Membership Sold Date
Workflow actions in Aesthetix CRM:
A Membership tag is added to the contact.
The tag can optionally be made dynamic based on the membership name (for example, "Membership - VIP Gold").
Customization Available: We can move this out of the locked workflows if you'd like to build custom automations. You can also use the Membership tag as a trigger in your own workflows to send email or SMS drip campaigns to new members.
What triggers it: A tag called pnow-create is added to a contact in Aesthetix CRM (either manually or via automation).
What happens:
The tag triggers a workflow in AX Connect that reads the contact's details.
We check for a date of birth. If there isn't one, we add the tag PNOW: needs DOB to the contact and stop. Nothing is created.
We send a create patient request to PatientNow Pro. The patient is usually created within 30 seconds to 1 minute, with the referral source AXCRM in PatientNow.
If PatientNow already has a patient with the same first name, last name and date of birth, PatientNow refuses to create a duplicate. We treat this as done: no second patient is created.
Fields to fill in before adding the tag:
Date of Birth (required; any common format works, for example 3/12/1985 or 1985-03-12)
First Name
Last Name
Gender
Date of birth is the one field we check before sending: without it, the contact gets the PNOW: needs DOB tag and nothing is sent. Fill in first name, last name and gender too. If PatientNow rejects a patient because one of them is missing, the rejection isn't reported back to Aesthetix CRM, so the contact gets no tag or note.
If the contact gets the PNOW: needs DOB tag: add the date of birth to the contact, remove both the PNOW: needs DOB and pnow-create tags, then add pnow-create again.
Common reasons a patient isn't created:
No date of birth (the contact gets the PNOW: needs DOB tag)
Missing first name, last name or gender (PatientNow rejects the patient, and the rejection isn't shown in Aesthetix CRM)
The patient already exists in PatientNow Pro with the same name and date of birth (no duplicate is created, by design)
If none of these applies, or adding the tag does nothing, contact support.
Your PatientNow Pro appointments also appear on a calendar in Aesthetix CRM named EMR Appointments. The calendar went live for PatientNow Pro practices on October 29 and 30, 2026.
Practices with several locations have one calendar per clinic, med spa and surgery center (for example, EMR Appointments · Downtown). Telehealth appointments and appointments at a location added later appear on your main location's calendar. If each of your locations has its own Aesthetix CRM account, each account has its own calendar.
What it's for: The calendar lets the CRM's appointment reports show confirmed, showed, cancelled and no-show counts that match PatientNow. It is a mirror of PatientNow Pro, not a booking calendar.
How appointments appear:
PatientNow Pro status | Calendar status |
|---|---|
Booked | Confirmed |
Checked In, Checked Out | Showed |
Cancelled | Cancelled |
No-Show | No-Show |
Deleted | Invalid |
When a patient reschedules, the original appointment is marked as rescheduled (it shows as Invalid on the calendar), so it doesn't count as a cancellation, and the new booking appears.
Times are shown in your location's time zone.
Patients with no usable email or phone don't appear on the calendar.
Block appointments don't appear on the calendar.
Only appointments created or changed in PatientNow Pro since your calendar went live appear. Older future appointments appear the next time they change in PatientNow.
The calendar is silent. It sends no confirmations, reminders or cancellation messages to patients, and no alerts to your team. We check it every day to make sure it stays silent.
Please don't:
Book, edit, move or delete appointments on the EMR Appointments calendar. Make changes in PatientNow Pro; the calendar follows.
Turn on notifications, reminders or Google invitations for this calendar.
Build a workflow with an Appointment Status trigger without a calendar filter. An unfiltered Appointment Status trigger fires for every synced PatientNow appointment, which can send patients duplicate messages. If you build appointment workflows, filter them to the calendars they are meant for.
For plastic surgery + med spa practices, the integration uses appointment categorization to route contacts to the correct pipeline and stage. This is one of the most powerful aspects of the PatientNow Pro integration.
During setup, each appointment type in PatientNow Pro is mapped to one of these appointment categories. The integration looks up each appointment's category from that mapping.
Surgical Consult
Surgical Appointment
Non-Surgical Consult
Non-Surgical Appointment
Block (does not update opportunities)
Post-Op (does not update opportunities)
Pre-Op (does not update opportunities)
Important: Post-Op and Pre-Op appointments don't update opportunities: the contact isn't moved in the pipeline, but its fields and notes are still updated. Block appointments aren't sent to Aesthetix CRM at all: no note, no field change, no pipeline move, and they don't appear on the EMR Appointments calendar.
Surgical Pipeline:
Appointment Category | Status | Pipeline Stage |
|---|---|---|
Surgical Consult | Booked | Consult Booked |
Surgical Consult | Checked Out | Consult Complete |
Surgical Consult | Cancelled / No-Show / Deleted | Cancelled / No-Show |
Surgical Appointment | Booked | Surgery Scheduled |
Surgical Appointment | Checked Out | Surgery Complete |
Surgical Appointment | Cancelled / No-Show / Deleted | Cancelled / No-Show |
Non-Surgical Pipeline:
Appointment Category | Status | Pipeline Stage |
|---|---|---|
Non-Surgical Consult | Booked | Booked |
Non-Surgical Consult | Checked Out | Patient |
Non-Surgical Appointment | Booked | Booked |
Non-Surgical Appointment | Checked Out | Patient |
Non-Surgical Consult / Appointment | Cancelled / No-Show / Deleted | Cancelled / No-Show |
Note for non-surgical-only practices: If your practice performs consults and treatments on separate days (rather than same-day), we can configure Consult Booked and Consult Completed stages on your non-surgical pipeline as well. Let us know during integration setup.
The workflow also checks whether a contact is a lead or an existing patient:
Existing patients maintain a single "won" status throughout the pipeline as they move between stages.
New leads keep an open status until they check out, at which point they're moved to the appropriate completed / patient stage.
The integration can't write the CRM's native Date of Birth field directly. To work around this, we bring the birthday from PatientNow Pro into a custom field called PNOW DOB.
A dedicated Birthday workflow then copies the value from PNOW DOB into the native Date of Birth field, keeping them in sync. This ensures that any birthday automations you've built in the CRM work correctly using data from PatientNow Pro.
The Birthday workflow runs when a contact enters the Order Paid workflow, since we have the date of birth from the completed bill at that point.
Several workflows in your Aesthetix CRM account are hidden and locked. This is intentional: these workflows contain the core integration logic, and modifications could break the integration. The locked workflows include:
PatientNow Appointments Update
PatientNow Order Paid
PatientNow Membership Update
PatientNow Birthday
If you need custom automation built on top of any of these (for example, a membership drip campaign), let us know and we can either unlock specific workflows or help you build triggers off of the tags and fields these workflows create.
All PatientNow-specific fields are organized in a PatientNow folder within your custom fields. These fields are shared between the PatientNow Pro and PatientNow Essentials integrations.
Custom Field Name | Type | Custom Value |
|---|---|---|
PNOW ID | Text |
|
PNOW Appt Status | Text |
|
PNOW Location | Text |
|
PNOW DOB | Date |
|
PNOW Unsubscribed | Single Options |
|
PNOW Last Order ID | Text |
|
PNOW Last Appt ID | Text |
|
PNOW Membership Sold Date | Date |
|
PNOW Membership Program Name | Text |
|
PNOW Membership ID | Text |
|
PNOW Membership Amount | Monetary |
|
PNOW Primary Employee | Text |
|
PNOW Event Type | Text |
|
PNOW Appt Reason | Text |
|
PNOW Appt Comments | Text |
|
In addition to the PatientNow-specific fields above, the integration also updates these standard Aesthetix CRM fields:
Next Visit Date and Next Visit Service (from booked appointments)
Last Visit Date and Last Visit Service (from the checked-out appointment)
Last Purchase (from the completed bill's line items)
Patient Lifetime Value
Invoice Paid Amount
Lead Status
Appointment Category
Gender
Contact Type
First Name, Last Name, Email, Phone
City, State, Address, Zip Code (if configured)
A usable email or phone is required. Placeholder and invalid emails are dropped. A patient with neither a usable email nor phone isn't synced, and doesn't appear on the EMR Appointments calendar.
Only real changes are sent. Editing an appointment's comments, reason or deposit alone sends nothing to Aesthetix CRM.
Checked In doesn't move the pipeline. It shows as Showed on the calendar; the contact and pipeline update at checkout.
Deleted appointments don't move the pipeline. They show as Invalid on the EMR Appointments calendar. A rescheduled appointment's cancellation or deletion is not sent.
PatientNow Pro doesn't always send cancellations and deletions. When PatientNow sends nothing for a plain cancellation (not a reschedule), the contact stays at its last stage and the calendar keeps the appointment as booked until it changes again. This is a PatientNow limitation.
Cancellations take about 10 minutes, and several changes for one patient take a little longer. A cancellation waits 10 minutes in case it's a reschedule. Several changes for one patient are held for about a minute, then sent 20 seconds apart: cancellations and no-shows first, then checkouts, then bookings, surgery last.
Last Visit Service is the checked-out appointment's service. The bill's line items go to Last Purchase, which fills in from each patient's next completed bill (no backfill).
PNOW Primary Employee is the appointment's provider. Bills no longer change it.
The EMR Appointments calendar is a read-only mirror. Don't book or edit on it, and filter any Appointment Status workflow to the calendars it's meant for, or it fires for every synced appointment.
Birthday uses a workaround. PNOW DOB is copied into the native Date of Birth field by a workflow, when a bill is completed.
Surgical opportunity value updates are opt-in. By default, only non-surgical pipeline opportunities get their values updated with Patient Lifetime Value.
Block, Post-Op and Pre-Op don't move the pipeline. Block appointments aren't sent at all. If a contact isn't moving in the pipeline, check whether their appointment is categorized as one of these.
Creating a patient needs a date of birth. Without one, the contact is tagged PNOW: needs DOB and nothing is created. Fill in first name, last name and gender too, because a rejection from PatientNow isn't reported back to Aesthetix CRM.
Custom fields are shared between Pro and Essentials. If you migrate between PatientNow versions, the same fields carry over.
Each bill counts once toward Patient Lifetime Value. A bill PatientNow sends again with the same total is ignored. An edited bill adds only the difference, which can be negative. Lifetime values recorded before November 2, 2026 aren't recalculated.
Only recent appointments move the pipeline. A change to an appointment that started more than 7 days ago updates the contact's fields and the calendar, but doesn't move the pipeline or start a workflow.
Feature | PatientNow Pro | PatientNow Essentials |
|---|---|---|
Sync method | Webhooks (about a minute; cancellations about 10 minutes) | Webhooks (about a minute) |
Cancelled status | Sent (not always, see limitations) | Never sent by PatientNow |
No-show timing | Immediate | Batch overnight (around midnight) |
Reschedule detection | Yes | No |
Moves to Patient / completed stage | On appointment checkout | Non-surgical: when the order is paid. Surgical: Consult Complete and Surgery Complete aren't set |
Payment trigger | Patient bill completed | Order completed (checkout) |
Membership trigger | Dedicated membership webhook | Part of the order |
PNOW Initial Visit field | Not used | Used |
PNOW Appointment Comments, Reason, Event Type | Used | Not used |
Patient creation tag | pnow-create | pnow-create |
Patient creation fields | Date of birth required; first name, last name and gender needed by PatientNow | 4 required (first name, last name, email, phone) |
EMR Appointments calendar | Yes | Yes |
Pipeline logic | Identical | Identical |
How do I know the integration received an appointment? Check the contact's Notes tab. Every appointment change adds a note with the appointment status, event type, appointment reason, appointment category and appointment ID. If there's no note, either we didn't receive the change or nothing that counts as a change was edited (see What counts as a change above).
Why don't I see a note when an appointment is edited? We only send a change when the status, date, time, length, provider, appointment type or location changes. Editing only comments, reason or a deposit sends nothing, by design.
Why didn't checking in a patient move them in the pipeline? Checked In only updates the EMR Appointments calendar. The contact moves when the appointment is checked out.
Why didn't a rescheduled patient move to Cancelled / No-Show? When you reschedule in PatientNow Pro, we recognize that the old appointment was replaced and don't send its cancellation. The new booking comes through as normal.
A patient cancelled and rebooked. Why didn't they move to Cancelled? When the new booking comes in within about 10 minutes of the cancellation, we treat it as a reschedule and the contact stays booked. At practices that use appointment categories, a patient who cancels but still has another upcoming appointment also moves back to that appointment's stage.
Why did a cancellation never reach Aesthetix CRM? PatientNow Pro doesn't always send a webhook when an appointment is cancelled or deleted. If a contact should have moved to Cancelled / No-Show and didn't, update the contact's stage manually and let support know the patient and roughly when the cancellation was made.
Why is a contact stuck in the wrong pipeline stage? Review the contact's notes for the audit trail. Common causes include an appointment categorized as Block, Post-Op or Pre-Op (which don't update opportunities), an appointment type mapped to the wrong category, or a cancellation PatientNow didn't send. Contact support if you need help investigating.
Why does Last Visit Service show something different from what the patient paid for? Last Visit Service is the service of the appointment that was checked out. What was billed is in Last Purchase. Last Purchase started filling on October 29, 2026, so it's blank for a patient until their next completed bill.
Why does an Order Paid note show a small or negative order total? The note shows the amount counted for that bill. When a completed bill is edited in PatientNow Pro and sent again, we count only the change, so the note shows the difference (for example, -$150 after a discount). Each bill's contribution to Patient Lifetime Value then equals its final total. If PatientNow sends a bill again without changing its total, nothing is added and no note appears.
Why didn't a patient get created in PatientNow Pro after I added the pnow-create tag? If the contact now has the PNOW: needs DOB tag, add their date of birth, remove both tags, and add pnow-create again. Otherwise check that first name, last name and gender are filled in: PatientNow rejects a patient missing any of them, and that rejection isn't shown in Aesthetix CRM. If PatientNow already has a patient with the same name and date of birth, no duplicate is created, by design. Contact support if none of these applies.
Why are there appointments on an EMR Appointments calendar I didn't book? That calendar mirrors PatientNow Pro so your appointment reports match it. It's silent (no messages to patients), and changes belong in PatientNow, not on the calendar. Appointments from before your calendar went live appear once they next change in PatientNow.
Can I build custom automations off the integration? Yes. You can use the tags added by our workflows (for example, Membership) as triggers for your own workflows, or trigger off custom field changes. If you build on Appointment Status, filter the trigger to the calendars it's meant for. If you need a locked workflow unlocked for customization, contact us.
How do appointment categories get mapped? During integration setup, we work with you to classify each of your PatientNow Pro appointment types into the appropriate category (Surgical Consult, Surgical Appointment, Non-Surgical Consult, Non-Surgical Appointment, Block, Post-Op, Pre-Op). If you add new appointment types later, contact us to get them categorized.
Does the integration support multi-location practices? Yes. The location of each appointment is written to the PNOW Location field. Practices with several locations get one EMR Appointments calendar per location, and if each location has its own Aesthetix CRM account, each location's appointments go to that account.
If something isn't syncing the way you expect, contact Aesthetix CRM support with the contact's name and roughly when the change was made in PatientNow Pro. For custom automation built on top of the integration, submit a Custom Build Request.