Write the wording once with AI and keep the client details out of it. Ask for twelve templates with merge fields such as [first name], [item] and [ticket number], store consent and dates in your own sheet, and send repair-ready texts as service messages. Send anniversary notes only to clients who agreed to hear from you.
The wording is the easy part. The damage comes from sending a fine sentence to the wrong person: a purchase anniversary to a client who has since lost their partner, an offer to someone who never agreed to marketing, a collection reminder for a piece that was collected on Tuesday. So the list, the dates and the consent record come first, and the AI comes second.
Service messages and anniversary notes follow different rules
Sort every message into one of two buckets before drafting anything. A service message is about something the client has left with you or bought: the ring is in the workshop, the estimate is ready, it can be collected. Those go to the contact details the client gave you for that job. A marketing message tries to bring someone back or sell something: an anniversary offer, a free check and clean, a new collection. In most places that needs the client's agreement first, and some channels expect a specific kind of agreement. I'm not a lawyer, so confirm the rules for your customers with a data-protection adviser. What follows is a way of working that is easy to defend.
The boundary is narrower than most shops assume. A repair-ready text that also mentions a sale is marketing. A message that asks for a review can count as marketing too. Keep service messages dull and complete, and let anniversary notes live on their own consented list.
This is also why the AI never needs your client list. It writes templates with merge fields, and your email tool, texting service or a basic mail merge fills in names and dates. Paste a client spreadsheet into a consumer chat and you have sent names, phone numbers and the dates people bought engagement rings to a third party for no benefit. A business plan whose terms say your content isn't used for training is safer, but there is no reason to take the risk at all. If you are still choosing tools, AI tools for a jewellery business, compared by the job they do sorts them by task.
Seven list segments, each with one trigger date
Most jewellers keep one long client list. Split it into segments and give each segment one trigger, a date or a status change, that decides when a message becomes due. The table shows the seven I would start with, the template numbers each one uses (the templates follow further down) and what the record has to show.
| Segment | Who is in it | What makes a message due | What the record must show | Templates |
|---|---|---|---|---|
| 1. In the workshop | Pieces you are holding for repair | A status change in the repair log | The contact details given for that job | 1, 2, 3 |
| 2. Ready, waiting | Finished repairs not yet collected | 7 and 28 days after "ready" | As above | 4, 5 |
| 3. Just collected | Repairs collected in the last week | Collection date plus 7 days | As above; no offers in the message | 6 |
| 4. Care check due | Owners of pieces with stones, prongs or clasps and no workshop visit for 12 months | Last visit plus 12 months | Marketing consent, by channel | 7 |
| 5. Anniversaries | Clients with a purchase date on file | Purchase date plus 1, 5, 10 or 25 years | Marketing consent, by channel | 8, 9 |
| 6. Remembered dates | Clients who asked you to remember a date | The date minus 21 days | A separate yes, recorded with the date and its label | 10 |
| 7. Paused | Opted out, bereavement or dispute note, refund in the last 90 days | Nothing sends | A reason; this segment overrides all the others | None |
Segment 7 does the most work. Every weekly run starts by excluding it. A bereavement note is the one most shops don't have, so add a free-text notes column and a pause column, and make it normal for anyone at the counter to type "pause" and a reason the moment they learn something that changes how a client should be contacted. The 90-day refund window is my suggestion; use whatever suits your returns policy.
A client can sit in several segments at once. Someone whose first-year anniversary and annual care check fall in the same fortnight should get one message, not two. Give the marketing messages a priority order: remembered dates first, then milestone anniversaries, then first-year notes, then care checks. Allow one marketing message per client in any 30 days, and let the first one that qualifies win.
The sheet: columns, and formulas that surface this week's messages
You can run all of this from one spreadsheet before buying any software. The columns that matter are a client ID (a short code such as C-0412, used instead of a name wherever you can), first name, purchase date, item type, last workshop visit, preferred channel, marketing consent (Y or blank), consent date, consent wording version, remembered date and its label, pause flag and pause reason. Contact details can stay in your till or repair-tracking system. The sheet only needs enough to tell you who is due.
Four formulas do the date work. The first finds the next occurrence of a purchase date, the second turns it into a number of years, the third flags the years you write for, and the fourth marks the row due when the date is within seven days and nothing blocks it. They work in Excel and in Google Sheets.
J2 Next anniversary (purchase date in C2):
=IF(DATE(YEAR(TODAY()),MONTH(C2),DAY(C2))<TODAY(),DATE(YEAR(TODAY())+1,MONTH(C2),DAY(C2)),DATE(YEAR(TODAY()),MONTH(C2),DAY(C2)))
K2 Years it will be:
=YEAR(J2)-YEAR(C2)
L2 Is it a year you write for?
=OR(K2=1,K2=5,K2=10,K2=15,K2=20,K2=25)
M2 Due in the next 7 days (F2 = marketing consent, I2 = pause flag):
=IF(AND(F2="Y",I2="",L2,J2-TODAY()<=7),"DUE","")For remembered dates, copy the first formula onto the remembered-date column and use a window of 14 to 21 days ahead instead of 0 to 7, because a gift needs lead time. If you would rather not write formulas yourself, ask an AI to write them, but give it only the column headers and two invented rows. Something like: "Here are my column headers. Write a formula that returns DUE when a purchase anniversary falls in the next 7 days, the client has marketing consent and the pause column is empty. Test it on these two made-up rows." Then check the result against dates you can verify by hand, including a purchase made on 29 February. Google Sheets AI prompts covers more of this, and cleaning messy data helps if the list you start from has duplicate clients or phone numbers in six formats.
Consent you can prove, and an opt-out that works
Consent that can't be shown later is consent you don't have. For each client who agrees to anything beyond repair updates, record four things: what they agreed to, which channels, the date, and how you asked (a till form, the website, or a member of staff at the counter). Keep the wording version too. When you change the wording next spring, you will know which clients saw which sentence.
Ask separately for separate things. Repair updates need no tick box because they travel with the job. Occasion reminders and care notes get their own tick box, and so does each channel. That matches what WhatsApp's own Business Messaging Policy recommends, which is to obtain a separate opt-in by message category, and it makes an opt-out easy to apply: taking someone off WhatsApp reminders doesn't also take them off email.
In places covered by data-protection law such as the GDPR, consent has to be an active choice. The regulation's own recital says silence, pre-ticked boxes and inactivity don't count. So the box is blank, the client ticks it, and the wording says in plain language what they will get and how often.
Counter script (read aloud, then record the answer):
"Would you like us to remember dates that matter to you, like an anniversary
or a birthday, and send you one short note about three weeks before? We would
use only the channel you choose, we won't share your details, and every note
tells you how to stop. You can change your mind at any time by telling us or
replying STOP."
Form wording (every box left blank):
[ ] Remind me about dates I give you: Email [ ] Text [ ] WhatsApp [ ]
[ ] Send me occasional care notes and purchase anniversaries: Email [ ] Text [ ] WhatsApp [ ]
Date(s) to remember: ____________ What it is for: ____________
We keep your details to look after your jewellery and, if you tick a box, to
send the notes above. Ask us to stop at any time.The opt-out has three jobs. It appears on every marketing message in words nobody can miss: "Reply STOP to stop these notes" on a text, an unsubscribe link in the footer of an email. It is honoured at once, in practice the same day, because the next scheduled send is the one that earns a complaint. And it is recorded, with the date, the channel and the segment flags updated. WhatsApp's policy says you must respect requests to block, discontinue or opt out of communications, whether made on or off WhatsApp, so a client who tells you at the counter to stop the WhatsApp notes has opted out as surely as one who tapped block.
One category needs its own rule: dates people give you in passing. A client who mentions a wedding anniversary while choosing a gift hasn't asked you to remember it. Offering "would you like a reminder?" is kind; quietly adding the date to a send list is not. Every remembered-date message should also carry a line that lets the client say the date is no longer one they want to hear about, with no explanation needed.
A prompt that writes templates, not messages to people
Create a Project in ChatGPT or Claude for this work and keep the prompt, the shop's voice notes and the approved templates inside it, so every new template starts from the same tone. Don't build a custom GPT for it: OpenAI is retiring those, and they stop running on 11 December 2026. A Project gives you the same stored instructions without that problem.
The prompt below sets the rules once. It asks for templates only, forbids invented offers and policies, and puts every gap in square brackets so that a person has to fill it. Paste it in, then ask for one template at a time.
You are drafting message templates for an independent jewellery shop.
Warm and plain, in the spelling your clients are used to. No exclamation marks, no emoji.
Rules:
1. Write templates only. Use square-bracket merge fields: [first name], [item],
[ticket number], [ready date], [opening hours], [shop phone], [shop name].
2. Never include a real client's details.
3. Never invent offers, prices, guarantees, storage terms or policies. If a fact
is missing, leave a gap in brackets, for example [our collection policy].
4. Never assume the occasion, the relationship or who wears the piece. No claims
about value, investment or "forever".
5. For each template give a text-message version under 300 characters in plain
characters (no curly quotes) and an email version under 90 words with a subject.
6. Service templates carry no offer or promotion. Marketing templates end with a
line saying how to stop.
Write template 8: first-year purchase anniversary. The shop will confirm the
offer, which is a check and clean within 30 days of the anniversary.Rules 3, 4 and 6 exist because of drafts like the next one. If your first prompt asks only for "a warm first-year anniversary text", expect something along these lines (illustrative output, not a recommendation):
Text: Hi [first name]! A year ago you made your forever choice with us. Come in
this month for a free check and clean of your [item], on us. We'd love to see
it again! No appointment needed.Five problems in forty words. "Forever choice" assumes an engagement and a sentiment you can't know; the piece may have been a gift or a treat. "Free ... on us" is an offer nobody authorised. "No appointment needed" is a policy the shop may not have. Two exclamation marks sit in a message from a business the client may only have met once. And there's no shop name, no opening hours and no way to stop the messages. Each of those problems is now a line in the prompt, and the corrected version of this text is template 8 below.
Check the length as well as the sense. Twilio's glossary puts a plain text at 160 characters for one segment and 153 per segment once it is split, but one emoji or curly quote switches the whole message to an encoding that allows only 70 (67 per segment when split). That's why the prompt asks for plain characters. Merge fields change the length too, so test the longest first name and item you hold.
Twelve templates, from repair received to re-confirmation
These are the twelve I would set up, in three groups. Each is the text-message version, under 300 characters before the merge fields are filled in. Ask the AI for a longer email version of any you want to send by email, and keep the same facts in both. Square brackets are merge fields or decisions that belong to you. I have left out exclamation marks, and anything about value or investment, on purpose.
Repair updates, sent as service messages
1. Repair received, sent when the ticket is created:
Hi [first name], we've received your [item] for [repair]. Your ticket number is [ticket number]. We'll message you by [estimate date] with a price and timing. No work starts until you've agreed it. [shop name]
2. Estimate ready, sent when the estimate is entered:
Hi [first name], the estimate for your [item] (ticket [ticket number]) is [amount], ready in about [days]. Reply YES to go ahead, or call [shop phone] with any questions. [shop name]
3. Ready to collect, sent when the status changes to Ready:
Hi [first name], your [item] is ready to collect. Ticket [ticket number]. We're open [opening hours]. Please bring this message or your ticket. Balance due on collection: [balance]. [shop name]
4. Collection reminder, sent 7 days after Ready:
Hi [first name], a reminder that your [item] (ticket [ticket number]) has been ready since [ready date]. We're open [opening hours]. If another day suits you better, reply with it and we'll hold it for you. [shop name]
5. Last reminder, sent 28 days after Ready:
Hi [first name], your [item] (ticket [ticket number]) is still with us. Our repair terms, which you agreed at drop-off, say [unclaimed-item terms]. Please collect it or call [shop phone] by [date] so we can agree what happens next. [shop name]
6. After-repair check, sent 7 days after collection:
Hi [first name], we hope your [item] is sitting right since the repair. If anything feels off, bring it in or call [shop phone] and we'll look at it. [shop name]
Decide four things before these go live. Template 1 promises that no work starts before the client agrees; delete that sentence if you do small fixes on the spot. Template 3 needs an honest balance, so the repair log must hold the price. Template 5 refers to terms the client agreed at drop-off, so print them on the repair ticket. If your terms don't say what happens to unclaimed items, fix that first, because the rules on unclaimed goods differ from place to place and a solicitor should check yours before you sell or dispose of anything. Template 6 asks one question and nothing else, with no review request and no offer, which is what lets it stay a service message.
For a high-value piece I would phone instead of sending template 2. A call makes it easier to explain a four-figure estimate, and the client can ask what the stone setting involves. The routine for estimates that never get answered is in following up unapproved repair estimates with AI, and how garages use AI to send repair updates shows the same status-change idea in a busier trade.
Care notes and anniversaries, sent only with consent
7. Annual care check, sent 12 months after the last workshop visit:
Hi [first name], it's been a year since your [item] was last in. Prongs and clasps can loosen with wear, so we offer a quick check [price or no charge]. Book on [booking line]. Reply STOP to stop these notes. [shop name]
8. First-year purchase anniversary, sent in the week before the date:
Hi [first name], it's a year since you chose your [item] with us. If you'd like it checked and cleaned, come in before [date] and we'll do it [offer to be confirmed]. [booking line]. Reply STOP to stop these notes. [shop name]
9. Milestone anniversary, for 5, 10, 15, 20 and 25 years:
Hi [first name], [number] years ago you bought your [item] from us. We'd be glad to give it a full check and clean, and to see how it has worn. [booking line]. Reply STOP to stop these notes. [shop name]
10. Remembered date, sent 21 days before, only to clients who asked for it:
Hi [first name], you asked us to remind you about [label] on [date]. If a gift would help, call [shop phone] or reply and we'll have something ready to see. If you'd rather not be reminded again, reply STOP. [shop name]
These four share a design rule: one idea and one action per message. The care check offers a check; it doesn't also announce new stock. Template 9 should change by year, so give the AI a second version for 25 years that is plainer and less promotional, because a piece worn for that long is an occasion on its own. Template 10 needs the label the client gave ("our anniversary", "Mum's birthday") and nothing else about them. Never add a guess about who the date is for. And don't send template 8 when the purchase was recorded as a gift: the person who paid for a piece is not always the person who owns it.
Consent and list upkeep
11. Confirmation of a remembered date, sent straight after the client agrees at the counter:
Hi [first name], thanks for visiting [shop name]. As you asked, we've saved [date] for [label] and will message you by [channel] about three weeks before. Reply STOP at any time to cancel.
12. Re-confirmation, sent when consent is older than your chosen limit (subject line for email: "Still want to hear from us?"):
Hi [first name], you asked [shop name] to send occasional care notes and reminders. Reply YES to keep them coming. If we don't hear from you, we'll stop sending them.
Template 12 is for consent that has gone stale. Some advisers prefer to stop messaging clients whose consent is older than a limit you set, rather than ask them to confirm, because the confirmation request is itself a message. Ask yours which they would choose, then apply it the same way to every client. Either way, anyone who doesn't answer moves to service-only. For the formula, a consent date column and =IF(TODAY()-G2>730,"RECONFIRM","") flags anything older than two years; change 730 to your own limit.
One month in a two-bench shop, with the sums
Take an independent jeweller with two people at the bench, two at the counter and 1,150 client records. These figures are illustrative, to show the arithmetic rather than to promise a result. After a consent clean-up, 410 clients have agreed to at least one kind of marketing, 640 are service-only and 100 are paused. A typical month brings 45 repair jobs. Of those, 28 need an estimate, 15 get the day-7 reminder, 4 reach the last reminder and about 40 get the after-repair check. On the marketing side, the sheet surfaces 8 care checks, 9 first-year anniversaries, 3 milestones and 5 remembered dates.
| Job | Messages a month | Minutes each: by hand / with templates | Month total by hand | Month total with templates |
|---|---|---|---|---|
| Repair updates (templates 1 to 6) | 177 | 3 / 1 | 531 minutes | 177 minutes |
| Care notes, anniversaries, remembered dates (7 to 10) | 25 | 5 / 2 | 125 minutes | 50 minutes |
| Re-confirmations (12), work nobody was doing before | 22 | none / 1.5 | 0 | 33 minutes |
| Friday review of the due list, 4 weeks of 15 minutes | n/a | n/a | 0 | 60 minutes |
| Total | 224 | 656 minutes (about 10.9 hours) | 320 minutes (about 5.3 hours) |
The shop gets back about 5.6 hours a month while also sending 22 re-confirmations and doing a weekly review it didn't do before. Setting up takes roughly six hours once, most of it spent on the consent clean-up and getting the twelve templates approved by whoever owns the shop's voice. The first line of the table is the real lesson: 177 of the 224 messages are repair updates that raise no consent question. If you are short of time, do templates 1 to 6 first. They carry the highest volume and the lowest risk, and a client who is told the piece is ready has no reason to ring and ask.
Running costs are small. Drafting a dozen templates is a one-off job, so a free chat plan may be enough; a paid plan is about $20 a month (Claude's pricing page lists Pro at $20 billed monthly or $17 billed annually, and ChatGPT Plus is also about $20). For email, the 410 consenting clients are too many for Mailchimp's free plan, which its pricing page limits to 250 contacts and 500 sends a month. Its Essentials plan starts at $13 a month, and the 500-contact tier would cover this list. Text messages are billed per message by your provider, so check the rate and how it handles a STOP reply before you commit.
Four drafts that needed editing, and what changed
These four illustrative drafts show the problems I would expect to meet in the first month. None needs a clever fix. Each needs one rule added to the prompt or one column added to the sheet.
- The sentimental overreach. Ask for template 9 on a tenth anniversary and a draft can come back as: "Ten years of love, and your ring still shines. Come and celebrate with us." It assumes a romance and a celebration when the record says only "item: ring, bought by client". The corrected text says "Ten years ago you bought your [item] from us" and stops there. The fix is rule 4 in the prompt, which forbids assuming the occasion, the relationship or the wearer.
- The invented policy. A draft of template 3 can end: "We'll keep it safe in our vault for up to six months." If the shop has no vault and no six-month promise, the model has filled a gap with something that sounds like a jeweller's policy. Rule 3 says to leave unknown facts as bracketed gaps, and the approved version names only the opening hours.
- The date that arrived at the wrong time. Suppose a remembered-date note for a wedding anniversary goes out to a client who was widowed since they gave you the date, and the colleague who heard the news never typed "pause". Nothing in the AI caused this; the process did. The fix is human: the Friday review includes reading the due list as a person and asking whether any name worries you, and once a year every remembered date is re-confirmed with the client.
- Two notes in one week. A client's first-year anniversary and annual care check both fell due, the sheet flagged both, and they received two messages five days apart. The fix is a "last marketing message sent" column and one more test in the due formula: add
OR(P2="",TODAY()-P2>30)inside the AND, so nobody gets a second marketing message within 30 days.
Where the messages go: email, WhatsApp or plain text
Anniversary and care notes suit email. The unsubscribe link is built into the tool, the cost per message is small, and there is room for a line about what a check involves. Check that your email tool can send on a date held in a contact field. If it can't, run the weekly due list as a manual send; at 25 messages a month that is a few minutes.
WhatsApp suits repair updates because clients actually read it. The WhatsApp Business app has Quick Replies for saved messages, Labels for tagging chats (a "Ready" label is handy) and a Greeting and Away Messages, which is enough for a small shop sending a handful of updates by hand each day. If you move to the WhatsApp Business Platform to automate sending, Meta's pricing page says each business number gets 1,000 free service messages a month, and from 1 October 2026 messages beyond that, plus utility templates sent inside the 24-hour window, are charged. It also says rates vary by message category and by recipient, so read the page before you automate. Messages you start outside that window need an approved template, and the policy requires opt-in either way. WhatsApp for small hotels goes through templates and handover in more detail.
Plain text messages reach everyone, but ask your provider two questions: what happens when someone replies STOP, and what each message costs. Keep to plain characters. A message over 160 characters is split into parts of 153, and one emoji or curly quote switches the encoding to 70 characters (67 per part when split), so a text that looked like one message can bill as three.
My default is simple. Repair updates go by whichever channel the client used to contact you. Anniversary and care notes go by email. Remembered dates go by the channel the client ticked. Anything about a high-value piece goes by phone.
A Friday check that keeps the system honest
Once the sheet is running, the risk moves from writing to sending. A short weekly routine catches most problems before a client does.
- Open the due list and read it as a person. Remove anyone whose record makes you hesitate, and add a pause reason so the next person knows why.
- Check the pause column against the week's refunds, complaints and opt-outs.
- Send, then enter today's date in "last marketing message sent".
- Apply every STOP, unsubscribe and "please don't" from the week the same day, across all channels.
- Scan the repair log for anything marked Ready for more than seven days and check that template 4 went.
Fifteen minutes is the target. If it takes longer, the sheet is asking you to do something a formula should do. Once a month, count opt-outs per 100 marketing messages sent. The absolute number matters less than a jump from the month before: if one appears, reduce the frequency before you touch the wording, and look at whether the messages that preceded it went out close together.
Questions jewellers ask before the first send
Does a repair-ready text need marketing consent?
A message about an item the client left with you is normally a service message, sent to the contact details they gave for that job. Keep it free of offers and review requests, because adding either can turn it into marketing. Rules differ by place and by channel, so ask a data-protection adviser to confirm before you rely on this.
Can I use a date a client mentioned at the counter?
Only if they asked you to remember it. Record the date, what it is for, the channel they chose and when they agreed. A date you overheard, or worked out from a purchase, is a prompt to offer a reminder, not permission to send one. Ask at the till, on its own tick box, away from the receipt.
Is it safe to paste my client list into ChatGPT?
It isn't necessary, so I wouldn't. The wording needs no real names: write templates with merge fields and let your email or text tool fill them in. If you want help with the list itself, give the AI column headers and a few invented rows, or use a business plan whose terms say your content isn't used for training, after reading those terms.
How often should I send anniversary messages?
Once per occasion is plenty: a first-year note, milestone years such as 5, 10 and 25, and any date the client asked you to remember. Cap marketing at one message per client in any 30 days and watch opt-outs after each send. If they rise, cut the frequency before you rewrite the words.
A client replied STOP on WhatsApp but has a repair with us. What now?
Stop all marketing straight away and record it. Move that job's updates to the phone or email, because WhatsApp's policy says you must respect requests to opt out or block, including requests made off WhatsApp. Once the repair is collected, leave the record on service-only.
Further reads
- ChatGPT Prompts for Jewellery Shops: 8 for Listings and Clients — Eight more prompts for listings and client emails.
- AI Service Reminders That Bring Garage Customers Back — Another repair-led trade turning service dates into return visits.
- Hotel Email Marketing With AI: Past-Guest Segments and Subject Lines — Segmenting past customers for email, shown in a hotel.
- AI for Jewellery Design: Concept Sketches to Client-Approved Renders — Keep client sign-off clear on made-to-order pieces.
- Customer Support AI Tools for Phone Repair Shops: Repair Status Updates — Repair status updates handled by tools, compared.
- AI Marketing Best Practices for a Local Business: A Pre-Post Checklist — A pre-send checklist for any local business message.
- AI Jewellery Model Generator: Keep Rings and Chains True to Scale — A step-by-step scale test for AI jewellery models, using a known ring size and chain length so you catch oversized rings and floating chains.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Meta's WhatsApp Business Messaging Policy, WhatsApp Business Platform pricing page and Business app features page; Mailchimp pricing page; Twilio's SMS character-limit glossary; the text of GDPR Recital 32 (all checked October 2026).