Client communication works best when it is attached to the service record

Why Collar is different: connected work, not just a calendar

Collar brings the pet-business journey into one operating picture: a customer books for a specific pet, the team delivers the service, and the related order, payment and follow-up stay connected. Depending on the business, that same platform can also support products, memberships, staff, branches and field routes. The value is in how the enabled parts work together—not a claim that other tools cannot offer them.

Keep messages close to context

Staff should be able to understand the customer, pet, booking, payment, and history before replying.

• Client and pet profiles
• Booking and order context
• Payment visibility
• Notes and forms

Make reminders useful

Reminders should reduce admin, improve attendance, and prompt needed customer action.

• Appointment reminders
• Form completion
• Vaccine and document prompts
• Payment and pickup instructions

Use campaigns carefully

Campaigns should support rebooking, memberships, retail, seasonal services, and customer education without overwhelming pet parents.

• Segmented audiences
• Service-specific offers
• Reactivation campaigns
• Membership and package messaging

Match the message to the booking state

A confirmation, a request for information, a waitlist acknowledgement and a campaign have different purposes. Write one template for each state and check the data it includes. A pet owner should always understand whether they have a confirmed booking and what action to take next.

• Keep pet health or handling details out of SMS lock screen previews.
• Make staff ownership of replies and failed delivery explicit.
• Check campaign audiences against current bookings and stated contact preferences.
• Test the sequence after cancellation or rescheduling so obsolete messages are not sent.

Audit the complete customer conversation

Map the messages an owner sees from first enquiry through rebooking. Each has a distinct job: acknowledgement, request for missing information, confirmation, reminder, change, collection update or follow-up. A good template makes the next action obvious without exposing sensitive pet details in a lock-screen preview.

• Test the sequence after a reschedule and a cancellation; obsolete details must not continue to send.
• Assign a person to monitor replies and failed delivery, especially for care-related questions.
• Separate service messages from promotional campaigns and respect contact preferences.
• Use real but fictionalized examples to check tone and clarity on a phone screen.

Make every template answer one question

An owner reading on a phone should immediately understand whether a service is confirmed, what they need to bring and how to reply. Overloaded messages are easy to skim incorrectly. Separate confirmation, preparation, reminder, change and follow-up so each can be tested against a single customer action.

• Use the pet name and correct location, but omit sensitive medical details.
• Distinguish a request acknowledgement from a confirmed appointment.
• Include the relevant cancellation or change route.
• Read the message aloud and remove language that hides the next step.

Design for exceptions and consent

Communication rules should account for a wrong number, unread in-app message or an owner who has opted out of marketing. Service notices and promotions have different purposes and may have different legal treatment. Decide who follows up when a critical message fails.

• Verify contact details when the owner makes a booking.
• Route failed delivery and replies to a named staff role.
• Respect campaign preferences and avoid using care messages for marketing.
• Recheck a changed appointment so the old time is not sent later.