Quick Text Settings
Quick Text Settings is the Setup page in Salesforce where an administrator turns on the Quick Text feature and decides how its snippets are organized and shared.
Definition
Quick Text Settings is the Setup page in Salesforce where an administrator turns on the Quick Text feature and decides how its snippets are organized and shared. Quick Text is a library of pre-written messages that users insert into emails, chat replies, tasks, events, and other text fields, so they do not retype the same wording for every customer.
The settings page itself is small. Its main job is to enable folder-based sharing through the option labeled "Share and organize quick text in folders." Once enabled, the day-to-day work moves to creating QuickText records, granting users access through permissions, and building folders that match how your teams actually respond to customers.
How Quick Text Settings fits into a real support workflow
What the settings page actually controls
Quick Text Settings lives under Setup. You reach it by typing Quick Text Settings in the Quick Find box and selecting it. In Lightning Experience the feature is already on, so the page is less about a master on/off switch and more about one decision: whether to organize and share snippets in folders. Selecting "Share and organize quick text in folders" and saving unlocks the folder model, which is how most teams manage Quick Text at scale. Before folder sharing existed, every Quick Text record was shared individually, which got painful once a library grew past a handful of snippets. Folders let you group related messages and share a whole set at once. The settings page is the gate for that capability. After you enable it, you rarely return, because the ongoing work happens in the Quick Text object, in permissions, and in the folders themselves. Think of this page as a one-time configuration step that sets the rules for everything built on top of it.
The QuickText object behind the feature
Every snippet you create is a record in the standard QuickText object, available in the API since version 24.0. The record holds the snippet text in a Message field, a Name used as the shortcut label, and a Channel value that controls where the snippet can be inserted. Channels include options like Email, Event, Task, Internal, Knowledge, and others, so a message written for an email reply will not clutter a task description. Because QuickText is a real object, it behaves like one. You can report on it, load records through Data Loader, deploy them between sandboxes, and reference them in automation. A companion object, QuickTextUsage, records when snippets are inserted, which gives you data to see which messages agents actually rely on. The Message field supports merge fields, line breaks, and special characters, so a snippet can greet a customer by name or pull in a case number rather than reading as generic boilerplate. This object-level structure is what separates Quick Text from a simple text expander.
Giving users access through permissions
Enabling the feature does not hand it to your reps. Access comes from permissions, and the cleanest way to grant them is a permission set. The relevant permissions cover reading, creating, and editing Quick Text, plus the object permissions on the QuickText object itself. Assign that permission set to the agents and sales users who need snippets, and leave it off the people who do not. This separation matters for governance. You might want a small group of team leads who can create and curate shared snippets, while frontline agents can read and insert them but not edit the shared library. Permission sets make that split easy without touching profiles. When a new hire joins, you assign the permission set and they immediately see the folders shared with them. When someone changes roles, you remove or swap the set. Keeping access in permission sets rather than profiles also means you can layer Quick Text onto many different profiles without rebuilding each one.
Folders, sharing, and team-specific libraries
Once folder sharing is enabled in the settings, folders become the unit of organization. You create a folder, drop related snippets into it, and share that folder with a public group, a role, or specific users. This is how a single org supports very different teams. Your service team can have a folder of troubleshooting replies, and your sales team can have a folder of follow-up and intro lines, with neither group wading through the other team's messages. Sharing a folder works like sharing a report or dashboard folder, so admins already understand the model. You decide who gets viewer access and who can manage the contents. A well-structured set of folders keeps the insertion list short and relevant, which is the single biggest driver of adoption. When agents open the Quick Text picker and see only the snippets that apply to their work, they use it. When they see hundreds of unsorted messages, they give up and type manually. Folder design is quietly one of the most important parts of a Quick Text rollout.
Inserting snippets where the work happens
Agents insert Quick Text in the places they already work: the email publisher, chat and messaging composers, the docked composer, and supported text fields on records. In a Lightning console, typing two semicolons in a row opens the Quick Text picker, where the user searches by name and inserts the message. The Channel value on each snippet decides which messages appear in a given context, so the list stays focused. When a snippet contains merge fields, Salesforce resolves them against the current record at insert time. A snippet that opens with the contact's first name and references the case number arrives personalized, not generic. Agents can edit the inserted text before sending, so a snippet is a starting point rather than a locked template. This is the moment all the configuration pays off. The folder structure, the permissions, and the Channel values all converge into a fast keystroke that drops in accurate, on-brand wording. Done well, it shaves seconds off every reply, and those seconds compound across thousands of interactions a week.
Adoption, governance, and where it overlaps with Macros
Quick Text rarely fails on technical grounds. It fails on adoption. An empty library gets ignored, so seed a starter set of approved snippets before launch and tell agents the insertion shortcut in plain terms. Review the shared folders on a regular cadence, retire snippets nobody uses, and promote the good ad-hoc messages agents have written into the shared set. The QuickTextUsage data tells you what is actually working. It also helps to know where Quick Text stops and Macros begin. Quick Text inserts wording into a field. Macros run a sequence of actions, and a macro can itself insert a Quick Text snippet as one of its steps. Many teams use both: Quick Text for the words, Macros for the clicks. Keeping that boundary clear prevents duplicated effort and confusion. When you treat the shared library as a living asset with an owner and a review schedule, Quick Text stays useful for years rather than rotting into a pile of outdated phrases new hires are afraid to use.
How to set up Quick Text Settings
Quick Text Settings is where you switch on folder-based sharing and set the foundation for a managed snippet library. The page is short, but the steps around it (permissions and folders) are what make the feature usable.
- Open Quick Text Settings
From Setup, type Quick Text Settings in the Quick Find box and select it. In Lightning Experience the feature is already enabled by default.
- Enable folder sharing
Select "Share and organize quick text in folders" and click Save. This unlocks the folder model used to share snippet sets with teams.
- Grant access with a permission set
Create or edit a permission set that includes read, create, and edit access for Quick Text, then assign it to the agents and reps who need snippets.
- Build and share folders
Create folders that match how teams respond, add QuickText records to each, set the correct Channel, and share each folder with the right group or role.
Turns on folder-based organization and sharing so you can group related snippets and share a whole set at once instead of record by record.
Controls where a snippet can be inserted, with values such as Email, Event, Task, Internal, and Knowledge, keeping each context's picker focused.
Holds the snippet text and supports merge fields, line breaks, and special characters so inserted messages can be personalized rather than generic.
- Enabling the feature does not grant it to users. Access still requires the Quick Text permissions, usually via a permission set.
- An empty library kills adoption. Provision a starter set of approved snippets before rollout, not after.
- Set the Channel correctly on each snippet, or messages will not appear in the publisher or composer where agents expect them.
- Quick Text is not Macros. Use Quick Text for wording and Macros for multi-step actions; a macro can insert a Quick Text snippet as a step.
Trust & references
Cross-checked against the following references.
- Enable Quick TextSalesforce
- QuickText | Object Reference for the Salesforce PlatformSalesforce
Straight from the source - Salesforce's reference material on Quick Text Settings.
Hands-on resources to go deeper on Quick Text Settings.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. Can a Salesforce admin configure Quick Text Settings without writing code?
Q2. Why is understanding Quick Text Settings important for Salesforce admins?
Q3. What is the primary benefit of Quick Text Settings for Salesforce administrators?
Discussion
Loading discussion…