Agents and Clients in Repliers
Explains the role of agent and client records in the Repliers data model, how the two entities are related, and why creating them is necessary for personalized features such as saved searches, favorite listings, valuation updates, branded communications, automated alerts, and two-way email or SMS messaging; Related terms include “agent and client records,” “client belongs to agent,” “personalized alerts,” “favorites,” “saved searches,” “valuation emails,” and “two-way messaging”; This conceptual article explains why the entities exist and how they support personalization, while the implementation guide is the better match for detailed CRUD operations.Few readersSetting Up Integrated Email Messaging With Repliers
Walks through configuring Repliers integrated email and two-way messaging with a dedicated domain or subdomain, adding the required DNS and verification records, customizing templates without breaking Repliers syntax, and testing sending, links and replies before enabling automated saved-search, favorite or valuation communications for real clients; Related terms include “set up Repliers email,” “dedicated sending domain,” “subdomain,” “DNS records,” “domain verification,” “two-way replies,” “custom email templates,” “test message delivery,” and “saved-search alerts”; Its focus is the complete messaging-domain setup, not merely template markup or domain eligibility rules.Few readersHow to Use the Messages API to Streamline User Authentication with Message Tokens
Explains how outbound message links can carry a unique message token, how an application resolves that token back to the associated client and message, and how the pattern can establish a streamlined passwordless session or personalized landing page while still respecting MLS® authentication and data-display requirements; Related terms include “message token,” “passwordless link,” “identify the client from a message,” “personalized landing page,” “resolve token to client and message,” and “MLS® authentication compliance”; It is most relevant when link-based identity is built from Repliers message tokens rather than the automatic recipient-email query parameter.Few readersHow To Send Your First Message Using Repliers
Walks through the prerequisites and API calls for sending a first Repliers message, including creating or selecting an agent, creating the client recipient, establishing the relationship, submitting an agent-to-client message, confirming that it was accepted and delivered, and using the same foundation for later alerts and two-way automation; Related terms include “send my first email or SMS,” “create an agent,” “create a client,” “link agent and client,” “post a message,” “check delivery,” and “start two-way messaging”; Its focus is the minimal first-message sequence before saved-search or automated communication workflows are added.Few readersUnderstanding Email Domain Requirements For Our Messaging Service
Explains why Repliers messaging needs a dedicated domain or subdomain with compatible MX and verification records, how an existing corporate mail setup can conflict with those records, what domain configurations are acceptable, and how correct separation improves sender verification, reply routing and deliverability for automated and two-way email; Related terms include “email domain requirements,” “dedicated subdomain,” “MX record conflict,” “existing company email cannot share records,” “domain verification,” “reply routing,” “sender authentication,” and “deliverability”; It helps decide what domain architecture is valid before following the broader messaging setup steps.Few readersEmail Template Syntax Guide
Documents the syntax available in Repliers email templates, including variable interpolation, conditional blocks, loops, URL escaping and supported message fields, and provides common formatting patterns, validation advice and troubleshooting guidance for building personalized saved-search, favorite, valuation and messaging emails without breaking template rendering; Related terms include “email template variables,” “conditional content,” “loops,” “URL escaping,” “supported fields,” “saved-search template,” “favorite alert template,” “template parse error,” and “personalized email”; It is most relevant when the problem is authoring or debugging template markup rather than configuring the sending domain.Few readersAutomatic Email Parameter Integration In Messages
Explains how Repliers automatically appends the recipient’s email address as a parameter to links in outbound messages, allowing downstream pages and compatible systems such as Follow Up Boss to identify the visitor, associate link clicks with the correct lead, and preserve attribution without manually editing every template link; Related terms include “email address added to links,” “recipient query parameter,” “identify a lead from a click,” “Follow Up Boss attribution,” “outbound message tracking,” and “automatic link personalization”; It is most relevant when the behavior is the automatic recipient-email parameter, not general message-token authentication or email-template syntax.Few readersImplementation guide for agents and clients
Provides the full agents-and-clients API workflow, including creating, retrieving, filtering, updating, transferring, disabling, deleting and tagging records, and explains how those identities support ownership and segmentation for saved searches, favorites, valuation tools, outbound messaging and two-way conversations; Related terms include “agents endpoint,” “clients endpoint,” “create or update client,” “transfer a client,” “disable or delete an agent,” “tags,” “filter records,” and “connect records to favorites, searches, or messages”; Its focus is detailed lifecycle operations rather than the conceptual overview of agents and clients.Few readers