Salesforce Quick Text: how to set it up, use it, and know its limits

Salesforce Quick Text lets reps insert saved messages into emails, tasks, and chats without leaving Salesforce. Learn how to set it up and share it, how it compares with templates and macros, and where it runs out.

A smiling rep in a headset at her computer beside a CRM record where the ;quote Snippet logs a quote follow-up, a Salesforce Quick Text alternative.

Sales reps and service agents spend a surprising chunk of every shift typing the same messages: greetings, follow-ups, case resolutions, call scripts. If your team works in Salesforce, Quick Text is built to solve exactly that.

Salesforce Quick Text lets your team save and reuse standard messages directly inside Salesforce. Reps press Ctrl+. on Windows or Cmd+. on Mac to open the message picker, select a saved response, and insert it without leaving the record they’re working on. Admins build and maintain the library. Reps do the inserting.

Where it gets complicated: there’s a 4,000-character cap per message, every addition or edit needs someone with edit rights, and the library stays inside Salesforce. Quick Text is also only one of the tools people mean by Salesforce text snippets, and knowing which to use saves admins rework. Knowing where each limit shows up makes it easier to decide what belongs in Quick Text and what belongs somewhere else.

Key takeaways

  • Quick Text is Salesforce’s built-in message library. Reps press Ctrl+. on Windows or Cmd+. on Mac to insert saved messages in email, chat, tasks, events, and other supported fields, and merge fields pull in record data automatically.
  • Admins control setup and access. Quick Text has to be enabled and granted through permission sets or profiles, and keeping create, edit, and delete rights with admins or team leads keeps the library limited to reviewed messages.
  • Pick the right native tool for the job. Quick Text suits short replies; Lightning Email Templates suit full emails; macros combine text with record updates; Account Engagement Snippets suit marketing content.
  • The limits show up as teams grow. Each message holds up to 4,000 characters, there’s no version history, bulk import needs the API, and the library stays behind when reps move to Gmail, Outlook, Slack, or Zendesk.
  • TextExpander carries approved messages beyond Salesforce. As a Salesforce text expander, its Snippets with fill-ins work in Salesforce and every other app reps type in, and when a shared Snippet changes, the whole team gets the update.

What is Salesforce Quick Text?

Salesforce Quick Text is a message library built into your Salesforce org. Reps access pre-written responses directly from the records they’re working on. No copy-pasting from a separate doc, no digging through a shared folder.

Quick Text shows up in most of the places your reps write: email composers, chat and messaging windows, task logs, event notes, Knowledge articles, social posts, and Case Comments. Anyone in your org with the right permissions can access it. You configure access through profiles or permission sets.

Here’s how it works in practice: a rep opens an email on a case record, presses Ctrl+. on Windows or Cmd+. on Mac, and the Quick Text picker appears. They type a few letters to filter messages, select the one they want, and click to insert. Messages can include merge fields like {!Contact.FirstName} or {!Case.CaseNumber} to pull in record data automatically.

Keyboard shortcut: Press Ctrl+. (Windows) or Cmd+. (Mac) from any supported Salesforce field to open the Quick Text picker.

High-volume customer service teams get the most out of Quick Text. Sales teams doing repetitive outreach benefit too. The common thread: anyone sending the same approved messages, repeatedly, at scale.

Quick Text vs. other Salesforce text snippet tools

“Salesforce text snippets,” or just Salesforce snippets, can mean several different tools, native and third-party. Each one fits a different job:

ToolBest forWhere it worksLimits
Quick TextShort reusable replies, call notes, and chat responses with merge fieldsEmail, chat and messaging, tasks, events, Log a Call, Knowledge, social, Case Comments4,000 characters per message; admin-managed; Salesforce only
Lightning Email TemplatesComplete emails with subject, layout, branding, and merge fieldsSalesforce email composer and automated emailsWhole emails, not paragraphs to drop into other messages
MacrosInserting text and updating records in one step, such as replying and closing a caseService Console and supported record pagesBuilt for service workflows; setup takes admin time
Account Engagement SnippetsReusable marketing content such as event details, bios, and legal footersAccount Engagement emails, templates, forms, and landing pagesMarketing assets only, not rep replies
TextExpanderApproved text with fill-ins that reps use in Salesforce and every other appSalesforce plus Gmail, Outlook, Slack, Zendesk, and any appDoesn’t read Salesforce record fields; use fill-ins instead

Salesforce’s native tools are strongest when content needs to stay close to records, permissions, and automation. Use Quick Text for record-aware replies, Lightning Email Templates for full emails, and macros when sending text is one step of a larger action. When the same wording needs to work outside Salesforce, use a cross-app tool.

How to enable Quick Text in Salesforce

