Yotpo SMS is an ecommerce-focused texting product, and people search for it when they want retention texts for an online store: abandoned basket nudges, post-purchase messages, review requests and offers. If you run a service business rather than a shop, the jobs look similar but the triggers are different, because your sales happen in meetings and proposals rather than at a checkout. This article does not review that product. It sets out what to check when choosing retention texting, and how service companies of 10 to 250 people run the equivalent jobs on the levelpartner.ai platform.
Ecommerce retention versus service retention
Online retail retention runs on store events: a basket left, an order placed, a product shipped, a repeat purchase window approaching. The texting tool listens to the store and fires messages.
Service retention runs on relationship events: a proposal sent, a meeting held, a project finished, a contract approaching renewal, a review due. Those events live in your CRM, calendars and invoices, not in a shop. A texting tool designed around store events has nothing to listen to.
That is the core question when choosing. Where do the events that should trigger your texts actually happen?
What to check when choosing retention texting
- Which system holds the trigger events, and whether the texting tool can see them without an export.
- Whether consent and opt-outs are shared with every other tool that messages your customers.
- Where replies go, and whether the person who owns the relationship sees them.
- Whether review requests can be sent only to customers who had a good outcome.
- Whether you can combine text, email and tasks in one sequence.
The service equivalents of retail retention texts
The abandoned basket becomes the stalled proposal: a short check-in a few days after a proposal goes unanswered. The post-purchase message becomes the onboarding welcome: a text on day one with the name of the person looking after them. The repeat purchase window becomes the renewal or review: a prompt before the anniversary of the engagement. And the review request stays the same, sent after a completed project or a closed transaction.
Before you start
- Pipelines in Opportunities that reflect your sales and delivery stages.
- SMS consent recorded on your contacts.
- Your reputation and review settings configured, if you plan to request reviews.
- Templates for each retention message, reviewed by the account lead.
How to build service retention texts
A service firm needs four retention workflows rather than a checkout flow: a check-in when a proposal has sat unanswered for a few working days, a welcome text when an opportunity is won, a review booking link a few weeks before a renewal date, and a review request when a project is complete. Each starts with a consent check and ends when the contact replies, so a person can take over. Build each one with the same platform steps.
- Go to Automation > Workflows.
- Create a new workflow or open an existing one.
- Choose the trigger that should start the automation.
- Add the Send SMS action.
- Enter the message you want to send.
- Add personalisation or a template where appropriate.
- Add Wait steps, conditions or other actions when needed.
- Test the workflow and SMS content.
- Publish the workflow when it is ready to run.
Imagine an agency that tries an ecommerce texting tool for its small online training shop and finds it cannot see agency client events. On the platform, suppose 25 proposals go quiet each month and a proposal check-in reopens 6 of them. Add a renewal prompt ahead of each client's renewal date, and if it booked planning calls with 70 clients a quarter, those are conversations a retail tool would never have triggered. The figures are hypothetical.
What it replaces
For service firms, this replaces manual chasing: account managers keeping their own lists of proposals to follow up and renewals to remember. Those lists are rarely complete and disappear when someone leaves. For review requests specifically, see sending review requests by text.
Time it takes
Building four retention workflows takes a day. Running them takes the time needed to answer replies and complete the follow up tasks they create, which replaces time already spent chasing.
The mistake most people make
Copying retail cadence. Ecommerce tools often send several messages a week around offers. A client paying a monthly retainer will not tolerate that. Service retention texts should be few, specific and tied to the relationship. For the rules that keep a list healthy, read best practice for business texting.
Sending a review request to every completed client automatically. Check the outcome first, or route unhappy clients to a person instead of a review site.
When an ecommerce texting tool is right
If your main revenue is an online store with frequent repeat purchases, a texting tool built around store events may be the better fit for that store. You can still run client relationships from the platform. For broader campaign planning, see planning a text campaign end to end, and for automated messages around bookings, read automated text messages for business.
Troubleshooting
The proposal check-in sends after the deal was won. The stage changed after the wait began. Add a stage check immediately before the send step.
Renewal prompts go out for clients who already left. The renewal date field was not cleared. Add a condition on active client status.
Review requests go to unhappy clients. Add a satisfaction check or an internal approval step before the request.
Frequently asked questions
Can a service business use an ecommerce texting tool?
It can for broadcasts, but it will not see proposals, meetings or renewals. Retention texts for services need CRM events.
What is the service version of an abandoned basket text?
A short check-in on a proposal that has gone quiet, sent by the person who wrote it.
Should retention texts come from a person or the business?
From a named person where there is a relationship, with the business name included for recognition.
Can I import my old texting history?
Contact and consent data can be imported. Message history usually stays in the old tool, so export it for your records.