Crafting a library testimonial request email
A library testimonial request email can turn a satisfied moment into useful library marketing. The strongest messages are brief, specific and grounded in a real outcome, such as a patron finding a novel, a student completing research, or a community group gaining visibility.
Requests work best when the sender understands the local relationship. In Australia, the request may come from a metropolitan council in Melbourne or Sydney, a regional library network, or a statewide service. Digital, suburban and regional outreach programs each need a different example to feel credible.
Treat the task as a small publishing conversation rather than a form-filling exercise. Explain what the quotation will support, offer an easy approval step and retain the recipient’s preferred attribution. The result is a clear path from agreement to a polished customer story.
Match the request to a useful story
Start with the campaign goal, not the request. Decide whether you need a short endorsement for a website, a detailed success story for a report, or a quotation explaining the human impact of a service. One request should produce one clearly defined asset.
| Request method | Best suited to | Main advantage | Common risk |
|---|---|---|---|
| Personal email | A known success | Specific and warm | Takes more staff time |
| Short survey | Many recent users | Quick to complete | Answers may sound generic |
| Draft for approval | A sensitive or complex story | Recipient retains control | Can feel scripted unless edited |
Recent stories usually sound more natural than memories from years ago. Anchor the request to a recent program, discovery visit or community partnership, and mention what changed for the participant. A precise observation is usually more persuasive than a grand statement about the whole library.
Invite the recipient to write in their own words, but make the prompt manageable. “Two or three sentences about what you used and what benefit you noticed” is more usable than “Please tell us about your experience.” If preferred, staff can interview them and send a transcript for approval.
Earn trust before you ask
A credible sender is part of the message. Use the library’s normal email address, a named staff contact and a familiar local identity. A reply from team@yourlibrary.au may appear less personal than a message from a librarian whose name and branch the recipient recognises. Explain who will see the quotation and where it will appear.
Privacy is equally important. If the library is covered by the Australian Privacy Principles under the Privacy Act 1988, collect only what is needed to contact the person and confirm permission. State or territory privacy rules may also apply to public-sector organisations. Keep the story, consent record and approved wording in a restricted file rather than an open staff document.
If the email promotes goods or services or forms part of a commercial electronic message, consider the Spam Act 2003, including its rules on consent and stopping messages. Even where that legislation does not directly apply, a clear opt-out and respectful frequency reduce unwanted contact.
Write a concise, personal request
Use a subject line that signals the topic, the small effort involved and the value of the response. “A quick quote about your library reading program” is clearer than “Testimonial request” because it gives immediate context. Keep the body focused on one request, avoid jargon and put the deadline near the end.
Subject: A quick quote about your library program
Hi Jordan, Your recent reading session helped you find a new author. Would you be comfortable sharing two or three sentences about the experience and the benefit you noticed? I can send a short draft for you to edit and approve, and your name does not have to appear if you prefer privacy.
A good body names the specific experience, explains the intended use, states the effort required and offers a clear next step. “Could you write a testimonial for our website?” asks too much and reveals little. Replacing it with “Your comments could help another reader discover the Thursday evening program” connects the request to a shared benefit.
Keep the tone warm but not ceremonial. Thank the recipient, avoid inflated praise before they agree, and give a realistic response date. If a public holiday or staff absence affects the schedule, allow extra time rather than sending repeated reminders.
Make approval simple and safe
Let the recipient see the proposed wording. A small feedback route, such as replying with “approved” or marking two changes, is easier than completing another form. Offer clear choices for attribution: full name and branch, first name and service, job title, or an anonymous quotation when a personal detail is unnecessary.
Keep the scope of consent visible. Permission to quote someone on a website does not automatically cover a newsletter, social post, presentation slide or media release. Record the approved wording and the channels or time period authorised. If the use will be broad, say so before the response arrives, not after a polished asset is ready.
Do not treat silence as consent or pressure a hesitant participant. If a story involves another person, a minor, an employer or sensitive information, check that sharing it is appropriate. A respectful request can be declined without harming the relationship, protecting both the participant and the library’s reputation.
Fit the request to Australian library routines
Australian library teams often work across busy shared inboxes, metropolitan branches and regional networks. Melbourne and Sydney councils may promote the same campaign through separate newsletters, while a statewide service may need approval across several departments. Campaigns often connect the library with local authors, community groups, book clubs or independent booksellers, allowing a quote to reflect the library’s role in the wider reading market. Address the responsible branch or campaign owner rather than sending duplicate requests from every team.
Timing matters because Australian public library calendars cluster around events such as Australia Day, Harmony Week, National Sorry Day and NAIDOC Week, as well as school holidays. Send requests early enough for approval and editing, but not so early that the program details may change. A quick follow-up after five business days is usually enough; frequent chasing can make a valuable relationship feel administrative.
Many patrons discover programs through council newsletters, Facebook and Instagram, then respond by email, although some branches still use printed feedback cards. Support both habits where a response channel is mixed. Include email in the main message, and offer a reply card or phone interview for older patrons, people with limited data or community groups without easy email access.
Turn one response into several assets
A strong quotation has more value once the permission covers its intended uses. With agreement, adapt it for a service page, annual report, staff presentation, campaign newsletter or social post. Keep the core words recognisable so the person still recognises their contribution; tailor only the length, format and supporting context. The Library Marketing Toolkit’s campaign microsite example shows how a focused special-library campaign can give approved stories a clear home.
Build a simple content record containing the approved quote, attribution, consent details, channels, date and any restrictions. This prevents an old testimonial from being reused after a program ends or a staff member leaves. If a quotation needs updating because circumstances have changed, seek fresh approval instead of silently rewriting it.
Measure what the story achieves. Track visits to the page carrying it, newsletter clicks, program enquiries, registrations and direct references to the testimonial. A modest customer story may support awareness, while a specific quote beside a program listing can influence action. Compare those signals with the effort spent collecting and editing the response.
Send a request people can answer
Before sending, confirm that the email names one person, one experience, one proposed use and one easy action. Check the sender, reply route, deadline, attribution choice and approval method. If no response arrives, send one courteous reminder, then close the request respectfully. A well-timed note is more productive than repeated chasing.
Save the final wording so other teams can learn from it. Keep records that show permission and approved edits, and mark the testimonial as ready only after the recipient has confirmed. This habit makes future requests faster while preserving the standards that earned the first contributor’s trust.
Choose one recent library success, send the personalised request this week, and give its recipient a clear, low-friction way to say yes.