In Lightning Experience, Quick Text is typically enabled by default in modern Salesforce orgs. In Salesforce Classic, it must be explicitly enabled. Either way, verify the setting is active before your team starts using it.

  1. Go to Setup in Salesforce.
  2. In the Quick Find box, type Quick Text Settings.
  3. Click Quick Text Settings.
  4. Toggle Enable Quick Text to on.
  5. Click Save.

Lightning vs. Classic: Lightning Experience uses the settings path above. If your org runs Salesforce Classic, use the Quick Find box in Setup and search for Quick Text Settings to access the same configuration page.

Already inside Salesforce? See our full list of Salesforce keyboard shortcuts to work faster across every record type.

How to grant users access to Quick Text

Enabling Quick Text org-wide doesn’t automatically give everyone access. Access comes through permissions you configure separately.

Two ways to do it:

  • Permission sets (recommended): Create a permission set with the Quick Text permissions you want, then assign it to specific users. It’s flexible, and you won’t need to touch profiles every time someone new joins the team.
  • Profiles: Edit the profile for a user group and add Quick Text permissions directly.

Quick Text permissions come in two tiers:

  • Quick Text: Read. Users can insert existing messages. Grant this to all reps.
  • Quick Text: Create/Edit/Delete. Users can build and modify messages. Limit this to admins or designated team leads.

Restricting creation rights keeps the library clean. Reps see only reviewed, approved messages, not half-finished drafts or outdated templates someone forgot to delete. Note that users with a Salesforce Platform license can’t be given Quick Text access.

How to create Quick Text messages

With Quick Text enabled and permissions set, admins can start building the message library.

  1. Go to Setup, search Quick Text in the Quick Find box, and open the Quick Text list.
  2. Click New.
  3. Fill in the fields using the reference table below.
  4. Click Save.

Quick Text field reference:

FieldWhat it doesExample
NameInternal label reps see when browsing“Support: Refund acknowledgment”
MessageThe text that inserts into the record“Hi {!Contact.FirstName}, we’ve received your request.”
CategoryOptional grouping for browse filtering“Greeting,” “Follow-Up,” “Closing”
ChannelControls which Salesforce channels show this messageEmail, Chat, Phone
GroupWho can access this messageAll Internal Users, a Public Group, or Private

Merge field syntax:

  • {!Contact.FirstName} for the contact’s first name
  • {!Case.CaseNumber} for the case number
  • {!Account.Name} for the account name

Character limit: The Message field holds up to 4,000 characters. Long scripts, multi-paragraph templates, and rich-text-heavy messages hit this ceiling fast. For anything longer, split the content across multiple Quick Text entries.

Bulk creation: No native CSV import exists in Setup. For large migrations, admins with API access can use Salesforce Data Loader to insert records directly into the QuickText object. For everyone else, creation is manual, one entry at a time.

Need a starting point? Browse our customer service email templates. Copy, adapt, and paste them straight into your Quick Text library.

How to insert and use Quick Text

Once messages are in the library, using them takes seconds. From any supported Salesforce field:

  1. Press Ctrl+. (Windows) or Cmd+. (Mac) to open the Quick Text picker.
  2. Type a few letters to filter by message name or content, or scroll by category.
  3. Click the message, or press Enter when it’s highlighted.

The message inserts at your cursor position. Merge fields fill in automatically from the current record’s data.

Supported channels:

ChannelWhere Quick Text appears
EmailEmail composer on any record
Chat and MessagingChat and messaging windows in the service console
PhoneLog a Call comments
TaskTask comments
EventEvent description
KnowledgeRich text fields in the article editor
SocialSocial publisher
Case CommentCase record (added Spring ’26, Lightning Experience only)

The library stays inside Salesforce. Reps who switch to Gmail, Outlook, Slack, or any other tool leave that library behind. For live chat scripts that need to travel across platforms, you need something that goes beyond Salesforce.

How to use Quick Text in a Salesforce task or Log a Call

To use Quick Text in a task or Log a Call, the message needs the Phone or Task channel. Then click into the Comments field, press Ctrl+. on Windows or Cmd+. on Mac, pick the message, and review the text before you save. Merge fields fill in from the record as the message is inserted.

Set up a message for call notes

  1. From the App Launcher, open the Quick Text tab and click New Quick Text.
  2. Give it a name reps will recognize, such as “Call: Left voicemail,” and write the message. Messages can include line breaks, lists, and merge fields.
  3. Under Channel, select Phone for Log a Call notes and Task for task comments. A message with no channel selected can’t be used anywhere.
  4. If the message uses merge fields, click Preview to check it against a real record, then click Save.

Insert it while you log a call

  1. Open the record, start Log a Call, and click into the Comments field.
  2. Press Ctrl+. (Windows) or Cmd+. (Mac), or click the Quick Text button in the toolbar.
  3. Select the message. Merge fields that don’t apply to the record come out blank, so read the note over before you save it.

