Templates · Newsletters
Customer product newsletter template
Release highlights, a how-to and one call to action for your customers
Start with this template →Sign in
Opens on reph with the template ready to start. No account needed; sign in to keep your document.
Filled example
The template filled in for a made-up company, so you can see what good looks like.
What's new in Fernhill, October
From the Fernhill team · October 9, 2026
This month you can plan delivery routes around how long chilled goods can stay out of the fridge. We also made reordering faster on phones, and fixed the bug that doubled some invoice lines.
Highlight: Cold-chain routing
Until now, Fernhill planned delivery routes by distance. Cold-chain routing plans each van's day around the cargo instead: frozen orders go out last and arrive first, and no stop puts chilled goods outside their safe window. In the pilot, nine grocers cut spoiled or late orders from 4.1% to 1.3%.
It is on for every Routes customer today. Open Routes > Settings > Cold chain and set the maximum minutes for chilled and frozen goods. Turn on cold-chain routing
Also new
- Faster mobile reordering: reorder last week's order in one tap from the home screen.
- Supplier price alerts: get an email when a supplier raises a price by more than 5%.
- Fix: invoices with split deliveries no longer show duplicate lines.
- Fix: the driver app now syncs routes changed while a phone was offline.
How to: set up a weekly standing order
- Open Orders and pick the order you place every week.
- Choose Repeat and set the day and cutoff time.
- Add a quantity rule if you want it to adjust, for example "match last week's sales plus 10%".
- Review the first three generated orders under Upcoming and confirm.
Standing orders save the average store about 40 minutes a week.
From the community
Mendez Family Markets runs eleven stores across southern Colorado. Carla Mendez, their operations director, told us that since switching to cold-chain routing they have not thrown away a single delivery of ice cream, even through a July heat wave. Her team now uses the saved van hours for a second afternoon delivery slot on weekends.
Try it
Set your cold-chain limits →
The template
Show the blank template
Customer product newsletter
From the [workspace] team · [date]
A two-sentence hello: what's new and why it matters to the reader.
Highlight: [feature name]
What it does, who it's for, and a screenshot. One link to try it.
Also new
- [Improvement]: one line.
- [Fix]: one line.
How to: [task]
A real workflow a customer can finish in five minutes.
- Step one
- Step two
- Step three
From the community
A customer story or a great use of the product.
Try it
Call to action →
Questions
- How often should it go out?
- Monthly, or right after a release big enough to change how customers work
- What if nothing big shipped?
- Lead with the how-to or a customer story; a useful issue beats a skipped one
- Who should it come from?
- A named person, usually the PM or founder, not a no-reply address
- How do customers subscribe?
- Share the list's signup link from the workspace's Audiences panel on your site or in the product; each one confirms by email
- What goes in the preview text?
- One line that finishes the subject's thought; most inboxes show it next to the subject, and you set it in the send dialog
- Can I check it first?
- Send me a test in the send dialog emails only you, so you can click every link before customers do
Fill it with your agent
Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.
Find my reph doc "Customer product newsletter" with search_docs, then read it with read_doc. Draft the highlight and Also new from this cycle's release notes and the headline feature's PRD, and the how-to from its help article. Find the last issue with search_docs and use get_reader_signals to keep what was read and clicked. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (screenshots needed, flagged features) with add_comment quoting that section's heading line, then call request_review with a one-line summary.
Related templates
Feature brief
Short brief aligning team on a feature before design
Product managerDesignerEngineerPRD / requirements doc
Problem, users, requirements, success metrics and scope for a feature
Product managerEngineerDesignerExperiment (A/B) plan
Hypothesis, variants, metrics, sample size and decision rule
Product managerResearcherEngineerLaunch checklist
Everything to ship a feature: eng, docs, support, marketing
Product managerManagerRelease notes
What shipped, what changed, and how to upgrade
EngineerTech leadProduct managerAgency client newsletter
A branded newsletter an agency writes for a client, with a clear call to action
MarketerSalesFounderStart with this template →Sign in