Quick Text Settings

Administration 🔴 Advanced
📖 4 min read

Definition

Quick Text Settings is a Setup page where administrators enable and configure Quick Text, which provides pre-written text snippets that users can insert into emails, chats, and other text fields. Quick Text reduces typing time and ensures consistent messaging across the support and sales teams.

Real-World Example

The admin at BrightStar Telecom enables Quick Text Settings and creates 30 commonly used snippets for the support team, such as "Thank you for contacting support. I'd be happy to help with your issue" and "I've escalated your case to our technical team. You'll hear back within 4 business hours." Agents insert these with a few keystrokes instead of typing them each time.

Why Quick Text Settings Matters

Quick Text Settings is the Setup page in Salesforce where administrators enable and configure the Quick Text feature. From this page, admins toggle Quick Text on or off for the organization, configure which channels support Quick Text (email, live chat, messaging, social), and manage access to Quick Text creation and usage. Once enabled, administrators or designated users can create Quick Text records that are available to specific channels or universally. The settings page also controls whether Quick Text is available in Lightning Experience, Salesforce Classic, or both, ensuring compatibility with the organization's UI strategy.

Properly configuring Quick Text Settings is a prerequisite for realizing the productivity and consistency benefits of the feature across an organization. Admins who simply enable Quick Text without a governance plan end up with a sprawling library of inconsistent snippets created by individual users, many containing outdated information or informal language that doesn't align with brand standards. Best practice involves enabling Quick Text, restricting creation permissions to a designated team (often knowledge management or training), and establishing a review process for new snippets. Channel-specific enablement is also important; a snippet written for email may be too long for live chat, so organizations need separate snippet libraries tuned to each channel's constraints. The Settings page is the starting point for building this structured approach.

How Organizations Use Quick Text Settings

  • BrightStar Telecom — BrightStar's admin enabled Quick Text Settings and restricted snippet creation to the Quality Assurance team. They built 30 standardized snippets for the support team and 20 for the sales team, each reviewed by the communications department for brand consistency. Agents can use snippets but cannot create or modify them, maintaining messaging quality.
  • CrestWave Financial — CrestWave's admin configured Quick Text Settings to enable snippets in both email and live chat channels but with different libraries. Email snippets include formal language with full disclosures, while chat snippets use concise, conversational phrasing. This channel-specific approach reduced chat handle time by 20% without sacrificing email formality.
  • PeakPath Adventures — PeakPath's admin initially enabled Quick Text without restricting creation permissions. Within 3 months, 200 user-created snippets cluttered the library, many with outdated pricing and inconsistent tone. The admin reconfigured settings to limit creation to the training team, archived 150 duplicates, and established monthly snippet reviews.

🧠 Test Your Knowledge

See something that could be improved?

Suggest an Edit