Overview
Custom Values in PXME allow you to personalize communication, automate repetitive tasks, and standardize workflows. By using placeholders (merge fields), PXME automatically pulls in the correct contact, appointment, or company information, saving time and ensuring consistency across messages, emails, and automations.
What Are Custom Values?
Custom Values act like shortcuts. Instead of typing details manually (like a contact’s name or appointment time), you insert a placeholder, and PXME fills in the correct data when the message is sent.
Example:
Message with Custom Value:
“Hi {{contact.first_name}}, your appointment is scheduled for {{appointment.start_time}}.”Message client receives:
“Hi Sarah, your appointment is scheduled for Tuesday at 3:00 PM.”
Types of Custom Values
Contact Information
First name, last name, phone, email.
Personalize texts, emails, and reminders.
Company Information
Business name, phone, email, and address.
Ideal for email templates and signatures.
Appointment Details
Appointment date, time, and service.
Perfect for confirmations and reminders.
User/Staff Information
Staff name, email, or calendar link.
Useful for scheduling and lead assignments.
Custom Fields
Fields you create to capture unique info (child’s age, referral source, etc.).
Adds flexibility for pediatric or family-specific data.
How to Insert a Custom Value
While creating a message, email, or workflow, place your cursor where the value should appear.
Click Custom Values.
Select the category (Contact, Company, Appointment, etc.).
Choose the specific field (e.g., {{contact.first_name}}).
Save your work.
Best Practices
Always test messages with a sample contact to confirm values populate correctly.
Use Custom Values in templates to save time and ensure consistency.
Keep personalization natural—avoid overloading messages with too many placeholders.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article