Quick Text you save for your own Email use also appears as a shortcut in Salesforce’s Outlook and Gmail integrations with Inbox, but shared Quick Text doesn’t. For call notes and follow-ups that need to work everywhere, the TextExpander Chrome extension works as a Salesforce text expander, expanding the same Snippets in Salesforce, Gmail, and the other web apps your team uses. See all TextExpander integrations.

Salesforce Quick Text examples by role

Examples with merge fields work as Quick Text inside Salesforce; replace the bracketed parts before sending. Where a message also needs to go out from Gmail, Outlook, or Slack, the same wording works as a Salesforce text snippet in TextExpander, with fill-ins in place of merge fields.

Sales outbound intro

Hi {!Contact.FirstName}, I work with teams at companies like {!Account.Name} on [the problem you solve]. Would a 15-minute call next week be useful to see if we can help?

Post-demo follow-up

;sfdemo
Hi {Fill-in: first name}, thanks for your time today. As promised, here’s {Fill-in: resource}. Next step: {Fill-in: next step} on {Fill-in: date}.

Call note

;sfcallnote
Call with {Fill-in: contact}. Discussed {Fill-in: topics}. Pain: {Fill-in}. Next step: {Fill-in}. Follow-up {Fill-in: date}.

Support first response

Hi {!Contact.FirstName}, thanks for reaching out. I’ve opened case {!Case.CaseNumber} and I’m looking into it now. I’ll update you by [time].

Customer success renewal check-in

Hi {!Contact.FirstName}, your renewal for {!Account.Name} is coming up on [renewal date]. Can we find 20 minutes to review how things are going and plan for next year?

TextExpander banner: your approved messages in Salesforce and everywhere else, with a button to get started free

How to share and organize Quick Text

A Quick Text library grows fast. Without structure, reps end up with 50 messages and no clear idea which one fits the situation. Set up sharing and categories before you build.

Sharing options run from broad to narrow: open a message to the entire org, limit it to specific public groups (support, sales, onboarding), scope it to a role in your org hierarchy, or mark it private so only the creator sees it. In Lightning Experience, this works through standard org sharing rules. In Classic, manage sharing per record using the “Sharing” button on each Quick Text entry.

Categories matter more than most teams expect. Reps filter by category in the picker, so “Support: Escalation” and “Sales: Outreach” save real time compared to one long undifferentiated list.

Before you build, answer these four questions:

  • Who needs access?
  • What messages do they send most?
  • What channels do those messages go through?
  • Who owns updates when content changes?

Governance: who owns shared text

Shared messages need owners. Assign each category to a person who approves new messages and reviews existing ones on a schedule, such as quarterly for support replies and whenever pricing or policy changes. Use a naming pattern that shows the team and purpose, retire messages nobody uses, and keep a short list of who to ask for changes. The principles behind organizing your snippet library apply here too: consistent naming, clear ownership, and a regular review cycle.

To remove a message, open it from the Quick Text tab and delete it; anyone with Delete permission can do this, which is another reason to keep that permission narrow.

TextExpander for teams banner: one approved library, updated without a Setup queue, with a button to see TextExpander for teams

Salesforce Quick Text limitations

The 4,000-character cap is the one that bites first. Any message longer than that has to be split across multiple entries, which works until you’re maintaining three interconnected pieces of a single email template. Long call scripts and multi-paragraph onboarding messages hit this wall fast.

Beyond that, here’s what to factor in before building a team-wide workflow around Quick Text:

  • Every new message and every edit requires a user with Create/Edit permissions. Reps submit requests and wait for an admin to make the change. For fast-moving teams, that queue creates real lag.
  • The library lives in Salesforce. Reps working in Zendesk, Gmail, Outlook, or Slack are on their own.
  • No version history or audit trail. There’s no native way to see who last edited a Quick Text entry or restore a previous version. Once a message is overwritten, the original is gone.
  • Bulk import requires API access. Building a large library otherwise means manual entry, one message at a time.
  • Rich text behavior is inconsistent across channels. Formatting that looks clean in one context may not carry over when inserted into a different record type.

Quick Text isn’t available where I need it

Check the message’s Channel setting first; a message only appears in the channels selected on it, and one with no channel appears nowhere. Then check that the user has the Read permission and that the field supports Quick Text. Some page types and custom components don’t.

We need snippets outside Salesforce

Quick Text can’t follow reps into Gmail, Outlook, Slack, or a help desk. If the same approved wording needs to work there, keep record-aware replies in Quick Text and put cross-app text in a Salesforce text expander that also works everywhere else reps type. Teams that need canned responses across multiple tools usually end up with both. Angelina E., a TextExpander customer, describes where that leads: “All of our email templates live in TextExpander now, replacing both GMail Canned Responses and Salesforce templates. With just a few keystrokes I have an entire email populated and customized to my customer.”

