Dial-Tone Multi-Frequency (DTMF)
Dial-Tone Multi-Frequency (DTMF) is the touch-tone signaling standard that telephone keypads use to send digits over a voice line.
Definition
Dial-Tone Multi-Frequency (DTMF) is the touch-tone signaling standard that telephone keypads use to send digits over a voice line. Each key produces a pair of audio tones that the receiving system interprets as a specific digit or symbol (0-9, star, hash, and A-D in some legacy systems). In Salesforce, DTMF support is part of Service Cloud Voice and Salesforce CTI integrations: contact-center systems use DTMF tones for IVR menu navigation, queue selection, account number entry, and conditional routing before a call ever reaches an agent.
Service Cloud Voice surfaces DTMF capture through its Amazon Connect Contact Flow editor, where admins define prompts that collect DTMF input and route based on the digits. Recorded DTMF tones are also surfaced in call transcripts and analytics, with optional tone suppression to mask sensitive entries like PINs in the recording. The actual customer interactions happen via the telephony provider (Amazon Connect for Service Cloud Voice; legacy CTI providers for older setups).
How DTMF integrates with Salesforce Service Cloud Voice
DTMF as a telephony primitive
DTMF is a signaling standard from 1963 designed to replace rotary-dial pulses with audible tones. Each key on a phone keypad produces a unique pair of frequencies: 1 is 697 + 1209 Hz, 5 is 770 + 1336 Hz, and so on. The receiving switch decodes the pair and interprets the digit. DTMF works over any audio channel, including modern VoIP, which is why touch-tone IVR menus still work in 2026 despite the underlying telephony network having changed completely.
DTMF in Service Cloud Voice''s IVR
Service Cloud Voice (Salesforce's cloud telephony platform, powered by Amazon Connect) uses DTMF for inbound IVR navigation. Admins build call flows in the Amazon Connect Contact Flow editor with prompts like Press 1 for sales, press 2 for support. The customer's keypress travels through the audio channel as a DTMF tone pair, Amazon Connect captures it, and Service Cloud Voice routes the call based on the value. The full flow is configurable in the Salesforce-hosted Amazon Connect instance.
DTMF capture and IVR security
DTMF can capture sensitive data like account numbers and PINs. Service Cloud Voice supports tone suppression: the captured DTMF tones are masked in the call recording so audit logs do not contain the customer's PIN. The captured value is encrypted in transit and stored encrypted at rest. PCI-compliance scenarios specifically require this masking; without it, recordings containing DTMF for credit-card entry violate PCI DSS.
DTMF and contact-flow routing logic
After DTMF capture, contact flows route based on the digit. A simple case: 1 for sales routes to the sales queue. A complex case: customer enters a 9-digit account number, the flow queries Salesforce via a Lambda function to identify the account, retrieves the VIP flag, and routes to a priority queue if true. DTMF capture is the input; everything after is conditional logic in the flow editor.
DTMF in outbound dial scenarios
Outbound dialers also generate DTMF: when a callback connects, the dialer can send DTMF tones to navigate the recipient's IVR (press 1 for English, then enter the account number). Service Cloud Voice supports outbound DTMF generation through contact-flow steps, useful for callback queues that need to navigate menu trees automatically.
DTMF analytics and the agent experience
DTMF inputs collected before a call reaches an agent are surfaced in the agent's screen pop. If a customer entered their account number in the IVR, Service Cloud Voice attaches that value to the call record and the Salesforce screen pop shows the matching contact. This eliminates the thanks-for-your-account-number-now-please-tell-it-to-the-agent-again frustration that legacy IVRs created.
Where DTMF fits in 2026''s voice landscape
DTMF is decades old but stubbornly relevant. Voice bots (Einstein Voice Bot, Dialogflow, others) can replace DTMF menus with natural-language input, but DTMF still dominates IVR design because it is universal, accessible (hearing-impaired customers can still use it), and works in noisy environments. Modern contact centers blend both: voice bot for natural conversations, DTMF for unambiguous data entry like account numbers.
How to capture and route on DTMF in Service Cloud Voice
DTMF capture happens inside the Amazon Connect Contact Flow that Service Cloud Voice provides. Configure the prompt, the capture step, and the conditional routing branches; the rest is the customer's keypad.
- Open the Amazon Connect Contact Flow editor
From the Service Cloud Voice console, navigate to your Amazon Connect instance and open the Contact Flow you want to modify. The editor is hosted by Amazon Connect, embedded in the Salesforce UI.
- Add a Get Customer Input block
Drag a Get Customer Input block onto the canvas. This is the DTMF-capture node. Connect it after your welcome prompt or routing logic.
- Configure the prompt
In the Get Customer Input block, set the prompt text (the Text-to-Speech voice the customer hears). Example: Welcome to support. Press 1 for billing, press 2 for technical support, press 0 for an operator.
- Set DTMF input options
In the block''s properties, set the input type to DTMF, the timeout (typically 5 seconds), and the maximum digits (1 for a single-key choice, more for an account number). Each option (1, 2, 0) gets a labeled branch on the block.
- Wire the branches to routing logic
Each branch connects to a downstream block: a queue, another Get Customer Input, a Lambda function call, or a transfer. The 1-branch might route to the Billing queue; the 2-branch to Technical Support; the 0-branch directly to the operator queue.
- Publish and test
Save the contact flow, click Publish. Make a test call to the phone number, navigate the IVR with your keypad. The agent''s screen pop in Salesforce should reflect the path you took.
Get Customer Input with max digits 1. Used for menu navigation: 1 for sales, 2 for support.
Max digits set higher (4-12). Used for account numbers, PINs, ZIP codes.
Mask captured DTMF in call recordings. Required for PCI-compliant credit-card capture.
After DTMF capture, route based on a Lambda function''s response (looking up the customer in Salesforce, checking VIP status, etc.).
- DTMF capture timeout defaults are short (5 seconds typical). Customers entering long account numbers slowly will time out. Configure timeout per use case.
- Voice bots and DTMF compete for the same audio channel. If both are enabled, the bot may interpret DTMF tones as background noise. Choose one or the other per IVR step.
- Tone suppression must be configured explicitly. Default recording captures DTMF tones; if your IVR collects credit-card data, you must enable tone suppression or risk a PCI violation.
- DTMF over poor VoIP connections can drop tones. Customers on weak connections occasionally hear I did not get that, please try again. Build the IVR to allow retries gracefully.
Trust & references
Straight from the source - Salesforce's reference material on Dial-Tone Multi-Frequency (DTMF).
- Service Cloud Voice OverviewSalesforce Help
- Amazon Connect Contact FlowsAWS Documentation
Hands-on resources to go deeper on Dial-Tone Multi-Frequency (DTMF).
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. What is DTMF?
Q2. What is DTMF used for in contact centers?
Q3. Is DTMF being replaced?
Discussion
Loading discussion…