25 text expansion examples that save time every day
Practical shortcuts for customer support, developers, sales, HR, and everyday work.
Steal these
The hardest part of text expansion isn’t setting it up. It’s figuring out what to save. So here are 25 snippets people actually use, grouped by the kind of work they’re for. Copy the ones that fit, tweak the wording so it sounds like you, and pick triggers you’ll remember.
Every trigger here starts with two dots, like ..sig. That way a snippet only fires when you mean it to, and never halfway through a normal word. Anything in curly braces, like {name}, gets filled in when the snippet expands. More on that at the end.
Customer support
Support is where snippets pay off fastest. The same handful of questions come in all day, so the same handful of answers should be one trigger away.
1. Refund confirmation ..refund
Hi {name}, no problem at all. I've started your refund now. It'll land back on your original payment method within 5 to 7 business days, and you'll get an email as soon as it goes through.
The {name} field pops up when you type the trigger, so it still reads like you wrote it just for them.
2. Shipping times ..shipping
Orders ship within 1 to 2 business days. Once yours is on the way, you'll get a tracking link by email. Most orders arrive 3 to 5 days after that.
When the policy changes, update it once and every reply after that is right.
3. Follow-up ..followup
Hi {name}, just checking in on this one. Did the steps above sort things out? If not, reply here and I'll pick it straight back up.
The message everyone means to send and half of us forget.
4. Checking with the team ..hold
Thanks for your patience! I'm checking this with the team now and will get back to you within the hour.
Probably the most-typed sentence in support. Might as well be one trigger.
5. Friendly sign-off ..close
Glad we got that sorted! If anything else comes up, just reply to this email and it'll come straight back to us. Have a great {day}!
{day} fills in the day of the week, so Friday's customers get wished a great Friday.
Developers
Most of what developers type outside the editor is the same few templates and replies. Your IDE snippets can't follow you into GitHub, Slack or Jira. These can.
6. Pull request template ..pr
## What ## Why ## How to test ## Screenshots
Same headings on every PR, so reviewers always know where to look.
7. Bug report ..bug
Steps to reproduce: 1. Expected: Actual: Browser / OS:
Better bug reports, because the questions are already there.
8. Deploy notice ..deploy
Deploying {service} to production now. I'll post here once it's live. Shout if you see anything odd.
Keeps the channel in the loop without you having to think about the wording.
9. Standup update ..standup
Standup, {today}
Yesterday: {cursor}
Today:
Blockers: none
The date fills itself in, and your cursor lands right where you start typing.
10. Ask for a repro ..repro
Thanks for the report! Could you add the steps to reproduce, what you expected to happen, and what happened instead? A screenshot helps a lot too.
Polite, complete, and never typed out by hand again.
Sales
A sales day is mostly the same few messages sent to different people. Placeholders keep them personal. The trigger keeps them quick.
11. First reach-out ..intro
Hi {name}, thanks for your interest in what we do! I'd love to hear a bit more about what {company} is working on and see if we can help. Do you have 20 minutes this week?
Two fields, and it still sounds like a person wrote it.
12. Book a demo ..demo
Here's a link to book a demo at whatever time suits you: https://cal.example.com/demo It takes about 30 minutes, and you'll see exactly how it'd work for your team.
Your booking link is never more than a trigger away.
13. Gentle follow-up ..checkin
Hi {name}, just bumping this back to the top of your inbox. Happy to answer any questions, or I'll leave you be if the timing isn't right.
Support already took ..followup, and every trigger has to be unique. Short and memorable beats clever.
14. Pricing summary ..plans
Plans start at $12 per user per month, billed yearly. The full breakdown is here: https://example.com/pricing
Quote the same numbers every time, not whatever you remember.
HR and recruiting
Recruiting runs on messages that have to be warm, clear and sent on time. Having them ready means they actually go out.
15. Interview invite ..interview
Hi {name}, thanks for applying for the {role} role! We'd love to set up a 30 minute call. Pick any time that works for you here: https://cal.example.com/interview
Name, role, link. Done in seconds.
16. Kind rejection ..reject
Hi {name}, thank you for taking the time to interview for the {role} role. We've decided to move forward with other candidates this time, but we really enjoyed meeting you and wish you the best with your search.
Nobody enjoys writing this one. Writing it well once means every candidate gets a proper reply.
17. Offer email ..offer
Hi {name}, great news! We'd love to offer you the {role} position. Your formal offer is attached. Take your time looking it over, and let me know if you have any questions.
The fun one. Still worth getting the wording right every time.
18. First-day welcome ..welcome
Welcome to the team, {name}! Your first day is {start}. You'll get your laptop and logins that morning, and lunch is on us.
Consistent onboarding, whoever's doing the hiring this month.
Everyday stuff
Whatever your job is, you type these a few times a day. They're the easiest place to start.
19. Email address ..em
jamie.rivera@example.com
Signup forms, invites, logins. You'll use this one more than you think.
20. Meeting link ..meet
https://meet.example.com/jamie-rivera
No more digging through your calendar to find it.
21. Address ..addr
221 Example Street Springfield, 12345
For every checkout page and delivery form.
22. Signature ..sig
Cheers, Jamie Rivera Operations Lead, Example Co. +1 555 0100
Works in any app, not just the email client you set it up in.
Dynamic snippets
Snippets don't have to be fixed text. Variables like {today} fill themselves in, and placeholders like {name} ask you for a value before anything gets typed.
23. Tomorrow's date ..eta
I'll get this over to you by end of day {tomorrow}.
No checking the calendar to work out what tomorrow's date is.
24. Dated note ..note
Note, {today}:
Handy for call notes, logs and anything you'll want to search by date later.
25. Email skeleton ..hey
Hi {name},
{cursor}
Thanks,
Jamie
Greeting and sign-off in one go, with your cursor waiting in the middle for the actual message.
Where to go from here
Don’t set up all 25 at once. Pick the five you’d use today, live with them for a week, and add more as you catch yourself retyping something. Wondering whether it’s worth it for your job? Read who text expansion is for. Still choosing a tool? We compared ten in the best text expanders in 2026.
Common questions
- What makes a good snippet trigger?
- Short, easy to remember, and not a word you would ever type for real. Starting every trigger with the same prefix, like two dots, takes care of the last part, so ..sig expands but the word sig on its own never does.
- Can a snippet include details that change each time?
- Yes. Placeholders like {name} ask you for a value when the snippet fires, and variables like {today} or {tomorrow} fill in on their own. A {cursor} variable puts your cursor back in the right spot once the text is in.
- Will snippets make my messages sound robotic?
- Not if you write them the way you normally talk. Add a placeholder for the person's name and anything else that changes, and nobody on the other end will know it took you a few keystrokes.
- Can my whole team use the same snippets?
- Yes. With JAST's Team feature, a group of snippets is shared with everyone on the team, so support replies, sales emails and recruiting messages stay the same no matter who sends them.
Try JAST
Windows and macOS, one license for two devices, and nothing you type ever leaves the machine.