TextExpander: a Salesforce text expander for sales and service teams

Quick Text works well for messages that stay entirely inside Salesforce. When messages need to travel outside the platform, run longer than 4,000 characters, or be updated without routing through an admin, a text expander for Salesforce fills the gap.

TextExpander works in Salesforce and every other app your team uses: Gmail, Outlook, Slack, Zendesk, and anything in Chrome or on the desktop. The same Snippet library follows reps wherever they work, so one set of approved Salesforce text snippets covers every channel.

  • Room for longer content: full email templates, multi-section call scripts, fill-in fields, and images fit in a single Snippet.
  • Fill-ins that work anywhere: fill-in fields and pop-up menus let reps personalize a template without leaving the keyboard, in any app, on any page.
  • Self-service team sharing: admins share Snippet Groups and control who can edit them, so updates don’t wait in a Setup queue. On Business and Enterprise plans, reps can suggest changes through Snippet Requests for an owner to approve.
  • Instant updates: when a shared Snippet changes, every team member gets the new version immediately.

A. Thomas, a Client Service Coordinator in financial services, described the cross-app difference:

Extremely easy to set up & train team on, and then once the team was trained we are able to use it every day! We can use it in Salesforce, Microsoft Office, or literally any other text box. It allows us to standardize language and save time. Customer Support has been great as well in helping us troubleshoot problems.

A. Thomas, Client Service Coordinator, Financial Services

The right split: use Quick Text for Salesforce-native responses that rely on record merge fields. Use TextExpander when messages need to travel, run long, or be managed without admin involvement. It fits naturally into the broader set of sales productivity tools modern teams rely on, and the same approach works for Outlook Quick Parts.

Take your Quick Text library beyond Salesforce

Save your follow-ups, call notes, and support replies as Snippets with fill-ins, and use them in Salesforce, Gmail, Outlook, Slack, and every other app. Share them so the whole team sends the current version.

See what changes when every approved message is one shortcut away. Free forever, no credit card required.

Frequently asked questions

How do I create a new Quick Text in Salesforce?

Go to Setup, search for Quick Text in the Quick Find box, open the Quick Text list, and click New. Add a name, the message text (with merge fields if you like), a category, the channels where it should appear, and who can access it, then click Save. You need the Quick Text Create permission to do this.

How do I use Quick Text in Salesforce?

Click into a supported field, such as the email composer or Log a Call comments, and press Ctrl+. on Windows or Cmd+. on Mac. Type a few letters to filter, then select the message to insert it at your cursor. Merge fields fill in from the current record, so review the text before you send or save.

Where can I use Quick Text in Salesforce?

Quick Text works in the email composer, chat and messaging, Log a Call and task comments, event descriptions, Knowledge article rich text fields, the social publisher, and Case Comments in Lightning Experience. Each message only appears in the channels selected on it.

What is the character limit for Salesforce Quick Text?

Each Quick Text message holds up to 4,000 characters. Longer scripts and multi-paragraph templates need to be split into several entries, or kept in a tool without that constraint, such as a Lightning Email Template for full emails or a TextExpander Snippet for text used across apps.

Can I use Salesforce Quick Text in Gmail or Outlook?

Only partly. Quick Text you save for your own Email use can appear in Salesforce's Gmail and Outlook integrations, but shared Quick Text doesn't, and it doesn't work in other apps like Slack. To use the same approved messages everywhere, save them as TextExpander Snippets, which expand in Gmail, Outlook, Salesforce, and any other app.

What's the difference between Salesforce Quick Text and Salesforce text snippets?

Salesforce Quick Text is a specific built-in feature: admins save short messages that reps insert with Ctrl+. or Cmd+. inside Salesforce, with merge fields that pull in record data. "Salesforce text snippets" is a broader term. Inside Salesforce, Snippets are an Account Engagement feature for reusable marketing content in emails, forms, and landing pages, not rep replies. Many teams also use the term for text expander Snippets, such as TextExpander, which insert approved text from a short abbreviation in Salesforce and every other app. Use Quick Text for record-aware replies inside Salesforce, and a Salesforce text expander when the same wording needs to work in Gmail, Outlook, or Slack too.

Keep reading

View all posts →
salesforce keyboard shortcuts and hotkeys Sales 60 Popular Salesforce Keyboard Shortcuts & Hotkeys A sales rep in a headset types on her laptop beside an email where the ;recap Snippet expands into a call recap with next steps, a sales productivity shortcut. Sales Best Sales Productivity Tools A smiling sales rep in a headset above an email where the ;followup Snippet inserts the team’s shared, approved follow-up, an example of sales team collaboration. Collaboration & Teamwork Adding TextExpander to Your Sales Collaboration Tools
Salesforce Quick Text: how to set it up, use it, and know its limits