Back to blog
mac productivity text expansion snippets

10 Things You Should Never Have to Type Twice on Your Mac

Your email signature, your address, your standard follow-up message — here are the 10 things every Mac user should turn into text expansion shortcuts.

By Aaron Hampton 5 min read

Some things you type so often that your fingers could do it blindfolded. Your email signature. Your mailing address. That polite follow-up you send three times a week. You’ve typed each one hundreds of times, and you’ll type them hundreds more.

Unless you set up text expansion. Here are the ten things every Mac user should turn into a shortcut — type a trigger, get the full text. No more retyping what you already know by heart.

1. Your email signature

You sign every email. The name, the title, the phone number, the website. It’s always the same, and it’s always tedious to type out.

Suggested trigger: ;sig

Why it matters: Even if your email client has a built-in signature, it doesn’t help when you’re writing in Slack, Notion, or a web form. A text expansion trigger works everywhere. Five seconds saved per email, multiplied by every email you send, adds up fast.

2. Your full mailing address

Billing forms, shipping forms, account registrations, government paperwork. Your address shows up constantly, and auto-fill doesn’t always catch it.

Suggested trigger: ;addr

Why it matters: It’s not just the time. It’s the annoyance of typing your street, city, state, and zip code into yet another form field that couldn’t be bothered to auto-detect it. One trigger, done.

Whether it’s Zoom, Calendly, Google Meet, or Cal.com, you share this link constantly. In emails, in Slack, in DMs.

Suggested trigger: ;meet

Why it matters: Digging through your calendar app to find and copy the link takes longer than it should. A trigger puts it at your fingertips in any app, any time.

4. Your standard follow-up email

“Just checking in on this — wanted to make sure it didn’t fall through the cracks. Let me know if you need anything from my end.”

You’ve typed some version of this hundreds of times. It barely changes. It shouldn’t require rewriting.

Suggested trigger: ;fup

Why it matters: Follow-ups are one of the highest-frequency email types. A trigger with a fill-in field for the recipient’s name makes each one feel personal while taking two seconds to send.

5. Your phone number

Forms, contact pages, email signatures, business card exchanges. You type your phone number more often than you realize.

Suggested trigger: ;phone

Why it matters: It’s short, but you type it everywhere. And if you have a work number and a personal number, set up ;phonew and ;phonep to keep them separate.

6. Your standard introduction

The two-sentence version of who you are and what you do. You use it in emails, LinkedIn messages, conference bios, and introductions.

Suggested trigger: ;intro

Why it matters: Writing your intro from scratch every time means it comes out slightly different each time. A snippet keeps it consistent and polished. Update it once when your role changes, and every future introduction is already correct.

7. Your polite decline

“Thank you for reaching out — I appreciate you thinking of me. Unfortunately, I’m not in a position to take this on right now, but I wish you the best with it.”

You need this more than you want to admit. Meeting invites, collaboration requests, pitches, favors.

Suggested trigger: ;decline

Why it matters: Declining is emotionally expensive. When it takes effort to compose, you delay it. A snippet makes it painless to say no promptly and politely, which is more respectful to the person asking than leaving them waiting.

8. Your invoice payment reminder

“Friendly reminder that invoice #[X] for $[Y] was due on [date]. Please let me know if you have any questions or if payment has already been sent.”

If you freelance or run a business, you send this regularly. It’s awkward to write and easy to automate.

Suggested trigger: ;invoice

Why it matters: Use fill-in fields for the invoice number, amount, and due date. TypeSnap asks for those values when the trigger fires, so the message is specific without manual editing. One trigger covers every overdue invoice.

9. Your GitHub PR template

Description, test plan, related issues, screenshots section. If you write pull requests, you know the format. It’s the same skeleton every time.

Suggested trigger: ;pr

Why it matters: A PR template as a text expansion snippet means you get the structure instantly in any Git tool — GitHub, GitLab, Bitbucket, or a terminal-based workflow. No dependency on repository-level templates.

10. Your professional thank-you note

“Thank you for taking the time to [X] — I really appreciate it.”

Interviews, referrals, favors, mentorship sessions. The thank-you note is universal, and a fill-in field makes each one specific.

Suggested trigger: ;thanks

Why it matters: Gratitude is best when it’s prompt. A snippet removes the friction between feeling thankful and expressing it. Type the trigger, fill in what you’re thanking them for, send.

These ten are just the start

After a month of using text expansion, you’ll naturally start spotting other candidates. That Slack status you set every morning. That project update format. That code comment you write in every file. The pattern recognition happens on its own once you’ve experienced how much time the first ten triggers save.

TypeSnap ships with 165 curated snippets across email, customer support, development, and professional templates. Import a pack to get a running start, or build your library from scratch using the list above.

Either way, these ten things should never require full manual typing again.

Download TypeSnap and turn your most-typed text into two-keystroke shortcuts.

Stop typing the same things over and over

TypeSnap expands your snippets instantly. One-time purchase, no subscription.

Get TypeSnap · $17.99

Ready to type less?

Join thousands who've switched to TypeSnap. Your snippets, your Mac, your privacy.

Download TypeSnap — $17.99
Notarized Mac App No data collection Made by an indie developer