Does a third-party keyboard work in the Phone app’s keypad on iPhone?
Open the Keypad tab in the Phone app and there is no globe key anywhere on it, on any iPhone, with any keyboard installed. That is not the same restriction as the one on a password or phone-number field — the dial pad was never a text field to begin with, so there was never a keyboard for any app, Apple’s own included, to be swapped into.
You have a keyboard you actually chose running in Messages, Notes, every app you open — then you switch to the Phone app to dial a number or punch in an extension, look for the globe key out of habit, and it is not there. Not greyed out, not hiding behind a long-press, just absent, in a way it never is anywhere else you type. It is worth knowing this happens to every keyboard equally, Apple’s own included, and that it is a different situation from the more familiar case of a keyboard getting swapped out for something you tapped into.
This is not the phone-number-field rule
A separate guide on this site covers why a custom keyboard disappears specifically in the phone number row of Contacts, or a signup form asking for your number — Apple names that field type directly in its own developer documentation as one a third-party keyboard is not eligible to type into, the same deliberate exception made for password fields. That rule is about a real text field: the cursor is genuinely sitting in an editable field, and iOS insists on its own keyboard being the one attached to it. The Keypad tab in the Phone app is not that. It is a different case, one step further back.
Why there was never a keyboard to swap
A keyboard, on iOS, only ever appears because some text field asked for one. The Keypad tab is not a text field with a restrictive type attached to it — it is a purpose-built dialing control, a fixed grid of large tap targets Apple drew for entering a number to call, the same kind of screen that has existed since long before any app, Apple’s own keyboard included, could plug a software keyboard into a text field at all. Tapping a digit there updates the number shown above it directly, the same way tapping any other button in an app runs a piece of code rather than typing a character into a field. There is no cursor sitting in an editable box waiting on whichever keyboard happens to be active, so there was never a moment for a globe key, a theme or a key sound to attach to.
The number display above the keys is not quite a text field either
The row where digits appear as you tap them looks like it could be an ordinary field, and it does accept one keyboard-adjacent gesture: long-press it and Paste still shows up, because that action routes through the system pasteboard menu rather than through any software keyboard. What it never does is accept typed input from a keyboard, custom or otherwise — the only way a number lands in it is by tapping the dial pad underneath, which is a fair way to tell it apart from a genuine text field a keyboard could have been attached to.
The in-call keypad works the same way
Once a call connects, tapping Keypad brings up the same kind of grid for sending tones during the call — reaching an extension, entering a PIN for a conference line, navigating an automated phone menu. It is built the same way as the pre-call dial pad, for the same reason: sending a DTMF tone mid-call is not text landing in a field, it is a button press sending a signal, so it carries no globe key either, on Apple’s keyboard or any third-party one.
What still works normally around it
This is narrow rather than contagious. Switch to the Contacts tab to add a note on that same contact, or to Messages to text the number you just dialed, and your usual keyboard is right there with its usual theme, sound and lighting — the dial pad does not change how any other field in the Phone app, or any other app, behaves. It is specifically the two dialing grids, before and during a call, that have nothing for a keyboard to plug into.
Where Kibo fits
Kibo works in any ordinary text field an app hands it, the phone number row in Contacts included, once you have tapped into a field iOS actually allows it into — but the Phone app’s own dial pad gives no app’s keyboard, Kibo or Apple’s, anywhere to appear, for the same underlying reason no keyboard is missing anything during a passkey sign-in covered elsewhere on this site. None of this touches Full Access, which Kibo reads only for the Copy word, Copy line and Paste buttons on its own toolbar. It is free to download.
Frequently asked questions
Why is there no globe key on the Phone app’s Keypad tab?
Because the dial pad was never a text field. A software keyboard — Apple’s own or a third-party one — only ever appears because a text field requested it, and the Keypad tab is a fixed grid of buttons Apple built for dialing, not a field of any kind. There is no keyboard slot for a globe key to belong to.
Is this the same rule that swaps out a custom keyboard in a phone number field?
No, a different one. A phone number field in Contacts or a signup form is a genuine text field that iOS reserves for its own keyboard by field type. The Phone app’s Keypad tab is not a text field of any type, so that restriction never even comes up — there was no keyboard slot there to restrict in the first place.
Does the in-call keypad behave the same way?
Yes. Sending a tone to an extension or an automated menu mid-call works through the same kind of dedicated grid as the pre-call dial pad rather than a text field, so it shows no globe key either, regardless of which keyboard is installed.
Try it on your own keyboard
Kibo is a free custom keyboard for iPhone with real mechanical key sounds, a wardrobe of themes and RGB backlight effects. No account, no ads, and it works with Full Access left off.