RCS for Home Services

Top use cases

• Appointment confirmation and reminders. A branded message with the date, the arrival window and one-tap Confirm or Reschedule, aimed at the no-access visits that cost a whole slot.
• Technician on the way. The tech's name and photo sent before arrival, so the customer knows who is at the door. In our view this is the highest-value message in the category.
• Quote and repair approval. Photos or a short clip of the actual problem, the finding, the price, and an Approve button, so work is authorised without a callback.
• Review requests and rebooking. A branded request sent while the job is still fresh, and seasonal service reminders that arrive looking like the business rather than like spam.

In practice

A homeowner books an HVAC service call and gets a branded confirmation with the arrival window and a Reschedule button. On the morning, a message arrives with the technician's name and photo and a live arrival estimate. On site, the technician sends a short clip of a failing capacitor with the price and an Approve repair button; the homeowner taps Approve while standing in the kitchen. After the visit, a review request arrives from the same verified thread the whole job ran in. The next section lays that out message by message.

The arrival sequence, message by message

The sequence below is illustrative: Comfort Air is a fictional HVAC company and Marco a fictional technician, written for this guide rather than captured from a live send. It shows what each message carries, what the buttons do, what a phone without RCS receives instead, and who deals with the reply. The general reminder workflow, for any industry, is on appointment reminders.

Two design choices keep this sequence cheap and clear. The confirmation, reminder and late notice are text with reply buttons, which US carriers bill as Rich text per 160-byte segment, while only the technician card and the quote carry a picture and are billed as Rich Media. And every fallback line starts with the company name, because the SMS version carries no verified badge.

Who owns the reply

Arrival messages invite replies ("can he use the side gate?", "I'll be ten minutes late home"), and the answer depends on who receives them.

• Buttons are structured replies. Each tap maps to an action: confirm the booking, open the reschedule page, record the approval. They can be handled by your booking or field-service system through the API, or by a bot, without anyone reading them.
• Typed replies go to one queue. On SimplyRCS, replies land in the shared Inbox, routed to a dispatch queue where one person takes ownership of the thread, so two people never answer the same customer. The dispatcher relays what the technician needs to know.
• Technicians do not text from their own phones. A personal number carries no verified identity, leaves no record in the job, and hands the customer a number the company does not control. The technician's name and photo travel in the company's thread instead.
• Opt-outs come first. STOP and HELP are handled before any automation or bot sees the reply, and a customer who opts out of marketing should still receive the arrival messages for a job they booked, which works cleanly when transactional and marketing traffic were registered separately.

What a phone without RCS receives

Every message in the sequence has a plain-text version, and it should make sense on its own: the company name first, the technician's first name, the time, and a link or a reply keyword where the RCS version has a button. The photo does not travel by SMS. If the technician's face matters for that customer, the fallback can be sent as MMS instead, at the MMS rate. RCS fallback to SMS explains how fallback should be driven by delivery status, so nobody gets the same notice twice.

The technician photo

• Ask first. Get each technician's agreement before their photo goes to customers, and let them choose the picture.
• First name only. A first name and a current photo answer "who is at my door" without publishing a surname or a personal number.
• Keep it current. A photo from five years ago defeats the purpose.

What to measure

The useful numbers are operational: the share of visits where nobody was home, how many customers rescheduled with a tap instead of calling, confirmation rate the day before, and the time from quote sent to approval. Because the sequence falls back to SMS for phones without RCS, the same report compares the two formats on your own customers.

What the sequence costs

At SimplyRCS's published rates, the seven messages above cost about five cents per job before carrier fees, assuming each text fits in one 160-byte segment: five text messages with buttons at $0.0039 a segment and two picture cards at $0.0150 each. Carrier surcharges are passed through at cost and listed per carrier on the pricing page. A two-person team running 300 jobs a month would spend roughly $15 on these messages before carrier fees.

Why the doorstep changes the trust calculation

Most industries want a customer to read a message. Home services needs a customer to open a door. An unbranded text from an unknown number asking someone to expect a stranger at their home is asking a lot, and it is exactly the pattern scam callers imitate. A message carrying the company name, logo and verification checkmark, with the technician's photo attached, answers the question the customer is actually asking.

Where SimplyRCS sits

Flat, published pricing suits a category with sharp seasonal peaks, because a heating business sending heavily in January is not negotiating a new contract to do it. Every message falls back to SMS or MMS automatically, so a customer on an older handset still gets the arrival notice.